Why buyers need categories
Procurement systems use the classification code of each cart line to route approvals, post the cost to the right account and report spend by category. A cart without codes, or with codes at the wrong level, is often rejected or sent back by the buyer’s system.
UNSPSC vs ECLASS
| UNSPSC | ECLASS | |
|---|---|---|
| Origin | United Nations / GS1 US | ECLASS e.V., Germany |
| Typical buyers | SAP Ariba, international buyers | German industry, SAP buyers |
| Structure | Segment, family, class, commodity (8 digits) | Four levels plus properties |
| Example | 46181504 · protective gloves | Ask the buyer for the version they use |
Always check the version and the level of detail the buyer requires: some want the full 8-digit UNSPSC commodity, others accept the class level.
Where the code goes
cXML · ItemDetail
<ItemDetail>
<UnitPrice><Money currency="EUR">4.80</Money></UnitPrice>
<Description xml:lang="en">Safety gloves, size 9</Description>
<UnitOfMeasure>PR</UnitOfMeasure>
<Classification domain="UNSPSC">46181504</Classification>
</ItemDetail>OCI · cart field
NEW_ITEM-MATGROUP[1] = 46181504How to map your catalogue
- Get the standard, version and level from the buyer’s supplier documentation.
- Map your store categories to codes once, at category level.
- Override the code on single products that need more detail.
- Test a cart with a product from each category before UAT.
In PunchOut Rocket the mapping lives in the gateway dashboard: different buyers can use different standards on the same store, and your store’s own categories do not change.
PunchOut on the store you already have
PunchOut Rocket connects WooCommerce, Magento, PrestaShop and nopCommerce to SAP Ariba, Coupa and SAP via cXML or OCI. From €163/month per site, 30-day free trial.