12 Questions to Ask Trade Compliance Vendors in a Demo

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

The short answer

The questions that separate trade compliance vendors are the ones they must answer live, on your own SKUs: will it run on your process and the data you have, what does it ask before it gives a code, what happens to your catalog when a tariff changes, who approves each code and what record is kept, and what it does not do. For a trade compliance manager at an electronics maker with 20,000 SKUs and three demos booked, send these 12 questions and ten hard SKUs a week ahead, and score every vendor on the same script.

Next step:Get the policy briefings

In this post
  1. What are the best questions to ask vendors during demos to assess trust?
  2. What questions should we ask vendors about compliance coverage?
  3. How should you run three demos so the answers are comparable?
  4. How does GingerControl answer these 12 questions?
  5. Putting the 12 questions on your own SKUs
  6. References

I'm Chen Cui, co-founder of GingerControl. We sit on the other side of these demos, so the list below includes the questions we would least like to be asked badly. This post is for the demo itself. The contract-stage checks, security terms and exit clauses are in the 20-point checklist before signing; a ranked list of vendors is in the trade compliance software buyer's guide.

What are the best questions to ask vendors during demos to assess trust?

The best questions make the vendor work on your data in front of you, because a live answer on your hardest SKU tells you more than any slide about accuracy or integrations.

#QuestionA good answer sounds like
1Will you run on our process, or do we change ours to fit your software?They map your flow back to you: who requests a code, who approves it, where the result goes
2What data do you need to start, and what if we have no ERP trade module or our data is messy?They name fields and sources, and say what they do when the data is missing or messy
3Can you read the documents we actually have: supplier emails, PDFs, spreadsheets, images?They name the formats and what they do not read
4Classify three of our hardest SKUs live. What does it ask before it gives a code?Questions about composition, function or use, before any code
5Show the reasoning: which GRI, which Section and Chapter Notes, which CROSS rulings, read when?A reasoning chain for each digit level, with rulings read during the decision, not pasted after
6What is your accuracy figure measured on, and what counted as correct?Whose products, how many, which digit level, who judged it
7A rule takes effect tomorrow. Show the list of our SKUs it hits and what each now owes.Your SKUs, each duty layer on its own line, for the entry date
8When a part, supplier or BOM changes, what is rechecked and who is told?A named trigger, a named owner, a dated record
9Who approves each code before it reaches our ERP or an entry, and what record is kept?A named approver and a record kept at least five years under 19 CFR 163.4 [1]
10Where does our data run, who can see it, and does it train your models?A dedicated environment, access by role, never used for training
11What do you not do?Plain limits: filing, screening, AD/CVD, legal advice, countries not covered
12What happens before we sign, and what does it cost?A proof on your own flow, a written quote, dated phases

Bottom line: For a trade compliance manager running three demos for a 20,000-SKU electronics catalog, questions 4, 7 and 9 decide most evaluations: a vendor that asks before it classifies, rechecks your catalog when a rule moves and records who approved what will hold up; one that only shows its own catalog has shown you a product, not a fit.

Quotable insight: The most revealing moment in a trade compliance demo is not the first code but the first question. A tool that returns a 10-digit code for your hardest composite part in seconds, without asking what it is made of or what it does, has just shown you how it will treat the 19,990 SKUs you did not bring.

What questions should we ask vendors about compliance coverage?

Ask what the system covers by market, by duty layer, by export regime and by job, and ask it in writing before the demo, because coverage gaps are cheaper to find on paper than in month three.

Coverage areaAskWhy it matters for a Taiwan, China, Mexico, U.S. group
Classification marketsWhich countries' codes, at how many digits?The U.S. needs 10 digits; Mexico and Canada have their own schedules
Duty layersEach layer separately, for which import country, by entry date?2026 brought three big U.S. duty changes: IEEPA ended, Section 122 ran February 24 to July 23, the forced-labor Section 301 began July 24 [2] [3] [4]
Export controlEAR and ECCN only, or ITAR too?Some classifiers, ours included, cover the EAR's Commerce Control List but not the USML
Screening and filingDo you screen parties? Do you file entries?Usually separate tools and separate licenses
Legal roleWho is the licensed customs broker in your process?Classifying for entry can be customs business under 19 U.S.C. 1641 [5]; see what counts as customs business

Question 7 is where most demos break, because a rule change is the work that grows. The U.S. tariff schedule was revised 21 times between January 16 and October 9, 2026 [6]. A vendor that answers with an alert email has answered half; the other half is your SKU list with the new duty on each line. How alerts differ from rechecks is covered in newsletters vs alerts matched to your HTS codes, and how a rule change flows through classification, export control and duty in one compliance workflow.

Compare trade policy alert services by sources, product matching, effective-date information and follow-up actions.

How should you run three demos so the answers are comparable?

Run every demo on the same script, the same ten SKUs and the same scorecard, with each approver scoring their own block right after the call.

  1. Send the 12 questions and ten SKUs a week ahead. Pick a composite module, a part with steel or aluminum content, a part with several origins, one whose duty changed in 2026, and one with a thin supplier description.
  2. Block the demo in three parts. Your SKUs and the reasoning (compliance), a rule change and the recheck (compliance and finance), data, security and cost (IT and the CFO).
  3. Score each answer: shown live, explained, or not answered. A slide counts as explained.
  4. Ask for a proof on your own flow from the two vendors left, before any contract.

If R&D owns the product specs, invite them for question 2: their concern is what leaves the building, and it is easier to answer in the room than in a later email. The numbers that follow the demos go into the trade compliance software ROI calculator, the business case around them into how to build the business case for trade compliance automation, and the decision between building, buying or having a system fitted is in build vs buy for trade compliance AI.

How does GingerControl answer these 12 questions?

Here are our answers, so you can hold us to the same script.

#GingerControl's answer
1GingerOS runs on your process and the data you have, ERP or not; we prototype your flow before any contract
2It starts from whatever data you have: with no ERP we set up the data storage environment and design a data flow for you; messy data is cleaned and organized first, then the AI system is built
3It reads anything in text or image form, such as emails, PDFs and Excel files; it does not read video
4It asks for missing product facts before it suggests an HTS code ("Ginger doesn't guess. It asks.")
5GRI 1 to 6 reasoning with Section and Chapter Notes, CROSS rulings read during the classification, code determined in stages at 4, 6, 8 and 10 digits
699.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products (the Quick classifier); an internal test, not an independent benchmark, so test your own sample
7GingerOS checks every SKU against a new rule, lists the ones it hits and shows each affected part's new duty and next step; U.S. duty only
8It watches changes in your ERP, PLM and supplier records and rechecks export control, FTA eligibility and origin documents
9A person approves each code; approved results are written back to your ERP with an audit trail; records kept five years
10Your dedicated environment, encrypted in transit and at rest, monitored around the clock, access by role, never used to train models
11We do not file entries, screen denied parties, calculate AD/CVD, cover ITAR, or give legal advice; duty is U.S. only; classification covers the U.S., Canada (10-digit classification numbers) and the EU in beta
12The Prototype Week: a clickable prototype of your own flow in three days, a requirements meeting the same week, then a quote; GingerOS is quoted per project, typically 8 to 16 weeks to go-live

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. Brokers and small businesses that do one product at a time use the same reasoning in the Classification Researcher inside the GingerLite app, $150 a month for 300 credits, with top-ups if you run out.

The workflow for AI research tools for licensed customs brokers keeps research support separate from the broker’s reviewed filing decision and the importer’s responsibilities.

Putting the 12 questions on your own SKUs

The fastest way to score us is to make us answer question 12 first: 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 send us your ten hardest SKUs

References

  1. 19 CFR 163.4, Record retention period
    Data cited: records kept for five years from the date of entry
    Source: 19 CFR 163.4 (eCFR)
  2. Executive Order 14389, Ending Certain Tariff Actions, 91 FR 9437
    Data cited: signed February 20, 2026; the additional ad valorem duties imposed under IEEPA "shall no longer be in effect" and, as soon as practicable, "shall no longer be collected"
    Source: 91 FR 9437, Federal Register
    Published: February 25, 2026
  3. Proclamation 11012, Imposing a Temporary Import Surcharge (Section 122), 91 FR 9339
    Data cited: signed February 20, 2026; surcharge on goods entered from February 24, 2026, through July 23, 2026 (in effect through 12:01 a.m. EDT on July 24, 2026)
    Source: 91 FR 9339, Federal Register
    Published: February 25, 2026
  4. Office of the U.S. Trade Representative, Notice of Actions in Section 301 Investigations of Acts, Policies, and Practices of Various Economies Related to the Failure of Each Economy To Impose and Effectively Enforce a Prohibition on the Importation of Goods Produced With 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
  5. 19 U.S.C. 1641, Customs brokers
    Data cited: the definition of customs business, which includes the classification and valuation of merchandise for entry
    Source: 19 U.S. Code § 1641 (Cornell LII)
  6. U.S. International Trade Commission, HTS release list
    Data cited: 2026 HTS Revisions 1 to 21, Revision 1 effective January 16, 2026, Revision 21 effective October 9, 2026 (current on October 11, 2026)
    Source: USITC HTS release list
    Published: read October 11, 2026

Questions people ask

What are the best questions to ask vendors during demos to assess trust?

Ask questions the vendor can only answer live on your own data: classify three of your hardest SKUs and show what it asks first, show the list of your SKUs a new tariff rule hits, and show who approves each code and what record is kept. For a compliance manager comparing three vendors across 20,000 SKUs, a slide answer to any of these is a warning sign.

What questions should we ask vendors about compliance coverage?

Ask which markets it classifies for, which duty layers it calculates and for which countries, whether export control covers ITAR or only the EAR, and whether it screens parties or files entries. For an electronics maker with Taiwan, China, Mexico and U.S. entities, GingerControl classifies for the U.S., Canada and the EU in beta, calculates U.S. duty only, and does not screen or file.

A vendor says their AI is 95% accurate. What should we check before we believe it?

Check what was tested, who ran the test and what counted as correct: a 10-digit match, a 6-digit match or a broker accepting the code. For a 20,000-SKU electronics catalog, rerun 30 of your own hard SKUs. GingerControl's 99.86% at the 10-digit level is its own internal test of 1,000+ products, not an independent benchmark, which is exactly why your own sample matters more than anyone's figure.

Should we bring our own SKUs to a trade compliance vendor demo?

Yes, and send them a week ahead so every vendor gets the same set. For an electronics maker, pick ten: a composite module, a part with metal content, one with several origins, one whose duty changed in 2026, and one with a thin supplier description. A demo on the vendor's own catalog shows the product; a demo on yours shows the fit.

Should we ask for a product demo, a trial, or a proof of concept?

Start with a demo on your own SKUs, then ask for a proof on your own flow before any contract. For a manufacturer with four entities, a trial of a generic app tells you little about approvals and ERP write-back. GingerOS starts with the Prototype Week: a clickable prototype of your own flow in three days, with zero permissions and zero production data, then a quote.

How should the demo be structured so the CFO and IT director get their questions in?

Split it into three blocks with the same script for every vendor: your SKUs and the reasoning, a rule change and the recheck, then data, security and cost. For a demo with a compliance manager, a CFO and an IT director, give each block to the person who owns it and score it right after, before the next vendor's demo blurs the answers.

How many vendor demos is too many?

Three is usually enough when each runs the same script on the same SKUs; more than four tends to blur the comparison. For a team of two evaluating trade compliance software alongside daily work, a shortlist from a written questionnaire first saves days: any vendor that cannot answer the coverage and data questions in writing does not need a demo.

Can we accept a vendor's SOC 2 report instead of a full security questionnaire?

Accept it for general controls, but still ask the questions it may not answer directly. For an IT director reviewing a trade compliance vendor, those are whether your data trains the vendor's models, whether it runs in a dedicated environment or a shared one, how unusual access is flagged, and how long records are kept. A SOC 2 report describes controls in general terms; it may not answer those four for your data.

What should we ask a vendor if we don't have an ERP trade module?

Ask what the system needs to start and where it gets it when there is no ERP trade module. For an electronics maker whose part facts sit in supplier emails, PDFs and spreadsheets, the right answer names those sources. GingerOS runs on your process and the data you have, ERP or not: with no ERP we set up the data storage and design a data flow for you.

How do we validate vendor claims about references?

Ask for a reference with your shape, not the vendor's biggest logo: similar SKU count, entities, product type and data situation. For a 20,000-SKU electronics maker, ask the reference what the first rule change after go-live looked like and how long their own team spent on it. A reference who cannot describe a recheck has not used the system for one.

Your next step

New to importing, or new to the compliance seat?

Hand this to GingerOS.

Get the policy briefings Talk it through with our team

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 Trade Basics

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