McKinsey research into mid-mile and last-mile handovers found that waste created at blind handoffs between shippers, dispatchers, third-party logistics providers, and carriers accounts for between 6% and 13% of carrier revenue.
Split shipments, cross-docking, and pool distribution are three different answers to the same question, which is what to do with freight that arrives configured for one destination and needs to leave configured for several. They are usually bought as three capabilities. They are executed at one point. What follows is what each flow requires, why most systems support them in isolation, and what a single platform needs to run all three.
What each of the three flows is
Cross-docking. Maersk defines it as a logistics process in which products move from the supplier or manufacturer directly to the customer, with minimal or no storage in between. Freight crosses the facility rather than resting in it.
Split shipments. A single inbound consignment is divided at the facility into multiple outbound shipments, each with its own destination, carrier, and commitment. Also described as deconsolidation.
Pool distribution. Less-than-truckload shipments bound for the same region are consolidated into a full truckload for linehaul, then deconsolidated at a regional pool point for final delivery.
MIXMOVE frames all three as the same operation viewed at different points in the network. Each one takes an inbound unit whose onward commitment is not what its inbound record says it is, and reassigns it. The reassignment is the operation. The flow name describes only where it happens.
Why they are usually treated as separate problems
The three flows entered logistics through different doors. Cross-docking came from retail replenishment. Split shipments came from parcel and freight forwarding. Pool distribution came from less-than-truckload carriers seeking linehaul density.
Each developed its own tooling, its own vocabulary, and its own place in the software stack. Cross-docking became a warehouse management system module. Pool distribution became a transport management system itinerary. Split shipments became an order management function.
The operational reality never respected that division. All three happen on the same dock, frequently to the same trailer.
Why buyers are now asking for all three together
Order profiles have fragmented. A single inbound trailer routinely contains freight destined for regional consolidation, direct store delivery, and individual customer split, and the correct treatment differs per pallet.
Cost pressure has removed the tolerance for running three parallel processes. Deloitte found that 66% of retail executives surveyed plan to restructure their supply chains if input costs rise, and that 30% already use AI for supply chain visibility, rising to an expected 41% within a year.
Compliance has raised the cost of an incomplete record. Under CSRD, transport emissions require traceable activity data. A movement reassigned in one system and reported in another produces a figure that cannot be defended.
What existing stacks cannot do
Warehouse management systems govern stored inventory. Freight that is not being put away sits outside their model, so cross-docking is handled as an exception rather than as a flow.
Transport management systems plan movement between locations. They can model a pool point as an itinerary step, but they do not see what physically arrives, so a split decision made on the dock is invisible to them until it has already happened.
Visibility platforms report position. They can confirm a trailer arrived and cannot change what leaves it.
The result is that the single most consequential decision in the network, which is what an inbound unit becomes on the way out, is governed by three systems and owned by none. That is the interface where the McKinsey handover waste is generated.
The five capabilities a single system needs
Item-level inbound identification. The system must know what is physically on the trailer before unloading, not what the advance shipping notice claimed at origin. Every downstream decision depends on this.
Commitment matching in real time. Each inbound unit must be matched against live outbound commitments at the moment of arrival, so that flow, split, and pool decisions are made against current network state rather than against a plan set days earlier.
A single reassignment model. Cross-dock, split, and pool must be outcomes of one decision process rather than three separate workflows. Where they are separate, freight is handled twice and reconciled manually.
Instruction delivery at the point of work. The dock team must receive the sortation instruction where the work happens. A decision correct in a planning system and absent on the dock floor is not a decision.
A continuous execution record. Every reassignment must be captured as it occurs, at item level, with the resulting record available for billing, service measurement, and emissions reporting without reconstruction.
The three layers where the decision is made
Execution layer. Physical identification, sortation, and load confirmation on the dock.
Orchestration layer. Commitment matching, reassignment logic, and instruction delivery across sites.
Intelligence layer. The record produced by the first two, structured for billing accuracy, service performance, and Scope 3 transport reporting.
Most stacks have the first and the third. The missing layer is the second, which is the only one that can decide between the three flows while the freight is still on the dock.
What the evidence shows
McKinsey attributes between 6% and 13% of carrier revenue to waste at handover points, with dwell time named as a leading driver.
Deloitte reports that 59% of executives surveyed anticipate positive return on investment from supply chain AI initiatives within 12 months.
Across MIXMOVE deployments, hub operations have recorded up to 130% higher warehouse hub throughput, up to 80% fewer errors, up to 50% less warehouse space, and up to 58% labour cost savings. Fill rate improvements of 10% to 20%, dwell time reductions of 40%, and up to 15% more billable output have been recorded. The platform is in use across 35+ distribution companies in 20+ countries.
At 3M, a decade of collaboration produced a 35% reduction in transport costs, a 50% reduction in CO₂ emissions, and a 90% truck fill rate.
“By using the MIXMOVE software, 3M managed to reduce transport costs by 35% and CO₂ emissions by 50%.”
— Patrick Van De Vyver, Former Head of EMEA Logistics Operations, 3M
How MIXMOVE HUB OS governs the shared decision point
MIXMOVE HUB OS is purpose-built for the orchestration layer. Inbound freight is identified at item level on arrival and matched against live outbound commitments before unloading decisions are made. A unit with a full-load regional commitment is pooled. A unit with multiple destination commitments is split. A unit with a confirmed onward departure is cross-docked. The three flows are outcomes of one decision rather than three processes.
Sortation instructions surface at the point of work, so the decision reaches the dock floor while the freight is still there.
MIXMOVE HUB OS runs alongside an existing TMS, WMS, or ERP as an orchestration layer, or as a standalone platform where no system currently governs the dock.
MIXMOVE DI takes the execution record and structures it for network-level reporting, including Scope 3 transport reports built to ISO 14083 methodology, which supports CSRD disclosure and ETS2 exposure calculation from operational data rather than from estimates.
The three flows share one decision point. Governing it in three systems is what generates the handover cost. Governing it in one turns the dock into a network instrument.
Book a MIXMOVE HUB OS walkthrough to see split, cross-dock, and pool decisions made on a single inbound trailer.
Frequently asked questions
What is pool distribution?
Pool distribution consolidates less-than-truckload shipments bound for the same region into a full truckload for linehaul, then deconsolidates them at a regional pool point for final delivery. It reduces linehaul cost per unit and the number of consignments in transit.
How do split shipments, cross-docking, and pool distribution relate to each other?
All three reassign an inbound unit to a different outbound configuration. Cross-docking moves it straight through, splitting divides it across multiple destinations, and pooling combines it with other freight for a shared linehaul. They are variations of one decision, not three separate capabilities.
What should a system support to run all three?
Item-level inbound identification, real-time matching against live outbound commitments, a single reassignment model covering all three flows, instruction delivery at the point of work, and a continuous execution record available for billing and emissions reporting.
Does this replace an existing TMS or WMS?
Not necessarily. An orchestration layer governs the dock decision and passes the result to the systems that plan freight and manage inventory. MIXMOVE HUB OS operates alongside an existing TMS, WMS, or ERP, or as a standalone platform.
