Skip to content

Dispatch

From confirmed order to gate-out, in one sequence.

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

The gap between sold and shipped.

Dispatch is where an order stops being information and starts being goods on a vehicle. It is also where most businesses lose the thread.

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.

What left is not what was ordered

A short shipment is agreed at the gate and communicated verbally. The invoice goes out for the full order anyway.

No proof of what went out

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.

Loading waits on paperwork

The vehicle is loaded and standing while a delivery note and a gate pass are typed up somewhere else.

Capabilities

What the Dispatch app covers.

Everything between a confirmed order and a delivery someone has confirmed receiving.

Planning

What goes out today, on what, in what order.

  • Dispatch plan
  • Priority
  • Consolidation
  • Vehicle assignment
  • Scheduling

Picking and loading

What was actually taken off the shelf.

  • Pick list
  • Batch and serial capture
  • Loading sheet
  • Short shipment
  • Verification

Documents

Produced from the dispatch, so they cannot disagree with it.

  • Delivery note
  • Gate pass
  • Packing list
  • Transport documents
  • Reprints

Execution

What left, when, and what happened to it.

  • Gate-out
  • In transit
  • Proof of delivery
  • Returns
  • Exceptions

Visibility

What is pending and what is stuck.

  • Dispatch status
  • Pending dispatch
  • Daily dispatch report
  • Per-branch view

Workflow

One dispatch, six stages.

Each stage records what happened rather than what was planned to happen.

Order to delivery

A dispatch moves through six stages: confirmed sales order, dispatch plan, picking, loading, gate-out and delivery.

  1. 01 Sales order

    DN-2026-0412

    Confirmed

  2. 02 Dispatch plan

    DN-2026-0412

    Planned

  3. 03 Pick

    DN-2026-0412

    Picked

  4. 04 Load

    DN-2026-0412

    Loaded

  5. 05 Gate out

    DN-2026-0412

    Dispatched

  6. 06 Delivery

    DN-2026-0412

    Delivered

Use cases

Where it earns its place.

A warehouse dispatching daily

A plan built from confirmed orders each morning, with picking and loading recorded as they happen rather than written up afterwards.

Deliveries that get disputed

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.

Branches dispatching independently

Each branch dispatches from its own stock under its own permissions, while the order and the customer stay shared.

Works with

Dispatch on its own is useful. Connected, it is the point.

These read and write the same Core OS records, so a handover between them passes a reference rather than a retyped copy.

Sales

Quotations, price lists and the order everything downstream reads.

Read about Sales

Trade

Import and export orders with their documentation and landed cost.

Read about Trade

See the full catalogue

FAQ

Questions about Dispatch.

Does a dispatch have to start from a sales order?

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.

What happens on a short shipment?

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.

Can we produce delivery notes and gate passes from it?

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.

Is there proof of delivery?

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.

Show us a day of dispatches.

We will run the same day through the platform, from the morning plan to the last gate pass.