B2B cross-border duties on FedEx: where distributor flows need a different IOR pattern

When the consumer DTC duty default doesn’t fit

A US-based apparel manufacturer expands into wholesale, opening B2B channels alongside their existing DTC Shopify store. The first international wholesale order goes to a French distributor. The merchant’s existing FedEx integration applies the same duty-handling pattern it uses for consumer DTC — DDP at checkout, merchant becomes the importer of record, duty pre-paid. The package ships. The French distributor receives it, then calls support: “Why is your invoice showing the duty? I’m the importer of record. My customs broker handles this. Now I have to reconcile a duty payment I didn’t make.”

This is the failure mode that B2B cross-border duty handling exists to prevent. The mechanics aren’t complicated — the distributor has their own customs broker relationship, their own local tax accounting, their own EORI or GST registration. They expect to be the importer of record. Pre-paid duty by the upstream supplier breaks their accounting flow.

The carrier-side capability for the right pattern is clean on FedEx. The integration layer is where most B2B-on-Shopify and B2B-on-WooCommerce merchants still apply consumer-DTC duty defaults to flows where B2B-distributor handling is the right pattern.

This article describes what B2B cross-border duty handling actually requires, where the workflow consistently breaks, and what the integration layer needs to do for distributor-side IOR flows to work cleanly.

What B2B distributor flows actually need

A B2B cross-border shipment to an established distributor typically looks operationally different from a consumer DTC shipment to a private buyer. The distributor has:

A customs broker relationship in their jurisdiction (or in-house customs capability)
A registered EORI (EU), GST registration (India, Australia), VAT registration, or jurisdiction-equivalent
Tax accounting that reconciles import duties against their books
Established import workflows they’ve built over years with their suppliers

When the merchant applies DDP (Delivered Duty Paid) to this flow, the merchant becomes the IOR and pre-pays duty. The distributor receives a package they didn’t pay duty on. The distributor’s customs broker has nothing to do for the shipment. The distributor’s accounting can’t book the duty as a deductible import expense because they didn’t pay it. The relationship that the distributor built with their broker over years gets disrupted by a duty-handling default the merchant didn’t think about.

The pattern that fits B2B distributor flows is typically DDU (Delivered Duty Unpaid) — the distributor remains the IOR, their EORI/GST/VAT goes on the FedEx manifest in the recipient customs identifier field, duty is assessed at the border against their account, their broker handles clearance, and the merchant’s invoice covers goods and shipping but not duty. The distributor’s existing import process runs the way it always has.

Where the workflow actually breaks — three failure patterns from the merchant base

Three patterns show up consistently across merchants running B2B alongside DTC on the same shipping integration:

1. Global DDP default applied to B2B flows. The merchant enabled DDP for cross-border DTC and the integration applies it to every cross-border order — including the wholesale B2B orders. Distributors receive duty-paid shipments they didn’t want duty-paid. The merchant’s customs invoicing balloons. Reconciliation gets messy at month-end. The fix is per-account or per-buyer-type duty handling — DDP for consumer DTC, DDU for established B2B accounts — but most multi-carrier shipping apps don’t store IOR election at the account level.

2. Recipient customs identifier not captured for B2B accounts. The merchant has DDU set as the right default for B2B, but their integration doesn’t capture the distributor’s EORI / GST / VAT at account-setup time. The shipment leaves with the recipient customs identifier field blank. Destination customs holds the shipment requesting the identifier. The merchant’s support team has to extract the identifier from the distributor mid-fulfillment, often with a 24-72 hour delay before customs releases the package. The right pattern stores the recipient customs identifier on the B2B account record (not the order record) so it flows automatically to every shipment.

3. DDP-vs-DDU election treated as a per-order checkbox. Some integrations expose IOR election as a per-order toggle the operations team flips manually. At small B2B volume this works; at production B2B volume — distributors placing weekly purchase orders — the toggle gets missed on a rotating share of shipments. Some go DDP when they should have gone DDU. Some go DDU when the buyer is actually a small B2C account that needed DDP. The pattern is consistent: per-order decisions made by ops at the moment of fulfillment are operationally fragile across recurring B2B flows.

These three patterns explain the bulk of B2B cross-border duty-handling issues we see in the merchant base.

The workflow that holds up at scale

The workflow that doesn’t break stores the IOR election and the customs identifier at the account/buyer level, not at the order level. When a B2B account is set up, the merchant configures the distributor’s EORI / GST / VAT, the duty-handling election (DDU vs DDP — almost always DDU for established distributors), the customs broker contact information if relevant for special-handling categories, and any account-specific HS classification overrides for the product mix.

When orders flow from that B2B account, the shipment builder reads from the account record. The customs identifier flows to the FedEx manifest. The IOR flag is set correctly. The commercial invoice carries the right declared values. The distributor receives the shipment through their normal import flow, with their broker handling clearance against their identifier, and their tax accounting captures the duty payment they actually made.

Consumer DTC flows on the same merchant’s storefront continue to apply DDP where that’s the right pattern — the integration distinguishes B2B and DTC flows at the order-context level, not by asking ops to remember.

Where this sits in the broader B2B cross-border picture

B2B-on-Shopify and B2B-on-WooCommerce continue to be one of the faster-growing segments inside eCommerce. Apparel brands launching wholesale tiers, food and beverage manufacturers shipping to retail accounts, cosmetics brands serving multi-location salon chains, hardware makers shipping to distributor partners. The platform infrastructure for B2B storefronts has matured significantly in 2024-2025. The shipping-app infrastructure has lagged.

For cross-border B2B specifically, the duty-handling pattern is often where the lag shows up first. The carrier-side capability for distinguishing DDU and DDP, for routing recipient customs identifiers correctly, and for handling the B2B IOR flow has been clean on FedEx for years. The integration layer typically applies consumer-DTC patterns by default and the failure mode emerges the first time a distributor pushes back.

For FedEx International Trade Services and the B2B account team, this is one of the cleaner workflow areas where joint visibility with integrator partners would land — the merchant is already running B2B operations, the carrier capability supports it, and the integration-layer gap is where the friction currently sits.

B2B cross-border duty workflow automation still feels like one of the under-built capability areas across Shopify and WooCommerce shipping infrastructure as the B2B-on-platform trend continues.

Happy to connect with anyone on the FedEx International Trade Services / B2B accounts side exploring B2B cross-border workflow automation further.

This article reflects patterns observed across PluginHive’s B2B-on-Shopify and B2B-on-WooCommerce merchant base on FedEx. B2B import requirements, IOR election rules, and destination-country customs broker conventions evolve — verify current jurisdiction-specific guidance and FedEx International Trade Services documentation before commercial commitments.