How do version changes break spend trends?
Published | Updated
A buyer or supplier meeting version breaks for the first time needs one sentence first: a code moved, added or deleted between versions, so the same purchase counts in a different place next year, in UNSPSC as managed by the United Nations Development Programme since 1 January 2025. A trend that jumps at a version boundary is a coding change until proven otherwise.
Level of detail for version breaks
| What it shows | Where it misleads |
|---|---|
| Broad view of version breaks | that a code moved, added or deleted between versions, so the same purchase counts in a different place next year |
| Close view of version breaks | that a trend that jumps at a version boundary is a coding change until proven otherwise |
| Practical use of version breaks | the claim that a code moved, added or deleted between versions, so the same purchase counts in a different place next year |
Finding the shelf for version breaks
Think of version breaks as occupying one shelf position defined by the claim that a code moved, added or deleted between versions, so the same purchase counts in a different place next year. A trend that jumps at a version boundary is a coding change until proven otherwise. That position decides which families a buyer searches when looking for version breaks and which reports will count it. Reports that span a version change should flag the boundary on the chart, not bury it in a footnote. A shelf position for version breaks that is roughly right is still wrong for reporting, because reports add shelf positions for version breaks together without asking how rough they were.
From broad shelf to version breaks
To narrow toward version breaks, start broad and ask at each pair whether a code moved, added or deleted between versions, so the same purchase counts in a different place next year still holds. A trend that jumps at a version boundary is a coding change until proven otherwise. Each yes moves the reading one level finer, and each no sends the reader back to a neighbouring pair for version breaks. Reports that span a version change should flag the boundary on the chart, not bury it in a footnote. That loop for version breaks, repeated patiently, is the whole method, and there is no shortcut version of it for version breaks that stays reliable.
Where version breaks goes wrong in practice
With version breaks, the error to watch for is reports that span a version change should flag the boundary on the chart, not bury it in a footnote, set against the fact that a code moved, added or deleted between versions, so the same purchase counts in a different place next year. A trend that jumps at a version boundary is a coding change until proven otherwise. Errors of this kind with version breaks survive because the resulting code still looks valid, with the right number of digits and a plausible title for version breaks. Only a check against the current codeset wording for version breaks exposes them, which is why checking is a habit rather than a one-off task.
Before moving on from version breaks, run one last check: does the claim that a code moved, added or deleted between versions, so the same purchase counts in a different place next year still hold in the current codeset wording for version breaks? A trend that jumps at a version boundary is a coding change until proven otherwise. Reports that span a version change should flag the boundary on the chart, not bury it in a footnote.
Leave version breaks with this: a code moved, added or deleted between versions, so the same purchase counts in a different place next year is the claim, and the current UNDP codeset is the check. Reports that span a version change should flag the boundary on the chart, not bury it in a footnote. Any tender, catalogue or report about version breaks that carries both the claim and its version can be followed by the next person who picks it up, which is the standard every UNSPSC quotation for version breaks should meet.