How are UNSPSC versions numbered?

In UNSPSC, as managed by the United Nations Development Programme since 1 January 2025, version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date. Version labels let a reader pin a code statement to one release, rather than to UNSPSC in general. That is the short answer, and the rest of this guide unpacks it for version numbering.

Where version numbering sits on the shelf

On the shelf, version numbering belongs where version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date, and version labels let a reader pin a code statement to one release, rather than to UNSPSC in general. The shelf position is not a matter of taste, because the codeset wording for version numbering sets the neighbours it sits beside and the broader shelf it sits under. A reader who can say where version numbering sits can also say where it does not sit, which is often the more useful half of the knowledge. A guide that names no version names no checkable statement, however accurate its wording sounds.

How the pairs narrow toward version numbering

The digits narrow toward version numbering by the usual UNSPSC logic: each pair refines the pair before it, so version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date becomes more specific at every step. Version labels let a reader pin a code statement to one release, rather than to UNSPSC in general. The narrowing toward version numbering stops at the level the evidence supports for version numbering, and stopping early is honest while claiming a finer level for version numbering without evidence is not. A guide that names no version names no checkable statement, however accurate its wording sounds.

Four things to keep beside version numbering while working

• the claim that version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date
• the detail that version labels let a reader pin a code statement to one release, rather than to UNSPSC in general
• the caution that a guide that names no version names no checkable statement, however accurate its wording sounds
• the version and managing body, UNDP since 1 January 2025, beside any code quoted for version numbering

What trips readers up with version numbering

What trips people up with version numbering is that a guide that names no version names no checkable statement, however accurate its wording sounds, even though version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date. Version labels let a reader pin a code statement to one release, rather than to UNSPSC in general. The trap is familiar because it looks like carelessness when it is really a wording problem: the titles for version numbering and its neighbours resemble each other closely enough to invite a quick, wrong choice. Slow reading of both wordings for version numbering, side by side, is the unglamorous cure for version numbering.

Before moving on from version numbering, run one last check: does the claim that version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date still hold in the current codeset wording for version numbering? Version labels let a reader pin a code statement to one release, rather than to UNSPSC in general. A guide that names no version names no checkable statement, however accurate its wording sounds.

Carry one habit away from version numbering: version labels such as UNv26.0801, where the summary source cites 14 August 2023 as that release’s date, checked against the current UNDP codeset before it is quoted anywhere that matters. A guide that names no version names no checkable statement, however accurate its wording sounds. A code for version numbering quoted that way can be verified by the next reader, and verification is the whole point of having a shared classification at all.