Domain catalogue Supply chain

Commodity and tariff codes

Harmonised system, tariff and commodity codes assigned to golden items, with validity and evidence, so customs, sourcing and reporting classify the same way.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSnowflakelakehouseDatabrickslakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN COMMODITY AND TARIFF CODESCommodity and tariff codesone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the commodity and tariff codes record comes from, how it is assembled, and who reads it. Other systems have their own page.
3 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
2
hierarchies the record sits in
catalogue
3
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

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.

The golden record

4 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Code listsHS chapters, national tariff lines, UNSPSC, ECCN
wins: reference owner, versioned
Assignmentsgolden item → code per scheme and country, valid dates
wins: trade compliance
Evidenceclassification reason, ruling reference, reviewer
wins: trade compliance
Attributesduty rates, preferential origin, licence requirements
wins: customs data
How records match

The keys, in order

item + scheme + countrycode within a scheme version

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.

Where it sits

2 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
HSsection → chapter → heading → subheading → national line
UNSPSCsegment → 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.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columncode exists in the scheme version valid at the date
duty rate is between 0 and 100
Rowan assignment has a reviewer and a reason
an item shipped across a border has an HS code for each country pair
Businessone active code per item per scheme and country
assignments older than 24 months with no review open a task
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Customs declarationstrade system
Shipmentstransport
Duty paidAP
items with no codeduty by chapterreclassifications per month

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.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Trade compliance edits; sourcing and logistics read; the evidence visible to auditors. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/commodity/lookup
{
  "item": "M-1183920",
  "scheme": "HS",
  "country": "DE"
}
response
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.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

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.

illustrative scenario · Commodity and tariff codes
Terms on this page

HS codeThe Harmonised System classification used for customs worldwide.
ECCNAn export control classification number.
RulingA customs authority's binding decision on a classification.
Golden recordThe one record for a real commodity, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

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.

How long to the first golden view?

One working day for the first two sources; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

High-tech and semiconductor, Industrial manufacturing, Consumer goods, Life sciences. The industry pages show the domains each starts with.

See your first domain built on your data

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.