Why it exists
Each merchant names their stages differently. Here are three pipelines that mean the same thing:
For Sendocki, these are just labels. But to calculate a confirmation rate, the system needs to know: “which stages represent a confirmed order?”
That’s where the standard state comes in: these three stages are all associated with the “Confirmed” state. You keep label freedom, Sendocki keeps figure consistency.
The list of standard states
Sendocki uses 9 standard states that cover the entire lifecycle of an order:A stage without a standard state stays displayed in the Kanban, but it feeds no indicator and triggers no automation (stock, carrier, commissions). Useful for purely operational stages (e.g. “Preparation”).
Specify a reason
For three states — Cancelled, Delivery failure and Returned — you can specify a reason. It’s useful for your reports: knowing if your failures come from wrong addresses, unreachable customers, defective products, etc.- Cancellation reasons
- Delivery failure reasons
- Return reasons
- Customer refused the order
- Customer unreachable
- Address issue
- Duplicate order
- Price disagreement
What each state can trigger
When an order arrives at a stage associated with a standard state, here’s what Sendocki can do automatically:Essential states
For your dashboard to work correctly, at least one stage must be associated with each of these states:- ✅ New — to measure incoming volume
- ✅ Confirmed — to calculate the confirmation rate
- ✅ Delivered — to calculate the delivery rate and revenue
- ✅ Cancelled — to calculate the cancellation rate
What’s next?
Recommended stages
See concrete examples of stages and their states
Adjust a stage
Change a stage’s state safely
