Sales

Why "Pending" and "Dispatched" Are Different States for a Sale

An order that is written down but not yet loaded still counts as inventory. Here is why that distinction has to be built into the system, not just remembered.

28 August 2026 · 5 min read

A sale and a dispatch feel like the same moment if you've never had a system separate them. A customer orders, you write it down, the order is "sold." But a plant doesn't actually work that way, and treating a written-down order as the same event as goods leaving the gate is one of the more common reasons finished stock figures stop matching the yard.

Two different facts, two different moments

A sale is an agreement: a customer, a set of products, a rate, sometimes an amount received on the spot. A dispatch is a truck actually leaving with the goods. Between those two moments, the cases are still sitting in the yard. They're spoken for, but they haven't gone anywhere. If a system reduces finished stock the moment a sale is created, it's treating an intention as if it already happened.

Why this matters more than it sounds like it should

Say a plant takes five orders in a morning for the same product but only has stock to fulfil three of them once accounting for what's actually ready to load. If "sale created" and "stock reduced" are the same event, all five look fulfilled on paper, and the shortfall only surfaces at the gate, in front of a driver and a customer. Keeping the sale in a pending state until it's actually dispatched means that shortfall shows up in the system first, where it can be planned around, not discovered at the gate.

What actually changes at dispatch

Only two things happen when a sale moves from pending to dispatched: finished stock for that product comes down by the quantity sold, and the customer's outstanding balance goes up by the sale amount (less anything already received). Neither of those should happen earlier, because neither is true yet.

This applies just as much to a can or jar delivery business

A 20-litre can delivery business often runs on standing orders and periodic billing rather than one-off retail sales, but the same logic holds: a jar allocated to a delivery run isn't gone from stock until it's actually left. Keeping "sale" and "dispatch" separate is what keeps a delivery business's stock figures honest even when orders and actual loading happen at different points in the day.

The simplest test

If you can create an order and then decide, an hour later, that it needs to change before anything has physically moved, and that change costs you nothing to make, you have a system that separates the two states correctly. If changing an order after it's "sold" means untangling stock and balance movements that already happened, it doesn't.

See how sales and dispatch work as separate steps

Related

Bring your plant operations into one flow.

Start with a 14-day trial. No card is needed to try it, and nothing you record is ever deleted if a subscription lapses.