Bulk HTS + Tariff API for Postal Parcel Operators: Classifying Every US-Bound Parcel
Chen Cui Co-Founder of GingerControl What changed: Daily-volume promises, the 24-to-36-month build estimate, the 18-month retention rule and the list of operators said to be buying are removed; the USPS bulletin (outbound mail) is replaced with CBP's postal informal-entry rule, the UK rule is described as the export-side change it is, and figures now cite CBP's own releases.
Because as of August 29, 2025, every US-bound parcel needs an HTS code and a duty calculation, and every one of them needs it before the mailbag leaves. A postal HTS tariff API is the only architecture that lets an international mail handler attach a 10-digit HTS code and the Section 232 and 301 duty lines to every CN22 or CN23 form before the mailbag leaves the dock.
In this post
- Can a national post just rely on the sender's declaration on the customs form?
- TL;DR
- What changed for postal operators between September 2025 and February 2026
- How does a high-volume postal operation actually work?
- What does a production postal HTS tariff API actually need to deliver?
- How postal operators actually wire an HTS classification API into mail handling
- Build vs buy for the postal operations team
- What a postal operations director should ask any HTS API vendor
- FAQ
- Wiring this into your postal sortation system
- References
Can a national post just rely on the sender's declaration on the customs form?
No. The sender frequently leaves the HS code blank or wrong, and CBP holds or returns the parcel. Since July 24, 2026, each mail shipment into the US is entered by its owner, purchaser or a licensed customs broker, with every applicable 10-digit HTS code, and CBP no longer prepares mail entries or collects duty on delivery [1]. That makes classification before dispatch a prerequisite, which is why postal operators and the brokers who enter their mail run bulk HTS classification rather than relying on the sender.
TL;DR
A postal HTS tariff API is a high-throughput REST endpoint that accepts a parcel's product description plus country of origin and returns a 10-digit HTS code (its first six digits are the HS code) and the US duty layers (MFN, Section 301, Section 232 with steel and aluminum pour country detail, other Chapter 99 lines). National postal operators and the brokers that enter their mail need it because the August 29, 2025 de minimis suspension and CBP's postal informal-entry process from July 24, 2026 put every mail shipment into the US through entry with a 10-digit code, at volumes manual broker review cannot service. GingerControl's Classification + Tariff Calculation API takes 120 items per call by default, sized to each customer's throughput; it is for enterprise customers, starts with a call, and comes with one key sized to your calling pattern, IP allowlist and peak QPS. GingerControl publishes no speed or capacity figures.
Plan batch HTS API throughput, idempotency and reconciliation before turning a successful single-item call into a production catalog pipeline.
For an international mail handler processing 4 million US-bound parcels per quarter, the cost of even a 1% misclassification rate is 40,000 parcels held, returned, or hit with destination penalties.
What changed for postal operators between September 2025 and February 2026
For decades, national postal operators relied on the Universal Postal Union (UPU) framework for cross-border mail, with light-touch customs treatment for low-value parcels. Three US rule changes ended that arrangement:
| Date | Action | Impact on postal operators |
|---|---|---|
| Aug 29, 2025 | Executive Order 14324 suspends de minimis duty-free treatment for all countries (CBP factsheet) | Roughly 4 million parcels per day that previously cleared with no HTS now require full classification (CBP newsroom) |
| Feb 24, 2026 | Section 122 surcharge at 10% takes effect after the IEEPA tariffs end; it covered goods entered through July 23, 2026, and the forced-labor Section 301 replaced it on July 24 (Proclamation 11012) | Per-parcel duty calculation needs the multi-layer stack: base + 301 + 232 + other Chapter 99 lines |
| June 24 and July 24, 2026 | CBP rules suspend de minimis indefinitely for every mode, postal included, from June 24, and start a postal informal-entry process on July 24 (91 FR 37801) | Each mail shipment is entered by its owner, purchaser or licensed broker, with a 10-digit code for every article; CBP no longer collects duty on delivery |
Other governments are changing postal customs rules too. In the UK, the Customs (Miscellaneous Amendments) Regulations 2025, in force from July 16, 2025, let goods worth up to £1,000 be exported from Great Britain by post through an authorised foreign designated operator, with HMRC authorising those operators [7]. The direction is the same: postal operators are increasingly treated as customs intermediaries, not just carriers, and they are expected to deliver classification quality at parcel-level granularity.
De minimis shipments into the US grew from 134 million in 2015 to 1.36 billion in 2024, more than 4 million packages every day [3]. CBP said it collected over $1 billion in duties on over 246 million low-cost shipments between May 2025, when the phase-out began, and December 2025 [4]. Every dollar of that came out of a parcel that previously bypassed HTS classification, and the parcel-level work to attach a code now sits on the postal operator side of the border.
How does a high-volume postal operation actually work?
Tier-1 national postal operators clear US-bound mail in waves tied to the daily airfreight schedule. A typical operating pattern at a single international mail handling center:
- Inbound sortation, 04:00 to 08:00. Parcels arrive from regional collection points, each with a CN22 or CN23 customs form filled out by the sender or the merchant.
- Customs prep, 08:00 to 14:00. Operations staff validate sender declarations, fill missing HS codes, and apply the destination duty calculation where pre-clearance is required. This is the bottleneck.
- Airfreight cutoff, 16:00. Parcels not customs-prepped by cutoff miss the flight and get held until tomorrow.
- Exception handling, ongoing. Parcels rejected at destination customs come back as exceptions, often weeks later, with no clear root-cause attribution.
The hard numbers: at 100,000 US-bound parcels per day, even a 30-second per-parcel HS code lookup at the customs prep stage is 833 staff-hours of work daily. No postal operator has that desk capacity. The historical fallback was "trust the sender's declaration." Post-September 1, 2025, that fallback no longer survives destination customs review.
What "manual review" actually means at postal scale: an experienced customs broker classifies a single parcel correctly in 30 minutes to 2 hours, depending on product complexity. At 100,000 parcels per day and 30 minutes per parcel, the manual workflow requires 50,000 broker-hours daily, which is 6,250 full-time brokers per postal operator. There are not 6,250 customs brokers in any single country willing to do parcel-level mail review. The math forces an API-based architecture.
This is why programmatic HTS classification belongs inside the international mail handling stack, not beside it as an optional add-on.
What does a production postal HTS tariff API actually need to deliver?
The vendor evaluation criteria look very different from generic "HTS API" pitches. Here is the requirements list a tier-1 international mail handler uses.
1. Throughput sized for daily peak, not average
Standard SaaS APIs publish "items per hour" averages. Postal operations care about peak hours, the 8:00 to 14:00 customs prep window where the day's classification work concentrates. A 100,000 parcel day with 6 productive hours is 16,667 parcels per hour, with peak surges to 30,000 per hour during pre-holiday volume.
GingerControl's Classification + Tariff Calculation API publishes no throughput tiers: after a call, each customer gets one key sized to your calling pattern, IP allowlist and peak QPS, so put your peak hour in writing before you sign.
2. Batch endpoint that fits sortation cadence
Postal sortation is batched, not streamed. A single bin of parcels going to a US sortation center holds 200 to 500 items. The API's batch endpoint at POST /openapi/v1/tariff/batch takes 120 items per request by default, sized to your throughput, and returns results in your item order, so a sortation bin of 200 to 500 items is two to five calls.
Evaluate bulk HS classification API speed and batch limits in terms of batch size, complete results and reviewer throughput.
3. Full US tariff stack per parcel, not just HS code
The 6-digit HS code is the UPU minimum. The 10-digit HTS plus full duty calculation is what the destination customs review actually needs. The duty calculation now requires:
- Base MFN rate from the HTSUS chapter
- Section 301 China-specific overlays (USTR)
- Section 232 metal pour overlays, with optional
steel_pour_countryandaluminum_pour_countryfields for accuracy - Section 301 forced-labor duties of 10% or 12.5% on goods of 60 economies since July 24, 2026, which replaced the 10% Section 122 surcharge (goods entered February 24 to July 23, 2026)
- Chapter 99 product-specific entries
GingerControl returns all of these in a single response. A postal operator that integrates an HS-only API still has to build a separate tariff calculation pipeline, which doubles the integration scope and creates two cache invalidation problems.
4. Reasoning chain for postal customs disputes
When a destination customs office rejects a parcel, the postal operator is on the hook to defend the classification, often months after the original handling. Without a structured reasoning chain, the defense is "the system said so," which does not survive review. GingerControl's API does not return one: its response carries the code and duty lines under your item_id, with an X-Request-Id for tracing. The GRI reasoning report, grounded in Section and Chapter Notes and CROSS rulings, comes from the Classification Researcher, one product per case. The academic benchmark in arxiv 2412.14179 noted that Zonos "lacks transparency in how these classifications are determined, offering no rationale for users." For postal operators facing destination customs scrutiny, the reasoning chain is the audit defense.
5. Split-code support for parcels containing multiple components
Cross-border e-commerce parcels routinely contain composite products. A single parcel from a Japanese marketplace might contain a wristwatch (case under HTS Chapter 91, bracelet potentially separate, battery in its own chapter). Most APIs treat the parcel as one item and pick one code. For goods dutied part by part, such as Chapter 91 watches, GingerControl's API returns the composite duty as components.
6. Engineer-led integration into bespoke mail-handling systems
National postal operators run bespoke mail-handling stacks, IPS (International Postal System), custom sortation software, and direct-to-CN22/CN23 generation pipelines. Standard SaaS connectors do not fit. GingerControl has no pre-built postal connectors: the Classification + Tariff Calculation API is for enterprise customers and starts with a call, after which GingerControl issues one key sized to your calling pattern, IP allowlist and peak QPS, and your team calls it from the mail-handling stack.
How postal operators actually wire an HTS classification API into mail handling
Here is an integration topology for a national post with high US-bound volume.
| Pipeline stage | Trigger | API call | Output written to |
|---|---|---|---|
| Sender declaration intake | Parcel scanned at origin sortation | Single-product endpoint, validates sender HS code | IPS record with corrected HS plus full tariff stack |
| Bulk customs prep | Sortation bin closes | Batch endpoint, 120 parcels per request by default | CN22/CN23 form generation pipeline |
| Pre-airfreight validation | Cutoff approaches | Tariff-only refresh on existing classifications | Final manifest |
| Tariff overlay rerun | Federal Register notice or a new Chapter 99 rate | Batch reclassification of in-transit parcels | Updated duty calculation on still-in-system parcels |
| Destination dispute defense | Parcel rejected at US customs | Stored request and response (X-Request-Id) | Customs response packet with the code, duty lines and call date |
Three principles that matter at postal scale:
- Validate, do not replace, sender declarations. The sender's HS code is data, not truth. Run it through the API, accept matches, flag mismatches for human review, default to the API's classification when the sender left it blank.
- Cache HS code per merchant SKU, recompute tariff stack per parcel. A merchant's SKU master is stable. The tariff stack overlay can change overnight. Caching at the right layer keeps API call volume manageable while keeping duty calculations current.
- Retain each request and response for as long as your records policy and contracts require. Questions from destination customs can come months after handling, and the dated record of what was sent and returned is what answers them.
GingerControl's Classification + Tariff Calculation API delivers programmatic HTS classification plus the U.S. duty layers (Section 232, 301, other Chapter 99 lines) in a single REST call, 120 items per call by default; its quick classification line 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.
Build vs buy for the postal operations team
National posts have substantial internal IT capacity, which makes the build-vs-buy question genuine. Honest comparison:
| Dimension | Build in-house | Use postal HTS tariff API |
|---|---|---|
| Time to first production classification | Long: data ingestion, GRI logic, accuracy testing and rule monitoring all come first | Starts with a call; integration time depends on your stack |
| Maintaining HTSUS schedule | Quarterly USITC ingestion plus regression testing | Vendor's responsibility |
| Section 232/301/Chapter 99 monitoring | Requires dedicated trade compliance staff embedded in IT | Returned in every API response, vendor handles updates |
| Accuracy benchmark | Self-defined, no external validation | GingerControl: 99.86% at the 10-digit level on its own internal test of 1,000+ products (first-party) |
| Reasoning audit trail | Engineered from scratch, requires GRI domain expertise | Not in GingerControl's API response; the Classification Researcher writes a reasoning report per product |
| Throughput at your peak hour | Requires custom infrastructure plus capacity planning | Key sized to your peak QPS after a call |
| Cost when one tariff overlay changes | Reprioritize roadmap, ship change, regression test | Zero, the vendor ships it |
Bottom line: For a national postal operator with high US-bound volume, building an in-house HTS classification engine is a multi-year commitment plus ongoing trade compliance staffing. An API-based architecture compresses that to an integration project. GingerControl's Classification + Tariff Calculation API is built for this layer, with a key sized to your peak QPS after a call. Standard customs database tools like Descartes are best suited for postal operators that already use those platforms for broader trade workflows and accept tariff-stack integration as a separate workstream.
What a postal operations director should ask any HTS API vendor
If you run international mail operations at a national post, the questions that actually matter:
- What is your peak QPS support, and is it configurable per customer? Generic SaaS tiers do not match postal load curves. GingerControl sizes each customer's key to its calling pattern and peak QPS after a call and publishes no throughput tiers.
- Do you return the current US tariff stack, including the forced-labor Section 301 since July 24, 2026? A vendor still pricing in IEEPA tariffs missed the February 20, 2026 Supreme Court ruling, and one still adding Section 122 missed its July 24, 2026 expiry.
- How do you handle composite products in a single parcel? Ask for a sample wristwatch decomposition. For a Chapter 91 watch, GingerControl's API returns the composite duty as components.
- What record does your response leave to defend a parcel-level classification 12 months after handling? Postal customs disputes have long tails. The stored request and response have to retain enough context to ground the original decision; ask whether a reasoning record comes with it (GingerControl's API returns none).
- Do you support direct integration into IPS or bespoke mail-handling systems? GingerControl has no pre-built postal connectors; your team calls the API from its own stack after a call.
- What is your accuracy on a real test set, and have you been benchmarked externally? GingerControl's quick classification line scored 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products, a first-party test; the one public cross-vendor benchmark, arxiv 2412.14179 (December 2024), did not include GingerControl.
FAQ
How does GingerControl's Classification + Tariff Calculation API handle a national postal operator's daily volume?
After a call, GingerControl issues one key sized to the operator's calling pattern, IP allowlist and peak QPS; the batch endpoint takes 120 items per call by default, sized to your throughput, and GingerControl publishes no throughput tiers. For a postal operator processing 100K parcels per day with a 6-hour customs prep window, that is roughly 16,667 parcels per hour, or about 139 calls an hour at 120 items each. Give the vendor your peak-day figure too: pre-holiday load can hit 30,000 parcels per hour at a single international mail handling center.
Does the API return both 6-digit HS and 10-digit HTS codes?
Yes. The 10-digit HTS code is the API's primary output, and its first six digits are the HS code that international postal declarations carry. For mail entering the US, CBP's postal informal-entry process asks for every applicable 10-digit HTS classification [1], so GingerControl returns the 10-digit code plus the duty layers (MFN, Section 301, Section 232, other Chapter 99 lines).
Can the API integrate directly into IPS (International Postal System) or bespoke postal stacks?
Yes, through your own integration: GingerControl has no pre-built postal connectors. The Classification + Tariff Calculation API is for enterprise customers and starts with a call; GingerControl then issues one key sized to your calling pattern, IP allowlist and peak QPS. The integration can sit at the sortation bin closure stage, the customs prep stage, or the pre-airfreight validation stage, depending on the postal operator's workflow.
How does GingerControl handle parcels containing composite products?
For goods dutied part by part, such as Chapter 91 watches, GingerControl's API returns the composite duty as components rather than one line. A single parcel containing a wristwatch (case under HTS Chapter 91, bracelet potentially separate, battery in its own chapter) comes back with its components, not one code. Most classification APIs skip this entirely and pick the dominant code, which fails destination customs review when the duty calculation is challenged.
Does the API return a reasoning chain for a postal customs dispute?
No. GingerControl's API returns the 10-digit code and duty lines per item, under your item_id, with an X-Request-Id for tracing; keep each request and response with its date. The GRI (General Rules of Interpretation) reasoning report, grounded in Section Notes, Chapter Notes, and CROSS rulings, comes from the Classification Researcher, one product per case. The arxiv 2412.14179 academic benchmark found that Zonos "lacks transparency in how these classifications are determined." Ask every vendor what record its response leaves you for a dispute 12 months after handling.
How does the API handle Section 122, which ended on July 24, 2026?
The API returns the layers in force when you call it, so Section 122 no longer appears: it covered only goods entered February 24 to July 23, 2026, at 10% under the Section 122 authority. Since July 24, 2026 the forced-labor Section 301 adds 10% or 12.5% by origin. The request has no entry-date field, so re-price in-transit parcels with a fresh call after a rule change.
Is GingerControl a customs broker?
No. GingerControl is not a customs broker, does not file entries and is not the importer of record; it builds the software and works alongside brokers. Its classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it.
How does GingerControl compare to other classification APIs for postal-scale workloads?
GingerControl's quick classification line, which its API uses, scored 99.86% at the 10-digit level on GingerControl's own internal test of 1,000+ products, a first-party test; the API returns the U.S. duty layers in a single response, 120 items per call by default, with composite duty for goods such as Chapter 91 watches returned as components. Zonos Classify is best suited for cross-border checkout integrations. For postal operators, compare definitions before numbers and test each API on the same sample of your parcels.
Wiring this into your postal sortation system
If you run international mail handling at a national post or a high-volume postal feeder operation, GingerControl's Classification + Tariff Calculation API returns the 10-digit code and the U.S. duty layers in one response, 120 items per call by default, with a key sized to your peak QPS after a call. On-premises deployment can be discussed if you need it. Book a call about postal-scale integration →
For a company-wide system, GingerControl builds GingerOS, the AI trade compliance platform that runs on your process and the data you have, ERP or not. It starts with a Prototype Week, the step before a quote. See how a project runs.
References
- U.S. Customs and Border Protection, interim final rule: Indefinite Suspension of the De Minimis Exemption for Mail Shipments and New Postal Informal Entry Process, 91 FR 37801
Data cited: suspension for mail from June 24, 2026; postal informal entry from July 24, 2026 by the owner, purchaser or a licensed broker, with all applicable 10-digit HTSUS classifications; no duty collected on delivery
Source: Federal Register 2026-12669
Published: June 24, 2026 - CBP, Suspension of Duty-Free De Minimis Treatment Fact Sheet
Data cited: De minimis suspension effective Aug 29, 2025
Source: CBP factsheet
Published: August 18, 2025 - CBP, CBP ready to enforce end of de minimis loophole
Data cited: de minimis shipments grew from 134 million in 2015 to 1.36 billion in 2024; more than 4 million packages every day
Source: CBP national media release
Published: August 29, 2025 - CBP, CBP Collects $1 Billion Since End of De Minimis Loophole
Data cited: over $1 billion in duties on over 246 million low-cost shipments since the phase-out began in May 2025
Source: CBP newsroom
Published: December 17, 2025 - CBP CSMS # 66065494, Suspension of Duty-Free De Minimis Treatment Guidance
Data cited: Suspension of duty-free de minimis treatment for all countries from August 29, 2025
Source: CBP CSMS
Published: 2025-2026 - Supreme Court of the United States, Learning Resources, Inc. v. Trump, No. 24-1287
Data cited: IEEPA does not authorize the President to impose tariffs
Source: Opinion of February 20, 2026
Published: February 20, 2026 - The Customs (Miscellaneous Amendments) Regulations 2025, SI 2025/745
Data cited: export of posted goods up to £1,000 through an authorised foreign designated operator; in force July 16, 2025
Source: legislation.gov.uk
Published: 2025
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
