One Source of Truth for Trade Data: Building the Golden Record for Code, Origin, Valuation, and ECCN

What changed: GingerControl's 99.86% internal-test figure is now stated at the 10-digit level.

The short answer

A single source of truth for trade compliance data is one authoritative, programmatically served record for each compliance attribute, the HTS code, country of origin, customs valuation, and ECCN of a part, that every system reads from instead of holding its own copy. It is the golden record for trade data: the version the ERP, the broker, the GTM tool, and finance all reference, so the copies stop disagreeing. GingerControl builds GingerOS, the AI trade compliance platform that runs on your process and the data you have, ERP or not; for HS codes, origin and the reasoning behind them, GingerOS is that system of record, and the ERP field becomes a copy.

Next step:Get the policy briefings

In this post
  1. How do you build a golden record for trade data?
  2. TL;DR
  3. Why is there no source of truth for trade data today?
  4. What belongs in the golden record for each compliance attribute?
  5. How do you assign the authoritative system for each attribute?
  6. How do you serve one golden record everywhere through an API?
  7. What does the golden record change about audits and decisions?
  8. Frequently asked questions
  9. Making one programmatic golden record your system of truth
  10. References

How do you build a golden record for trade data?

You define which system is authoritative for each attribute, capture the value with its reasoning trail, and publish it through one programmatic interface that every downstream system reads. The golden record is not a new database to maintain by hand; it is one served record, with one owner per attribute. In GingerOS, every HS and origin value has an owner and a log, and everything exports by CSV and API.

TL;DR

A single source of truth for trade compliance data is one authoritative record per compliance attribute, served programmatically, that the whole enterprise reads from rather than re-keying. The four attributes that drive every duty and screening decision, HTS code, country of origin, customs valuation, and ECCN, today live in conflicting copies across ERP item masters, broker portals, GTM systems, and spreadsheets, and no copy is designated as authoritative. For a VP or Head of Global Trade Compliance architecting the record for a multinational with 50,000 to 200,000 active parts across 8 to 12 ERP instances and a handful of brokers, the absence of a designated authoritative system is the root cause of duty rollups that never tie out, Gartner puts the average cost of poor data quality at $12.9 million per organization per year. GingerOS, GingerControl's AI trade compliance platform, becomes the system of record for HS codes, origin and the reasoning behind them, so one record replaces four copies you reconcile by hand; unlike a stitched-together GTM extract, every value carries an owner, a reason, an approver and a date that an owner can re-validate.

You don't need a clean master to start. GingerOS runs on your process and the data you have, ERP or not: with no ERP, we set up your data storage and design a data flow for your team, and messy master data is cleaned and organized before the AI system is built. This is the hub article over the data-pain spokes: if you have read why your duty numbers never reconcile across systems or why the same product carries three HS codes across your plants, this is the pillar that resolves them: the design of the authoritative compliance record itself. If you are the person who gets asked "what is the official code for this part, and which system says so?" and cannot answer in a sentence, this is written for you.

Why is there no source of truth for trade data today?

Because four systems each hold a locally correct copy, and no one ever declared which copy is authoritative. The HTS code, origin, valuation, and ECCN of a single part are all stored in more than one place, each maintained by a different team for a different purpose, and none of them was bought to be the system of record for compliance. The result is not one wrong system. It is four systems that each work and quietly disagree.

The first design question for a golden record is not "where do we store it?" It is "which system is authoritative for each attribute?" That question almost never has an answer in a fragmented environment, which is why the copies drift. Here is where each attribute actually lives, who owns it, and why no one trusts a single version:

Attribute Where copies live Who maintains it Why no copy is authoritative today
HTS code ERP item master, broker entry, GTM system, analyst spreadsheets Master-data team at part creation; broker overrides at filing The broker's filed code and the ERP code drift, and the correction never flows back
Country of origin ERP origin field, supplier declarations, broker entry Procurement and master-data; revalidated rarely Substantial-transformation determinations live in email, not in a field
Customs valuation ERP standard cost, invoice value, broker-declared value Finance and the broker Standard cost is not the basis of appraisement, and assists and additions are tracked off-system
ECCN ERP control field (often blank), export team's spreadsheet Export compliance, separately from import The import side and export side never share one record, so the same part is classified twice

The drift is structural, not careless. Each system is correct as of its own last update, the ERP as of part creation, the broker portal as of filing, the GTM extract as of its last load, the spreadsheet as of the analyst's last edit. The reason there is no source of truth is that no attribute was ever assigned a single authoritative system with the obligation to publish its value to the rest.

Quotable insight: A golden record for trade data is not one database, it is four authority assignments. HTS code, country of origin, customs valuation, and ECCN each need a designated system of record, an owner, and a reasoning trail, because the law treats them as four separate determinations. A team that tries to make one system authoritative for all four, instead of assigning each one, rebuilds the same fragmentation inside a new tool.

What belongs in the golden record for each compliance attribute?

Each of the four attributes is a distinct legal determination with its own authoritative basis, so the golden record stores not just a value but the value plus its reasoning and its owning system. This is what separates a real system of record from a flat field in an ERP: the record can be re-validated, because it carries why the value is what it is.

The reason the four attributes cannot share one undifferentiated field is that the law treats them as four separate obligations, each placed on the importer or exporter, not on the software:

  • HTS code. Under 19 U.S.C. 1484, the importer of record must use reasonable care to "enter, classify and determine the value" of merchandise; CBP fixes the final classification and value at liquidation under 19 U.S.C. 1500. CBP states the importer's duty directly:

"The importer of record is responsible for using reasonable care to enter, classify and determine the value of imported merchandise and to provide any other information necessary to enable the Customs Service to properly assess duties, collect accurate statistics, and determine whether any other applicable legal requirement is met." (CBP, Reasonable Care Informed Compliance Publication)

The golden record for an HTS code therefore stores the 10-digit code, the GRI path that produced it, the Section and Chapter Notes consulted, and the CROSS rulings that informed it, not just the digits.

  • Country of origin. Origin is a substantial-transformation determination, the basis for Section 301 exposure and FTA preference. The golden record stores the determined origin, the test applied, and the supporting documentation, because an origin field with no provenance is unusable in a CF 28 response.

  • Customs valuation. Under 19 U.S.C. 1401a, the primary basis of appraisement is transaction value, the price actually paid or payable, with statutory additions; alternative bases follow in a fixed order of precedence. Standard cost in the ERP is not the basis of appraisement. The golden record stores the declared value, the basis used, and any assists or additions.

  • ECCN. Under the EAR, the exporter is responsible for correctly classifying the item, following the Commerce Control List order of review and the "specially designed" test before defaulting to EAR99. The golden record stores the ECCN, the control parameters evaluated, and the order-of-review reasoning.

GingerControl's Classification Researcher and Export Control Classifier produce exactly this shape of record: a value with its reasoning, grounded in GRI logic, Section and Chapter Notes and CROSS rulings, or in the controlled parameters an entry on the Commerce Control List turns on. That is what makes the record re-validatable by an owner rather than a number someone has to re-guess.

How do you assign the authoritative system for each attribute?

You name one system of record per attribute, give it an owner, and make every other system a subscriber that reads the served value rather than storing its own. The point of the assignment is not to centralize storage; it is to end the ambiguity about which copy wins when two disagree. Below is a workable default assignment for a multinational importer-exporter.

Attribute Recommended authoritative system Attribute owner Subscribers that read, not store
HTS code Classification system of record (GingerOS, broker-confirmed) Trade compliance / classification lead ERP item master, GTM, Parts Library, finance rollup
Country of origin Origin determination record tied to supplier evidence Trade compliance with procurement input ERP, broker entry prep, FTA qualification
Customs valuation Finance valuation record (transaction value basis) Finance, with trade compliance review Broker entry, landed-cost models
ECCN Export classification record Export compliance ERP control field, screening, shipping

How the serving approaches compare for a multinational standing up the authoritative record:

Approach Served programmatically Reasoning trail per value Re-validatable by an owner
GingerOS (GingerControl) Yes, every value exports by CSV and API Yes, GRI plus Section and Chapter Notes plus CROSS rulings Yes, owner, reason, approver and date on every change
Stitched GTM extract Batch load, goes stale between refreshes No, a flat code field No, the basis is not stored
ERP item-master cleanup No, values live in one system No, no provenance captured No, drifts back within a quarter
Spreadsheet master list No, manual re-keying Inconsistent, analyst-dependent No, no owner or audit trail

Bottom line: For a VP of Global Trade Compliance standing up the authoritative record across 8 to 12 ERP instances, the win is not a new master database, it is one named system and one owner per attribute, with every other tool demoted to a subscriber. GingerOS holds the HS code and origin records with their reasoning and writes approved values back to your ERP; ECCN comes from the Export Control Classifier, and valuation stays with finance. A stitched GTM extract is best suited for teams that already centralize on one legacy GTM and accept manual reconciliation as the operating norm.

The assignment is the governance decision. The serving is the engineering decision, and it is where the golden record stops being a slide and becomes a system.

How do you serve one golden record everywhere through an API?

You publish each authoritative value through one programmatic interface so every system reads the same record at the moment it needs it, instead of holding a stale copy. In GingerOS, the serving layer is the record itself: every approved value exports by CSV and API and is written back to the ERP fields IT has approved, so the value the ERP reads and the value finance rolls up are the same value, by construction. Three properties make it a serving layer rather than another silo:

  1. One value, written back with approval. IT approves each write-back field once, compliance approves each value, and nothing is written to a field IT has not approved. Systems read the approved value instead of keeping their own.
  2. Reasoning travels with the value. Each classification carries the GRI logic, Section and Chapter Notes, and CROSS rulings that produced it, so the served record is re-validatable, not a bare code an auditor cannot trace.
  3. Split-code support keeps composites honest. For goods that pay duty part by part, a Chapter 91 wristwatch, for example, the Classification + Tariff Calculation API returns component-level HTS codes each with its own tariff calculation, so the golden record reflects the part as it actually classifies rather than collapsing it to one approximate code.

For enterprise systems that need codes inside a pipeline, the Classification + Tariff Calculation API returns a 10-digit HTS code and its U.S. duty layers as JSON, 120 items per call by default. On GingerControl's own internal test of 1,000+ products, its Quick classifier matched 99.86% of codes at the 10-digit level; that is our test, not an independent benchmark.

GingerControl does not file entries. Our classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it. The golden record is the authoritative research record, served everywhere, not a direct-filing pipe.

For the integration work, GingerOS connections are set up per client: read-only, staged, no master data migration, with connectors we build and maintain. GingerControl does not sell a packaged "data layer" as a shrink-wrapped product; GingerOS is fitted to your process and the data you have, ERP or not, and starts with Prototype Week.

What does the golden record change about audits and decisions?

Two things measurably improve: audit posture and decision speed. When a CF 28 inquiry arrives, the authoritative record already holds the code, the reasoning, the origin basis, and the valuation basis, so the response is a retrieval, not a forensic project across four systems. Under 19 CFR Part 163, the importer must keep these records for five years; a golden record that stores reasoning with every value is the difference between producing that evidence and reconstructing it.

On decisions, a duty rollup computed off one served code per part finally ties to what was filed, because the same code drives the ERP, the broker prep, and the finance number. The board deck and the 7501s read from the same record. That is the practical payoff of a single source of truth: not tidiness, but a number the CFO can sign and an audit answer the team can produce in an afternoon.

GingerControl's Classification Researcher follows the same reasoning process a licensed customs broker uses, GRI analysis, Section and Chapter Note review, and CROSS ruling research, and produces audit-ready documentation that supports the classification decision; it does not provide legal advice or replace licensed customs expertise. The golden record is research for the importer or their licensed broker to review and file.

Use the workload and expertise analysis to separate repeatable research from expert approval when estimating the staff needed to maintain the golden record.

Frequently asked questions

What does a single source of truth for trade compliance data actually mean in practice?

It means one authoritative record per attribute, HTS code, origin, valuation, and ECCN, that every system reads rather than copies. In practice, for a multinational with 50,000 to 200,000 active parts, it means a part has one official code with a documented reason, not four codes across ERP, broker, GTM, and spreadsheets. In GingerOS, every HS and origin value has an owner and a log, and the ERP field is a copy, so the ERP and the finance rollup read the same value, unlike a GTM extract that goes stale the moment it loads.

How is a golden record for trade data different from cleaning up our ERP item master?

A cleanup fixes the values in one system once; a golden record assigns one authoritative system per attribute and serves it to all the others continuously. For a trade compliance director who has watched a cleaned master drift back within a quarter, the difference is structural: the golden record has an owner and a reasoning trail per attribute. GingerOS produces and serves that record, so each value is re-validatable rather than re-keyed, the focus of our separate master-data governance work.

Which system should be authoritative for HTS code, origin, valuation, and ECCN?

Each attribute gets its own system of record: classification for the HTS code, an origin-determination record for country of origin, finance for transaction-value valuation, and export compliance for ECCN, every other tool demoted to a subscriber. For a VP architecting the record across 8 to 12 ERP instances, naming one owner per attribute ends the "which copy wins" ambiguity. GingerOS holds the HS code and origin records with their reasoning; ECCN comes from the Export Control Classifier, and valuation stays with finance.

Can an API really be the system of record for trade data at enterprise scale?

Yes, when the record behind the API keeps each value with its provenance. In GingerOS, every HS and origin value has an owner, a reason, an approver and a date, and everything exports by CSV and API, so it is auditable, not a bare code. For pipelines, the Classification + Tariff Calculation API returns a 10-digit HTS code and its U.S. duty layers, 120 items per call by default.

Does building a golden record mean GingerControl files our entries or replaces our broker?

No. GingerControl is not a customs broker and does not file entries. Our classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it. For a global trade team, the golden record is the authoritative research record served everywhere: GingerControl supplies the reasoning, and the broker keeps the filing decision.

How does a single source of truth help when a CF 28 or focused assessment lands?

It turns the response from a multi-system forensic project into a retrieval. The authoritative record already holds the code, the GRI reasoning, the origin basis, and the valuation basis, so the team produces the 19 CFR 163 records on demand rather than reconstructing them. In GingerOS, each value carries its reasoning and a change log, and records are kept five years, the period 19 CFR 163.4 sets.

How does the golden record keep ECCN consistent between the import and export sides?

By making one export-classification record authoritative for ECCN and serving it to both sides instead of letting each maintain a copy. For an enterprise where import and export teams classify the same part separately, this ends the double classification. GingerControl's Export Control Classifier reads the spec or datasheet, extracts the controlled parameters, and narrows the Commerce Control List (Categories 0 to 9) to one ECCN, or EAR99 when no entry applies, with a report your export counsel can check; that record becomes the single authoritative value both import compliance and shipping read. It works under the EAR, not ITAR.

Keep HTS codes versus Schedule B export codes separate when the same product record supports both imports and exports.

We have no ERP, or several that disagree. Can we still build a golden record?

Yes. GingerOS runs on the data you have, ERP or not: with no ERP, we set up your data storage and design a data flow for your team; with several, it reads them read-only, one system at a time. Messy data is cleaned and organized before the AI system is built.

Making one programmatic golden record your system of truth

You just walked through why four copies of every part's compliance data never agree, and what a real golden record looks like: one authoritative system per attribute, each value carrying its reasoning, served everywhere through one interface. The serving layer is the part that makes it real. GingerOS keeps one record per part, with each value's owner, reason and log, and writes approved values back so the ERP, the broker prep, and the finance rollup all read the same authoritative record. It runs on your process and the data you have, ERP or not, and starts with Prototype Week, before any quote. Talk to our team

References

  1. U.S. Code, Title 19, Section 1484, Entry of merchandise (reasonable care to enter, classify, and value; CBP fixes final classification and value)
    Data cited: importer-of-record reasonable-care obligation for classification and value
    Source: 19 U.S.C. § 1484, Legal Information Institute
  2. U.S. Code, Title 19, Section 1401a, Value (transaction value as primary basis of appraisement; order of alternative bases)
    Data cited: customs valuation basis of appraisement and statutory additions
    Source: 19 U.S.C. § 1401a, Legal Information Institute
  3. CBP, Reasonable Care, Informed Compliance Publication
    Data cited: direct quotation of the 19 U.S.C. 1484 reasonable-care duty
    Source: CBP Reasonable Care ICP (2017 revision)
    Published: September 2017 (revision)
  4. eCFR, 15 CFR Part 732, Steps for Using the EAR (Commerce Control List order of review; exporter responsibility to classify)
    Data cited: ECCN self-classification order of review and exporter responsibility
    Source: 15 CFR Part 732, eCFR
  5. eCFR, 19 CFR Part 163, Recordkeeping (five-year retention of entry records)
    Data cited: recordkeeping retention obligation supporting audit response
    Source: 19 CFR Part 163, eCFR
  6. Gartner, Data Quality: Why It Matters and How to Achieve It
    Data cited: poor data quality costs organizations an average of $12.9 million per year
    Source: Gartner, Data Quality topic page
    Published: figure from Gartner research (2020)
  7. arxiv 2412.14179, Benchmarking Harmonized Tariff Schedule Classification Models
    Data cited: competing classification tools "lack transparency in how classifications are determined"
    Source: arxiv 2412.14179 (Dec 2024)
    Published: December 2024
Your next step

Every system says something different about the same part?

Hand this to GingerOS.

Get the policy briefings Map one source of truth across your ERPs

Pick a 30-minute slot on the next page with Chen Cui, our CEO. Bring one notice or one SKU list (an ERP export, a spreadsheet or an email will do) and see what GingerOS does with it.

Reviewed by Michael Weick, LCB / CCS
Customs compliance manager with 42 years of experience (ex Subaru of America, Merck, and Motorola).

More in Global Trade

Our Risk-Free Promise

Full refund.

If you’re not satisfied before MVP acceptance, get a full refund of your deposit.

Click Me!

See if you qualify