The anatomy of a WhatsApp order

A WhatsApp order is not a single message; it is a small negotiation with several possible outcomes. Systems that treat it as a linear funnel break the moment a customer asks to change something. Teams need a way to track what is agreed and what happens next.

The nine states

1. 01Inquiry: a product question arrives in the shared inbox.
2. 02Quote: availability and price are confirmed (this is where manual sellers write numbers they later contradict).
3. 03Order created: the conversation becomes a record with an ID, not a chat memory.
4. 04Payment request recorded against the order, with an amount and reference.
5. 05Payment confirmed only after a verified provider event, not when a message says 'sent'.
6. 06Fulfilled: dispatched, handed over, or redeemed.
7. 07Delivered: with a timestamp that is not 'the rider said'.
8. 08Changed: quantity or item edits that keep the audit trail intact instead of starting a new chat thread.
9. 09Refunded or closed: the reason is recorded where the next agent can see it.

An order-level Paystack flow exists in Vendale's QA source. Do not assume it is part of the current public release unless the release record and Vendale team confirm the exact client/server pair and live provider path. No live provider transaction has been accepted; treat the flow above as implementation context until then.

Where each state breaks by hand

Quotes break when prices change mid-week. Order creation breaks when the order lives in six screenshots. Payment breaks when a till number is copy-pasted wrong. Fulfilment breaks when two agents both promise the last unit. Each of these is a state-machine problem wearing a people-problem costume.

The test

Open any order from last month. Can you see what was promised, what was paid, and what changed, in one place, in under ten seconds? If not, the states exist only in people's heads, and people take leave.