Who Uses an HTS Classification API? 9 Industries Compared

The cross-border shipping API integration guide separates classification and duty data from the carrier's booking and label functions.

Why are these companies replacing manual HTS lookup with an API?

Because the volume outgrew people. De minimis was suspended for every country on August 29, 2025 and suspended indefinitely by CBP rules from June 24, 2026, so every U.S.-bound parcel needs an HTS code and owes duty ^[1]. Researching one product by hand against today's duty stack takes 30 minutes to 2 hours, by GingerControl's estimate. At catalog scale that only works in software.

---

---

Why does this market exist now, not five years ago?

Three changes moved HTS codes from the broker's desk into software:

The duty stack also moved. A 10% Section 122 surcharge applied to goods entered from February 24 to July 23, 2026, after the Supreme Court held that IEEPA does not authorize tariffs ^[2]; since July 24, 2026 the forced-labor Section 301 applies at 10% or 12.5% depending on the economy ^[3]. One SKU's duty now involves the base rate, Section 301 layers, Section 232 metals and other Chapter 99 lines.

Which 9 industries use HTS classification APIs?

Each row is a kind of business that needs codes at volume; the companies named are examples of the type, not GingerControl customers.

Bottom line: For software that has to put a code on every SKU or parcel bound for the U.S., an HTS classification API is a buy-versus-build decision, and building means owning GRI logic, rulings research and every rule change yourself. GingerControl's Classification + Tariff Calculation API covers U.S. imports. For checkout duty across destinations, checkout providers are the better fit.

---

Use case 1: cross-border 3PLs coding each merchant's catalog

A 3PL releases outbound waves on a fixed schedule, and before a wave can go, each parcel needs a commercial invoice with a declared value and an HTS code. The code belongs to the SKU, not the parcel, so the work is to classify each merchant's catalog at onboarding and look it up afterwards. At 30 minutes to 2 hours of research per product by hand, 5,000 SKUs is 2,500 to 10,000 hours. Nobody staffs that.

With GingerControl's batch endpoint:

POST /openapi/v1/tariff/batch
X-Api-Key: <key>
{
  "items": [
    { "item_id": "SKU-001", "description": "...", "country_of_origin": "CN" },
    ...up to 120 items by default
  ]
}

5,000 SKUs is 42 calls of 120, run within the quota set for your key. Results come back in the order you sent them, each tagged with your item_id, with a summary of how many succeeded and failed. GingerControl publishes no completion-time figure, so plan the onboarding schedule from timings on your own traffic. The full 3PL pattern is in the 3PL HTS classification API guide.

Use case 2: postal operators coding every U.S.-bound commercial item

Since July 24, 2026, each mail shipment into the U.S. is entered by its owner, purchaser or a licensed customs broker, with a 10-digit code for every article, and CBP no longer prepares mail entries or collects duty on delivery ^[1]. For a post or broker handling U.S.-bound mail at volume, that is a code per item before the shipment is entered:

1. The item enters sortation and its customs form is read.
2. The description goes to the API, which returns a 10-digit code (its first six digits are the HS code).
3. The code goes into the entry data for the shipment.
4. The item continues to its outbound flight.

The batch endpoint fits sortation bins: 120 items per call by default, with the key sized to the operator's traffic when it is issued. More detail is in bulk HTS and tariff API for postal operators.

Use case 3: customs filing software and broker tech stacks

Filing software and in-house broker tools need a check before an entry is prepared: does the code on the invoice match the product, and what U.S. duty layers come with it for this origin? A single-item call returns the 10-digit code and the layers in force, which the software sets beside the code on the invoice. Where they differ, a broker looks.

The broker decides. Under U.S. law customs business, which includes classifying goods being entered, takes a broker's license ^[4]. GingerControl's classifications are for general reference, educational and planning purposes; before a code goes on an entry, a licensed broker reviews it. For the broker's own research on a hard product, the Classification Researcher in the GingerLite app writes the GRI reasoning, one product at a time.

What about marketplaces and DDP checkout? A checkout needs duty and import tax for every destination, low-value thresholds and often a guarantee, quoted before the customer pays. That is the job of checkout providers such as Zonos and Avalara, not of a U.S. tariff API. The architecture is in real-time DDP at checkout.

For a BigCommerce storefront, the BigCommerce tariff API integration guide places classification and duty calls in the catalog and checkout flow.

Use case 4: ERP, OMS and PIM enrichment

An integrator builds a workflow that fires when a new material enters the product master and fills in the HTS code and origin before the material reaches purchasing and sales. A single API call fits inside that workflow with room for validation and write-back; GingerControl publishes no response times, so measure them on your own SKUs. Patterns that hold up in production:

• Reconcile by item_id: the batch endpoint requires a unique item_id per item, which doubles as your key.
• Retry 429s on Retry-After, not blindly.
• Cache by description, origin and the steel and aluminum pour countries, the inputs that decide the answer.
• Log X-Request-Id with every call so support can trace it.

For a company that wants classification, duty and rule checks fitted to its own process rather than an API to wire up, GingerControl builds GingerOS, which runs on your process and the data you have, ERP or not.

Use case 5: rechecking a catalog after a rule change

When the Supreme Court ruled on February 20, 2026 and a Section 122 surcharge took effect four days later, every importer with a large catalog had to work out which SKUs' duty changed. With an API, the approach is to rerun the catalog in batches of 120, within your quota, compare the duty layers with the previous run and pass only the changed SKUs to the trade desk. Section 232 status matters for the comparison: Section 122 did not stack on Section 232 duties, and Section 232 articles are exempt from the forced-labor Section 301 ^[3]. The optional steel_pour_country and aluminum_pour_country inputs carry the facts Section 232 needs.

Because the API returns the layers in force on the day of the call, run it after the effective date, or use GingerControl's Tariff Calculator, which takes an entry date.

---

What separates a usable HTS API from the rest?

Buy or build?

Building makes sense if you classify one or two narrow product groups, your volume is low and steady, and a licensed broker on staff checks the results.

Buying makes sense if you handle many chapters or composite goods, your volume is high or growing, the duty stack has to stay current through rule changes, and you need a consistent process to show reasonable care under 19 U.S.C. 1484.

FAQ

Which industries are the biggest users of HTS classification APIs?

Likely cross-border 3PLs and postal operators, by number of items coded, because every merchant catalog and every commercial item bound for the U.S. needs a code. Customs filing software, ERP integrators and sourcing platforms call APIs for checks and enrichment. Marketplaces need duty at checkout, which checkout providers such as Zonos and Avalara handle.

How is an HTS classification API different from a classification app?

An app is what an analyst uses to research one product, with questions and a written reasoning report. An API is what software calls for many products with no one at a screen. GingerControl has both: the Classification Researcher in the GingerLite app, which writes the GRI reasoning, and the Classification + Tariff Calculation API, which returns codes and U.S. duty layers without a reasoning report.

Can a small ecommerce brand use an HTS classification API directly?

Most should not need to. A brand usually gets codes through its 3PL or sets them itself: GingerControl's GingerLite app is $150 a month for 300 credits and gives each product a 10-digit code with its reasoning. The API is for enterprise systems, 3PLs and postal operators and starts with a call.

What about latency and throughput at peak load?

GingerControl publishes no latency or throughput figures. The batch endpoint takes 120 items per call by default, and each key is sized to the customer's traffic when it is issued. Caching results by SKU, origin and pour countries keeps repeat lookups off the API.

How does GingerControl handle Section 301 and Section 232 layers?

The response returns each duty layer in force on the day of the call, each Chapter 99 group as its own list in the tariffs object; Section 122 ended with goods entered on July 23, 2026. Section 232 metal duty uses the optional steel and aluminum pour-country inputs, which can differ from the finished product's origin.

What about audit trail and reasonable care?

The API returns the code and its duty layers; its manual documents no reasoning trace. The written GRI reasoning that supports reasonable care comes from GingerControl's Classification Researcher, one product at a time, or from GingerOS, which records the reasoning behind each approved classification. Before a code goes on an entry, a licensed customs broker reviews it.

How does API integration start?

With a call. GingerControl then issues one key sized to your calling pattern, IP allowlist and peak QPS; there are no public test keys. The contract is on the API reference page.

---

Where to go next

• 3PLs: 3PL HTS classification API for bulk imports
• Postal operators: bulk HTS and tariff API for postal operators
• Checkout teams: real-time DDP at checkout

If your team is evaluating, book a call. For a company-wide system rather than an API, GingerControl builds GingerOS, the AI trade compliance platform that runs on your process and the data you have, ERP or not. See how a project runs.

---

References

1. U.S. Customs and Border Protection, interim final rule on de minimis, 91 FR 37789
   Data cited: de minimis suspended for every country since August 29, 2025; suspended indefinitely for every mode, postal included, from June 24, 2026; postal informal-entry process from July 24, 2026: each mail shipment entered by its owner, purchaser or licensed broker with every 10-digit code; no duty collected on delivery (91 FR 37801)
   Source: Federal Register 2026-12670 and Federal Register 2026-12669
   Published: June 24, 2026
2. Proclamation 11012, Section 122 surcharge, 91 FR 9339
   Data cited: 10% on goods entered from February 24, 2026 through July 23, 2026
   Source: Federal Register 2026-03824
   Published: February 25, 2026
3. USTR, Notice of actions in the Section 301 investigations, 91 FR 47318
   Data cited: forced-labor Section 301 from July 24, 2026, 10% or 12.5% by economy; Section 232 articles exempt (9903.05.90)
   Source: Federal Register 2026-15181
   Published: July 28, 2026
4. 19 U.S.C. 1641, Customs brokers
   Data cited: customs business, including classification of goods being entered, requires a license
   Source: 19 U.S.C. 1641, Legal Information Institute