Harpy Glossary

IXD (Inbound Cross Dock)

Amazon & D2C glossary · Harpy Media

An IXD (Inbound Cross Dock) is a specialised Amazon facility that receives large inbound shipments — often palletised or containerised — breaks them down, sorts by destination, and forwards inventory to regional fulfilment centres. It never fills customer orders; it’s the network’s distribution layer.

What is IXD?

An IXD (Inbound Cross Dock) is a specialised Amazon facility that receives large inbound shipments — often palletised or containerised — breaks them down, sorts by destination, and forwards inventory to regional fulfilment centres. It never fills customer orders; it’s the network’s distribution layer.

IXDs exist to solve a network-scale problem: a container landing at one point can’t sit there while 40 FCs each wait for their slice. The cross-dock decouples inbound from distribution — big shipments arrive in bulk and efficient flows, and inventory fans out toward the FCs that need it — which is why large vendors and direct-import flows predominantly route through them.

What routing through an IXD changes for you

Four practical differences. Shipment structure: IXDs reward volume — full pallets, container-scale deliveries, and cartons built for smooth handling. Sellers shipping in dribs and odds end up in the wrong channel; vendors and importers with palletised flow use the fast lane. Timing: cross-docking adds a hop, so transit to sellable can be a touch longer than a direct FC delivery in some lanes — the trade is predictability and placement quality (inventory lands where demand is, not where you happened to ship it). Documentation: the pallet/carton labelling and ASN accuracy discipline from the rest of the inbound stack matters MORE here — cross-docks are throughput machines, and mislabelled freight has nowhere to hide. And placement strategy: routing through an IXD is effectively delegating distribution, which reduces your inbound-placement fees exposure (you stop guessing FC-by-FC splits) at the cost of some direct control.

When the IXD channel is the right door

The profile that fits: enough volume that palletised shipments are routine (roughly, the flows where full-LTL and container patterns exist), broad distribution needs (many FCs, national spread — exactly what cross-docks optimise), and tolerance for delegated placement in exchange for lower hassle-to-shelf. The profile that doesn’t: small, frequent, fine-grained shipments where direct FC invoicing gives better control of where thin stock lands, or special-handling products whose requirements outrun cross-dock standardisation. The practical test most sellers meet: as inbound volume grows to the point where maintaining FC-by-FC splits becomes its own job, the cross-dock question answers itself — and the first trial shipments usually confirm it by landing cleanly, if the labelling and data discipline travelled with them.

In practice

A vendor crossing into container-scale replenishment switches their national flow to IXD routing: full pallets, standardised cartons, ASN verified against physical counts before dispatch. First wave receives cleanly, and the distribution fan-out achieves a placement spread the vendor’s manual splits never managed — fewer out-of-stock messages from half the country, shorter average delivery promises, and a measurable conversion benefit from the better placement. The vendor’s quarterly inbound cost lands lower despite paying for the extra hop, because misplacement had been the expensive part.

⚠️ Watch out. A seller sends small, mixed, lightly-labelled shipments into a cross-dock route suited to palletised volume — and watches them slow-walk through receiving while their labels get second-guessed. The channel amplifies whatever discipline arrives with the freight; arriving without any, it amplifies that instead.
💡 Harpy tip. Before routing volume through an IXD, run the labelling and carton-accuracy checklist from your prep spec against one test shipment — then confirm the receiving report matches. Cross-docks reward the prepared and expose the improvised.

How Harpy Media helps

Inbound routing strategy — direct FC, cross-dock, and programme flows modelled against your volume and placement needs — is part of our supply-chain design work.

IXD FAQ

What is an IXD?

Inbound Cross Dock — an Amazon facility that receives large shipments, sorts and breaks them down, and forwards inventory to regional FCs; it never fulfils customer orders.

How is an IXD different from an FC?

FCs store and ship to customers; IXDs are distribution waypoints — receive, sort, forward. Larger shipments and palletised freight flow through them.

Should I route my inbound through an IXD?

At volume, with palletised flows and national distribution needs, usually yes — it simplifies placement; small or specialised shipments may do better with direct FC deliveries.

Want these numbers watched for you, every week?

Book Free Consultation

New guides, straight to your inbox.

Practical D2C playbooks as we publish them. No fluff, no spam — unsubscribe anytime.