Wholesale order lifecycle
The wholesale order lifecycle in Serat: draft, submitted, confirmed, shipped, delivered and cancelled, with payment status tracked separately.
A wholesale order carries two independent states: where it is in the fulfilment process, and whether it has been paid. Keeping them separate matters, because in wholesale a confirmed order that is not yet paid is completely normal.
Fulfilment states
Status | Meaning |
|---|---|
Draft | The buyer is still building the order. Nothing is committed. |
Submitted | The buyer has sent it. The seller now owns the next step. |
Confirmed | The seller has accepted it, including quantities and prices. |
Shipped | The goods have left. |
Delivered | The goods have arrived. |
Cancelled | The order will not be fulfilled. |
Payment state
Payment status is tracked on its own, so an order can be shipped and unpaid, or paid and not yet shipped, without either fact being distorted to fit a single combined status.
What each transition should mean in practice
Submitted. Treat this as the clock starting. A buyer who does not hear anything after submitting will call.
Confirmed. This is the commitment. Confirm what you can actually ship rather than the whole request, and reflect changes in the order itself so the buyer sees them.
Shipped. Attach the tracking information here, so the buyer stops asking where the order is.
Delivered. Useful for measuring your own lead times honestly.
Cancelled. Better than leaving an order confirmed and unfulfilled indefinitely.
Reconciliation
After changing an order, check its current state in both the portal and the retail workspace. If the two views disagree for longer than expected, ask an administrator to investigate before making the same change again.