Harmonised system, tariff and commodity codes assigned to golden items, with validity and evidence, so customs, sourcing and reporting classify the same way.
Today tariff codes are typed per plant and per ERP; the same part clears customs under two codes and the duty is paid twice or audited once.
With Lima the commodity codes are read where they live, matched on item + scheme + country and code within a scheme version, assembled field by field and published as one golden record per real commodity, with every source key underneath. The declarations and shipments that used an assignment, and the review history are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Codes are reference data with versions; assignments are master data with evidence; both keep history for audits.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| HS | section → chapter → heading → subheading → national line |
| UNSPSC | segment → family → class → commodity |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | code exists in the scheme version valid at the date duty rate is between 0 and 100 |
| Row | an assignment has a reviewer and a reason an item shipped across a border has an HS code for each country pair |
| Business | one active code per item per scheme and country assignments older than 24 months with no review open a task |
| Transactions in the bed | Read from |
|---|---|
| Customs declarations | trade system |
| Shipments | transport |
| Duty paid | AP |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the declarations and shipments that used an assignment, and the review history.
Trade compliance edits; sourcing and logistics read; the evidence visible to auditors. The twelve layers apply on every door; see security.
POST /api/v1/golden/commodity/lookup
{
"item": "M-1183920",
"scheme": "HS",
"country": "DE"
}200 OK
{
"code": "8533.21.00",
"valid_from": "2025-01-01",
"reviewer": "E-20117",
"duty_rate": 0.0,
"eccn": "EAR99"
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Commodity codes read from T604 · T604T (GTS: /SAPSLL/CLSNR).
Open the SAP S/4HANA page →Trade classifications read from GTM tables (Global Trade Management) · EGP item classification.
Open the Oracle Fusion Cloud page →Commodity code read from CONFORMED.COMMODITY_CODE.
Open the Snowflake page →Commodity code read from silver.commodity_code.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A semiconductor equipment maker classified 210,000 items once and published the codes to both ERPs. Duplicate classifications fell to zero and the customs broker stopped querying every third shipment.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.
High-tech and semiconductor, Industrial manufacturing, Consumer goods, Life sciences. The industry pages show the domains each starts with.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.