Stop running trade compliance by hand.

GingerOS is the AI-native system that runs trade compliance across your systems: classification, duty, origin documents, export controls and rule changes. You approve, and the know-how stays with you.

GingerOS · Tariff Approved
  1. Ginger A tariff rule changed. 38 SKUs are hit.
  2. Ginger One part has no origin certificate. Asking the supplier.
  3. Ginger They replied. Duty goes from 0% to 25%. Ready for you.
  4. Tiffany Approved.
  5. Ginger Recorded, and synced to your ERP.
Section 232 Steel and aluminum 38 SKUs
Duty on 38 SKUs 0% → 25% Origin certificate received
SKUs hit
38
Duty redone
38
Left for you
2
External portal
  • Email Connected
  • Supplier portal Replied
  • Slack, Teams Connected
Origin certificate 1 steel part · due in 2 days Origin certificate.pdf No login. One link.

Illustration with sample data: a Section 232 notice lands on the Compliance Radar and Ginger brings it into GingerOS. One part has no origin certificate, so she opens the External portal and requests it in the supplier portal; the supplier uploads Origin certificate.pdf and she brings it back. Duty on 38 SKUs moves from 0% to 25%, and two items reach the to-do list, “Approve the Section 232 change” and “Review 2 mixed-metal SKUs”. Ginger ticks the first once the compliance manager approves it in chat.

From your systems, and back again.

Ginger plugs into what you already run, tidies the scattered files, does the work, and writes the approved answer back.

GingerOS · Your systems Synced
  1. Ginger I plug into your ERP, PLM and shared drive.
  2. Ginger One record per part, and the origin declaration is missing.
  3. Ginger I classified it: HTS code 8518.30.2000.
  4. Ginger Missing a fact? I go and ask.
  5. Ginger Nothing is final until you say so.
  6. Tiffany Approved.
  7. Ginger Written back to your ERP, with the paperwork attached.
Part 50-1180 Wireless earbuds
FieldStatus
Spec sheetFound
BOMFound
SupplierFound
Origin declarationFound
HTS code 8518.30.2000 4 rounds of reasoning
  • ERP Written back
  • PLM Read
  • Shared drive Read
External portal
  • Email Replied
  • Supplier portal Connected
  • Slack, Teams Connected
To SonicLink SZ Origin declaration for part 50-1180 Could you send the origin declaration for the wireless earbuds? Ginger, for Tiffany’s team
From SonicLink SZ Re: Origin declaration for part 50-1180 Attached, signed today. Origin declaration.pdf

Illustration with sample data: Ginger reads one part, wireless earbuds 50-1180, from the ERP, PLM and shared drive and finds its origin declaration missing. She gets HTS code 8518.30.2000, emails the supplier from the External portal, brings back Origin declaration.pdf from their reply, adds “Approve part 50-1180” to the to-do list, and writes the approved answer back to the ERP.

Every code keeps its paperwork.

Round by round: the rule it used, every heading it weighed, and why each one stayed or went.

GingerOS · Classification Reasoning on record, 4 rounds
Classification Decision 8518.30.2000 Wireless earbuds Resolved
Model reasoning process

I show my work. Every round.

Round 1 Determining 4-digit HEADING: 8518

GRI 1 / Section XVI Note 3

The retail set is classified by its essential character, which is the earbuds. The earbuds are a composite machine performing both radio reception and sound reproduction. Under Section XVI Note 3, they are classified by their principal function of sound reproduction.

Provision (candidate)Why it is relevantSelection / exclusion reason
8518Provides for headphones and earphones, whether or not combined with a microphone.Selected because the principal function of the earbuds is sound reproduction.
8517Provides for apparatus for transmission or reception of voice, images or other data.Excluded because radio reception is not the principal function of the goods.

Round 2 Determining 6-digit Subheading: 8518.30

GRI 6

At the 6-digit subheading level, the goods are evaluated against the provisions for microphones, loudspeakers, headphones, and amplifiers.

Provision (candidate)Why it is relevantSelection / exclusion reason
8518.30Provides for headphones and earphones, whether or not combined with a microphone.Selected because the goods are wireless earbuds.
8518.10Provides for microphones and stands therefor.Excluded as the goods are earbuds, not standalone microphones.
8518.21 - 8518.29Uncoded group providing for loudspeakers.Excluded as the goods are earphones, not loudspeakers.

Round 3 Determining 8-digit Subheading: 8518.30.20

GRI 6

Within subheading 8518.30, the goods must be further classified based on whether they are line telephone handsets.

Provision (candidate)Why it is relevantSelection / exclusion reason
8518.30.20Provides for other headphones and earphones.Selected because the wireless earbuds are not line telephone handsets.
8518.30.10Provides for line telephone handsets.Excluded because the goods are wireless Bluetooth earbuds, not handsets for line telephony.

Round 4 Determining 10-digit HTS Code: 8518.30.20.00

Statistical

The 8-digit subheading 8518.30.20 is not further subdivided, so the goods inherit its sole 10-digit statistical reporting number.

Provision (candidate)Why it is relevantSelection / exclusion reason
8518.30.20.00Statistical reporting code for other headphones and earphones.Selected as the only reporting code for the chosen legal subheading.
Classification session complete. Total thinking time: 3:15

Illustration with sample data: the classification record for wireless earbuds shows four rounds of reasoning, one per level of the code, each with the rule it applied and every candidate heading with why it was selected or excluded, ending at HTS code 8518.30.2000. Ginger takes the code to the Compliance Radar to watch and files “Reasoning on record, 4 rounds” on the to-do list.

A rule changes. Ginger rechecks first.

Ginger finds every part it hits, redoes the work, and hands you what is left.

GingerOS · Compliance Radar Two left, waiting for you
  1. Ginger A new Section 232 notice. Aluminum parts are added.
  2. Ginger 38 of your SKUs are hit. Here is each one.
  3. Ginger I already reclassified 3 and recalculated duty on all 38.
  4. Ginger Two need your judgment. Approve and I write them back.
  • Tariff
    38 SKUs hit
  • Class.
    3 SKUs reclassified
  • PGA
    0 no change
  • Export
    0 no change
  • FTA
    0 no change
Notice Federal Register
Section 232 Aluminum derivatives added Effective in 14 days
Impact on your company
SKUs hit38 of 4,210
Plants3
Open purchase orders14
Already done Done
  • 3 SKUs reclassified, with the reason
  • Duty stack recalculated on 38 SKUs
  • New landed cost sent to finance
Left for you Your turn
2 SKUs mix aluminum and steel Two need your judgment.

Illustration with sample data: a Section 232 notice is checked against all five radars, 38 of 4,210 SKUs are hit, Ginger reclassifies 3 and recalculates duty on all 38, and adds “Review 2 mixed-metal SKUs” to the compliance manager’s to-do list.

Missing a fact? Ginger goes to get it.

Not just email. Chat, a supplier portal, whatever your partners already use. We build it around you.

GingerOS · Origin Reply in, finishing the check
  1. Ginger This origin check is stuck. The new supplier never sent a declaration.
  2. Ginger So I asked them, the way they like to be asked.
  3. Ginger Three days, no reply. I followed up.
  4. Ginger They answered in chat. I am finishing the check now.
50-2291 Battery tray housing Origin declaration received
External portal
  • Email Sent
  • Supplier portal Received
  • Slack, Teams Replied, day 6
To NewCast TH Origin declaration for part 50-2291 We need the country of origin before PO 7710 ships. The link takes two minutes. Ginger, for Tiffany’s team
Origin declaration Part 50-2291 · due in 3 days Origin declaration.pdf No login. One link.
Ginger Hi! Could you confirm the country of origin for part 50-2291?
NewCast TH Made in Thailand. Sending the declaration now.

Illustration with sample data: an origin check for part 50-2291, a battery tray housing, is blocked, so Ginger opens the External portal. She emails the new supplier, follows up in chat (Slack or Teams) on day 3 and opens a request in the supplier portal. The supplier answers in chat and uploads Origin declaration.pdf, and she brings it back to finish the check, adding “Approve the origin check, part 50-2291” to the to-do list.

You decide. Ginger learns.

Approve, or reject with a reason. Ginger rethinks and keeps your rule for next time.

GingerOS · Classification Your rule applied
  1. Ginger Part 50-2291: I propose 8507.90.80. My reasons are in the report.
  2. Tiffany · Trade Compliance Manager Rejected. We hold a binding ruling for this tray family. Keep 8708.99.81.
  3. Ginger Understood. I reran it with your ruling.
  4. Tiffany Approved. Write it back.
  5. Ginger I saved that as one of your company rules.
  6. Ginger A similar tray came in. I used your rule this time.
Proposed HTS code Approved
8708.99.81 8507.90.80
50-2291 · Battery tray housing
Basis Your binding rulingGRI 1
Your company rules
  • New suppliers: ask for an origin declaration first
  • Prototype parts: ask R&D for the material
  • Tray family 50-22: follow your binding ruling Taught by Tiffany, 2026-09-12 New
50-2304 Battery tray, long Your rule applied

Illustration with sample data: Ginger proposes HTS code 8507.90.80 for part 50-2291 and adds “Decide on part 50-2291” to the to-do list. The compliance manager rejects it citing the company’s binding ruling, Ginger reruns it to 8708.99.81, saves the ruling as a company rule, and applies it on its own to a similar tray.

Onboard Ginger, the expert who never quits.

Trade compliance know-how is hard to train. Keep it with Ginger, who never leaves.

Your company rules Kept
  • New suppliers: ask for an origin declaration first
  • Prototype parts: ask R&D for the material
  • Tray family 50-22: follow your binding ruling Taught by Tiffany, 2026-09-12

Illustration with sample data: in the last scene Ginger walks in, ticks “Company rule saved” on the to-do list, and sits on the card of company rules she keeps, three rules including the one the compliance manager taught her.

Compliance Radar Live
Tariff Section 232 · 38 SKUs Done
  • Tariff
    1
  • Class.
    0
  • PGA
    0
  • Export
    0
  • FTA
    0
To-do
  • Done: Approve the Section 232 change
  • To do: Review 2 mixed-metal SKUs
  • Done: Supplier certificates checked

Illustration with sample data: the Compliance Radar panel puts five radars on one scope, Tariff, Classification, PGA, Export and FTA, and shows the notice Ginger is working on and how many items are open on each. The To-do panel lists the decisions waiting for a person.

Questions for any AI vendor.

Take it to every vendor on your shortlist, including us.

Vendor checklist

GingerOS meets 15 of 17 today. How your data is used is written into the contract, and security is answered in your review before you sign. Our answers are self-assessed, so ask us to show each one.

Which trade compliance jobs does it run, start to finish?
A named list, each job from trigger to record: classification, duty, origin and trade agreements, export controls and rule changes. Not only a classifier.
GingerOS watches new rules and changes in your ERP, PLM and supplier records. It checks every SKU against a new rule and shows each affected part’s new duty and next step. It asks for missing product facts before it suggests an HTS code and records the reasoning for your approval. It rechecks export control classification (ECCN), FTA and trade agreement eligibility and origin documents, requests expired certificates from suppliers, and writes approved results back to your ERP with an audit trail.
Show me the reasoning behind one real classification.
Every statement has a source, rulings are cited, and it says why the other code was rejected.
Every code carries its reasoning at each level of the code, the rulings it relied on, and why the other code lost.
Can the AI finalize anything on its own?
Never. A named person approves every final decision.
No. A named person on your side approves every final decision.
What happens when I override it?
The override is kept with your name and reason, and it is reused next time.
It is kept with your name and reason and becomes the precedent for that part.
Does it learn how our company does things?
Your corrections and house rules are kept and applied to similar products next time.
In the contract
Yes, we build that into your GingerOS: a rejection with your reason becomes a company rule that Ginger applies to similar parts next time.
When data is missing, does it guess?
It asks the person who has the fact and flags the gap.
It asks one question at a time, only what the decision needs, and waits for the answer.
Can you start from our data as it is, even without an ERP?
Yes. The vendor works from the files you have and does the cleanup, not you.
Yes. With no ERP, we set up your data storage and design its flow; messy data we clean first. It reads emails, PDFs, spreadsheets and images.
When a rule changes, what happens to past decisions?
The affected SKUs and past entries are listed, with the impact.
The affected SKUs come back to your queue, and past entries hit by an approved change are listed with the duty difference.
Can I export an audit pack, and how long are records kept?
The full history exports any time, and records can be kept the five years customs requires.
Every record exports, and records can be kept for the five years 19 CFR 163.4 requires.
How do you connect to our systems, and who maintains it?
Read-only first, one system at a time, maintained by the vendor, with write-back only to named fields.
We start from files that already flow, then connect read-only, one system at a time. We build and maintain the connectors.
How was accuracy tested, and will you test on our products before we pay?
A named test set, an answer key from your experts, and a pass line agreed in advance.
Yes, and our own figure is on record: 99.86% at the 10-digit level on GingerControl’s own internal test of 1,000+ products. Then we test on your products: we agree a test set, an answer key and a pass line, and the deposit is refundable until MVP acceptance.
Who is liable if a code is wrong?
No vendor can take your liability. A good one helps you document your own reasonable care, and never calls its output legal advice.
You are, and no vendor can change that. GingerOS keeps the reasoning, the approver and the date, so you can document your reasonable care.
Will your tool replace our customs broker?
No. A licensed broker still reviews the code and files the entry.
No. Our codes are for general reference, educational, and planning purposes; your licensed customs broker reviews each one and files the entry.
Is it legal for your AI to give us 10-digit codes?
Yes, as research for reference, education and planning, with a licensed customs broker reviewing the code before it goes on an entry.
Yes, as research: our codes are for general reference, educational, and planning purposes, and your licensed customs broker reviews each one before it goes on an entry.
Do you train AI models on our data?
No training of shared models on your data, and the terms are written into the contract.
We never use your data to train AI models, and how your data is used is written into the contract.
What happens to our data if we leave?
Everything exports in formats you can read without them.
Every record exports by CSV and through the API.
Which security controls and attestations do you hold today?
What they hold now, not what they plan, with the report or the evidence.
Ask us
Encryption in transit and at rest, and access by role. Ask us where we stand on anything else; we answer your security review in full before you sign.

See the timeline and the team.

Typically 8 to 16 weeks in five phases, and who each side sends to each one.

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