HomeBlogThe Vendor Order Lifecycle: 7 Stages From Placed to Paid
Operations

The Vendor Order Lifecycle: 7 Stages From Placed to Paid

Placed, confirmed, dispatched, delivered, invoiced, paid: every vendor order moves through the same stages. Naming them is the first step to never losing an order again.

10 min read

Ask ‘where’s my order?’ and you’ll get ‘it’s coming’ or ‘almost done’. Neither of those is a status. But every order you place moves through the same seven stages of the vendor order lifecycle, whatever the vendor and whatever the goods, and once you can name the stages, ‘where’s my order’ finally has a one-word answer.

The seven are Draft, Placed, Confirmed, Dispatched, Delivered, Invoiced, Paid. Nobody certifies this and there’s no methodology to buy. It’s just the honest sequence of what happens between deciding you need something and the money leaving your account. A restaurant ordering vegetables, a hardware store ordering cement, a salon ordering stock: same seven stages, different goods.

The seven stages at a glance

StageMeansWho moves it
DraftYou are still deciding what to orderYou
PlacedThe order has gone to the vendorYou
ConfirmedThe vendor has said yes, at a price and a dateVendor
DispatchedThe goods have left the vendorVendor
DeliveredThe goods arrived and were countedYou (whoever received them)
InvoicedThe vendor has billed youVendor
PaidThe money has gone outYou

Notice the alternation. You, you, vendor, vendor, you, vendor, you. An order is a conversation with turns in it, and most of the trouble in buying happens when nobody is sure whose turn it is.

Stage 1: Draft

A draft is an order you’ve started but haven’t sent. The kitchen manager walks the store cupboard on Wednesday evening and writes down what’s running low. Nothing has gone to the vendor, nothing is committed, nobody owes anybody anything. You move it forward by sending it.

The failure here is the draft that never got sent while everyone assumed it had. It’s the quietest failure in the whole lifecycle because there’s nothing to chase: no vendor waiting, no message thread, no trace at all. You find out on Saturday when the deliveries arrive and the one thing you actually needed isn’t among them.

The opposite failure is a business with no draft stage whatsoever, where every shortage turns into an instant WhatsApp message. That works fine until you’re sending the same vendor four separate messages a day, each one a separate order in his head, and the delivery charge arrives four times.

Has this been sent, or is it still on my list? That’s the question.

Stage 2: Placed

Placed means the order has left you and reached the vendor. For most small businesses that’s a WhatsApp message, a phone call, or a salesman who came by and wrote it in his own book. All three count. The format matters much less than the fact that somewhere there’s a written record of what you asked for, with a date on it.

A phone order with nothing written down is the weakest version of this stage, and it’s still everywhere. If you order by phone, send a one-line message afterwards: “Confirming today’s order: 20 bags cement, delivery Thursday.” Eight seconds, and it turns a future argument into a lookup.

Now it’s the vendor’s turn, and he moves the order on by confirming it. What goes wrong at this point is usually delivery in the postal sense rather than the human one: the message went to the wrong person, or to a number nobody watches, or at 11pm to a salesman who was off the next day. Placed doesn’t mean received. Two grey ticks tell you a message reached a phone, not that it reached anyone who intends to act on it.

So the thing to check is whether a person saw it. Not whether a handset did.

Stage 3: Confirmed

This is the stage everyone skips and everyone regrets skipping. An order isn’t real until the vendor says yes. “ok 👍” counts, honestly, because vendors are busy and a thumbs-up is how business gets confirmed in most of the world. Just write down when it came, andwhat they were saying yes to.

A real confirmation answers three things: yes we have it, this is the price, this is the date. Miss any one of the three and what you’re holding is an acknowledgement of receipt. The vendor who replies “👍” to an order for 30kg of coffee beans at last month’s price hasn’t agreed to last month’s price. He’s agreed that a message arrived.

The vendor moves this stage. You own the chasing. And the usual failure is silence read as agreement: you send the order, hear nothing back, and assume it’s handled because it usually is. Nine times out of ten you’re right, which is exactly what makes the tenth time so expensive.

What date did they commit to, and did they say a price?

Stage 4: Dispatched

Dispatched means the goods have physically left the vendor: loaded on a truck, handed to a courier, given to the delivery boy on his round. It’s the first stage where something moves in the real world instead of in a conversation.

Plenty of small businesses skip it, and for a same-day vegetable delivery that’s a reasonable call. It earns its keep the moment lead times run longer than a day, because a four-day-old order that’s confirmed but not dispatched is a completely different problem from one that’s dispatched but not delivered. The first needs a call to the vendor. The second needs a call to the driver.

The vendor moves it, usually with a message along the lines of “sent, vehicle no. …”. Watch out for “dispatched” used as a soothing noise: some vendors will tell you an order has gone out when it has been picked and is sitting in a corner of the warehouse. Ask for something checkable, a vehicle number or a docket number or the driver’s phone, and the answer tends to change quickly.

What’s the vehicle or docket number?

Stage 5: Delivered

Delivered means the goods arrived and someone counted them against what you ordered. Those are two separate events and the second one is what matters. A pile of boxes by the back door isn’t a delivery. It’s a pile of boxes.

Partial deliveries live here, and they’re the normal case rather than the exception. You ordered 50, the truck brought 42, and the only person who knows that is the person who signed for it. Record the received quantity per item, not just a tick. That record is your goods receipt note whether or not you ever call it that, and here’s what a GRN contains and how to handle short deliveries.

Whoever physically receives the goods moves this stage forward, which in practice is often the most junior person in the building at the busiest moment of the day. Design for that.

What goes wrong is predictable. The receiver signs the delivery note without counting, because the driver is double-parked and eleven other things are happening, and three weeks later the invoice bills the full quantity and there’s nothing to argue with.

How many actually arrived, of each item?

Stage 6: Invoiced

The vendor bills you. Sometimes the invoice comes with the goods, sometimes at month end, sometimes only when you chase it. Invoiced is where the order stops being about logistics and starts being about money.

Before an invoice moves to Paid it should agree with the two records you already have: what you ordered, and what arrived. That comparison is called three-way matching, which sounds far grander than it is. Three questions, ninety seconds. If the invoice bills 50 and your delivery record says 42, you’ve just found money.

The vendor issues it, you check it. The classic failure is the invoice that lands, goes into a pile, and gets paid at month end by someone who wasn’t there when the goods came. Then there’s the invoice that never arrives at all, which feels like a win right up until three months of them land together.

Does this bill match what we ordered and what we received?

Stage 7: Paid

The money has gone out, against a specific order, in a specific amount, on a specific date. The order is closed.

Paid is the easiest stage to record and the one most often recorded badly, because payments get made in batches. You transfer one amount covering six invoices from the same vendor, and the link between that payment and the individual orders lives only in the head of whoever made the transfer. Six weeks later the vendor says one of the six is still outstanding and you can’t prove otherwise.

Partial payments deserve the same treatment as partial deliveries: record what was actually paid against the order, not what was intended. You move this stage yourself, and the question worth answering while you still remember is which orders the payment covered.

The two axes: status vs acknowledgement

A stage moving forward and the other party agreeing that it moved are two different events. This is the bit that trips people up.

When you mark an order Delivered, you’re recording your view of the world, and the vendor hasn’t agreed to it. When the vendor marks it Dispatched, that’s his view, and you haven’t verified it. Most of the time the two views agree and nobody even notices there were two. The moments that cost money are exactly the moments they diverge: he says dispatched Tuesday, you say nothing arrived until Friday; you say 42 bags, he says 50.

So treat every stage as having two parts, who moved it and whether the other side acknowledged the move. You don’t need a system for that. You need the habit of a one-line reply. “Received 42 of 50 today, short 8 bags” is an acknowledgement, and it converts a future argument into a settled fact at the only moment when both parties still remember the truck.

One more bit of vocabulary. “Confirmed” belongs to a single stage, the vendor saying yes to the order. Everywhere else the word is “acknowledged”. Keeping those two apart is worth more than it sounds when three people are discussing the same order at once.

Where orders actually get stuck

Seven stages, and in practice almost all the losses happen in two gaps.

Placed but never confirmed

You sent it. Nobody said yes. Nobody said no. The order sits in a state of assumed progress until the day it was supposed to arrive, and then you find out it was never in anyone’s production plan. The order itself is the cheap part. The emergency is what costs you: buying the same goods locally at retail price, or telling a customer the job can’t happen on Thursday.

Delivered but never invoiced

The goods came, you used them, and no bill ever appeared. This one feels like free money and very much isn’t. Untracked liabilities pile up silently, then arrive as a single large month-end surprise, usually in the same month as something else expensive. Worse, by the time the invoice appears nobody can verify what was actually delivered, so you pay what it says.

The weekly review that catches both

Once a week, pull two lists:

  1. Orders placed more than 48 hours ago with no confirmation.
  2. Orders delivered more than two weeks ago with no invoice.

Then send two kinds of message: “Chasing confirmation on this, still coming Thursday?” and “Please send the bill for last week’s delivery.” Ten minutes, once a week. Pound for pound it’s the best-value habit in small-business buying, and it only works if your orders live somewhere you can filter by stage, which is the entire practical argument for having stages at all.

That’s what an order board does. Every order sits in one of the seven stages, and the two dangerous lists become two columns you glance at. OrderBookApp is built around this lifecycle, with WhatsApp sending attached to the Placed stage. The discipline still matters more than the tool: a whiteboard with seven columns beats a beautiful system nobody updates.

Making the stages stick

Getting a team to actually use stages comes down to three habits:

  • Keep the status in one place. If it lives partly in a chat, partly in a notebook and partly in someone’s head, it lives nowhere. Let the chat be the conversation and not the record. Here’s a practical system for orders placed over WhatsApp.
  • Whoever does the thing records the thing. The receiver marks Delivered, because he’s the only one who counted. Not the owner, later, from memory.
  • Statuses go forward. If an order has to move backwards, something went wrong that’s worth a note: a rejected delivery, a cancelled line. Record the reason, because those notes are the raw material for judging vendors later on.

That last point compounds. A year of stage data is also a year of vendor data: who confirms fast, who dispatches late, who short-delivers, who bills correctly. Turning that record into a simple vendor score is the natural next step once the stages are running.

Keep reading

Frequently asked questions

How is this different for services?
The middle stages compress. A plumber or a designer has nothing to dispatch, and "delivered" means the work got completed and checked rather than goods turning up. What still matters is Placed, Confirmed (agreed scope, price and date), Delivered (work accepted), Invoiced and Paid. For longer jobs, split the order into milestones and run each one through the same sequence. A half-finished job nobody has accepted is the services version of a delivery nobody counted.
Do I need all 7 stages?
No. Most small businesses run four: Placed, Confirmed, Delivered, Paid. Add Draft when you want to batch a day of shortages into one order instead of four messages. Add Dispatched once lead times run longer than a day and "where is it" needs two different answers. Add Invoiced the moment you have vendors who bill at month end rather than with the goods. Start with four and let the others earn their place, because a stage nobody updates is worse than no stage.
Who should update the status?
Whoever performs the action, at the moment they perform it. The person who sends the order marks it Placed. The person who receives the goods marks it Delivered, with the counted quantity. The person who pays marks it Paid. The usual failure is funnelling every update through the owner, who then does them all in a batch from memory on Sunday night, at which point the statuses are fiction and the team stops trusting them.
What if the vendor never confirms anything?
Some vendors will not reply and you cannot make them, so set your own rule instead. If there is no confirmation within a fixed window, 24 or 48 hours depending on your lead times, you call. The call is the confirmation, and you record it as one with the date and what was agreed. A vendor who repeatedly needs a chasing call is telling you something useful about how he will behave on the day an order actually matters.
#Order Lifecycle#Order Tracking#Operations
Share