Landed Cost API: HTS Plus the Full US Tariff Stack for D2C Brands After De Minimis
Chen Cui Co-Founder of GingerControl What changed: Distinguished June24 postal suspension from July24 entry procedure and October22 compliance date; verified91FR37801 DATES.
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 including the forced-labor duties since July 24, 2026, Section 232 on listed metal articles, and any other Chapter 99 entries. One request, one response, full landed cost ready to render in checkout or post to an order management system.
In this post
- Why does a D2C brand suddenly need a landed cost API in 2026?
- TL;DR
- What changed that broke every D2C duty spreadsheet
- What the full US duty stack actually looks like in October 2026
- What a production landed cost API actually has to do
- How a D2C brand actually wires a landed cost API into checkout
- Build vs buy for the D2C engineering team
- What a D2C engineering lead should ask any landed cost API vendor
- FAQ
- When DDP at checkout actually has to work
- References
Why does a D2C brand suddenly need a landed cost API in 2026?
Because the $800 de minimis exemption that every direct-to-consumer cross-border brand quietly relied on is gone: suspended for every country on August 29, 2025, and suspended indefinitely by CBP rules in 2026. Now every order entering the US needs a real duty calculation, and a Shopify Plus or headless brand needs it at checkout and at order confirmation, usually from a US import duty API, not from 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 on listed metal articles, the forced-labor Section 301 that replaced the 10% Section 122 surcharge on July 24, 2026, and any other applicable Chapter 99 entries. The checkout itself, quoting and collecting duty as DDP, is the job of checkout services such as Zonos and Avalara; GingerControl does not sell one. What GingerControl gives a D2C brand is GingerLite, the GingerControl app at $150 a month for 300 credits: the Classification Researcher for each SKU's 10-digit code with its reasoning, the Tariff Calculator for every US duty layer by entry date across 200+ origins, and Compliance Radar for new US trade notices that hit your codes.
The tariff calculation in ecommerce checkout guide places duty estimation after classification and before the customer sees the final order price.
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.
What changed 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. Four 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 24, 2026 | Section 122 surcharge at 10% takes effect for goods entered through July 23, 2026; the forced-labor Section 301 replaced it on July 24 (Proclamation 11012) | A new tariff layer applies to almost every country, and rate moves require real-time refresh |
| June 24, 2026 | CBP interim final rules suspend de minimis indefinitely, including postal, from June 24; the new postal informal-entry process starts July 24, 2026 (91 FR 37789, 91 FR 37801) | The suspension is no longer something to wait out |
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.
The de minimis repeal impact on small importers guide shows how per-parcel filing and processing change a small seller's cost model.
DDP checkout is now the standard for every serious cross-border D2C brand. DDP requires a real duty calculation per order, and that calculation is only as good as the HTS code and duty layers behind it.
What the full US duty stack actually looks like in October 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 | Proclamation 11021 | Listed steel, aluminum and copper articles, charged on full value since April 6, 2026 |
| Section 301 forced labor | 91 FR 47318 | 10% or 12.5% by origin since July 24, 2026 (12.5% for China), replacing the expired 10% Section 122 surcharge |
| Chapter 99 | HTSUS | Product-specific overlays |
A typical D2C order from China to the US in October 2026:
- A $50 cotton hoodie under HTS 6110.20.20: 16.5% MFN rate
- Plus 7.5% Section 301 (List 4A)
- Plus 12.5% forced-labor Section 301
- Total: $50 × (1 + 0.165 + 0.075 + 0.125) = $68.25 before shipping and fees
A spreadsheet that just stored "16.5% duty for HTS 6110.20.20" is now off by 20% 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, so classification is a real bottleneck. A useful API accepts a product description plus country of origin and returns the 10-digit HTS code. Where a code needs its reasoning on record, GingerControl's Classification Researcher takes one product at a time, 3 to 5 minutes with its full GRI reasoning report, and asks what your spec sheet leaves out before it decides.
2. Full tariff stack in the same response
The API has to return MFN, Section 301 including the forced-labor duties, Section 232 on listed metal articles, and other 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. Origin and metal detail per item
Duty depends on the country of origin, and for Section 232 metal articles on facts such as the metal's share of the article and where it was melted and poured. An API that takes only an HTS code and a destination cannot get those lines right.
4. Latency that fits checkout
A D2C checkout flow typically targets sub-second total latency, so no classification call belongs on the synchronous checkout path. Pre-classify and pre-calculate the tariff stack at SKU intake, cache the result, and refresh on tariff change events. The checkout then reads the cache.
5. Batch submission for catalog enrichment
A 1,200-SKU catalog onboarding should take a handful of batch calls, not 1,200 single ones.
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 asks, the question is "why this HTS code on this date," and a code with no reasoning behind it is hard to defend. GingerControl's Classification Researcher writes that reasoning, grounded in Section and Chapter Notes and CROSS rulings, one product per case.
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 call | Product master HTS plus full tariff stack |
| Catalog enrichment | Bulk catalog migration | Batch calls | 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 a new Chapter 99 rate | 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. On July 24, 2026 the 10% Section 122 surcharge ended and the forced-labor Section 301 began the same day. Brands that had reclassification jobs ready refreshed their duty cache in hours, not days.
Where GingerControl fits: checkout DDP is a job for a checkout service such as Zonos or Avalara. GingerLite, the GingerControl app at $150 a month for 300 credits, covers the duty facts behind it: the Classification Researcher for the 10-digit code and its reasoning, the Tariff Calculator for every US duty layer by entry date across 200+ origins, and Compliance Radar for new US trade notices that hit your codes.
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) | Depends on the vendor and your stack |
| Maintaining HTSUS schedule | Quarterly USITC ingestion plus regression testing | Vendor's responsibility |
| Section 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 | Vendor-stated, each on its own sample; test on yours |
| Reasoning audit trail for CBP | Has to be engineered from scratch | Varies by vendor; ask for a sample |
| Engineer headcount | 1 to 2 engineers for initial build, ongoing maintenance | One integration engineer; timing depends on your stack |
| 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. For checkout DDP, Zonos (with a guaranteed landed cost) and Avalara Cross-Border are built for it. For the classification and duty facts underneath, GingerLite covers a D2C brand's day-to-day work at $150 a month for 300 credits; GingerControl's Classification + Tariff Calculation API is for enterprise systems, after a call.
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 the current 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.
- 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 at the 10-digit level on a sample of my own catalog? A figure from the vendor's own test set is a starting point, not an answer.
- Do you decompose composite products into component-level codes? A wristwatch SKU that returns one code instead of its components will fail destination customs review.
- What record does your API leave to defend a classification under a CBP Focused Assessment? Ask for a sample. If the reasoning is not grounded in GRI plus Section Notes plus CROSS rulings, the merchant's broker will not sign off. GingerControl's Classification Researcher writes that report, one product per case.
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 duty stack in one call, so a checkout or order system can use it. A tariff calculator is a tool a person uses: you enter an HTS code, value and entry date and see the duty. GingerControl's Tariff Calculator, part of the GingerLite app, compares US import duty across 200+ origins with the base rate, each Section 232 and 301 line, MPF and HMF, for the entry date you enter.
Does GingerControl provide DDP checkout for Shopify Plus or headless commerce stacks?
No. Quoting and collecting duty at checkout is what checkout services such as Zonos and Avalara are built for. GingerControl covers the duty facts behind it: GingerLite's Classification Researcher for the 10-digit code with its reasoning, and the Tariff Calculator for every US duty layer, so the codes your checkout service uses are right. Whatever you use, pre-classify SKUs at intake, cache the duty keyed by SKU plus country of origin, and read the cache at checkout.
For a BigCommerce storefront, the BigCommerce tariff API integration guide places classification and duty calls in the catalog and checkout flow.
How does GingerControl handle Section 122, which ended on July 24, 2026?
The Tariff Calculator prices each entry by its entry date: Section 122 applies only to goods entered February 24 to July 23, 2026, at 10% under Proclamation 11012, and entries from July 24, 2026 get the forced-labor Section 301 of 10% or 12.5% by origin instead. For a brand reconciling orders across that date, that is the line to check.
Does the Tariff Calculator handle Section 232 for products with steel or aluminum?
Yes, for US imports. It detects Section 232 for goods of Chapters 72, 73, 74 and 76 from metal content and pour country, and shows each Section 232 line separately from the base rate and the Section 301 lines.
How accurate is GingerControl's classification on a real D2C catalog?
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, not an independent benchmark. Test any vendor on the same sample of your own catalog, because misclassified SKUs translate directly into chargebacks at checkout or destination customs holds.
Can GingerControl integrate with Shopify Plus, BigCommerce, or headless commerce platforms?
GingerControl has no pre-built commerce connectors. A D2C team uses the GingerLite app: classify each new SKU once in the Classification Researcher, price it in the Tariff Calculator, and load the code and duty into your PIM or checkout service. The Classification + Tariff Calculation API is for enterprise systems and starts with a call.
Does GingerControl handle split-code products like SKUs containing multiple components?
For goods dutied part by part, yes. For a wristwatch under HTS Chapter 91, the Tariff Calculator lists each component (movement, case, strap, battery) and the inputs it needs, rather than one line.
Is GingerControl a customs broker?
No. GingerControl builds software and works alongside licensed brokers; it does not file entries, act as importer of record, or give legal advice. The Classification Researcher follows the reasoning a broker uses, GRI analysis, Section and Chapter Notes and CROSS rulings, and our classifications are for general reference, educational, and planning purposes; before a code goes on an entry, your licensed customs broker reviews it.
When DDP at checkout actually has to work
If you run a D2C brand shipping into the US, put the checkout on a DDP service and the duty facts on GingerLite: the Classification Researcher for each new SKU's 10-digit code with its reasoning, the Tariff Calculator for every US duty layer by entry date across 200+ origins, and Compliance Radar for the notices that hit your codes. The GingerLite app is $150 a month for 300 credits, with top-ups if you run out. Open GingerLite →
For an enterprise system that needs classification and duty layers by API, the Classification + Tariff Calculation API starts with a call. Book a call →
References
- 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, E-Commerce FAQs
Data cited: 1.36 billion de minimis parcels in fiscal year 2024
Source: CBP E-commerce FAQs
Published: 2024 - 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 - USPS, Postal Bulletin 22682
Data cited: USPS 6-digit HS code mandate effective Sept 1, 2025
Source: USPS Postal Bulletin
Published: 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 - 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 - 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 - Federal Register, CBP interim final rules suspending de minimis
Data cited: indefinite de minimis suspension for non-postal and postal shipments effective June 24, 2026; new postal informal-entry process effective July 24 and specified 145.12 compliance provisions effective October 22, 2026
Source: 91 FR 37789, 91 FR 37801
Published: June 24, 2026 - Legal Information Institute, 19 U.S.C. § 1484
Data cited: Reasonable care framework, importer-of-record responsibility
Source: 19 U.S.C. 1484 - Federal Register, Proclamation 11021, Section 232 metals
Data cited: Section 232 metal duties charged on full customs value from April 6, 2026
Source: 91 FR 18201
Published: April 2026
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
