Duty Tax API Pricing Compared: GingerControl, Zonos, Avalara
I compare duty and tax API pricing from GingerControl, Zonos, Avalara, and Easyship to help you model unit economics post-de-minimis at catalog scale.
Co-Founder of GingerControl, Building scalable AI and automated workflows for trade compliance teams.
Connect with me on LinkedIn! I want to help you :)How does duty and tax API pricing actually work in 2026?
Duty and tax API pricing falls into three models in 2026: per-order pricing (Zonos charges $2 plus 10% of duties and taxes per guaranteed landed cost order), pay-as-you-go per-request (Easyship and similar), and request-based tier pricing (GingerControl and most enterprise platforms). The right model depends on whether your unit economics are per-checkout, per-shipment, or per-classification at catalog scale.
Why does duty tax API pricing matter more after February 2026?
The February 28, 2026 Section 321 suspension eliminated de minimis treatment globally, forcing every cross-border parcel through formal HTS classification. The Congressional Research Service projects U.S. parcel volume shifting from 800-900 million annual de minimis packages down to 200-300 million, which means the cost of a duty calculation on every single shipment is now part of every ecommerce, 3PL, and marketplace P&L.
TL;DR
Three pricing models dominate the duty and tax API market: per-order (Zonos: $2 + 10% of duties and taxes), pay-as-you-go (Easyship: pay-per-request published), and request-based with volume tiers (GingerControl, Avalara: scaled pricing for 1K to 100K+ daily requests). For a checkout collecting guaranteed landed cost, per-order makes sense. For a 3PL or marketplace running bulk catalog classification or recalculating duty after every Section 232 update, request-based pricing is the only model that does not destroy unit economics. GingerControl is built for that second use case.
Last updated: May 2026
How each pricing model actually works
Zonos: per-order plus percentage of duty
Per Zonos's published pricing, Zonos charges $2 per guaranteed landed cost order plus 10% of duties, taxes, and other import fees. For an ecommerce checkout where the customer absorbs the duty as a customer-paid fee, the model is reasonable: the merchant pays nothing out of pocket, the customer pays the per-order fee as part of the duty line item, and Zonos guarantees the duty amount against under-collection. The model breaks down when the merchant pays the duty itself (DDP business models) or when the same product is classified or recalculated repeatedly.
Avalara Cross-Border: usage-based, quoted
Avalara uses a usage-based pricing model that is not publicly listed. Procurement gets a quote based on transaction volume, integration complexity, and whether the buyer is bundling AvaTax (U.S. sales tax) with the cross-border module. The model favors enterprise buyers already standardized on Avalara for tax. For finance teams modeling unit economics on a 100K-SKU catalog re-audit, the lack of public pricing makes the cost case hard to build before procurement engagement.
Easyship: pay-as-you-go per request
Easyship uses transparent pay-as-you-go pricing for its API tier, attractive for SMB ecommerce volume. The cost per request is published, which lets brands and small 3PLs model unit economics directly. The trade-off is that pay-as-you-go pricing escalates faster than tiered pricing once volume crosses a few thousand requests per day, which is where catalog-scale operations begin.
GingerControl: request-based with volume tiers
GingerControl uses request-based pricing with volume tiers, scaling from 1,000 to 100,000+ requests per day. Pricing is structured around the unit economics of catalog-scale operations: bulk classification, daily recalculation after rate changes, and per-order classification for checkouts and 3PL workflows. Each request returns full GRI-driven HTS classification, CROSS ruling research, and itemized U.S. tariff stack (Section 232, 301, Chapter 99, Section 122).
GingerControl is AI global trade compliance infrastructure that helps importers, exporters, and customs brokers classify products, simulate tariff costs, and track policy changes.
Pricing model comparison
| Pricing dimension | GingerControl | Zonos | Avalara Cross-Border | Easyship |
|---|---|---|---|---|
| Pricing model | Request-based with volume tiers | $2 + 10% of duty per order | Quoted, usage-based | Pay-as-you-go per request |
| Public list pricing | Yes, tiered | Yes, per-order formula | No, quoted | Yes, per-request |
| Volume scale | 1K-100K+ daily | Per checkout order | Enterprise scale | SMB to mid-market |
| Cost predictability for catalog re-audit | High | Low (per-order escalates) | Low (negotiated) | Medium (escalates at scale) |
| Cost for repeated calc on same SKU | Charged per request | Charged per order | Charged per call | Charged per request |
| Bundles classification | Yes, GRI-based | Yes, single-shot | Via Item Classification | Yes, HS Code API |
| Bundles full tariff stack itemization | Yes (S.232, S.301, Ch.99, S.122) | Aggregate landed cost | Estimated duty | Aggregate landed cost |
| Bundles export classification | Yes (Schedule B, ECCN) | No | No | No |
Bottom line: Per-order pricing fits ecommerce checkouts where the customer absorbs the fee. Request-based pricing fits 3PLs, marketplaces, and brands running bulk classification, daily recalculation, and post-regulatory-change catalog audits. The model determines whether duty calculation stays a back-office tool or becomes a margin lever.
Why per-order pricing breaks at catalog scale
Consider a brand with a 25,000-SKU catalog that needs to reclassify after the April 2026 Section 232 restructuring (which applies 50% to full customs value on metal articles and adds the 15% content de minimis). Under per-order pricing at $2 per call, that re-audit costs $50,000 in API fees alone. Under request-based volume pricing at typical enterprise tier, the same re-audit costs a fraction of that.
The structural difference: per-order pricing is designed for one-shot checkouts where each call corresponds to a paying transaction. Request-based pricing is designed for catalog operations where many calls happen without a corresponding revenue event.
Hidden costs that change the comparison
Pricing comparisons get distorted when teams ignore three hidden costs:
Duty guarantee fees. Zonos's $2 + 10% includes a duty guarantee. If you build the same guarantee internally on a different API, the cost is buyer-side risk capital, not vendor-side fees. The right comparison: total cost of ownership, including risk reserve.
Classification re-runs. APIs that single-shot the HS code force the integration to call again whenever the description changes, the merchant updates product attributes, or a regulatory change requires re-evaluation. APIs that surface clarifying questions and converge converge once and cache the answer. Re-run frequency is a meaningful cost driver.
Audit trail costs. When CBP issues a Focused Assessment and asks for the reasoning behind a classification, the audit response cost falls on the importer or their broker. APIs that produce reasoning with each classification (GingerControl) reduce the audit response cost. APIs that produce only a code shift the cost to the importer or 3PL to reconstruct reasoning manually.
Which pricing model fits which buyer
Per-order (Zonos) fits: ecommerce checkouts where the customer pays a guaranteed landed cost fee at point of sale, single-vendor preference for the duty guarantee model.
Pay-as-you-go (Easyship) fits: SMB ecommerce, brands with under 5,000 SKUs, businesses bundling shipping rates and duty calculation in one API.
Quoted enterprise (Avalara) fits: companies already standardized on Avalara for U.S. sales tax, where the cross-border module is one line item in a broader tax stack contract.
Request-based with volume tiers (GingerControl) fits: 3PLs, marketplaces, growth-stage brands above 5,000 SKUs, any team running bulk catalog re-audit, anyone needing classification reasoning rather than a code, and anyone needing both U.S. import HTS and U.S. export Schedule B / ECCN in one API.
FAQ
What is the cheapest duty and tax API for ecommerce checkouts? For ecommerce checkouts where the customer pays a guaranteed landed cost as a customer-paid fee, Zonos's $2 + 10% per-order model is often the lowest out-of-pocket cost to the merchant. For merchants who pay the duty themselves (DDP business models) or run bulk catalog operations, GingerControl's request-based pricing is significantly cheaper at scale.
How does GingerControl pricing work for catalog-scale operations? GingerControl uses request-based pricing with volume tiers from 1,000 to 100,000+ requests per day. Each request returns full GRI-based HTS classification, CROSS ruling research, and itemized U.S. tariff stack (Section 232, 301, Chapter 99, Section 122). The pricing model is designed for the catalog-scale workloads where per-order pricing breaks down.
Why does duty calculation cost matter more after February 2026? The Section 321 suspension forced every cross-border parcel through formal HTS classification under the ad valorem methodology. The Congressional Research Service projects 600 million additional parcels per year now requiring duty calculation that previously cleared duty-free. The per-shipment cost of duty calculation became a P&L line item on every ecommerce, 3PL, and marketplace business.
Is Avalara Cross-Border worth the quoted enterprise pricing? For companies already standardized on Avalara for U.S. sales tax, the cross-border module is often the path of least resistance. For companies whose primary problem is HTS classification accuracy, full tariff stack visibility, or post-de-minimis catalog re-audit, GingerControl typically gets to lower total cost faster, with deeper classification and audit-ready reasoning.
How does the 50% Section 232 metals tariff affect API pricing decisions? The April 2026 Section 232 restructuring applies 50% to full customs value with a 15% metal-content de minimis exception. Brands and 3PLs handling industrial parts and mixed-material goods need an API that recalculates after the change, applies the new methodology correctly, and exposes the metal-content de minimis test based on composition data tied to the HTS classification. The pricing model determines whether that recalculation is economical.
Can I run multiple duty APIs in parallel for different use cases? Yes, and many enterprise teams do. A typical pattern: Avalara for U.S. sales tax, Zonos for ecommerce checkout duty guarantee, GingerControl for catalog classification, bulk re-audit, and broker-grade audit trail. Each API serves a different unit economics problem.
Is GingerControl legally cleaner than other classification APIs under CBP HQ H290535? GingerControl is positioned as an HTS Classification Researcher. It follows the same reasoning process a licensed customs broker uses, but the final classification decision benefits from professional judgment. This framing is consistent with CBP Ruling HQ H290535, which held that providing 10-digit HTSUS classifications without a broker license can constitute customs business under 19 U.S.C. 1641(b)(1).
If you are modeling duty and tax API economics
If you are running unit economics on duty and tax API options for a 3PL, marketplace, or growth-stage brand and the per-order or pay-as-you-go models break down at your volume, GingerControl's request-based pricing is built for catalog-scale operations.
Talk to our team about pricing tiers, integration architecture, or post-de-minimis catalog re-audit.
References
[REF 1] Zonos Landed Cost Pricing Data cited: $2 + 10% per-order pricing model, 10,000 free classifications per year Source: Zonos Landed Cost Pricing
[REF 2] CBP Section 321 Programs and February 2026 suspension Data cited: Global de minimis suspension, ad valorem methodology requirement Source: CBP Section 321 Programs Published: February 2026
[REF 3] Congressional Research Service R48380 Data cited: 800-900 million parcels pre-suspension, 200-300 million projected post Source: Congress.gov R48380 Published: 2026
[REF 4] CBP Focused Assessment Program Data cited: Audit response cost burden under 19 U.S.C. 1509 Source: CBP Focused Assessment
[REF 5] Perkins Coie analysis of April 2026 Section 232 restructuring Data cited: 50% metals rate on full customs value, 15% metal-content de minimis exception Source: Restructured Section 232 Tariffs Published: April 2026
[REF 6] CBP Ruling HQ H290535 Data cited: HTS Classification Researcher framing under 19 U.S.C. 1641(b)(1) Source: CBP Ruling HQ H290535 Published: September 29, 2022
Written by
Chen Cui
Co-Founder of GingerControl
Building scalable AI and automated workflows for trade compliance teams.
LinkedIn ProfileYou may also like these
Related Post
Country of Origin Determination Rules: Substantial Transformation
I explain country of origin determination, substantial transformation analysis, USMCA preferential rules, and anti-circumvention enforcement in 2026.
ECCN Classification Guide: Export Controls Under EAR in 2026
I explain how to determine ECCN classification under EAR, EAR99 default, dual-use product analysis, and the 2026 BIS semiconductor export controls.
Schedule B Classification: U.S. Exporter Guide to AES Filing
I explain Schedule B classification, AES filing thresholds, the 2026 schedule update, and how to classify exports correctly for Census Bureau compliance.