Warehouse-to-transport guide
Unify the handoff—not just the navigation.
A shared menu does not make WMS and TMS unified. Allocation, package, label, load, milestone, proof, charge, exception, and ownership must remain correlated from warehouse promise through transport settlement.
The operational spine
Follow one order across both domains.
Order, stock, service, delivery constraint.
Allocate, pick, consolidate, pack.
Rate, service, funding, label.
Load, route, tour, driver, carrier.
Milestone, exception, POD, signature.
Charge, invoice, audit, claim, margin.
Integration tests
Break the warehouse-to-transport handoff.
Invalidate the stale rate.
Change dimensions or weight after quoting and verify the old quote cannot buy a mismatched label.
Return one label outcome.
Submit the same idempotency key twice and interrupt after funding reserve.
Keep the order recoverable.
Retain package, quote, funding, error, retry, carrier option, and operator ownership.
Do not overwrite stronger evidence.
Normalize source time, confidence, sequence, and correction instead of regressing the shipment silently.
Keep delivery commercially open.
Separate delivered status from accepted proof, invoice release, claim window, and customer communication.
Trace the variance.
Compare contract, quote, shipment facts, accessorial evidence, carrier invoice, tolerance, and recovery action.
Data model questions
Do the domains share identity or copy text?
Package and pallet lineage
Warehouse carton, handling unit, dimensions, weight, contents, label, and shipment package remain linked.
Leg, stop, load, and tour
Transport execution names sequence, mode, executor, custody, plan, actual time, and evidence.
Separate lifecycle ownership
Order, fulfilment, shipment, label, tender, tour, proof, invoice, and claim states do not collapse into one ambiguous status.
Sell, buy, and pass-through
Client sell price, carrier buy cost, usage charge, tax, invoice, settlement, and margin retain separate provenance.
Control tower
See the exception without leaving its warehouse context.
Dispatchers and supervisors need active loads, vehicles, milestones, delays, and recovery beside package and order truth—not a spreadsheet export from last night.
- Warehouse readiness before dispatch.
- Shipment and route exception ownership.
- Delivery proof and financial close.
