A shopper adds a product to cart, sees a price, and completes checkout. Weeks later, a carrier knocks on the same shopper’s door asking for an unexpected duty payment before releasing the package. That gap between the price shown and the price actually owed explains why DDP landed cost software exists. It also explains why so many Shopify and VTEX brands get checkout duty estimation wrong.
This guide breaks down how duty and tax estimation actually works on both platforms. It covers what data has to be correct before any number at checkout can hold up, and how carrier integration determines whether that number survives once the parcel reaches customs.
What does DDP landed cost software actually calculate
DDP landed cost software estimates the full cost of getting a product to a customer’s door. That includes the product price, shipping, import duty, and destination country tax, all displayed as one total before the customer pays. Delivered Duty Paid, or DDP, means the seller collects and remits these charges upfront. The customer never receives a surprise bill at delivery.
The calculation depends on three inputs working together. The product’s Harmonized System classification sets the duty rate. The declared value and country of origin determine which trade rules and thresholds apply. The destination address determines the tax regime, whether that means VAT in the European Union, GST in several markets, or a country specific structure like Brazil’s import tax system. Get any one of these three wrong, and the number at checkout will not match what customs actually charges.
Why checkout duty estimation fails most often
Missing or incorrect product data causes the most common failure on both Shopify and VTEX, not a platform limitation. Shopify calculates duties and import taxes using the Harmonized System code and country of origin assigned to each product. When a product lacks an HS code, Shopify falls back to the product’s description and category instead. If none of those three data points exist, Shopify skips duty calculation for that order entirely, even when the destination country has duty collection enabled.
That silent failure is dangerous precisely because it looks like success. The order goes through and checkout completes. Nothing alerts the merchant that duty was never calculated. The customer then receives an unexpected charge at delivery regardless of what the checkout implied.
VTEX takes a different approach. It routes tax calculation through an external service rather than a native duty engine. When a shopper changes their cart, VTEX’s Checkout API sends a request to a connected tax provider, which returns applicable taxes for each product. This gives merchants more flexibility to plug in a specialized provider. It also means accuracy depends entirely on how well that external service is configured, and on it responding within VTEX’s five second timeout window. VTEX does not retry if the external service times out.
Getting product data right before anything else
Before enabling duty collection on either platform, every product going into international channels needs three data points confirmed: HS code, country of origin, and an accurate declared value. This is not a one time setup task. New products added after the initial configuration inherit the same requirement. A single missing code can silently exclude that product from duty calculation on an otherwise correctly configured store.
For brands with large catalogs, this is usually the real bottleneck, not the platform’s technical capability. Classification needs to happen at the SKU level, since two similar products can carry different duty rates depending on material composition, function, or intended use. Automating HS code assignment without human review at launch tends to create errors. Those errors often surface only after the first wave of international orders ships.
Matching duty collection to the correct label type
Once duty collection starts at checkout, the fulfillment side of the operation has to match it. Shopify requires DDP shipping labels once duty and import taxes are collected at checkout, not standard labels. Using a standard label after collecting duty at checkout means the carrier still invoices the customer at delivery, creating the exact double charge that DDP was supposed to prevent.
Teams miss this detail more often than they should, particularly when the group managing checkout configuration sits separate from the group purchasing shipping labels. The fix is procedural, not technical. Confirm that every DDP enabled destination has a matching DDP label workflow before the first order ships. Audit new team members against this rule specifically, since anyone unfamiliar with the setup can easily default to a standard label.
Carrier integration determines whether the estimate holds up
A landed cost number only holds up as well as the carrier data feeding it. DHL, FedEx, and UPS each publish their own rate structures. Delivered Duty Paid support varies by service level and destination. That means a duty and tax calculator has to reconcile carrier specific rules against the destination country’s actual tariff schedule.
Shopify handles this through two paths. Merchants can use the native Managed Markets duty calculator, which requires Shopify’s own carrier calculated shipping. Or they can connect a third party app that links to multiple carriers independently. Eligible merchants on Managed Markets also receive a duty guarantee, where Shopify covers the gap if the collected duty amount fell short. That guarantee shifts some compliance risk away from the merchant, though eligibility depends on region and account type.
VTEX approaches carrier integration as part of its broader Cross Border feature set. That includes international freight calculation and integration with partner carriers, alongside centralized tax and fee management by market. One documented case involved a Brazilian fashion brand expanding into Portugal and Spain through VTEX Cross Border. The brand achieved delivery in five days from Rio de Janeiro to Porto while managing multiple domains, translated catalogs, and region specific tax configuration through a single dashboard.
Reconciling checkout estimates against actual customs charges
No duty calculator gets it right on day one without verification. After the first invoice arrives from a carrier, compare the duty and tax amount charged at checkout against what customs actually charged at the destination. This single comparison catches more configuration errors than any other step in the process, because it tests the entire chain at once, product data, tax logic, and carrier handling, against a real world outcome.
If a considerable gap shows up between the checkout estimate and the customs invoice, the root cause is almost always one of three things. An HS code might not match the actual tariff classification. A destination tax rate might have changed without an update to the store’s configuration. Or a carrier might apply a different duty treatment than the one assumed at checkout. Run this reconciliation periodically, not just once, since tax rules and carrier policies both change over time without necessarily notifying the merchant.
Building landed cost visibility into the customer experience
Estimating duty accurately behind the scenes solves half the problem. Presenting that estimate clearly enough for the customer to trust it before paying solves the other half. A landed cost total that only appears after multiple checkout steps, or that breaks into confusing line items, creates the same hesitation as no estimate at all.
The most effective checkout experiences show one clear total that includes product price, shipping, duty, and tax before the payment step. They also make more detail available on request, so a curious customer can see what makes up that number without it cluttering the primary view. This matters more for cross border D2C brands than for domestic sellers. International customers already expect hidden costs, so a transparent total sends one of the strongest signals a checkout can give that the brand has its compliance operation under control.
Choosing between native platform tools and specialized providers
Both Shopify and VTEX offer paths to duty calculation without a third party integration, but neither path covers every brand completely. Shopify’s native duty calculator works well for merchants who want minimal engineering effort and can operate within its requirements: skip Shopify’s own fulfillment network, add HS codes to every product, and ship through a carrier that supports DDP labels. Brands with more complex classification needs, multiple fulfillment origins, or requirements outside Shopify’s supported carrier list typically need a specialized integration instead.
VTEX built its external tax service model for flexibility from the start. The platform itself does not constrain the choice of provider, but that also means the merchant or its technology partner carries the full burden of selecting and correctly configuring that provider. Brands running Cross Border specifically choose their tax and export partner during initial setup, not as an afterthought. Treat that decision as seriously as the catalog and currency choices made at the same stage.
What this means for cross border operations
Checkout duty estimation is not a feature to toggle on and forget. It depends on product data that teams have to maintain as catalogs grow, carrier workflows that have to match whatever checkout configured, and periodic reconciliation against real customs charges to catch drift before it becomes a pattern of customer complaints. Brands running on Shopify and VTEX side by side, or migrating between them, often discover that duty logic does not transfer cleanly, since the two platforms solve the same problem through fundamentally different architectures.
ShipSmart connects Shopify and VTEX checkouts to carrier integrations across DHL, FedEx, and UPS, calculating landed cost accurately at checkout and keeping duty collection aligned with the DDP labels and customs data each shipment actually needs.
See how ShipSmart works for Shopify and VTEX checkout duty estimation
