Embedded HS Classification for SaaS: How to Add It Without Building It
Chen Cui Co-Founder of GingerControl What changed: The tool list, ranks and references are updated.
SaaS platforms embed HS classification by calling a classification API from their own product (an ERP, order system, TMS or marketplace) and showing the result inside their workflow, instead of building a classifier. The design choices that matter are what the API returns (a code, duty, a reason), how users review it before it reaches an entry, and the legal line: CBP has held that giving others codes beyond six digits for goods they will import is customs business. For a platform serving 500 importers, build the review step, not the classifier.
In this post
Embedded HS classification means your users get tariff codes inside your software, from an API you call, rather than from a separate tool. GingerControl's Classification + Tariff Calculation API is one such API: it returns a 10-digit HTS code with its U.S. duty layers in one call, for enterprise customers after a call, with one key sized to your calling pattern. I'm Chen Cui, a GingerControl co-founder. This post covers the design and the legal line for any API you embed; it is not legal advice.
How do you embed HS classification in a SaaS platform without building it?
You call a classification API from your product, show the code with its context, and add a review step, in that order:
- Map your product fields (name, description, materials, use, origin) to the API's input. Thin descriptions produce thin codes.
- Call the API in batches where the vendor allows; GingerControl's API takes 120 items per call by default, sized to your throughput.
- Show the code with its context: the HTS description, the duty for the user's origin and date, and any reasoning or confidence the API returns.
- Let the user review and approve, and route codes for entry to their licensed broker.
- Log every result with the date and HTS revision; recheck when the schedule changes.
Quotable insight: For a SaaS platform, the classifier is the part you can buy; the review step is the part your users will judge you on. A code that appears with its duty, its reason and an approve button helps an importer meet reasonable care. A code that appears silently in a field helps no one, and may put the platform on the wrong side of CBP's customs business line.
What should the embedded experience show your users?
Show enough for a user to check the code, not just copy it.
| Element | Why it matters |
|---|---|
| The code and its official description | Users can see what the code covers |
| The facts sent to the API | A wrong fact explains a wrong code |
| Duty for the user's origin and date | The code's real cost; Section 301 and 232 depend on origin and entry date |
| Reasoning or confidence, if the API returns it | Something to review, not just accept |
| Date and HTS revision | By our count of the USITC's release list, the 2026 HTS had 21 revisions by October 9, 2026 [1] |
| Review and approval status | Who checked it, and whether a broker confirmed it |
Where is the legal line for platforms?
The line is whether the platform gives users codes beyond six digits for goods they will import, and whether that output is kept apart from entry filing. Classifying goods "for others" is customs business that needs a broker license, while six-digit classification is not (HQ H290535) [2]. In HQ H350722, CBP applied that to a platform's AI tool: suggestions "beyond the six-digit level ... if the merchandise being classified will be entered" were customs business, while a tool giving general information "disconnected from an actual or intended importation", operating "separately from the portal connecting importers to brokers", with a "meaningfully implemented" disclaimer, was permissible [3]. The same ruling found that merely transmitting data between importers and brokers was not customs business.
Review legal limits of trade compliance disclaimers before assuming a general-reference statement changes the customs-business analysis.
The ruling is walked through service by service in what CBP ruling HQ H350722 says about AI classification tools; the procedure your users can follow is in how to use AI classification tools legally. Ask customs counsel how your product's design fits.
Which classification APIs can a platform embed?
Several vendors sell classification APIs; they differ in what one call returns and how access works.
| API | What one call returns, from its own pages | Access |
|---|---|---|
| GingerControl Classification + Tariff Calculation API | A 10-digit HTS code and U.S. duty layers in force when called; split-code composite duty as components | Enterprise, after a call |
| Gaia Dynamics Platform API | "classification suggestions ... with reasoning and confidence" and estimated tariffs | On request; no API price published |
| Zonos Classify | HS codes of 6 to 14 digits for nearly 200 countries | 1,000 free, then from $500 a month |
| Avalara Item Classification API | Country-specific codes for more than 180 countries; an MCP server for AI agents | Quote-based |
| TariffLens API | hts_code, reasoning, supporting_rulings for U.S. HTS and EU CN | On request; no price published |
Sources: [4]. Scored side by side in the best HTS classification APIs; the head-to-head with Avalara's classification (formerly 3CE) is in 3CE vs GingerControl. GingerControl does not publish white-label or resale terms; API access starts with a call. GingerControl's classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your user's licensed customs broker reviews it. GingerControl is not a customs broker, does not file entries, and does not give legal advice.
Should you build, embed or both?
Embed when classification supports your product; build only when classification is your product. The trade-offs are in build vs buy for HTS classification, and the free USITC API for schedule data, which a platform can use alongside a classification API, is explained in HTS lookup API vs manual classification.
Wiring classification into your platform
Start with the review screen your users will see, then pick the API that fills it. If your users import into the United States and need the code with its U.S. duty layers, the Classification + Tariff Calculation API returns both in one call. Talk to us about embedding the API
References
- U.S. International Trade Commission, HTS release list (read October 11, 2026)
Data cited: 32 revisions to the 2025 HTS; Revision 21 of the 2026 HTS effective October 9, 2026
Source: USITC HTS release list - U.S. Customs and Border Protection, ruling HQ H290535 (September 29, 2022)
Data cited: "Classifying goods for others is 'customs business'"; classification to the six-digit level is not customs business
Source: CBP CROSS, HQ H290535 - U.S. Customs and Border Protection, ruling HQ H350722 (January 16, 2026)
Data cited: the six-digit line and nexus to entry; general information "disconnected from an actual or intended importation"; operating "separately from the portal connecting importers to brokers"; disclaimer "meaningfully implemented"; data transmission between importers and brokers not customs business; "A tool does not constitute a 'person'"
Source: CBP CROSS, HQ H350722 - Gaia Dynamics Platform API and API access pages; Zonos Classify page and plans page; Avalara Tariff Code Classification and Classification MCP Server pages; TariffLens API docs; SimplyDuty Pricing page; Descartes Product Classification and Duty Determination page (all read October 11, 2026)
Data cited: Gaia "classification suggestions ... with reasoning and confidence" and estimated tariffs, API access on request, no API price published; Zonos 6 to 14 digits, nearly 200 countries, 1,000 free then from 500 USD a month; Avalara more than 180 countries, MCP server; TariffLens fields hts_code, reasoning and supporting_rulings for US-HTS and EU-CN, access on request, no price published; SimplyDuty Product Classification API £0.10 per API call; Descartes "Powerful API and SaaS scalability", no published price
Questions people ask
How do SaaS platforms add HS classification without building it?
They call a classification API from their own product and show the result inside their workflow. For an ERP or marketplace serving 500 importers, the work is mapping product fields to the API's input, displaying the code with its duty and reasons, adding a review and approval step, logging each result with its date, and rechecking codes when the HTS changes.
Can a SaaS platform show its users 10-digit HTS codes?
It depends on how the codes are used, so ask customs counsel. CBP has held that classifying goods for others beyond six digits is customs business (HQ H290535) and applied that to an AI tool on a platform whose users' goods would be entered (HQ H350722). In that ruling, general reference output kept apart from the broker portal, with a meaningfully implemented disclaimer, was permissible; six digits is not customs business.
What should a classification API return for an embedded use?
At minimum the code and its description; ideally the duty for the user's origin and date, the reasoning or confidence behind the code, and a timestamp you can tie to an HTS revision. For a TMS handling 3,000 SKUs a month, GingerControl's Classification + Tariff Calculation API returns a 10-digit HTS code with the U.S. duty layers in force when it is called.
How do I keep embedded HS codes current when the HTS changes?
Store the date and HTS revision with every code and recheck when a revision touches your users' chapters. By our count of the USITC's release list, the 2025 HTS had 32 revisions and the 2026 HTS had 21 by October 9, 2026. For a platform holding 50,000 user SKUs, the free USITC API's releaseList endpoint tells you when a new revision is posted.
How much does an embedded classification API cost?
Public prices read October 11, 2026: SimplyDuty's classification API is 0.10 pounds a call, and Zonos Classify starts at $500 a month after 1,000 free classifications. Avalara, Descartes and GingerControl quote enterprise API access. For a platform with 20,000 calls a month, ask each vendor for its per-call limit and volume terms in writing.
Do embedded classification APIs work for e-commerce marketplaces?
Yes, and the best fit depends on the job. For a marketplace calculating duty at checkout in many countries, Zonos and Avalara are built for that. For a platform whose sellers import into the United States and need the code with its U.S. duty layers, GingerControl's API returns both in one call, 120 items per call by default.
Should the platform or its users own the classification decision?
The user who imports the goods owns it: the importer of record files the classification using reasonable care under 19 U.S.C. 1484, and CBP said in HQ H350722 that a tool is not a person, so where customs business is involved a licensed broker must decide. For a platform serving 300 importers, design the product so users and their brokers review and approve codes.
What should a SaaS team ask a classification API vendor before signing?
Ask what each response contains (code, duty, reasons), the per-call limit, how keys are issued, which HTS revision a result used, how results are dated, and what the vendor says users may do with the codes. For a platform team planning 10,000 calls a month, also test 50 items your users' brokers already classified and compare.
Classifying SKUs one ruling at a time?
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
