01Define the consolidation policy
Name the work-order type, facility, policy, priority and effective dates. Define mandatory match fields and prohibited combinations. Microsoft documents shipment-consolidation policies that group order lines through controlled fields and filters; use that concept without assuming its system fields are universal. Decide whether existing open shipments may accept new lines, whether consolidation happens before or after warehouse release and when it locks. Separate same-customer shipment consolidation from transport hub consolidation and from sample consolidation across suppliers. Record the expected benefit—fewer packages, lower freight, route efficiency or customer preference—so exceptions can be evaluated against a clear purpose. Test the policy on edge cases before automatic release.
02Build a traceable candidate population
List source order, line, schedule, version, customer or owner, ship-to, item, quantity, unit, release status, requested date, delivery mode and packaging or document requirement. Confirm the lines are approved, not canceled, not already fully shipped and not on a blocking hold. Reconcile reservations and available inventory. Preserve customer requisition, contract or project references needed at receipt. When several lines appear identical, keep their source identities rather than merging quantity prematurely. If one order has lines for different modes, destinations or restrictions, split the candidate population before consolidation. Record why each included line passed and each excluded line failed the policy. This audit population prevents the consolidation engine from silently dropping a line.
03Check compatibility and capacity
Verify legal entity, consignee, address, route, carrier service, delivery window, Incoterm or commercial context where applicable, ownership, temperature, dangerous-goods classification, security, customs status, shelf life, stackability and customer labeling. Use qualified controls for regulated goods. Check vehicle, pallet, carton and handling capacity from supported measures; do not invent dimensions or weights. Confirm that early delivery for one order will not breach another order's requested window. Prevent goods for different customers from entering one customer-facing package unless the approved process explicitly separates them. A shared transport load can contain several shipments, while a consolidated shipment can contain several order lines; model those layers rather than treating load and shipment as synonyms.
04Allocate packages to source orders
Create consolidation ID, version and shipment hierarchy. Assign each item quantity to its source order line, then assign packed units to cartons, cartons to pallets or cages and those units to the shipment or load. GS1 EPCIS supports aggregation events for logistics units assembled for shipping; preserve additions and removals so the hierarchy remains current. Control mixed-SKU and mixed-order cartons with a packing map, unit counts and readable internal references. Decide how shared packaging, freight and handling charges are allocated without changing product quantities. Avoid one generic pallet line that cannot explain which customer order is inside. Confirm the receiving party can interpret the chosen hierarchy and documents.
05Align labels, documents and tracking
Generate the appropriate shipment, package and carrier references while preserving all source-order links. Check ship-to, consignee, route, package count, handling marks, customer references and required documents. A consolidated despatch advice can carry several order references when the trading relationship supports it; UNECE DESADV provides structure for orders, consignments, packages and items but is not a universal requirement. Decide whether one master tracking ID has child package IDs and communicate that hierarchy. Do not duplicate a source line across multiple documents after a retry. When one package is relabeled or moved, update its predecessor-successor link and affected control totals. Protect customer and commercial data on outward labels.
06Control change and deconsolidation
Lock the candidate set at the defined cutoff. If an order is canceled, held, changed, damaged, unavailable or assigned to another route, remove the exact line and packages through a new consolidation version. Recalculate capacity, package hierarchy, documents, labels, cost allocation and delivery promise. Preserve the old version and removal reason. Do not leave an empty source order reference on the shared shipment or allow a removed carton to stay on the load. When a whole consolidated shipment must split, create successor shipments and map each original package and line to one successor. Route partial quantities deliberately. Inform customer service or carrier when the change affects tracking, package count or delivery expectation.
07Reconcile shipment and delivery outcomes
Bridge each source line from ordered and released to consolidated, packed, loaded, shipped, delivered, returned, canceled or residual. Reconcile consolidated package counts to loading and manifest records. Trace from source order to shipment and tracking, then reverse from every package to source orders, customer and destination. Investigate missing allocation, duplicate line, wrong-customer package, residual staged carton, label mismatch and delivery exception. Monitor consolidation rate, packages saved, deconsolidation rate, wrong-merge incidents, residuals, late changes and claims without allowing savings to override accuracy. Compare promised and actual delivery by source order because a master shipment status can hide one failed child package. Close only when all source lines and package identities have supported final states.