Your desk · Trade compliance
Starts when a new item appears in your ERP or PLM
Today
New part numbers arrive every week. The hard ones take an hour or two, and the reasoning rarely gets written down.
How GingerOS carries it
GingerOSHow it works with your teams
Stop chasing every department for answers.
GingerOS reads from the systems your engineers, buyers, sales team and brokers already use. When one of them changes something, it does the research and brings you the decision. They keep working as they do. You approve.
- 3 SKUs recheckedECN-2291New classification
- Origin recheckPO 7710Needs you
- Estimate to confirmRFQ-118Needs answer
- Broker used another codeEntry 3391Asked broker
- 38 SKUs hit, new rateSection 232New rate
- Declaration expired62-3310Requested
ConnectedERPPLMSupplier masterBroker feeds
Illustration with sample data: six notifications from other systems, such as a PLM engineering change and a Section 232 notice, move one by one into a Review queue window, where each lights up its row with a status such as Needs you or New rate.
Loop in every department. Add no steps.
Pick a department to see what it hands you, and what it never has to do.
ERPItem 50-2291
New item createdBattery tray housing, Monterrey plantGathered
- DrawingB-2291 rev CPLM
- MaterialAluminum 6061, extrudedPLM
- SupplierAlu-Parts MXERP
GingerDoes the tray ship with cells installed?
YouNo. Empty housing, cells go in later.
Reasoning
- GRI 1: an empty housing is a part, not a battery
- Sec. XVI Note 2(b): made for one Li-ion pack
8507.90.80New classification
Your turnReview and approveApproved
Lands on your desk. A queue sorted by what changed, with the reason already written.
Written back
- Code, reasoning and rulings saved
- Written to your ERP · HS field
- Kept 5 years from each entry that uses it
What you see
Your review queue
- 50-2291 · Battery tray housingNeeds answer
- 41-0672 · Trim bracketNew classification
- 50-1184 · Roof railVerified
- Re-key what already sits in the ERP or PLM.
- Dig for why a code was chosen.
R&D and compliance
Starts in your PLM, when an ECN is released
Today
Engineering changes a material or a coating in the PLM. Compliance finds out when a shipment is held.
How GingerOS carries it
PLMECN-2291
Housing material changedSteel to aluminum 6061Gathered
- SKUs touched3PLM
- Code relied onSteel contentRecord
- Current code7326.90.86Record
GingerDoes the new housing carry any sensor or radio?
R&DNo. Structural part only.
Reasoning
- The steel basis no longer holds after ECN-2291
- Now an article of aluminum, not of steel
7326.90.867616.99.51Reclassified
Your turnReview 3 SKUsApproved
Lands on your desk. The SKUs the change touched, each with the ECN attached.
Written back
- 3 SKUs updated in your ERP
- Each linked to ECN-2291
What they see, in their own system
PLM · ECN-2291
- Housing materialSteel to aluminum
- Export checkNo license needed
- One question for you1 parameter
- Fill in a new required field.
- Hand over the formula or the full spec sheet.
Procurement and compliance
Starts in the PO and the supplier master
Today
A buyer switches supplier to save on price. The new origin can cost the trade agreement and raise the duty, and compliance hears last.
How GingerOS carries it
ERPPO 7710
New supplier on a POAlu-Parts MX to NewCast THGathered
- Part50-2291 · Battery tray housingERP
- New originThailandSupplier master
- Rule that appliedUSMCA regional contentRecord
GingerPlease confirm the country of origin for part 50-2291.
SupplierMade in Thailand. Declaration attached.
Reasoning
- Origin moves from Mexico to Thailand
- The trade agreement no longer covers this part
0% duty25% dutyWarning sent to buyer
Your turnReview origin recheckReviewed
Lands on your desk. An origin recheck with the supplier’s declaration already attached.
Written back
- The buyer saw it before saving the PO
- Declaration filed on the part’s record
What they see, in their own system
PO 7710 · before you save
- Origin changes for 14 partsOrigin
- Trade agreement lost on 3 assembliesWarning
- Duty on this part+25%
- Wait for an approval before saving a PO.
- Chase supplier declarations by email.
Sales and compliance
Starts when an RFQ comes in
Today
A customer wants a delivered-duty-paid quote within two weeks. Sales has a concept drawing, and compliance can only guess the code.
How GingerOS carries it
CRMRFQ-118
Quote request, DDP DetroitConcept drawing, no BOM yetGathered
- Closest part50-2291Record
- DestinationUnited StatesRFQ
- Duty stackMFN + Section 232Tariff data
GingerAssume aluminum and no cells, like 50-2291?
YouYes, go with that.
Reasoning
- Estimated from the closest classified part
- US duty stack as of today’s date
$14.20 / unitEstimated at RFQ
Your turnConfirm assumptionsConfirmed
Lands on your desk. A short list of assumptions to confirm. Nothing else.
Written back
- The quote carries its assumptions
- Firmed up when the BOM arrives
What they see, in their own system
Quote · RFQ-118
- Landed cost, US$14.20 / unit
- AssumesAluminum, no cells
- StatusEstimated at RFQ
- Wait on compliance to send a quote.
- Ask three departments to fill in a customer’s origin form.
Logistics, brokers and compliance
Starts when a broker files an entry
Today
Each broker picks its own code for the same part. Compliance checks entries by email, one at a time.
How GingerOS carries it
Broker feedEntry 3391
Entry filed by the Canada brokerLine 4 filed as 8708.99Gathered
- Approved code8507.90.80Record
- Filed code8708.99Broker feed
- OriginMexicoRecord
GingerLine 4 differs from the approved list. Which list did you use?
BrokerAn old one. We will correct it.
Reasoning
- The filed code differs from the approved record
- The broker worked from an outdated list
8708.998507.90.80Mismatch found
Your turnSettle the codeSettled
Lands on your desk. Only the disagreements, with both codes side by side.
Written back
- Approved list resent to all 3 brokers
- Correction noted on Entry 3391
What they see, in their own system
Approved code list · sent
- Broker, United StatesIn sync
- Broker, MexicoIn sync
- Broker, Canada1 question
- Stop a shipment for an extra check.
- Guess the code for a trial shipment.
Finance and compliance
Starts when a tariff notice is published
Today
A tariff notice lands and finance asks what it will cost. The answer takes weeks, in a spreadsheet nobody can trace.
How GingerOS carries it
Federal RegisterSection 232
Aluminum derivatives: more parts addedEffective in 14 daysGathered
- SKUs touched38Record
- PlantsMX, US, THERP
- Entries a year214Broker feed
GingerTwo SKUs mix aluminum and steel. Count them as aluminum?
YouYes, aluminum is the larger share.
Reasoning
- New rate applied per SKU and per plant
- Every line traces to its classification
3.1% of COGS3.4% of COGSExposure ready
Your turnConfirm 2 SKUsConfirmed
Lands on your desk. The handful of SKUs that need your call.
Written back
- Exposure view sent to finance
- Duty change: +$412,000 a year
What they see, in their own system
Exposure view · Section 232
- SKUs hit38
- Duty change a year+$412,000
- Reserve needed$0
- Export cost data by hand once a year.
- Get a number without the reason behind it.
IT and compliance
Starts with read-only access, one system at a time
Today
The HS code is a field in the ERP with no history. Every rule change, someone asks IT to export the list again.
How it connects
ITAccess
Read-only access grantedERP first, then the PLMGathered
- Fields mapped42ERP
- Owner per fieldNamedIT
- Master data movedNoneERP
GingerWhich fields may GingerOS write back to?
ITHS code and origin. Nothing else.
Reasoning
- Write-back limited to two named fields
- Connectors run and are maintained on our side
2 fieldsScope set
IT’s turnSign off write-backSigned off
Lands on your desk. No more asking IT for an export. The list is always current.
Written back
- Every change has an owner and a log
- No new login for other departments
What they see, in their own system
ERP field · HS code
- OwnerTrade compliance
- Last change2026-09-12
- Change log4 entries
- Run an eighth system.
- Migrate master data.
Legal and compliance
Starts when a mistake is found, or customs asks
Today
A misclassification turns up. Legal has to decide on a disclosure without knowing which entries it touched.
How GingerOS carries it
CustomsCF-28
Request for informationEntries of 50-2291, last three yearsGathered
- Entries touched214Broker feed
- Reasoning at the timeOn recordRecord
- ApproverTiffanyRecord
GingerInclude both the Mexico and US entities?
YouYes, both.
Reasoning
- Evidence pack: reasoning, rulings, approvals
- A timeline of every change to the code
Pack readyComplete
Legal’s turnDecide what to sendDecided
Lands on your desk. A pack to review, not a week of digging.
Written back
- Kept for five years
- Exported in the format customs asks for
What they see, in their own system
Evidence pack · 50-2291
- Entries touched214
- Reasoning on recordComplete
- Kept until2031-09-12
- Rely on someone’s memory of why.
- Treat our output as legal advice.
Your company works its own way. Let’s sketch it.
GingerOS is built around your process, not the other way round. Pick the notes that sound like you, or write your own.
- We work in gates: quote, development, production.
GingerThen every code carries a status for each gate, and passing a gate triggers the recheck.
Brainstorm it with usIllustration with sample data: a folder with a tab per department, where the open tab shows a six-step handoff sheet beside a GingerOS window that plays the steps in order, from the change that came in to what is written back.
The folder’s last tab, Your flow?, opens a board of sticky notes describing ways a company might work, plus a blank note for your own. Picking one pins it to a Your GingerOS · draft window, where Ginger replies with how GingerOS would fit.
Keep the final say.
Four rules keep a person in charge of every decision.
It asks before it guesses.
Missing a fact? It asks the person who has it, and waits.
Nothing reaches your ERP without you.
Your approval is the only way in, and every write-back is logged.
Other teams get a warning, never a gate.
Buyers and engineers keep working. The system flags; it never blocks.
Your override sets the precedent.
Change a call and it is kept with your name and reason, for the next time that part comes up.
Classification decisionNo. 4412
- Part
- 50-2291 Battery tray housing
- Proposed
- 8507.90.808708.99.81
- Basis
- Asked
- 2 questions, answered by you
- Signed by
- Not signed yet
Illustration with sample data: a GingerOS window holds a classification decision for a sample part, with the proposed code, its basis and a Signed by line reading Not signed yet. A cursor clicks Approve and the status turns Approved, noted as written to the ERP.
Questions for any AI vendor.
Take it to every vendor on your shortlist, including us.
GingerOS meets 13 of 14 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.
- 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.
- 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.
- 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. 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.
