Landed Cost API: HTS Plus the Full US Tariff Stack in One Call, Built for D2C Brands After De Minimis

What does a landed cost API return?

A landed cost API takes a product description, a country of origin, and a declared value, and returns the 10-digit HTS code plus every duty layer that hits the parcel at the US border, base MFN rate, Section 301, Section 232 with steel and aluminum pour country detail, Section 122 reciprocal surcharge, and any Chapter 99 entries. One request, one response, full landed cost ready to render in checkout or post to an order management system.

Why does a D2C brand suddenly need a landed cost API in 2026?

Because the August 29, 2025 de minimis repeal killed the $800 duty-free exemption that every direct-to-consumer cross-border brand quietly relied on. Now every order entering the US needs a real duty calculation, and the only viable architecture for a Shopify Plus or headless brand is to call a US import duty API at checkout and at order-confirmation, not to maintain a duty rate spreadsheet.

TL;DR

A landed cost API returns the full US duty calculation for a single SKU plus country of origin in one REST call. For D2C brands shipping into the US, the calculation now requires the 10-digit HTS code, the MFN base rate, Section 301 China overlays, Section 232 metal pour overlays, the Section 122 10% reciprocal surcharge that took effect February 23, 2026, and any applicable Chapter 99 entries. Stitching these together from public data sources is engineering work that takes a quarter and breaks every time CBP issues a CSMS update. GingerControl OpenAPI ships this as one endpoint, with 99.89% accuracy on a 1000+ product customer-tested benchmark, batch processing for catalog enrichment, and engineer-led integration into headless commerce stacks.

For a Shopify Plus brand pushing 5,000 orders per day across 1,200 SKUs into the US, the difference between a real landed cost and a spreadsheet estimate is the difference between a profitable DDP checkout and a chargeback flood.

Last updated: May 2026

What changed in nine months that broke every D2C duty spreadsheet

For most of the last decade, D2C brands shipping into the US used the Section 321 de minimis exemption to keep $800-and-under orders duty-free. The brand absorbed any small-value duty on the rare large order, and the spreadsheet of "approximate duty rates by country" was good enough. Three regulatory shifts ended that arrangement.

Date	Action	What it did to the D2C duty stack
Aug 29, 2025	Executive Order 14324 suspends de minimis duty-free treatment for all countries (CBP factsheet)	Every order now needs a real duty calculation, not a $0 default
Sept 1, 2025	USPS mandates 6-digit HS code on every international commercial customs declaration (USPS Postal Bulletin)	The HS code is now part of the order data, not a back-office afterthought
Feb 23, 2026	CBP guidance implements Section 122 reciprocal tariff at 10%, statutory ceiling at 15% (CBP CSMS)	A new tariff layer applies to almost every country, and rate moves require real-time refresh

The post-repeal data tells the story. CBP collected over $1 billion in additional duties in the first months after de minimis ended (CBP newsroom), money that used to stay with merchants and customers. For a D2C brand, the choice is binary: charge the duty at checkout (DDP, delivered duty paid) and absorb the conversion impact, or ship DDU (delivered duty unpaid) and let the customer get a surprise duty bill at the door, which destroys repeat purchase rates.

DDP checkout is now the standard for every serious cross-border D2C brand. DDP requires a real duty calculation per order. A real duty calculation requires a working landed cost API.

What the full US duty stack actually looks like in May 2026

Sticker shock for engineering teams who haven't touched tariffs in a year:

Duty layer	Source authority	Typical D2C impact
MFN base rate	USITC HTSUS schedule	0% to 30%, varies by HTS code
Section 301	USTR	China-origin overlay, often 7.5% to 25%
Section 232	Executive Orders, CBP CSMS	Steel and aluminum content, requires pour country detail
Section 122	Holland & Knight	10% reciprocal surcharge, ceiling at 15%
Chapter 99	HTSUS	Product-specific overlays

A typical D2C order from China to the US in May 2026:

A $50 cotton hoodie under HTS 6105.20.20: 32% MFN rate
Plus 7.5% Section 301
Plus 10% Section 122
Total: $50 × (1 + 0.32 + 0.075 + 0.10) = $74.75 landed before shipping

A spreadsheet that just stored "32% duty for HTS 6105.20.20" is now off by 35% of the order value. Every miscalculation is either a chargeback (when the duty under-collected at checkout) or a lost customer (when the duty over-collected and they switched to a competitor with accurate quotes).

What a production landed cost API actually has to do

The vendor evaluation for a D2C engineering team is not "can it return a duty rate." Every basic API does that. The real evaluation is whether the API can hold up at checkout latency, ship a complete tariff stack, and stay current as overlays change.

1. HTS code from a product description, not a pre-classified SKU

A serious D2C brand has thousands of SKUs and adds new ones weekly. The classification work is a non-trivial bottleneck. GingerControl OpenAPI accepts a product description plus country of origin and returns the 10-digit HTS code, no pre-classification step required. For a brand onboarding a new product line, this turns a multi-week broker engagement into an API call.

2. Full tariff stack in the same response

The API has to return MFN, Section 301, Section 232 (with optional steel_pour_country and aluminum_pour_country for accuracy on metal-containing products), Section 122, and Chapter 99 entries in a single response. APIs that return only an HTS code or only an MFN rate force the engineering team to wire a second tariff calculation pipeline, which doubles the integration scope and creates two cache invalidation problems whenever rates move.

3. Country of origin support beyond ISO 3166-1

GingerControl OpenAPI accepts ISO 3166-1 country codes plus the EU and UK as accepted origin values. The Section 232 endpoints additionally accept steel_pour_country and aluminum_pour_country fields, because metal pour origin is what determines Section 232 applicability, not the final assembly country.

4. Latency that fits checkout

A D2C checkout flow typically targets sub-second total latency. Single-product API latency averages 36 seconds at GingerControl, which is too slow to put on the synchronous checkout critical path. The right pattern is to pre-classify and pre-calculate the tariff stack at SKU intake, cache the result, and refresh on tariff change events. The synchronous checkout call then reads the cache, with the API as the source of truth for cache writes.

5. Batch endpoint for catalog enrichment

For a 1,200 SKU catalog onboarding, the batch endpoint at POST /openapi/v1/tariff/batch processes up to 200 items per request in parallel, completing in 3 to 5 minutes. A 1,200 SKU catalog is 6 batch calls fully parallelizable, the entire catalog enriches in under 10 minutes.

6. Reasoning provenance for the merchant of record

The merchant is the importer of record on most cross-border D2C orders, which means the merchant carries reasonable care obligations under 19 U.S.C. § 1484. When CBP audits, the question is "why this HTS code on this date." GingerControl returns full reasoning grounded in GRI logic, Section Notes, Chapter Notes, and CROSS rulings, the same elements CBP evaluates when assessing reasonable care. The arxiv 2412.14179 academic benchmark found competing classification APIs "lack transparency in how classifications are determined, offering no rationale for users." For a D2C merchant facing audit risk, the reasoning chain is the durable defense.

How a D2C brand actually wires a landed cost API into checkout

Here is the integration topology that works in production for Shopify Plus and headless brands.

Pipeline stage	Trigger	API call	Output written to
SKU intake	New product enters PIM	Single-product or batch endpoint	Product master HTS plus full tariff stack
Catalog enrichment	Bulk catalog migration	Batch endpoint, 200 SKUs per request	Duty cache keyed by SKU and origin
Checkout DDP quote	Cart enters checkout	Cache read, no API call	Duty line item rendered to customer
Tariff overlay rerun	Federal Register notice or Section 122 rate change	Batch reclassification of active SKU base	Refreshed duty cache
Order confirmation	Customer pays	Cache read for final duty	Order record, financial reconciliation

Three principles for D2C engineering teams:

Never put the API on the synchronous checkout path. Pre-classify at SKU intake, cache the tariff stack, refresh asynchronously on overlay changes. Checkout reads the cache.
Cache by SKU + country of origin pair, not just SKU. A T-shirt manufactured in Vietnam and a T-shirt manufactured in China have different duty stacks even with identical descriptions.
Stage a reclassification job behind a config flag. Section 122 rates moved between 10% and 15% inside a single week in February 2026. Brands that had reclassification jobs ready refreshed their duty cache in hours, not days.

GingerControl OpenAPI delivers programmatic HTS classification plus full U.S. tariff stack (Section 122, 232, 301, Chapter 99) in a single REST call, scaling to 200K+ classifications per day on standard production tier with custom enterprise tiers up to 100K per hour, 99.89% accuracy on a 1000+ product customer benchmark.

Build vs buy for the D2C engineering team

Honest comparison for a Shopify Plus or headless brand engineering team:

Dimension	Build with public data sources	Use a landed cost API
Time to first production duty calculation	8 to 12 weeks (HTS schedule ingestion, tariff overlay tracking, accuracy validation)	1 day for a single endpoint integration
Maintaining HTSUS schedule	Quarterly USITC ingestion plus regression testing	Vendor's responsibility
Section 122/232/301/Chapter 99 monitoring	Federal Register subscription, manual extraction, ongoing	Returned in every API response, vendor handles updates
Accuracy on real catalogs	Self-defined, no external validation	99.89% on a 1000+ product customer-tested benchmark
Reasoning audit trail for CBP	Has to be engineered from scratch	Returned per call as structured JSON
Engineer headcount	1 to 2 engineers for initial build, ongoing maintenance	API integration is one engineer, one day
Cost when one tariff overlay changes	Reprioritize roadmap, ship change, validate	Zero, the vendor ships it

Bottom line: For D2C brands handling 500 to 5,000 cross-border orders per day, building a landed cost calculation in-house is an 8 to 12 week engineering commitment plus ongoing tariff monitoring. An API-based architecture compresses that to a one-day single-endpoint integration, with full tariff stack returned automatically. GingerControl OpenAPI is the production-grade option built for this layer. Zonos is best suited for brands that want a packaged DDP checkout app and accept its 90%+ accuracy and limited reasoning provenance per the arxiv 2412.14179 benchmark.

What a D2C engineering lead should ask any landed cost API vendor

If you run engineering at a cross-border D2C brand and you're evaluating vendors:

Do you return the 10-digit HTS code or only a 6-digit HS? The 10-digit HTS is what determines the actual MFN rate and Chapter 99 applicability. A 6-digit HS is not enough.
Do you return Section 122 in the tariff stack response, with the current rate? A vendor still pricing in IEEPA tariffs missed the February 20, 2026 Supreme Court ruling.
Can your API accept a free-text product description and return a classification? This is the difference between an API that needs a pre-classified SKU (broker engagement required) and one that classifies on the fly.
What is your accuracy on a real-world catalog, with external benchmark data? GingerControl achieves 99.89% on a 1000+ product customer-tested benchmark.
Do you decompose composite products into component-level codes? A wristwatch SKU that returns one code instead of three (case, bracelet, battery) will fail destination customs review.
Can your reasoning JSON defend a classification under a CBP Focused Assessment? Ask for a sample. If it's not grounded in GRI plus Section Notes plus CROSS rulings, the merchant's broker will not sign off.

FAQ

What is the difference between a landed cost API and a tariff calculator?

A landed cost API takes a product description plus country of origin and returns the full duty stack in one call. A tariff calculator typically requires a pre-classified HTS code as input, which means the engineering team or a broker has to classify every SKU first. GingerControl OpenAPI is a landed cost API, classification plus tariff calculation are returned together, no pre-classification step required.

Does the GingerControl landed cost API support DDP checkout for Shopify Plus or headless commerce stacks?

Yes. The recommended pattern is to pre-classify SKUs and pre-calculate the tariff stack at SKU intake using the batch endpoint, cache the result keyed by SKU plus country of origin, and read from cache at checkout. The synchronous checkout latency is then bound by your cache lookup, not by the API. For a 1,200 SKU catalog, the batch endpoint enriches the entire catalog in under 10 minutes (6 calls of 200 SKUs each, fully parallelizable).

How does GingerControl handle the Section 122 reciprocal tariff that took effect February 23, 2026?

The API returns Section 122 as a layer in the full tariff stack response. CBP guidance set the rate at 10% effective February 23, 2026, with a statutory ceiling at 15% under the Section 122 authority. When the rate moves, the API response updates automatically. D2C brands that staged a reclassification job behind a config flag refreshed their full duty cache in hours after the February 2026 rate movement.

Does the API return Section 232 metal overlays accurately for D2C products with steel or aluminum components?

Yes. The API accepts optional steel_pour_country and aluminum_pour_country fields per request. Section 232 applicability is determined by metal pour origin, not final assembly country, which means a product manufactured in Vietnam with steel poured in China still triggers Section 232 China overlays. Most generic tariff APIs miss this distinction and over- or under-calculate the duty.

How accurate is the API on a real D2C catalog?

GingerControl OpenAPI achieves 99.89% classification accuracy on a 1000+ product customer-tested benchmark. The arxiv 2412.14179 academic benchmark found competing classification models including Zonos in the 90%+ range with no reasoning provenance. For a 1,200 SKU catalog, the difference between 99.89% and 90% is roughly 119 misclassified SKUs, which translates directly into chargebacks at checkout or destination customs holds.

Can the GingerControl landed cost API integrate with Shopify Plus, BigCommerce, or headless commerce platforms?

Yes. The API is REST-based and can be called from any commerce platform that supports custom backend integrations. For Shopify Plus, the typical integration sits in a backend service that enriches the product master at SKU intake. For headless commerce stacks (Commercetools, Saleor, Medusa, custom), the API integrates directly into the catalog enrichment pipeline. GingerControl ships a white-glove API Integration Service for non-standard platforms with engineer-led integration in a one-week typical onboarding.

Does the API support split-code products like SKUs containing multiple components?

Yes. GingerControl OpenAPI automatically decomposes composite products into component-level HTS codes, each with independent tariff calculation. A wristwatch under HTS Chapter 91 returns separate codes for the case, the bracelet, and the battery. Most classification APIs treat the SKU as one unit and pick the dominant code, which fails destination customs review and creates DDP miscollection at checkout.

Is GingerControl a customs broker?

No. GingerControl is an HTS Classification Researcher. It follows the same reasoning process a licensed customs broker uses, GRI analysis, Section/Chapter Note review, and CROSS ruling research, but the final classification decision benefits from professional judgment. GingerControl produces audit-ready documentation that supports the classification decision, it does not provide legal advice or replace licensed customs expertise. Per CBP Ruling HQ H290535, providing HTS classifications beyond 6 digits for specific goods intended for importation constitutes "customs business" and requires a licensed broker.

When DDP at checkout actually has to work

If you run engineering at a D2C brand shipping cross-border into the US and your DDP checkout now needs accurate landed cost per order, GingerControl OpenAPI returns the 10-digit HTS code plus the full US tariff stack in one call. 99.89% accuracy, batch endpoint for catalog enrichment, engineer-led integration into headless commerce stacks. Talk to our team about D2C integration →

GingerControl is not just a tool, we work with cross-border D2C brands on integration design, catalog enrichment workflows, and reclassification automation when tariff overlays change.

References

[REF 1] 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

[REF 2] CBP — E-Commerce FAQs Data cited: 1.36 billion de minimis parcels in fiscal year 2024 Source: CBP E-commerce FAQs Published: 2024

[REF 3] CBP — CBP Collects $1 Billion Since End of De Minimis Loophole Data cited: $1B+ in additional duties collected post-repeal Source: CBP newsroom Published: 2025

[REF 4] USPS — Postal Bulletin 22682 Data cited: USPS 6-digit HS code mandate effective Sept 1, 2025 Source: USPS Postal Bulletin Published: 2025

[REF 5] CBP CSMS # 66065494 — Suspension of Duty-Free De Minimis Treatment Guidance Data cited: Section 122 reciprocal tariff implementation guidance Source: CBP CSMS Published: 2025-2026

[REF 6] Holland & Knight — Supreme Court Strikes Down IEEPA Tariffs Data cited: Feb 20, 2026 ruling, Section 122 replacement at 10% with 15% statutory cap Source: Holland & Knight insights Published: February 2026

[REF 7] Covington & Burling — IEEPA Tariffs Terminated, Replacement Section 122 Tariffs Take Effect Data cited: Section 122 statutory framework, 15% ceiling, 150-day duration limit Source: Covington & Burling Published: February 2026

[REF 8] arxiv 2412.14179 — Benchmarking Harmonized Tariff Schedule Classification Models Data cited: Independent benchmark of HTS classification API accuracy and reasoning transparency Source: arxiv 2412.14179 Published: December 2024

[REF 9] LegalClarity — 19 U.S.C. § 1484 Importer Responsibilities Data cited: Reasonable care framework, importer-of-record responsibility Source: LegalClarity 19 USC 1484 Published: 2025