Dispatch runs off a spreadsheet
The loading plan is a file on one machine. If that person is out, the day starts by rebuilding it.
Dispatch
Dispatch reads the order, holds the stock, produces the paperwork and records what actually left. What was loaded and what was invoiced are the same list, because they come from the same record.
The problem
Dispatch is where an order stops being information and starts being goods on a vehicle. It is also where most businesses lose the thread.
The loading plan is a file on one machine. If that person is out, the day starts by rebuilding it.
A short shipment is agreed at the gate and communicated verbally. The invoice goes out for the full order anyway.
Three months later a customer disputes a delivery and there is nothing to point at but a signed paper note, if it can be found.
The vehicle is loaded and standing while a delivery note and a gate pass are typed up somewhere else.
Capabilities
Everything between a confirmed order and a delivery someone has confirmed receiving.
What goes out today, on what, in what order.
What was actually taken off the shelf.
Produced from the dispatch, so they cannot disagree with it.
What left, when, and what happened to it.
What is pending and what is stuck.
Workflow
Each stage records what happened rather than what was planned to happen.
A dispatch moves through six stages: confirmed sales order, dispatch plan, picking, loading, gate-out and delivery.
01 Sales order
DN-2026-0412
Confirmed
02 Dispatch plan
DN-2026-0412
Planned
03 Pick
DN-2026-0412
Picked
04 Load
DN-2026-0412
Loaded
05 Gate out
DN-2026-0412
Dispatched
06 Delivery
DN-2026-0412
Delivered
Use cases
A plan built from confirmed orders each morning, with picking and loading recorded as they happen rather than written up afterwards.
Proof of delivery held against the dispatch, with the date, the receiver and any exception, so a query months later has a record behind it.
Each branch dispatches from its own stock under its own permissions, while the order and the customer stay shared.
Works with
These read and write the same Core OS records, so a handover between them passes a reference rather than a retyped copy.
Quotations, price lists and the order everything downstream reads.
Real-time stock across warehouses, batches and serial numbers.
Trips, carriers and freight cost allocated to what moved.
Import and export orders with their documentation and landed cost.
FAQ
Usually, and that is the point — the dispatch reads the order rather than repeating it. Dispatches not tied to a sale, such as branch transfers or returns, are handled too.
The dispatch records what actually loaded. The order keeps the balance open, the unshipped stock is released or stays reserved as you decide, and the invoice is raised on what left rather than on what was ordered.
Yes, from the dispatch record itself, so the document and the movement cannot disagree. Reprints are tracked, which matters when a note is reissued at the gate.
Delivery confirmation is a stage on the dispatch, carrying the date, the receiver and any exception raised, so it is part of the record rather than a piece of paper in a file.
Have a different question? Talk to us.
We will run the same day through the platform, from the morning plan to the last gate pass.