The instructions are somewhere in an email.
The warehouse has an item list but no site contact, urgency or payment status. A long dispatch template is bypassed because filling it in feels slower than packing the order.
Solution 05 · Dispatch & delivery
Make every order’s priority, release status and delivery progress visible. Connect sales, the warehouse and freight around one handoff, so chasing an update does not become another job.
Where work gets stuck
The warehouse has an item list but no site contact, urgency or payment status. A long dispatch template is bypassed because filling it in feels slower than packing the order.
The cheapest carrier for a small box may be wrong for a long load or remote destination. Rough quoting dimensions become a booking price, and missing service requirements appear as extra charges.
A label exists, so everyone assumes the order left. Later, a consignment stalls in a depot. There is no named owner watching the exception or telling sales what has changed.
How we would build it
Operational status comes from confirmed actions. A forecast arrival and a confirmed delivery remain distinct.
Bring in the items, site contact, required date and carrier cutoff. Verify release status and warehouse availability.
Check before proceeding. Payment hold, missing address, unavailable item or missed cutoff? Put the order in an owned exception queue and agree the next step.
Confirm the actual items, dimensions and weight.
Use account rates, required arrival and access requirements.
Confirm the service, cost and consignment reference.
If the path stopsRate or ETA unavailable: request confirmation; never present an estimate as a booked service.
Verify collector or route, quantities and timing.
Link the pickup confirmation or delivery record to the order.
If the path stopsNo-show or changed destination: retain the open task and notify the order owner.
Confirm what can ship, what remains and any extra freight.
Link each shipment to its order lines and the remaining balance.
If the path stopsA part shipment must not mark the whole order delivered.
Update the linked shipment and stock through the ERP workflow. Feed finance the dispatch evidence. Route late or failed delivery events to an owner for a reviewed customer update.
Built around your business
Track readiness after the required inspection, finish or subcontract operation. Packing, certificates and delivery arrangements belong to the same handoff as the completed job.
Account for oversize loads, depot collection, unloading equipment and site access. A cheaper service that cannot meet the customer’s operational need is not the right recommendation.
We first assess native shipment management, warehouse tools and carrier integrations. A shared dispatch view should reference those records rather than become a second inventory ledger. When a carrier lacks reliable integration access, a clearly assigned manual confirmation is better than a misleading live status.
A useful result is measurable
We define the measures before the build, then review them with the people using the workflow.
Before we begin
We can compare available options, but price is only one input. Service coverage, lead time, load restrictions and handling requirements matter. Your team approves the booking.
Coverage depends on the carrier and available tracking data. We show the latest known event and its time, flag stale information and assign follow-up when an update is missing.
Not necessarily. Existing ERP shipment functions and warehouse tools may already provide most of the workflow. We configure and connect those before proposing another interface.
Start with the audit
We trace the process with your team, check what the current tools can do, and agree which improvement is worth building first.
Talk to us about your process