Automated Global HS Classification: How Do You Classify Across 100+ Countries?

What changed: 99.86% is stated at the 10-digit level, and the unsourced 70-80% figure for text-matching APIs is removed. Description shortened to one sentence under 160 characters.

The short answer

Automated global HS classification is the programmatic assignment of Harmonized System codes to products regardless of origin country, using a single API that accepts any ISO 3166-1 alpha-2 country code and returns a code whose first six digits are the international Harmonized System code. GingerControl's Classification + Tariff Calculation API returns a 10-digit U.S. HTS code with the U.S. duty layers in force when you call it: Section 301, Section 232 metals and other Chapter 99 lines. The quick classification line it uses scored 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products, a first-party test, not an independent benchmark.

Next step:Try the Classification Researcher on one product

In this post
  1. Can one API handle HS classification for every origin country?
  2. Why Global HS Classification Is Harder Than Single-Country HS Classification
  3. How GingerControl's Automated Global HS Classification API Handles Origin
  4. Global Batch Classification: 120 Items Per Call by Default, Multi-Origin
  5. Why 6-Digit Accuracy Matters for Global Classification
  6. Global HS Classification Performance
  7. What Automated Global HS Classification Solves for Each Customer Type
  8. Frequently Asked Questions
  9. Start Automating Global HS Classification
  10. References

The automated tariff code assignment for product catalogs workflow connects structured product facts to a repeatable classification and review process.

Can one API handle HS classification for every origin country?

Yes, because the 6-digit HS code is internationally harmonized. The World Customs Organization's Harmonized System is used by 200+ economies and covers 98% of world trade. The destination country adds national digits (the U.S. adds digits 7-10 for HTSUS). GingerControl's automated global HS classification API accepts any ISO 3166-1 alpha-2 origin code, including EU and UK aliases, and returns a 10-digit HTS code, whose first six digits are the international HS code, plus the U.S. duty layers for the origin in a single call.


TL;DR

Global trade is not single-country trade. A typical 3PL or ecommerce platform routes products from 30-80 origin countries through a single destination workflow. Manual HS classification cannot scale across that variety, and most automated HS classification APIs either hardcode origin assumptions or skip origin-specific tariff layers entirely. GingerControl's Classification + Tariff Calculation API accepts any ISO 3166-1 alpha-2 country code, supports EU and UK aliases, handles steel pour country and aluminum pour country fields for Section 232 country-of-melt rules, and returns the U.S. duty layers for every origin. The batch endpoint takes 120 items per call by default, sized to your throughput. CBP collected $216.7 billion in duties, taxes, and fees in FY 2025, with Section 301 layers concentrated on specific country pairs, which is exactly why origin-aware classification matters.


Why Global HS Classification Is Harder Than Single-Country HS Classification

The international 6-digit HS code is the same regardless of origin. What changes is the tariff stack applied to it.

A cotton T-shirt classified under HS 6109.10 carries the same 6-digit code whether it ships from Germany, Vietnam, China, or Bangladesh. But the duty calculation diverges immediately:

Origin MFN Section 301 (China lists) Forced-labor Section 301 (since July 24, 2026) Total layered rate
Germany 16.5% None None (the EU's combined cap of 10% is below the 16.5% MFN) 16.5%
Vietnam 16.5% None 12.5% 29%
China 16.5% 7.5% (List 4A) 12.5% 36.5%
Bangladesh 16.5% None 10% 26.5%

That table is simplified. Real global classification has to handle Section 232 (steel and aluminum, with country-of-melt rules), Section 301 (List 1-4 country-specific exclusions, and since July 24, 2026 a forced-labor Section 301 rate per economy), and Chapter 99 overlays that change quarterly.

A truly automated global HS classification API has to do all of this in a single call, for any origin country, without the integrating team having to maintain a tariff database themselves.

How GingerControl's Automated Global HS Classification API Handles Origin

The API accepts any ISO 3166-1 alpha-2 country code in the country_of_origin field. Two practical aliases are supported because they show up constantly in real product data:

  • EU is accepted and processed as the European Union origin
  • UK is accepted for the United Kingdom, and GB is processed as UK

For products that trigger Section 232 country-of-melt rules (steel and aluminum derivatives), the optional extra object accepts steel_pour_country and aluminum_pour_country fields. These follow the same ISO 3166-1 alpha-2 format as the primary country of origin.

{
  "description": "Cotton knit short sleeve T-shirt",
  "country_of_origin": "DE",
  "extra": {
    "steel_pour_country": "IT",
    "aluminum_pour_country": "FR"
  }
}

The response includes a 10-digit HTS code, whose first six digits are the international HS code, plus the U.S. duty layers in force for that origin on the day you call (shortened example):

{
  "hts_code": "6109.10.0012",
  "tariffs": {
    "general_rate": "16.5%",
    "special_rate": "Free",
    "Section 301": [],
    "Section 232 - Metals": []
  }
}

Global Batch Classification: 120 Items Per Call by Default, Multi-Origin

For 3PLs, marketplaces, and ecommerce platforms managing global product catalogs, batch classification across multiple origins is the only workable approach.

For a storefront catalog, the HS code API for ecommerce catalogs guide covers the product facts and integration points classification needs.

POST /openapi/v1/tariff/batch

{
  "items": [
    {
      "item_id": "SKU-DE-001",
      "description": "Cotton knit short sleeve T-shirt",
      "country_of_origin": "DE",
      "extra": { "steel_pour_country": "IT" }
    },
    {
      "item_id": "SKU-FR-002",
      "description": "Cotton crew neck T-shirt",
      "country_of_origin": "FR",
      "extra": {}
    }
  ]
}

Each item carries its own country_of_origin, so a single batch can contain products from 50 different origin countries and the API will return the correct tariff stack for each. The batch endpoint takes up to 120 items per call by default, sized to your throughput.

The response includes a per-item status field (ok or failed), so partial failures in a batch do not block the entire call. The summary object reports total, succeeded, and failed counts for reconciliation.

Why 6-Digit Accuracy Matters for Global Classification

The 6-digit HS code is the international common ground. It is also where most automated classification APIs fail, because GRI 3 (essential character analysis) operates at the 6-digit level and most APIs skip it.

The quick classification line GingerControl's API uses scored 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products, a first-party test, not an independent benchmark. The accuracy comes from two architectural choices:

Encoded GRI 1-6 logic. The General Rules of Interpretation are the legal framework that governs HS classification worldwide. They are not optional, and they are not specific to any one country. GingerControl applies GRI 1 through 6 as structured rules on every classification.

Section and Chapter Note enforcement. Section Notes and Chapter Notes are the legal exclusions and inclusions that determine which heading actually applies. They override text similarity. GingerControl applies them deterministically rather than as model hints.

Global HS Classification Performance

GingerControl publishes no latency or throughput figures for the API. The batch endpoint takes 120 items per call by default, and each customer's key is sized to its own throughput after a call.

What Automated Global HS Classification Solves for Each Customer Type

Customer type Pain point What the API delivers
Cross-border ecommerce Hundreds of origins, thousands of SKUs, checkout latency budget Batch classification ahead of catalog publishing; per-origin tariff stack for landed cost display
Global 3PL 50-200 client catalogs, weekly catalog updates Automated reclassification on catalog changes; per-shipment origin handling
International marketplace Seller-uploaded products from any origin Real-time classification on seller onboarding; per-origin duty disclosure
Multi-country importer Same product shipped from multiple sources Single API call per origin, the same classification logic for every source
Customs brokerage Manual classification across multiple importer clients API-driven first pass, broker reviews the codes before filing

Frequently Asked Questions

Does automated global HS classification work for export as well as import?

Yes at the 6-digit level. The international 6-digit HS code is the same whether the product is being exported or imported, which is the level the WCO Harmonized System harmonizes. GingerControl's API returns a 10-digit U.S. HTS code, whose first six digits are that international code, plus the U.S. import duty layers. For exports from the U.S., the same 6-digit code applies, and the destination country's tariff schedule determines the duty.

How does the API handle Section 232 country-of-melt rules?

Section 232 metals duties on steel and aluminum derivatives are often determined by the country where the steel was poured or the aluminum was smelted, not the country where the final product was manufactured. The API accepts steel_pour_country and aluminum_pour_country fields in the optional extra object, both following ISO 3166-1 alpha-2 format, and applies Section 232 entries to the response based on those values.

Can I send a batch with products from 50 different origin countries?

Yes. Each item in a batch request carries its own country_of_origin, so a single batch call can mix any combination of origins. The API processes each item independently, applies the correct tariff stack per origin, and returns per-item results with status: ok or status: failed. The batch takes up to 120 items per call by default.

What countries does the automated global HS classification API support?

The API accepts any ISO 3166-1 alpha-2 country code, plus the practical aliases EU for European Union and UK for United Kingdom (GB is processed as UK). The first six digits of the code returned apply internationally because they follow the WCO Harmonized System used by 200+ economies. The U.S. duty layers (Section 301, Section 232 metals, other Chapter 99 lines) are applied for U.S. import classification.

How does this differ from a U.S.-only HTS classification API?

A U.S.-only HTS classification API typically optimizes for U.S.-origin-aware tariff calculation but treats non-U.S. origins as edge cases. An automated global HS classification API treats every origin as a first-class input and applies the correct tariff layers based on that origin. GingerControl's API supports every ISO 3166-1 alpha-2 code as a first-class origin and applies Section 301 lines, the forced-labor Section 301 included, and Section 232 country-of-melt rules per origin.

How accurate is global HS classification at scale?

The quick classification line GingerControl's API uses scored 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products, a first-party test, not an independent benchmark. The architecture is the same per product: deterministic GRI logic and Section and Chapter Note enforcement.

How do I integrate the global HS classification API with my product catalog?

The API is for enterprise customers and starts with a call; after it, GingerControl issues one key sized to your calling pattern, IP allowlist and peak QPS. Book a call. Typical integration involves a one-time catalog backfill via the batch endpoint, then incremental classification on new SKU additions via the single-product endpoint or smaller batch calls.


Start Automating Global HS Classification

If you operate across multiple origin countries, the question is not "should we automate HS classification?" It is "which API handles every origin as a first-class input, calculates the U.S. duty layers, and keeps up with the volume our catalog actually moves?"

See the GingerControl API at gingercontrol.com/products/openapi. It is for enterprise systems, starts with a call and has no published price.

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. Book a call about embedding global HS classification into your production workflow.


References

  1. World Customs Organization, Harmonized System
    Data cited: 200+ economies use HS, 98% of world trade coverage
    Source: WCO Harmonized System
  2. U.S. Customs and Border Protection, Trade Statistics
    Data cited: $216.7 billion in duties, taxes, and fees collected in FY 2025
    Source: CBP Trade Statistics
    Published: 2025
  3. ISO 3166-1 alpha-2 Country Codes
    Data cited: International standard for country code representation
    Source: ISO 3166 Country Codes
  4. CBP Section 232 Investigations
    Data cited: Country-of-melt rules for steel and aluminum derivative products
    Source: CBP Section 232
  5. CBP Section 301 Trade Remedies
    Data cited: Country-specific tariff exclusions and modifications
    Source: CBP Section 301
Your next step

Classifying SKUs one ruling at a time?

Hand this to GingerOS.

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

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