

To succeed in the Amazon business or the Logistics industry, it is crucial to understand Amazon’s infrastructure.
Understanding IXD, RXD, and the Structured Problem Solving Frameworks creates value for anyone selling thousands of units on a monthly basis.
It also benefits anyone preparing for interviews at Amazon or other tech companies.
In this guide, I will break down three components of Amazon’s fulfillment network that collectively help the organization achieve operational excellence:
• Inbound Cross-Dock Facility (IXD)
• Regional Cross-Dock (RXD) Operations
• The practice framework
Each of these components performs a different function for Amazon.
Understanding how they complement each other will give you a competitive edge in both your business and your career advancement.
Amazon’s Three-Layer Fulfillment Infrastructure
The Amazon fulfillment network consists of three different facility types that work together like an advanced sorting machine.
The purple areas are a national cross-dock (IXD), the triangles represent regional cross-docks (RXDs), and the black shapes are fulfilment centres (FCs).
Understanding how Amazon’s fulfillment centers operate is crucial for optimizing your FBA strategy.
The realisation of Amazon’s infrastructure is what delivers millions of packages every day throughout North America, Europe, and Great Britain.
Here’s how the three layers work together:

- National Cross-Dock (IXD)
Your first entry point is when shipping to one location, where Amazon receives shipments from external sellers and vendors, sorts them rapidly, and redistributes products to appropriate destinations within 24-48 hours under normal conditions
- Regional Cross-Dock (RXD)
The middle layer handling FC-to-FC transfers, where Amazon rebalances inventory across regions, consolidates shipments for efficiency, and positions products closer to customer demand
Where your inventory actually lives for weeks or months, getting picked, packed, and shipped directly to customers who place orders
Cross-dock facilities are not shaped like traditional warehouses where goods are placed until the time comes to ship them; they are high-velocity sorting hubs that operate so that products move through to the next point in the supply chain as fast as possible.
Products in a traditional warehouse are unloaded when they arrive, stored, and later distributed to their final destination once there are enough products for shipment.
whereas, with a cross-dock facility, the products are sorted on arrival by their intended destination and immediately moved into the next stage of shipping, with only seconds between arrival and being in the hands of an additional shipping entity.
| Feature | IXD (National Cross-Dock) | RXD (Regional Cross-Dock) | FC (Fulfillment Center) |
|---|---|---|---|
| Processing Time | 24-48 hours under normal conditions | 1-3 days typical | Weeks to months (storage) |
| Primary Function | Sorting and redistribution hub | Inventory repositioning optimization | Store and fulfill customer orders |
| Shipment Source | External sellers and vendors | Internal FC-to-FC transfers | N/A (storage facility) |
| Storage Duration | Minimal (cross-dock model) | Minimal (cross-dock model) | Extended (fulfillment model) |
| Your Interaction | Direct shipping destination | No direct control | Where your products live |
IXD Operations: The National Cross-Dock Gateway

shipping to one location” with: “When you’re a merchant shipping to one location, which means you’re allowing Amazon to split your shipments across the country
Think of a cross-dock as literally just a sortation center to plan, sort, and reroute inventory to the corresponding regional DCs.
If you send a full truckload to an IXD like TMV8 hypothetically, this national facility will then de-sort on a pallet basis and send the corresponding pallets to the regionals, potentially sending to multiple regionals depending on where the stock is going.
Why IXD exists—the key benefits Amazon gains:
- Consolidated Shipments: Accept mixed SKUs and large volumes at strategic locations without requiring precise routing to specific FCs
- Intelligent Routing: Distribute products based on real-time demand forecasting and inventory levels across the network
- Network Flexibility: Optimize where products ultimately land to ensure faster customer delivery promises
- Capacity Balancing: Distribute inventory across the network to prevent warehouse overload at individual facilities
- Cost Efficiency: Reduce handling costs and improve overall network efficiency through centralized sorting
An IXD facility’s workflow consists of three distinct phases.
- Phase one (Receiving and Verification) involves the trucks at receiving bays bringing in shipments, unloading those trucks, and scanning the shipments into Amazon’s system.
and using an automated process to verify the shipment ID against the expected manifest (any discrepancy will trigger an alert).
- In phase two (Sorting and Routing), cases or pallets will be placed into Sorting Zones, where employees will scan the units or case packs for the shipping destination.
The system will then perform calculations using algorithms to find the fulfillment center that is closest to the customer and has a low inventory level, while meeting the delivery speed requirements based on where they live.
- Phase three (Consolidation and Dispatch) occurs when products are consolidated onto outbound pallets or Gaylords that go to designated FCs.
Shipments are staged, loaded onto trucks, and often dispatched on the same day they are received.
| IXD Operational Zone | Function | Equipment Used |
|---|---|---|
| Inbound Docks | Receive seller/vendor shipments | Dock doors, forklifts, pallet jacks |
| Sorting Area | Scan and route products | Conveyor systems, handheld scanners |
| Quality Control | Verify prep compliance | Inspection stations, label printers |
| Staging Area | Consolidate outbound shipments | Pallet wrappers, Gaylords |
| Outbound Docks | Dispatch to fulfillment centers | Loading equipment, truck scheduling systems |
IXD runs through a coordinated team structure of several positions.
Receivers verify inbound shipments,
Sortation Associates scan and route units,
Quality Auditors verify that the Prep and Product conditions are acceptable,
Outbound Coordinators move sorted inventory from the sortation process to trucks,
Process Assistants manage flow and resolve bottlenecks in processing.
Operations Managers ensure that all operations meet target and quality standards.
Amazon measures IXD performance against several key metrics: throughput velocity (from receipt to outbound shipments within 24 hours), accuracy rate (greater than 99.5%), dwell time (minimized), damage rate (less than 0.5%), and compliance with Prep procedures (greater than 95%).
Each of these metrics is designed to protect the overall efficiency of the supply chain network.
if targets slip, it creates backlogs of inventory throughout the network, resulting in delays to all customers.
Common IXD challenges that create delays:
- Improper Labeling: Missing FNSKU labels, poor label quality, or incorrect placement forces manual intervention and slows processing
- Poor Packaging: Inadequate packaging that doesn’t meet Amazon’s requirements creates damage, chargebacks, and potential shipment refusal
- Manifest Errors: Submitted details that don’t match the actual contents cause reconciliation delays requiring investigation
- Unlabeled Case Packs: Mixed SKU pallets without proper case labeling require time-consuming breakdown and re-sorting
- Seasonal Volume Spikes: Seasonal Volume Spikes: Q4 capacity overload leads to longer processing times across all shipments, sometimes extending to 7-10 days
This is where a lot of the bottlenecks happen. Last year in Q4, Amazon AWD used the nationals, and this is where a lot of bottlenecks happen between the national and the regional.
This causes a ton of issues for sellers who ship to one location, thinking it’s simpler, when in reality they’re adding days to their inbound processing time and risking stockouts during the most critical selling period of the year.
RXD Operations: Regional Cross-Dock Distribution

Regional Cross-Docks (RXD) represent the ultimate staging location for the inventory before it is allocated to fulfillment centers (FC).
Fulfillment Centers – e.g., IMD3 or LIO2 – are the final destinations for FBA orders, where inventory is actually stored, picked, packed, and shipped.
The Regional Cross-Docks, including AVP1, GYR2, or FTW1, receive the inventory from National Cross-Docks, route the inventory to the correct FC based on its corresponding shipping hub, and finally route it to the assigned storage location.
Sellers do not ship their product inventory directly to RXD’s; however, inventory movement is directly affected by the RXD networks.
The RXD will facilitate inter-FC transfers, consolidate shipments, and redistribute stock based on consumption rates.
Typically, when a seller’s inventory displays ‘Reserved’ or ‘In-Transit’ status within Seller Central, the seller’s inventory has been transferred through an RXD as Amazon physically relocated the inventory to the area of high seller demand.
Why Amazon uses RXD—strategic benefits:
- Demand-Based Positioning: Move products closer to customers likely to purchase them, reducing delivery times and improving customer experience
- Cost Optimization: Consolidate transfers to maximize truck utilization and reduce transportation expenses across the network
- Inventory Rebalancing: Redistribute stock from overstocked FCs to locations experiencing higher demand, preventing waste
- Delivery Speed: Position inventory strategically to maintain fast delivery promises across all regions consistently
- Network Flexibility: Enable smooth inventory flow even during FC maintenance or capacity constraints at specific locations
RXD operations resemble IXD workflows but focus on inter-FC transfers rather than inbound seller shipments.
Fulfillment centers send excess inventory or products needed elsewhere to RXD facilities,
shipments arrive consolidated onto trucks carrying inventory from multiple origin FCs,
And at RXD, associates sort inventory by destination FC, much like IXD sorts by initial placement.
Products get consolidated with other transfers heading to the same destination, loaded onto outbound trucks, and dispatched.
The goal is to maintain continuous inventory flow without creating storage bottlenecks that slow down the entire network.
| Critical RXD Metrics | What It Measures | Business Impact |
|---|---|---|
| Transfer Accuracy | Percentage reaching the intended destination FC correctly | Prevents availability gaps and customer dissatisfaction |
| Cycle Time | Duration for transfers to move through RXD | Impacts inventory availability and sales velocity |
| Consolidation Efficiency | How effectively RXD combines transfers | Reduces transportation costs significantly |
| Damage Rate | Units damaged during transfer | Internal quality metric affecting profitability |
| Throughput Capacity | Daily unit processing capability | Critical during peak seasons like Q4 |
The beauty of the RXD system for Amazon is efficiency because they can consolidate transfers from multiple origin FCs onto single trucks heading to the same regional destinations.
Maximizing truck utilization and minimizing transportation costs.
The challenge for sellers is visibility and control since you can’t see when Amazon decides to transfer your inventory, can’t control the routing, and have to simply trust that the system is working optimally for your business while watching units sit in “reserved” status.
Understanding inventory management principles helps sellers anticipate these transfers and plan accordingly.
Strategic Shipping: Optimizing Your Route to Market
Shipping through AWD or a single location forces your shipment through four hops forces your shipment through four hops:
- Warehouse → IXD (national) → RXD (regional) → FC → Customer — which creates delays.
Instead, advanced sellers ship full truckloads directly to regional cross-docks (RXDs). By splitting shipments into multiple full trucks (to avoid placement fees), they skip the national cross-dock entirely. Their route becomes:
- Warehouse → RXD (regional) → FC → Customer — only three hops, faster and less congested.
With direct-to-regional shipping and pre-booked appointments, inbound times are dramatically faster. This is where working with experienced FBA prep centers can streamline your operations significantly.
This is the core operational playbook: understand Amazon’s IXD → RXD → FC infrastructure and use regional entry points to speed up FBA receiving.
Pro tips for sellers shipping to maximize speed
- Labeling Best Practices
Ensure every unit has a scannable FNSKU label on the outside of poly bags or directly on products, use high-quality thermal labels that won’t smudge or fade during handling, place labels on flat surfaces away from seams and edges for optimal scanning, and avoid covering existing barcodes that might cause scanning confusion
- Packaging Requirements
Use sturdy corrugated boxes that meet Amazon’s packaging requirements, properly cushion products to prevent damage during sorting, and keep box weights within Amazon’s limits of 50 lbs for standard and 100 lbs for oversize.
- Documentation Accuracy
Submit accurate shipment manifests in Seller Central before shipping, double-check SKU quantities and box contents against your manifest, clearly label cases with contents and quantities for case pack shipments, and include shipment IDs on all box labels for easy identification
Four-Phase Problem-Solving Methodology
Develop a consistent problem-solving framework that you apply to every challenge, regardless of the specific problem domain.
This structure becomes second nature through weekly practice, helping you organize thinking under pressure and ensuring you don’t skip critical steps that interviewers expect to see.
Phase 1: Problem Understanding (5-10 minutes)
Restate the problem in your own words to confirm understanding, list assumptions and constraints explicitly, ask clarifying questions about scope, scale, and success criteria, and define what “done” looks like for this problem.
For example, if asked to design an inventory routing system, you’d clarify: “Are we optimizing for speed, cost, or a balanced approach? What’s the volume, thousands or millions of units daily? What are acceptable processing times?”
Phase 2: Approach Design (10-15 minutes)
Break the problem into logical components or phases, sketch a high-level approach before diving into details, identify potential bottlenecks or challenges upfront, and call out trade-offs between different approaches.
Using IXD knowledge, you might say: “We could route everything through a central hub like Amazon’s IXD model, or distribute directly to regional facilities.
Central routing simplifies coordination but adds a processing step. Direct regional routing is faster but requires more complex logistics.”
Phase 3: Detailed Solution (20-30 minutes)
Work through the solution methodically, explain your reasoning at each decision point, draw diagrams or write code and pseudocode as appropriate, and discuss how you’d validate correctness.
This is where your operational knowledge shines; you can sketch the three-layer network, explain sorting logic at each level, and reference actual metrics like throughput velocity under 24 hours or accuracy rates above 99.5% that real systems target.
Phase 4: Review and Optimization (5-10 minutes)
Summarize your approach and key decisions, address edge cases or limitations proactively, suggest potential optimizations or alternative approaches, and discuss how you’d measure success in production.
Reference RXD concepts: “For optimization, we could add regional cross-docks that consolidate transfers, similar to how Amazon rebalances inventory.
We’d measure transfer accuracy, cycle time, and consolidation efficiency.”
| Common Mistakes | Why It's Problematic | How to Avoid |
|---|---|---|
| Jumping to Solutions | Leads to solving the wrong problem | Always spend 5-10 minutes clarifying requirements |
| Silent Working | Leaves interviewers unsure of your thinking | Narrate your thought process continuously |
| Poor Time Management | Creates incomplete solutions | Set mini-deadlines for each phase |
| Ignoring Validation | Suggests a lack of thoroughness | Always discuss testing and edge cases |
| Perfectionism Paralysis | Prevents progress | Start with a working solution, then optimize |
Role-Specific Practice for Fulfillment Teams
Different jobs inside fulfillment need different kinds of practice. Here’s what each role should focus on, explained in plain English.
Software Engineers (who build fulfillment tech)
Engineers working on FC, SC, or delivery systems should practice:
- How to design systems that update inventory in real time
- How to optimize routes, picking paths, or order batching
- How to build services that don’t break during peak (big traffic spikes)
Simple examples:
- Designing a system that chooses the fastest bin for a picker
- Creating a tool that helps carriers pick the best route automatically
Operations Managers (who run the buildings)
Ops leaders should practice:
- Designing smoother warehouse workflows that reduce processing time
- Planning how much volume they can handle and when they’ll break
- Finding the true cause of problems—not just the surface symptoms
Simple examples:
- Changing the layout to reduce walking time
- Implementing best practices to reduce errors in order fulfillment
- Improving UPH (units per hour) without burning out associates
Product Managers (who build tools for fulfillment teams)
PMs need to practice:
- Thinking like both engineers and operators
- Deciding which features matter most
- Defining clear success metrics
Simple examples:
- Writing a feature that speeds up receiving by removing extra clicks
- Choosing which inventory tool gets built first
- Defining metrics like “dock-to-stock time” or “stow accuracy.”
Technical Program Managers (who connect tech + operations)
TPMs must be good at everything: tech, operations, coordination, and planning.
They should practice:
- Explaining complex fulfillment flows in simple words
- Managing programs that touch many teams (FC, SC, AMZL, transportation)
- Understanding real-world trade-offs
Simple examples:
- Explaining why bypassing a cross-dock speeds up delivery but raises cost
- Coordinating changes that affect IXD/RXD pathways
- Aligning tech teams with building operations
Clear, Real-World Fulfillment Examples
Network Design Example
A three-layer cross-dock (National → Regional → Local) saves money but adds extra stops.
Sending freight directly (IXD bypass) speeds things up but costs more. This teaches how networks balance:
- Speed
- Cost
- Accuracy
Process Improvement Example
Removing the IXD step can cut processing time from 7–10 days to 3–4 days.
But you pay more inplacement fees and need better forecasting.
This shows that every operational gain comes with a trade-off.
Metrics Everyone Should Know
These simple numbers explain how healthy a fulfillment operation is:
- Throughput speed: units per hour processed in pick and pack operations
- Accuracy: how often things are picked or sorted correctly
- Damage rate: items hurt during handling
- Cycle times: how fast inventory moves through each step
These numbers affect cost, speed, and customer happiness.
| Amazon Leadership Principle | How IXD/RXD Knowledge Helps | Example Application |
|---|---|---|
| Customer Obsession | Explain how IXD speed impacts delivery promises | Reducing IXD dwell time by 6 hours improves delivery estimates. |
| Invent and Simplify | Discuss process improvements to workflows | Implementing automated sortation reduces manual touchpoints. |
| Dive Deep | Demonstrate detailed operational knowledge | Understanding throughput metrics and their business impacts. |
| Deliver Results | Show grasp of operational constraints | Balancing speed with accuracy in high-volume environments. |
| Think Big | Propose network-level optimizations | How RXD facilities enable regional inventory strategy. |
Many successful sellers partner with 3PL fulfillment providers to optimize their cross-dock strategy and maintain competitive advantages.
Conclusion
Utilizing Amazon’s IXD and RXD cross-dock networks gives you two distinct advantages: .it increases your efficiency as an FBA seller and gives you an edge over your competitor when it comes to logistics interviews.
Shipping directly to a local Cross-Dock or routing through AMZ Prep’s IXD-optimized inbound network rather than using Amazon’s large National Cross-Docks will eliminate the bottlenecks and delays that many sellers face, reducing your inbound lead time from approximately 7–10 days to just 3–4 days on average.
Additionally, by creating a structured environment for developing practical skills through weekly practice, Cross-Dock allow you to take theoretical knowledge and turn it into actual expertise.
The combination of understanding practical Fulfillment Networks and being able to explain your solution effectively under duress gives the professional a clear advantage over the typical “reactive” seller.
Each time you practice on Cross-Dock, you compound your Business Acumen and will be ready for any Career Advancement opportunities when they arise.
FAQs
What's the difference between shipping to one location vs. multiple for FBA?
Shipping to one IXD inbound location is simpler but slower because Amazon redistributes inventory through several layers, adding 7–10 days to processing. Shipping to multiple FCs or regional cross-docks requires separate shipments, but gets the inventory sellable much faster, usually in 3–4 days.
Can sellers control where their inventory goes?
Not fully. Amazon decides final placement using demand, capacity, and delivery speed. You can only influence routing by selecting certain ship-to options (IXD, RXD, FC-direct). Once received, Amazon may still redistribute inventory internally, shown as Reserved or In-Transit.
What packaging and labeling issues cause delays?
Most delays come from bad or missing FNSKU labels, mixed SKUs without proper case labeling, weak packaging, and shipment manifests that don’t match what you entered in Seller Central. These issues force manual checks, slowing inbound processing
How do cross-dock facilities process inventory, and how long?
Cross-docks use a fast “receive → scan → sort → send out” flow. Under normal volume, products clear in 24–48 hours; during peak seasons, it can extend to 7–10 days. RXDs (regional cross-docks) typically move inventory within 1–3 days.
Why does my inventory stay ‘Reserved’ or ‘In-Transit’?
This usually means Amazon is rebalancing inventory across FCs through RXDs. These internal transfers often take 1–3 days, but can take longer in busy periods. Reserved status ensures items aren’t sold while moving through Amazon’s network.

Blair Forrest is the Founder of AMZ Prep, one of North America’s fastest-growing third-party logistics and fulfillment networks, built entirely without outside capital since 2016. Under his leadership, AMZ Prep has scaled to 50+ fulfillment centers across 6 countries, processing over 8 million units monthly and powering $2 billion+ in annual GMV for more than 5,000 brands worldwide including 437, Silverts, Saltyface, Unilever, Duracell, and JBL. A recognized authority in eCommerce logistics, Amazon FBA strategy, and supply chain optimization, Blair has helped thousands of sellers and brands master their fulfillment operations from first shipment to enterprise scale. He regularly consults on FBA prep, multi-channel fulfillment, last mile delivery, international expansion, and cost reduction strategies that save brands 20–40% compared to traditional 3PL providers. Blair’s insights on Amazon logistics, 3PL operations, and eCommerce growth are widely cited across the industry. Through AMZ Prep’s content, guides, and resources, he continues to share battle-tested strategies drawn from managing one of the largest independently owned fulfillment networks in North America.
Comments