What goes wrong when a report mixes levels?

In UNSPSC, as managed by the United Nations Development Programme since 1 January 2025, commodity detail and segment totals added together, double counting the same spend. Level mixing is the commonest arithmetic error in UNSPSC reporting, because it looks like thoroughness. That is the short answer, and the rest of this guide unpacks it for level mixing.

Where level mixing sits on the shelf

On the shelf, level mixing belongs where commodity detail and segment totals added together, double counting the same spend, and level mixing is the commonest arithmetic error in UNSPSC reporting, because it looks like thoroughness. The shelf position is not a matter of taste, because the codeset wording for level mixing sets the neighbours it sits beside and the broader shelf it sits under. A reader who can say where level mixing sits can also say where it does not sit, which is often the more useful half of the knowledge. A report should fix one level for each table, and use separate tables for other levels.

How the pairs narrow toward level mixing

The digits narrow toward level mixing by the usual UNSPSC logic: each pair refines the pair before it, so commodity detail and segment totals added together, double counting the same spend becomes more specific at every step. Level mixing is the commonest arithmetic error in UNSPSC reporting, because it looks like thoroughness. The narrowing toward level mixing stops at the level the evidence supports for level mixing, and stopping early is honest while claiming a finer level for level mixing without evidence is not. A report should fix one level for each table, and use separate tables for other levels.

Four things to keep beside level mixing while working

• the claim that commodity detail and segment totals added together, double counting the same spend
• the detail that level mixing is the commonest arithmetic error in UNSPSC reporting, because it looks like thoroughness
• the caution that a report should fix one level for each table, and use separate tables for other levels
• the version and managing body, UNDP since 1 January 2025, beside any code quoted for level mixing

What trips readers up with level mixing

What trips people up with level mixing is that a report should fix one level for each table, and use separate tables for other levels, even though commodity detail and segment totals added together, double counting the same spend. Level mixing is the commonest arithmetic error in UNSPSC reporting, because it looks like thoroughness. The trap is familiar because it looks like carelessness when it is really a wording problem: the titles for level mixing and its neighbours resemble each other closely enough to invite a quick, wrong choice. Slow reading of both wordings for level mixing, side by side, is the unglamorous cure for level mixing.

Before moving on from level mixing, run one last check: does the claim that commodity detail and segment totals added together, double counting the same spend still hold in the current codeset wording for level mixing? Level mixing is the commonest arithmetic error in UNSPSC reporting, because it looks like thoroughness. A report should fix one level for each table, and use separate tables for other levels.

For level mixing, the work is not finished when a code is chosen, because commodity detail and segment totals added together, double counting the same spend still needs its version and managing body beside it. A report should fix one level for each table, and use separate tables for other levels. Quote all three together for level mixing, and the next reader can do in minutes what took this guide several sections to explain about level mixing.