Receiving & dispatch
Three fictional scenarios show how a cross-dock, a parts store and a consolidation desk connect transport with usable receiving information. They are planning examples, not available facilities.
Short-dwell transfer example
Quay Cross-dock is a fictional operating scenario, not a physical warehouse offered for hire. Its purpose is to show the short interval between a terminal handover and an onward regional delivery. The example avoids a capacity claim: the load is accepted into the plan only after access, handling and a receiving window have been reviewed.
Read the scenarioLocation contextSpare-parts receiving example
Inland Parts Store is a fictional scenario for industrial replacement stock. It distinguishes a vehicle reaching the site, a package being received and a part being available for use. Those events can occur at different times and should not share one ambiguous status.
Read the scenarioLocation contextSupplier grouping example
Strait Consolidation Desk is a fictional receiving and grouping scenario. It asks whether several supplier orders are ready for the same movement, rather than assuming that a common destination makes them compatible. The site offers no physical handling location or published consolidation schedule.
Read the scenarioLocation contextA package count needs the identifiers and condition questions that make it useful to the receiving team. Keep a discrepancy visible until its designated owner resolves it.
An onward plan needs a release decision, destination and receiving slot. Movement and availability should remain separate even when the time between them is short.