20-Point Buyer's Checklist for Trade Compliance Software
What changed: Rebuilt the 20 points around reasoning, rechecks, audit trail and records, data, security and exit terms, with GingerControl's answers limited to confirmed facts; retired features and unsupported claims removed; re-checked on October 11, 2026.
Before you sign trade compliance software, check 20 points in six areas: how it reasons about each code, how it rechecks your SKUs when a rule changes, whether its audit trail and records survive five years under 19 CFR 163.4, what data it needs to start, how it secures that data, and how you leave. For a head of trade compliance at a chemicals group with 14 U.S. entities and 8,000 SKUs, six points are non-negotiable: reasoning on record, rechecks, a named approver, five-year retention, no model training on your data, and a full export at exit.
In this post
- What should a trade compliance software checklist cover before you sign?
- What security and audit trail requirements should trade compliance software meet for customs documentation?
- How do you score the 20 points?
- How does GingerControl answer the checklist?
- Running the checklist on your own flow
- References
I'm Chen Cui, co-founder of GingerControl. This checklist is the one we expect buyers to run on us, and our answers are at the end. It is for the contract stage. The questions to ask live in a demo are in questions to ask trade compliance vendors in a demo; switching from a current system is in the migration playbook; how vendors price is in pricing models compared.
What should a trade compliance software checklist cover before you sign?
It should cover six areas, each with points you can verify in a demo or in the contract, not on a slide.
Classification reasoning
- The system asks for missing product facts before it suggests a code.
- Each code shows its GRI steps and the Section and Chapter Notes behind it.
- CROSS rulings are read during the decision, not attached afterwards.
- For composite goods, it records which component gives the product its essential character under GRI 3(b), and why.
Duty layers and rechecks 5. Every duty layer appears on its own line for the entry date, including the 2026 changes: Section 122 only for goods entered February 24 to July 23, 2026, and the forced-labor Section 301 from July 24 [1] [2]. 6. When a rule changes, it rechecks every SKU and lists the ones it hits. 7. It watches your own changes too: new parts, suppliers and BOMs, not only government notices (why an alert alone is not enough). 8. Export control (ECCN or EAR99) and origin documents are rechecked, or clearly out of scope.
Audit trail and records 9. Every code has a named approver and a date. 10. Approved records cannot be edited; a correction creates a new dated version. 11. Records are kept at least five years from the date of entry [3]. 12. A record from 18 months ago comes back in the demo, with its reasoning.
Data and integration 13. It starts from the data you have, with a plan for entities with no ERP and for messy data. 14. Connections are read-only and staged, with no master data migration. 15. It reads the formats your data lives in: supplier emails, PDFs, spreadsheets, images.
Security and boundaries 16. Your data never trains the vendor's models, or anyone else's, in writing. 17. A dedicated environment, encryption in transit and at rest, monitoring of unusual access, access by role. 18. The vendor states plainly that it is not your customs broker, does not file entries and does not give legal advice, and shows how its output reaches your broker.
Contract and exit 19. You can export every code, its reasoning, approver and dates in a usable format, at any time and after termination. 20. A written quote with every fee, notice periods, and what happens to your records if the vendor is acquired or closes.
Bottom line: For a head of trade compliance at a 14-entity chemicals group, points 2, 6, 9, 11, 16 and 19 are the non-negotiables: a vendor that fails any one of them leaves you with codes you cannot defend, a catalog nobody rechecks, or records you cannot take with you.
What security and audit trail requirements should trade compliance software meet for customs documentation?
It should keep, for every code, the reasoning, the approver and the date in a record no one can silently change for at least five years, and hold the data in a dedicated, encrypted environment that never trains anyone's models.
| Requirement | Why it matters | How to verify it before signing |
|---|---|---|
| Reasoning stored with each code | The importer owes reasonable care in classifying (19 U.S.C. 1484) [4] | Ask for the stored record of a code approved last year |
| Named approver and date | Shows who decided, and when | Change a code in the demo and see both versions |
| No silent edits | An editable trail cannot show what you knew when you filed | Ask how a correction is recorded |
| Five-year retention from entry | 19 CFR 163.4 [3] | Contract clause, including after termination |
| No model training on your data | Formulas and specs stay yours | Contract clause, not a settings page |
| Dedicated environment, encryption, monitoring | Your data is not pooled with other customers | The vendor's written security answers, plus any SOC 2 or equivalent report it has |
Quotable insight: An audit trail that records who changed a code but not why is a log, not a defense. CBP asks why a code was chosen; the only answer that still holds five years later is the reasoning written at the moment of the decision and approved by a named person. Buy the reasoning, and the log comes with it.
If your current answer to "why this code?" lives in a spreadsheet, the gap is points 2, 9 and 10, whatever software you choose. The business case for closing it is in how to build the business case for trade compliance automation, and the numbers behind it in the trade compliance software ROI calculator.
Compare trade compliance tools for SMB importers against the small importer's actual duty exposure and number of products.
How do you score the 20 points?
Score each point as shown live, explained, or not answered, and treat any non-negotiable that is not shown live as a fail.
| Score | What it means |
|---|---|
| 18 to 20 shown or explained, all six non-negotiables shown live | Proceed to contract review |
| 14 to 17, all six non-negotiables shown live | Proceed, with the gaps written into the contract or the rollout plan |
| Any non-negotiable not shown live | Ask for a proof on your own flow before going further |
| Under 14 | Stop |
Run it with the people who can veto the deal: compliance on points 1 to 12, IT on 13 to 17, procurement and legal on 18 to 20, and R&D on 13 and 16 if your specs and formulas are involved. A group deciding whether to build instead should read build vs buy for trade compliance AI before scoring anyone, and one adding a system beside an incumbent suite should see Descartes vs GingerControl.
How does GingerControl answer the checklist?
Here are our answers, limited to what we can confirm in writing.
| Points | GingerControl's answer |
|---|---|
| 1 to 4 | Asks for missing product facts before suggesting an HTS code; GRI 1 to 6 reasoning with Section and Chapter Notes; CROSS rulings read during the classification; records which component gives a composite product its essential character |
| 5 | U.S. duty layers on their own lines for the entry date, MPF and HMF included, in the Tariff Calculator; GingerOS shows each affected part's new duty and next step; duty for U.S. imports only |
| 6 to 8 | GingerOS watches new rules and changes in your ERP, PLM and supplier records, checks every SKU against a new rule and lists the ones it hits, and rechecks export control, FTA eligibility and origin documents |
| 9 and 11 | A person approves each code; approved results go back to your ERP with an audit trail; records kept five years |
| 13 to 15 | Runs on your process and the data you have, ERP or not; read-only, staged connections, no master data migration; reads emails, PDFs, spreadsheets and images, not video |
| 16 to 17 | Customer data never trains our models or anyone else's; runs in the customer's own dedicated environment; encrypted in transit and at rest; monitored around the clock; access by role |
| 18 | GingerControl is not a customs broker, does not file entries, and does not give legal advice; before a code goes on an entry, your licensed customs broker reviews it |
| 20 | GingerOS is quoted per project after the Prototype Week; five phases, typically 8 to 16 weeks to go-live |
What we do not do, so you can rule us in or out: we do not screen denied parties, file entries, calculate AD/CVD, cover ITAR, or calculate duty for imports outside the U.S. GingerControl's Classification Researcher follows the reasoning a licensed customs broker uses: GRI analysis, Section and Chapter Note review, and CROSS ruling research. Its classifications are for general reference, educational, and planning purposes. A finance view of the same checklist, duty by entity, is in what tariff management software is.
Use the guide to when to hire an ITAR consultant when jurisdiction, technical-data controls or program design exceed the team's in-house expertise.
Running the checklist on your own flow
The cheapest way to score points 1 to 15 is on your own products before any contract. GingerOS starts with the Prototype Week: one call, then a clickable prototype of your own flow in three days, with zero permissions and zero production data, and a quote after. Book a GingerOS call and score us on your own SKUs
References
- Proclamation 11012, Imposing a Temporary Import Surcharge (Section 122), 91 FR 9339
Data cited: surcharge on goods entered from February 24, 2026, through July 23, 2026
Source: 91 FR 9339, Federal Register
Published: February 25, 2026 - Office of the U.S. Trade Representative, Notice of Actions in Section 301 Investigations Related to Forced Labor, 91 FR 47318
Data cited: Section 301 duties on products of 60 economies, effective 12:01 a.m. ET on July 24, 2026
Source: 91 FR 47318, Federal Register
Published: July 28, 2026 - 19 CFR 163.4, Record retention period
Data cited: records kept for five years from the date of entry, unless another period is specified
Source: 19 CFR 163.4 (eCFR) - 19 U.S.C. 1484, Entry of merchandise
Data cited: the importer of record's duty, using reasonable care, to make entry and file the declared value, classification and rate of duty of imported merchandise
Source: 19 U.S. Code § 1484 (Cornell LII)
Questions people ask
What security and audit trail requirements should trade compliance software meet for customs documentation before a long-term contract?
It should record who approved each code, when, and why, keep that record unedited for at least five years from entry under 19 CFR 163.4, and hold your data in a dedicated, encrypted environment that never trains the vendor's models. For a chemicals group with 14 U.S. entities, verify each one in the demo and write the data and retention terms into the contract.
What are the best systems for tariff code governance and audit readiness?
The best ones record the reasoning behind each code, a named approver and every later change, and recheck codes when a rule changes. For a group with 8,000 SKUs across 14 entities, GingerOS records the reasoning for your approval and writes approved results back to your ERP with an audit trail; SAP GTS or Oracle GTM fit groups that keep filing and screening inside one ERP.
What should a trade compliance checklist cover when a multinational evaluates compliance software?
Six areas: classification reasoning, duty layers and rechecks when rules change, audit trail and five-year records, data and integration, security, and contract and exit terms. For a multinational with entities in several countries, add one question per area about each entity: which codes it classifies, which duties it calculates, and whose records it keeps.
Can Excel provide an audit trail for HTS classifications?
Only a weak one: a spreadsheet can store a code and a note, but anyone can overwrite a cell without a record of who changed it, when, or why. For a compliance team keeping 8,000 SKUs across 14 entities, that is the gap CBP finds when it asks why a code was chosen three years ago. Version history helps; it does not record the reasoning.
Can a classification audit trail be edited after the fact?
A good one cannot: corrections should create a new dated version with its own approver, and the earlier version stays readable. For a chemicals group answering a CBP request about entries from 2023, an editable trail is worse than none, because it cannot show what the company knew when it filed. Ask the vendor to change a code in the demo and show both versions.
Do we need SOC 2 to pass a vendor security review?
Many IT teams ask for a SOC 2 Type II report or an equivalent, but it answers only general control questions. For an IT director reviewing trade compliance software, also ask whether your product data trains the vendor's models, whether it runs in a dedicated environment, how unusual access is flagged and blocked, and how long records are kept. Those answers belong in the contract.
Does the vendor train AI models on our product data?
Ask, and get the answer in the contract, because formulas and specs are exactly what R&D will not let leave the building. For a chemicals group classifying resins without disclosing formulas, the safe answer is never, as a setting the vendor cannot switch on. At GingerControl, customer data never trains our models or anyone else's, and it runs in the customer's own dedicated environment.
Can we get our classification history out if we cancel?
Only if the contract says so: ask for an export of every code, its reasoning, its approver and its dates, in a usable format, at any time and after termination. For a group that must keep records five years from each entry, losing the history at cancellation is a records problem, not just a migration cost. Test one export before you sign.
How many years must classification records be kept for CBP?
Five years from the date of entry for most records, under 19 CFR 163.4, and a different period where a specific rule says so. For a chemicals group filing entries every week across 14 entities, the system's retention has to outlive the contract term: a three-year agreement does not cover records from its first year, so ask what happens to them when it ends.
Do we need an ERP before we sign trade compliance software?
Not with every vendor, so ask what each one needs to start. For a group whose 14 entities run different systems, GingerOS runs on your process and the data you have, ERP or not: with no ERP, GingerControl sets up the data storage and designs a data flow for you, and messy data is cleaned and organized first. It reads emails, PDFs and spreadsheets, not video.
Shortlisting AI for trade compliance?
Hand this to GingerOS.
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




