Can codes be mapped between classifications?

The short answer is that mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity, in UNSPSC as managed by the United Nations Development Programme since 1 January 2025. A mapped code should be checked in the target classification’s own wording before it is quoted. Readers who grasp that sentence have the heart of mapping classifications already.

Narrowing the digits for mapping classifications

Narrowing toward mapping classifications works pair by pair, because mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity. A mapped code should be checked in the target classification’s own wording before it is quoted. A reader narrowing in this way should test every pair against the codeset wording for mapping classifications, not merely against a remembered title. Mappings that are carried through lower levels without checking, as the Canadian notes warn against, create false precision. The pair that fails the test for mapping classifications is where the narrowing went wrong, and it is cheaper to find it here than in a tender for mapping classifications.

A question about mapping classifications

The answer this guide gives	The check that follows
Broad view of mapping classifications	that mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity
Close view of mapping classifications	that a mapped code should be checked in the target classification’s own wording before it is quoted
Practical use of mapping classifications	the claim that mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity

What shelf does mapping classifications belong on?

Where mapping classifications sits follows from the fact that mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity, and a mapped code should be checked in the target classification’s own wording before it is quoted. Shelf position in UNSPSC is a claim about kind, not about importance, size or price, so mapping classifications sits beside kinds like itself even when the markets for those kinds differ wildly. Mappings that are carried through lower levels without checking, as the Canadian notes warn against, create false precision. Getting the shelf right for mapping classifications matters because every later move for mapping classifications, from tender lots to spend reports, starts from it.

The usual stumble over mapping classifications

The common stumble with mapping classifications comes from mappings that are carried through lower levels without checking, as the Canadian notes warn against, create false precision, while the underlying truth remains that mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity. A mapped code should be checked in the target classification’s own wording before it is quoted. Buyers and suppliers both stumble over mapping classifications, buyers by writing a lot that covers the wrong neighbour for mapping classifications, suppliers by coding a profile line that promises the wrong neighbour for mapping classifications. The codeset wording for mapping classifications, read in full, prevents both versions of the stumble.

Before moving on from mapping classifications, run one last check: does the claim that mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity still hold in the current codeset wording for mapping classifications? A mapped code should be checked in the target classification’s own wording before it is quoted. Mappings that are carried through lower levels without checking, as the Canadian notes warn against, create false precision.

The test of understanding mapping classifications is simple: can the reader explain why mappings can be published, as Canada published for GSIN to UNSPSC, but a mapping is a suggestion, not an identity without reaching for a code first? Mappings that are carried through lower levels without checking, as the Canadian notes warn against, create false precision. If the explanation of mapping classifications holds, the code will follow naturally, and if it does not, no code chosen for mapping classifications yet will rescue it.