Crossdocking - what it is and when it makes sense

Picture a hall with two rows of docks facing each other - dock row A on one side, row B on the other, 30-50 metres of open floor in between. The supplier's truck pulls up to dock A, goods come off the trailer on a pallet or a conveyor. The operator scans the SSCC or shipment label, the WMS checks the ASN and replies: this pallet goes to dock B7, that one to B12, the next to B3.

Three to six hours later the same pallet stands at dock B waiting for the outbound truck. It never visited a rack. It isn't sitting in any storage location - only in transit state, with the full scan history attached. By evening the hall is empty and the next day repeats the same cycle.

The whole economy of crossdocking comes from eliminating the two most expensive moves - put-away (placing on the rack) and picking (taking it off). In a storage operation those two moves generate 60-70% of handling cost. In crossdocking only sorting and bulk consolidation are left.

Pre-allocated crossdocking - goods from a supplier are assigned to a specific customer order before they even arrive. The pallet label carries the outbound order ID. The WMS doesn't have to think where to route the pallet, it knows in advance. The operator scans the SSCC, the system shows "dock B7, customer Biedronka, order 4488123". This is the fastest form, but it requires tight cooperation with the supplier and a working ASN exchange.

Consolidation crossdocking - goods from many suppliers reach a hub where they are sorted to a specific customer or route. The classic example is delivery to retail chains: 8 grocery suppliers bring goods to the crossdock, they get grouped into per-shop pallets and in the evening 12 trucks leave, one to each location. Logistically harder because it requires sorting, but it delivers a lot of value to the recipient - instead of 8 deliveries a day, just one.

In practice in Poland we usually meet hybrids - part of the stream is pre-allocated (goods for a specific order), part is consolidated (per-shop picking from many sources). A pure form of one type is rare.

Crossdocking makes sense with high rotation, low SKU variety and predictable time windows. Specifically:

• FMCG and retail chains. Biedronka, Lidl, Kaufland, Carrefour - all of them run transshipment in regional hubs. Goods from a manufacturer go to the hub, get sorted to specific shops and ship out the same night.
• Pharmaceutical distribution. Pharmacy wholesalers (Pelion, Neuca, Farmacol) use crossdocks to distribute to pharmacies - a drug from the central warehouse hits a regional hub in the morning and is on the pharmacy shelf by evening. Critical for the cold chain.
• Seasonal retail. Apparel, sporting goods, garden tools - port deliveries (Gdynia, Gdansk) are routed during peak season through a crossdock straight to shops, bypassing the central warehouse.
• Press and distribution. Newspapers, books, marketing materials - time windows are short (Monday's paper won't sell on Tuesday), so storing them makes no sense.
• Auto parts for service shops. Car parts ordered by garages - goods from a dozen manufacturers consolidated at a hub, dispatched in the evening to regional sorting centres and at the workshop the next day.

Where the assortment is wide, volumes low and orders irregular (a typical industrial parts warehouse with 50 thousand SKUs and 200 orders a day) - crossdocking doesn't fit. Better stay with classic storage and picking optimisation.

Crossdocking won't run if the system finds out about a delivery only when the truck rolls onto the dock. Data exchange with the supplier has to happen before goods arrive. Three components are essential:

• ASN (Advance Shipping Notice). An EDI message or file exchanged 4-24 hours before delivery, listing the pallets, their SSCCs, the GTINs and quantities of items, batch numbers and expiry dates. Thanks to the ASN the WMS knows what's coming and can plan in advance where each pallet goes.
• GS1 labels with valid SSCCs. Without an SSCC there is no unambiguous pallet identification - the operator has to unpack and count by hand. A GS1-128 label carrying the SSCC, content GTIN, quantity and expiry date allows the pallet to be received in a single scan.
• Integration with the supplier's system. In practice EDI (EANCOM, EDIFACT), REST API or CSV/XML file exchange over SFTP. The format is secondary - the key thing is that the data arrives before the truck.

Missing even one of these elements means falling back to classic receiving - count, verify, then decide where to route the goods. Instead of 6 hours the operation takes 18 and stops making sense.

Concrete items that genuinely drop when an operation moves from storage to crossdock:

• Lead time from supplier to end customer - from 5-7 days to 24-48 hours. That changes the commercial offer, not just costs.
• Stock in the warehouse - effectively zero. Working capital cycles faster, expiry risk drops to zero.
• Floor cost - a crossdock hall needs roughly 30-40% less floor space than a storage hall with the same throughput. No high-bay racks, no aisles, no put-away buffer zone.
• Product freshness - critical in FMCG, pharma, flowers, press. Manufacturer dispatches at 6:00, item is on the shelf at 18:00 the same day.
• Moves per pallet - 2 instead of 4-5. Fewer forklifts, fewer operators, less damage risk.

On the other hand new costs appear - investment in EDI, supplier discipline, dock equipment, sorters, a yard management system for time slots. The maths works above roughly 200 pallets a day with a steady inbound stream.

Crossdocking is a "just in time" operation - every element has to fire on schedule because there is no buffer. Things that can stop the operation:

• An error in the ASN. Supplier sent an ASN for 24 pallets, only 22 arrived - two customers won't get their goods because their orders were pre-allocated to pallets that don't physically exist. The WMS has to detect this in 5 minutes, not 5 hours.
• Late delivery. Truck was due at 6:00, arrives at 11:00. The 14:00 outbound window for the recipient evaporates - either you extend the shift or the customer gets goods the next day.
• No buffer for mistakes. In a storage warehouse you fix a wrong receipt the next day. In crossdocking every mistake has to be fixed within an hour because the rest is moving.
• Dependency on the supplier. If the supplier mislabels a pallet or sends the wrong batch - your system has no way to correct that, because there's no time buffer or warehouse space to "wait until the supplier fixes it".

The classic layout is an "I" (long, narrow hall with inbound docks on one long side, outbound on the other) or a "U" (docks on one side, sorting in the centre). Practical dimensions:

• Dock-to-floor ratio. Roughly 1 dock per 800-1200 sqm of hall. So an 8000 sqm hall needs 8-10 docks per side.
• Floor. Rated for 8-12 ton forklifts (because they cross constantly with full pallets). Anti-slip, with no bumps over 2 mm across 3 metres.
• Docks and dock levellers. Hydraulic levellers 1-1.8 m, fast roll-up doors, dock seals (for cold and warm). Without those the truck can't dock cleanly and loading/unloading drags out by 30%.
• Sorters and conveyors (optional). In high-volume operations where small parcels from many suppliers go to many recipients, a 360-degree scanner conveyor with a cross-belt sorter can replace 8-10 people doing manual sortation.
• Yard management system. Without one, trucks pile up at the gate and crossdocking loses its time advantage.

A typical crossdock scenario from the system's perspective - for a pre-allocated operation where supplier goods are already mapped to customer orders:

• 1. ASN. 6 hours before delivery the system receives the ASN over EDI. It creates a planned receipt with the list of SSCCs and the contents of each pallet.
• 2. Routing. The system automatically matches ASN lines to open customer orders. Each pallet gets a target outbound dock assigned.
• 3. Receipt. Truck pulls up to the inbound dock. Operator scans the pallet SSCC. The WMS shows on the terminal: "dock B7" - operator drives the forklift there.
• 4. Sorting/staging. The pallet stays in the lane in front of dock B7, or (in larger operations) goes onto a sorter that automatically routes it to the right zone.
• 5. Bulk consolidation. If a customer order spans many pallets from various suppliers, the system groups them in one outbound zone and confirms completeness.
• 6. Dispatch. Outbound truck pulls up to dock B7, the operator scans pallet SSCCs during loading, the system issues the dispatch document.
• 7. Closure. Once the truck leaves, the system generates the despatch advice (DESADV), invoices and reports. Cycle closed.

The whole sequence fits inside 4-8 hours, in some operations (FMCG distributed to regional shops) even 2-3 hours.

It's a myth that crossdocking belongs only to big logistics operators. In practice a small distribution company (think a regional food distributor serving 30-50 shops) can run a successful crossdock model in a 1500-3000 sqm hall with 4-6 docks.

The entry threshold for SMEs is:

• a regular inbound stream from a few stable suppliers (5-15 companies)
• a regular outbound stream to dozens of customers (typically 30-100 shops or pickup points)
• a WMS capable of handling the transshipment mode and accepting an ASN
• supplier discipline in producing ASNs and GS1 labels

The most common entry path is to start with one route or one customer - say you pick a chain of 20 regional shops you supply 4 times a week and run only that stream as a crossdock. The rest stays in classic storage. Six months later, when the operation has bedded in, you add another customer. Evolution, not revolution.

• Too small a staging area. The hall looks big when it's empty. When 40 pallets sit at 9:00 waiting for sortation and suppliers are still unloading, it suddenly turns out there's nowhere to put them. Rule of thumb: the staging area should hold 1.5x the daily pallet volume.
• No ASN, or ASN after delivery. "They'll email us a file the morning of delivery" - that doesn't work. The ASN has to land at least 4 hours before truck arrival, so the system can process it and prepare routing.
• Mismatched shifts. Crossdocking typically has two peaks - morning receipts, afternoon/evening dispatches. An 8:00-16:00 shift won't cover both. You need either two shifts or a flexible roster with a mid-day break.
• Confusing crossdocking with storage. "We hold goods 3-4 days and call it crossdocking" - that's just short-term storage with all its costs. The 24-hour line isn't arbitrary; above it you have to record locations, control stock and allocate floor cost.
• No quality check at goods-in. "Since we don't store, we don't check" - wrong. A defective pallet caught at the recipient travels back through the entire chain. A quick visual check and SSCC-vs-ASN match at the inbound dock is non-negotiable.

Crossdocking pays off when you have high rotation, a steady inbound and outbound stream, a short decision chain and document discipline at the supplier side. The more the operation looks like a rhythmic mill (every day the same deliveries at the same hours to the same recipients), the better. The more surprises, the less point.

From 17 years of WMS deployments at Weaver Software, the most common path isn't "I'm building a crossdock from scratch", it's "I'm converting part of my existing warehouse stream into transshipment mode". Weaver WMS handles both modes in parallel - normally stored items next to in-transit ones, with a separate workflow for receipt, sortation and dispatch, and native support for ASN and GS1 labels. So you don't have to swap the system when the business evolves from pure storage into a crossdock hybrid.