Where does a component stop and a finished good start?

Put plainly, the point where a part bought to be built in becomes a good bought to be used under UNSPSC, managed by the United Nations Development Programme since 1 January 2025. The codeset wording, not the size or price of the item, sets that point. The sections below work through what that means for component against finished in practice.

A working note on component against finished

• remember that the point where a part bought to be built in becomes a good bought to be used
• remember too that the codeset wording, not the size or price of the item, sets that point
• watch out because spare parts are the classic borderline, because a spare is finished for the buyer and a component for the maker
• quote component against finished only with its version and managing body attached

Finding the shelf for component against finished

Think of component against finished as occupying one shelf position defined by the claim that the point where a part bought to be built in becomes a good bought to be used. The codeset wording, not the size or price of the item, sets that point. That position decides which families a buyer searches when looking for component against finished and which reports will count it. Spare parts are the classic borderline, because a spare is finished for the buyer and a component for the maker. A shelf position for component against finished that is roughly right is still wrong for reporting, because reports add shelf positions for component against finished together without asking how rough they were.

From broad shelf to component against finished

To narrow toward component against finished, start broad and ask at each pair whether the point where a part bought to be built in becomes a good bought to be used still holds. The codeset wording, not the size or price of the item, sets that point. Each yes moves the reading one level finer, and each no sends the reader back to a neighbouring pair for component against finished. Spare parts are the classic borderline, because a spare is finished for the buyer and a component for the maker. That loop for component against finished, repeated patiently, is the whole method, and there is no shortcut version of it for component against finished that stays reliable.

Where component against finished goes wrong in practice

With component against finished, the error to watch for is spare parts are the classic borderline, because a spare is finished for the buyer and a component for the maker, set against the fact that the point where a part bought to be built in becomes a good bought to be used. The codeset wording, not the size or price of the item, sets that point. Errors of this kind with component against finished survive because the resulting code still looks valid, with the right number of digits and a plausible title for component against finished. Only a check against the current codeset wording for component against finished exposes them, which is why checking is a habit rather than a one-off task.

Before moving on from component against finished, run one last check: does the claim that the point where a part bought to be built in becomes a good bought to be used still hold in the current codeset wording for component against finished? The codeset wording, not the size or price of the item, sets that point. Spare parts are the classic borderline, because a spare is finished for the buyer and a component for the maker.

Carry one habit away from component against finished: the point where a part bought to be built in becomes a good bought to be used, checked against the current UNDP codeset before it is quoted anywhere that matters. Spare parts are the classic borderline, because a spare is finished for the buyer and a component for the maker. A code for component against finished quoted that way can be verified by the next reader, and verification is the whole point of having a shared classification at all.