Shopify Managed Markets Ends DDU: What the Cross-Border Duty Change Means for Enterprise Stores (2026)

Shopify's August 2026 platform updates carried a change that most merchants will skim past and that cross border stores cannot afford to: Managed Markets, Shopify's service for selling internationally, is ending Delivered Duty Unpaid. The same update window also set an August 26 checkout deadline for non Plus stores, but the duty change is the one with real financial teeth. If your store ships across borders, the model by which import duties reach your customer is about to change, and the checkout experience that determines your international conversion rate changes with it. Here is what is actually happening and what to do.

Term	What it means	Who pays duty, and when
DDU (Delivered Duty Unpaid)	Duty is not collected at checkout	Customer pays the carrier on delivery, often by surprise
DDP (Delivered Duty Paid)	Duty is calculated and collected at checkout	Customer pays up front, landed cost is known before purchase
Managed Markets	Shopify's cross border service handling duty, tax, and currency	Shopify calculates, merchant collects at checkout under DDP

What actually changed

Under Delivered Duty Unpaid, an international shopper checks out paying for the goods and shipping, and the import duty is billed separately by the carrier when the parcel reaches the border or the doorstep. The customer often does not see that charge coming. Ending DDU on Managed Markets means the duty now has to be estimated and collected as part of the order total at checkout, the Delivered Duty Paid model. The customer sees one number, the true landed cost, and pays it once.

For the merchant this is not a toggle, it is a data and checkout requirement. Delivered Duty Paid only works if the system can compute duty at the moment of checkout, and that computation depends on knowing, per product, the country of origin and the correct tariff classification, usually an HS code. A catalog that has been fine for domestic selling with none of that data attached is not ready for duty paid checkout, and the gap surfaces as either wrong duty estimates or a checkout that cannot quote a landed cost at all.

Why Shopify is doing it, and why it is correct

The surprise duty bill is one of the worst experiences in cross border retail. A shopper who thought they paid in full gets a demand from the carrier for a fee they did not expect, and a meaningful share of them refuse the parcel. That refusal becomes a return, a reverse logistics cost, and sometimes a chargeback, and the merchant eats all three. Delivered Duty Paid removes the surprise by making the landed cost visible before purchase, which raises completed international orders and cuts refusals, even though the checkout total looks higher because it now tells the truth.

So the change is aligned with merchant interest even though it adds work. The cost is real, though. Duty paid checkout is harder to build and harder to keep accurate, because tariff schedules change and misclassification means you either overcharge customers or absorb the shortfall yourself. This is the recurring pattern in cross border commerce: the customer facing simplification is paid for with backend complexity, the same trade we mapped in multi currency and cross border pricing on headless Shopify Plus.

What headless stores have to do that native stores get for free

On a native Shopify checkout, Managed Markets does the duty calculation and the collection inside Shopify's own checkout, and much of this transition is handled for the merchant. On a headless build, the storefront is yours and the checkout integration is a decision you own, which means the duty paid quote has to reach your custom cart and be presented before the customer commits. If your headless storefront calls Shopify's checkout for the final step, you inherit the calculation but you still have to surface the landed cost in your own cart UI so there is no jump at the last screen. If you have gone further and detached more of the flow, you own more of the quoting problem directly.

The decision table is straightforward once you frame it by how much of checkout you control.

Architecture	Who computes duty	Merchant's main task
Native Shopify checkout	Managed Markets, inside checkout	Attach origin and HS codes to catalog
Headless storefront, Shopify checkout for payment	Managed Markets at the checkout step	Surface landed cost in the custom cart before handoff
Deeply decoupled checkout	Your integration and duty provider	Own the duty quote, the accuracy, and the liability

This is the same reason the build versus buy line on headless keeps moving, and it is worth revisiting your platform assumptions when a change like this lands. We compared where that line sits now in commercetools versus Shopify Plus for enterprise headless. The more of checkout you own, the more of this duty transition becomes your engineering problem rather than Shopify's.

The catalog data work is the real project

The unglamorous truth is that the hard part of this transition is not checkout code, it is catalog hygiene. Duty paid checkout needs a country of origin and a correct HS code on every product that ships across a border, and for a large catalog assembled over years by different teams, that data is often missing, wrong, or inconsistent. Getting it right is a cross functional effort involving merchandising, compliance, and engineering, and it cannot be faked with a default value, because a wrong HS code means a wrong duty, which means either an overcharged customer or an unrecoverable shortfall on your side.

Start there. Audit the catalog for origin and classification coverage, fix the gaps, and only then worry about where the landed cost renders in the cart. A store that nails the checkout UX on top of bad classification data has built a fast path to charging the wrong amount.

The merchant of record question sits underneath all of this

Duties, taxes, and cross border liability are exactly the responsibilities a merchant of record takes on, and this change is a good moment to ask whether you want to carry that weight in house or hand it to a provider. Managed Markets moving to duty paid pulls Shopify further into that role for stores that use it, but merchants running their own cross border stack, or selling digital goods where the calculus differs, still have to decide who owns the tax and duty liability. We laid out that decision, with the trade offs, in Paddle versus Lemon Squeezy as a merchant of record. The Managed Markets change does not settle the merchant of record question for you; it just makes ignoring it more expensive.

When this applies to your stack

If you sell across borders on Shopify, treat the end of Delivered Duty Unpaid as a deadline, not a notification. Audit your catalog for country of origin and HS code coverage now, confirm where the landed cost will render in your checkout or headless cart, and decide deliberately how much of the duty quoting and liability you want to own versus delegate. The stores that handle this well will convert more international traffic because the price finally tells the truth up front; the ones that ignore it will find out through a spike in refused parcels.

Cross border checkout, catalog data readiness, and platform migration work like this is core to what we do at Contra Collective. If you are running an enterprise or headless Shopify build and want the duty paid transition handled without a conversion dip, we can help you scope the catalog work and the checkout integration together.

FAQ

What is the difference between DDU and DDP? Delivered Duty Unpaid collects no duty at checkout, so the customer pays the carrier on delivery, often unexpectedly. Delivered Duty Paid calculates and collects the duty at checkout, so the customer sees the full landed cost before buying. Shopify Managed Markets is moving from the first model to the second.

Does this affect non Plus stores? The duty change applies to stores using Managed Markets for cross border selling regardless of plan, and the same August 2026 update set a separate August 26 checkout deadline for non Plus stores. Confirm both against your own account, since rollout timing varies.

What catalog data do I need for duty paid checkout? At minimum a country of origin and a correct HS tariff code on every product that ships internationally. Missing or wrong classification produces wrong duty amounts, which means overcharging customers or absorbing the shortfall yourself.

Do headless stores need to do more work? Usually yes, because you own the storefront and cart, so you have to surface the landed cost in your own UI before the customer commits, and the more of checkout you have decoupled, the more of the duty quoting and liability you own directly.