Cross-docking is a distribution strategy where goods are received at the inbound dock and re-shipped almost immediately from the outbound dock — toward store, plant, or customer — with little or no putaway into rack. The value is speed and less inventory; the risk is burning On Time In Full (OTIF) if appointments and data do not arrive before the carton.
- staging, not days on floor
- Hours
- pre · consolidated · hybrid
- 3 types
- flow OTIF > rack occupancy
- 1 KPI
- appointments + ASN + door
- Sync
Cluster: freight journey · TMS · OTIF · POD.
What cross-docking is
In a pure cross, product is not put away into rack: it is sorted and leaves in hours (sometimes minutes). The dock is the transfer point — not a mini-warehouse in disguise.
Supply-chain model
Supplier, cross-dock, and customer
Mexican practice has variants: a few hours in temporary staging, LTL consolidations toward a regional DC, or “cross-dock” that is really floor storage without a warehouse management system (WMS) tracking locations. If product sits for days without a firm destination, it is not cross-docking: it is improvised inventory.
The short nickname in many DCs is X-Dock. Node functions still live in warehouse functions.
Vs traditional warehouse
They are not enemies: they are modes. The warehouse absorbs uncertainty with stock; cross-dock bets that information arrives before the carton.
Warehouse with rack
- Receive, putaway, and pick to ship
- Inventory buffer against delays
- Fixes errors during putaway
- Typical KPI: occupancy and fill rate
Dock crossing
- Receive, sort, and ship (hours)
- Little or no rack
- Data errors reach the customer
- Typical KPI: dock-to-dock and OTIF
How it works: crossing phases
The operable flow is orchestration, not “removing shelves.” Each phase needs data and an appointment before the physical move.
Phases
From ASN to outbound
Plan
ASN and appointments
Receive
Inbound dock
Sort
By destination
Stage
Hours, not days
Load
Outbound dock
Close
POD and docs
In Mexico the document close matters: remittance, CFDI (electronic tax invoice) and Carta Porte complement when the haul applies, plus usable proof of delivery (POD). Without that, the cross “ran” but accounts payable cannot audit the trip. Full map: freight journey.
Types: pre-distributed, consolidated, hybrid
The three types in most European guides also apply in Mexican DCs — with retail, food, and nearshoring examples.
Pre-distributed
What happens at the dock: Supplier already labeled by store/customer; transfer only
Mexico example: CPG to retail chain: pallets by store from plant
Consolidated
What happens at the dock: Open/sort and regroup by destination (more touches)
Mexico example: Several LTL suppliers to one FTL to DC or store
Hybrid
What happens at the dock: Flow-through + rack pick in the same outbound order
Mexico example: Same-day dairy + dry goods from rack to same store
On pre-distributed and consolidated flows, the unit load (tertiary packaging) must arrive countable at the dock: stable pallet, readable label, no overhang — otherwise the cross turns into a claim or rework.
Consolidated type
Inbound, sortation, and outbound
Consolidated is the textbook picture: trucks A and B inbound, quality control and order organization at the node, outbound by dock. If the ASN is late or a trailer misses its window, sortation becomes an expensive yard.
Benefits when the cross is synchronized
The benefit is not cosmetic: less inventory in transit and shorter cycle time — if the network can hold the pace.
- Less putaway and picking: fewer touches per carton on pre-distributed flows.
- Lower inventory at the node: capital and space freed for real staging.
- Better lead time to store when inbound and outbound appointments are tied.
- LTL–FTL consolidations: fewer scattered trips on dense corridors.
- Fits lean when you cut waiting and motion waste — see lean supply chain in Mexico.
Limits and sync failure modes
Cross-dock amplifies information errors. What a warehouse fixes during putaway arrives incomplete or late to the customer here.
Misaligned appointments
Yard / dock symptom: Trailers waiting for doors; eternal staging
Impact: Detention, Late OTIF, saturated yard
Weak ASN / labels
Yard / dock symptom: Cartons without destination; endless inspection
Impact: Extra touches, outbound shortages
Inbound delay
Yard / dock symptom: Outbound misses retail window
Impact: Chargeback / broken OTIF window
Value-added in the cross
Yard / dock symptom: Repack or kit queues
Impact: Stops being pure cross-dock
Loose POD / docs
Yard / dock symptom: Trip “delivered” without evidence
Impact: Accounts payable cannot close; dispute
When the cross fails, evidence matters: proof of delivery (POD) and trip traceability to reconstruct what arrived incomplete or outside the window.
When to use it in Mexico (DC and retail)
The decision is about flow and information — not a European brochure. Use hard criteria on Mexico–US corridors and domestic networks.
| Signal | Favors cross-dock | Discourages cross-dock |
|---|---|---|
| Demand | Orders already allocated / retail waves | Unpredictable assortment |
| Information | ASN and labels before arrival | Cartons without clear destination |
| Appointments | Inbound and outbound synchronized | Random arrivals |
| SKU / touches | High volume, few touches | Heavy kits / repack |
| KPI that rules | Dock-to-dock + OTIF | Rack occupancy only |
| Network | Plant–DC–store; consolidated LTL | Forcing one mode on the whole SKU mix |
Chain patterns (automotive, CPG, omnichannel): Mexico–US supply chain examples.
Operable checklist
Start with a pilot flow (one customer or family), not the whole network. Calibrate to your operation — we do not invent universal thresholds.
Elige un paso para ver el detalle
Detalle del paso · 01
Candidate flow with known destination on arrival
What OCL does at the handoff
OCL Cargo is an autonomous TMS with agents (computer use: they operate screens and portals). In cross-dock the pain is usually appointment sync, dock exceptions, and evidence when the cross fails — not DC layout.
Agents concentrate milestones and exceptions in a trip file; OCL can stamp invoice and Carta Porte when fiscal scope applies; they coexist with your WMS/TMS without a big-bang. Your team on exceptions. Guide: what a TMS is.
Key takeaways5 points
- Cross-docking = dock crossing: inbound, sort, and outbound, with little or no rack.
- Three types: pre-distributed (supplier labeled), consolidated (regroup at node), hybrid (flow + stock).
- It wins with predictable demand, ASN, aligned appointments, and measured OTIF — not “removing racks.”
- Useful KPIs: dock-to-dock hours, % without putaway, touches per carton, yard dwell, flow OTIF.
- In Mexico the typical failure is appointment sync + evidence (POD/docs); TMS and the trip file matter as much as layout.
Does your cross-dock speed flow… or only fill the yard?
Related reading
Frequently asked questions
A distribution strategy where goods are received at the inbound dock and re-shipped almost immediately from the outbound dock toward the customer or next node, with little or no putaway into rack. Plain Spanish ops term: cruce de andén (dock crossing).
Three useful types in Mexican DCs: pre-distributed (supplier already labeled by destination), consolidated (sort and regroup at the node), and hybrid (flow-through plus rack stock in the same outbound order).
Hours, not days. If you structurally measure temporary staging in full days, you are already running a warehouse without locations — not a cross-dock.
When demand is unpredictable, there is no reliable advance ship notice (ASN), inbound/outbound appointments are not synchronized, or the order needs heavy value-added (kits, complex repack) without a buffer. On Time In Full (OTIF) usually drops.
No. Many networks combine rack for safety stock and cross-dock for fast flow (daily retail, nearshoring plant–DC–store). The mistake is forcing one mode across the whole network.
Dock-to-dock hours, percent transferred without putaway, touches per carton, dwell at dock/yard, and flow OTIF. Rack occupancy alone does not prove the cross works.
Agents sync appointments, exceptions, and trip evidence (proof of delivery / POD, documents) into one file. OCL can stamp invoice and Carta Porte when fiscal scope applies, coexist with your WMS/TMS, and leave exceptions to your team. It does not replace DC layout on day one.