Customs Compliance Workflow Orchestration: Classification, Export Control and Duty in One Flow

What changed: Rewritten around GingerOS as it is today: one workflow for classification, export control and duty with named approvals and write-back, and an honest line on screening and licenses, which stay in a screening suite; retired services and unsupported coverage claims removed.

The short answer

A customs compliance workflow carries each new product, or each rule change, through classification, export control, duty and origin documents, with a named person approving each decision and one record at the end. The big suites cover classification, licenses and screening on their own model; few run the product decisions on your own process. For a director of trade compliance at an electronics maker adding 5,000 SKUs a quarter, the workable setup is GingerOS for the product decisions on your own process, and your screening suite for parties and licenses, connected so nothing is typed twice.

Next step:Try the Classification Researcher on one product

In this post
  1. What are the best platforms for customs classification, license, and screening workflows?
  2. How does one workflow carry a product from classification to duty?
  3. Where should a person approve, and what gets recorded?
  4. Should you integrate the tools you have or replace them?
  5. Putting your own flow into one workflow
  6. References

I'm Chen Cui, co-founder of GingerControl. We build the product-decision side of this workflow and not the screening side, so I'll be specific about the line between them. Choosing among whole suites is covered in the trade compliance software buyer's guide; screening itself is covered in the denied-party screening guide.

What are the best platforms for customs classification, license, and screening workflows?

The best setups split the work: one system for product decisions (HTS code, ECCN or EAR99, duty, origin) on your own process, and a screening suite for parties and licenses, because the suites that cover everything ask your process to fit theirs.

PlatformProduct classificationExport classification (ECCN, EAR99)Denied-party screeningLicense managementRuns on your process
GingerOSYes, reasoning recorded for approvalYes, rechecked with each changeNoNoYes
SAP GTSYesYesYesYesInside SAP
Oracle GTMYesYesYesYesInside Oracle
Thomson Reuters ONESOURCEYes (AI, with rationales)YesYesYes (licensing control)Ask
DescartesYes (AI-assisted)YesYes (Visual Compliance)Yes (export licensing)Configurable workflows

Suite capabilities are from each vendor's own pages as re-checked on October 7, 10 and 11, 2026 [1]; "Ask" means the vendor's public pages did not settle it. A head-to-head with one of these suites is in Descartes vs GingerControl. SAP, Oracle and Thomson Reuters publish no price for these suites, and Descartes gives only an indicative range for screening; GingerOS is quoted per project after the Prototype Week.

Bottom line: For a director of trade compliance at an electronics maker with 5,000 new SKUs a quarter and a screening system already in place, keep the screening suite for parties and licenses and run the product decisions in GingerOS on your own process. If you are standardized on SAP or Oracle and want everything inside the ERP, SAP GTS or Oracle GTM is the better single home.

How does one workflow carry a product from classification to duty?

It passes each decision forward as data, not as a retyped value, and stops for a person at each decision that carries legal weight.

  1. TriggerA new part, a supplier change or a new rule
  2. FactsMissing product facts requested from emails, PDFs and spreadsheets
  3. HTS codeGRI reasoning, notes and rulings recorded
  4. Export controlECCN or EAR99 rechecked
  5. Duty and originEach U.S. duty layer, FTA eligibility, origin documents
  6. ApprovalA named person approves each decision
  7. Write-backResults to the ERP with an audit trail

GingerOS does each of those steps fitted to your process, not from a template: it watches new rules and changes in your ERP, PLM and supplier records; asks for missing product facts before it suggests an HTS code and records the reasoning for your approval; rechecks export control, FTA eligibility and origin documents and requests expired certificates from suppliers; checks every SKU against a new rule and shows each affected part's new duty and next step; and writes approved results back to your ERP with an audit trail. It runs on your process and the data you have, ERP or not. A rule change usually reaches a team first as a newsletter or an alert; what each catches is in newsletters vs alerts matched to your HTS codes.

Quotable insight: In a customs compliance workflow the costly failure is not a wrong answer but a retyped one. The material and function facts that decide the HTS code also bear on the ECCN, and the code, with the origin, decides the duty. When each lives in its own tool, the same fact is typed three times and can be wrong three different ways, so the record that should explain the decision ends up contradicting itself.

For single products, the same reasoning is available as tools in the GingerLite app: the Classification Researcher for HTS codes and the Export Control Classifier, which narrows the Commerce Control List to one ECCN, or EAR99 when no entry applies, under the EAR only [4]. It does not cover ITAR, screen parties or determine licenses.

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.

Where should a person approve, and what gets recorded?

A person should approve every decision that goes on an entry or an export, and the record should keep the facts, the reasoning, the approver and the date for as long as the law requires.

DecisionWho approvesWhat the record keepsHow long
HTS codeYour compliance owner, then your licensed customs broker before entryProduct facts, GRI reasoning, notes and rulings, approver, dateFive years from entry under 19 CFR 163.4 [2]
ECCN or EAR99Your export compliance owner, with counsel where neededParameters read, CCL entry or EAR99 basis, approver, dateFive years under the EAR's recordkeeping rule, 15 CFR 762.6 [3]
Duty and originCompliance and financeLayers by entry date, FTA basis, origin documentsWith the entry records
Party screeningYour screening owner, in the screening suiteLists checked, such as the Consolidated Screening List [5], and the match decisionPer your screening tool

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; before a code goes on an entry, your licensed customs broker reviews it. GingerControl is not a customs broker, does not file entries, and does not give legal advice. What the record must hold, point by point, is in the 20-point checklist before signing.

Should you integrate the tools you have or replace them?

Integrate what does its job well, replace the handoffs, and start from the data you already have.

  1. Keep the screening suite if it already screens your orders; connect it to the product record instead of re-entering parts.
  2. Retire the ECCN spreadsheets by reading them in as starting data and rechecking each decision once.
  3. Connect the ERP read-only and staged, with no master data migration. With no ERP at a site, GingerControl sets up the data storage and designs a data flow for it; messy data is cleaned and organized first.
  4. Measure the handoffs you removed: minutes per new SKU from request to approved record, and the SKUs a rule change touches.

How to put those minutes into a business case is in the trade compliance software ROI calculator; whether to build the workflow in-house is in build vs buy for trade compliance AI; how a finance team views the duty side of the same record is in what tariff management software is.

Compare trade compliance software for import customs validation by what it validates before filing and what it audits after filing.

Putting your own flow into one workflow

The fastest test is your own flow: one call, then a clickable prototype of it in three days, with zero permissions and zero production data, and a quote after. GingerOS takes the product decisions, your screening suite keeps the parties. Book a GingerOS call to prototype your compliance workflow

References

  1. Vendor pages as recorded in GingerControl's competitor research
    Data cited: SAP Global Trade Services product page (tariff classification, sanctioned party list screening, managing licenses; pricing on request) and SAP Learning (ECCN control classes); Oracle Global Trade Management product page (tariff and export control classifications, restricted party screening, export licenses and permits); Thomson Reuters ONESOURCE Global Classification (HS and ECCN, "transparent rationales"), Denied Party Screening and Export Compliance ("licensing control") pages; Descartes product classification ("AI-assisted HTS classification"), Export Classification (ECCN to EAR99), Visual Compliance screening and Export License Management pages, with an indicative price range for screening only; read on each vendor's own site, October 7, 10 and 11, 2026, named and not linked
    Source: Tariff impact simulation platforms compared, where more of these suites' facts are cited with their dates
  2. 19 CFR 163.4, Record retention period
    Data cited: import records kept for five years from the date of entry
    Source: 19 CFR 163.4 (eCFR)
  3. 15 CFR 762.6, Period of retention (Export Administration Regulations)
    Data cited: records required by the EAR kept for five years
    Source: 15 CFR 762.6 (eCFR)
  4. 15 CFR 748.3 and 15 CFR 734.3(c)
    Data cited: classification requests to BIS; EAR99 for items subject to the EAR not listed on the Commerce Control List
    Source: 15 CFR 748.3 (eCFR), 15 CFR 734.3 (eCFR)
  5. International Trade Administration, Consolidated Screening List
    Data cited: the U.S. government's combined list of parties for export screening
    Source: Consolidated Screening List (trade.gov)

Questions people ask

What are the best platforms for customs classification, license, and screening workflows?

Suites such as SAP GTS, Oracle GTM, Thomson Reuters ONESOURCE and Descartes cover all three on their own model; few run the product decisions on your own process. For an electronics maker with 5,000 new SKUs a quarter, keep a suite for screening and licenses, while GingerOS runs classification, export control rechecks and duty on your own process, records the reasoning for approval and writes results back to your ERP, next to the screening suite you keep.

Is there a platform that handles classification, export control and screening in one workflow?

Some suites offer all three modules, but few run them on your own process with one record. For a company that imports components and exports controlled goods, the practical answer is one workflow for the product decisions (HTS code, ECCN or EAR99, duty, origin) and a screening tool for the parties on each order, connected so nothing is typed twice.

How does customs compliance software integrate with ERP systems?

Usually by reading item, supplier and order data from the ERP and writing approved results back, either through connectors or file exchanges set up per client. For a manufacturer on one ERP with no trade module, ask whether the connection is read-only, whether it migrates master data, and where the record lives. GingerOS connects read-only and staged, with no master data migration.

Can denied-party screening be automated, or do I still need a person?

The matching can be automated; resolving a possible match needs a person. For an exporter screening every new customer and order, software compares names against government lists such as the Consolidated Screening List and flags close matches, and someone has to decide whether a flagged party is the listed one, record why, and hold the order until they do.

Does every product need an ECCN?

No. Only items listed on the Commerce Control List get an ECCN; items subject to the EAR that fit no entry are EAR99. For an electronics maker, many standard parts end up EAR99, but anything with controlled performance parameters, such as some encryption or high-speed components, needs a real classification against the CCL categories before it ships.

Can a company classify its own products for export, or does BIS have to do it?

Exporters can classify their own items; BIS does not have to. For a company adding hundreds of products a quarter, self-classification is normal, with a formal classification request to BIS under 15 CFR 748.3 for items you are unsure about. GingerControl's Export Control Classifier narrows the CCL to one ECCN, or EAR99, and writes a report your export counsel can check.

Should we integrate our existing compliance tools or replace them with one platform?

Integrate the tools that do their job well and replace only the handoffs. For a team with a classifier, ECCN spreadsheets and a screening system, the screening system usually stays, the spreadsheets go, and the gap is one record across decisions. GingerOS works next to existing suites and writes approved results back to your ERP with an audit trail.

Can we keep using Excel while we move classification and ECCN decisions into one workflow?

Yes, and you should during the move. For a team whose ECCN decisions live in spreadsheets, the workflow can read those files as its starting data and run beside them until each decision has been rechecked and approved in the new record. GingerOS reads Excel, PDFs, emails and images, so the spreadsheets become inputs rather than a migration project.

Can AI approve classification and export control decisions automatically?

It should not. For a director of trade compliance responsible for HTS codes and ECCNs, the system drafts each decision with its reasoning and a named person approves it before it reaches the ERP or an order. GingerControl's classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it.

Do we need an ERP before we can run one compliance workflow?

No. For a manufacturer whose ERP talks to none of its compliance tools, or a site with no ERP at all, 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 before the AI system is built.

Your next step

Classifying SKUs one ruling at a time?

Hand this to GingerOS.

Try the Classification Researcher on one product Get your SKU list classified, reasons included

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 AI & Technology

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