What you can modify on a stage
Add a stage
1
Go to Pipeline
From the navigation, open Pipeline.
2
Click 'Add a stage'
A form opens with the fields to fill.
3
Fill in the information
- Name: short and clear (e.g. “Waiting supplier”)
- Color: choose a color distinct from neighboring stages
- Position: where in the flow to insert it
- Standard state: choose the system state it represents, or leave empty for a purely logistical stage
4
Save
The stage appears immediately in the Kanban and in all lists.
Rename a stage
You can change the name of a stage at any time, without impact on orders or indicators.1
Open the stage
In Pipeline, click the stage to modify.
2
Modify the name
Change the label. All views (Kanban, table, badges) update instantly.
3
Save
No order is moved — only the label changes.
Renaming never breaks indicators or automations: it’s the standard state that counts, not the name.
Reorder the stages
1
Reorganization mode
In Pipeline, activate the overview (all stages displayed in a list).
2
Drag and drop
Grab a stage and move it to the desired position. The others reorganize automatically.
3
Save
The new order is applied everywhere: Kanban, tables, lists.
Deactivate a stage
If you want to stop using a stage without losing history, deactivate it rather than delete it.- The stage disappears from the Kanban and from move menus.
- Orders that were in it remain visible in the table and reports.
- You can reactivate it at any time.
Delete a stage
1
Open the stage
In Pipeline, click the stage to delete.
2
Check the history
Sendocki tells you how many orders have already transited through this stage. If history is important, prefer to deactivate rather than delete.
3
Click 'Delete'
Confirm the deletion. Orders currently present on this stage are moved to the adjacent stage.
Some rules to know
No more than 7-8 useful stages
No more than 7-8 useful stages
Beyond that, your Kanban becomes unreadable and processing slows down. If you feel the need to add a 9th stage, ask yourself if an existing stage couldn’t cover it.
At least one stage for essential states
At least one stage for essential states
New, Confirmed, Delivered and Cancelled must always have at least one associated stage. Otherwise some dashboard indicators cannot be displayed.
A stage cannot do everything
A stage cannot do everything
Avoid “catch-all” stages like “Various”. Better two clear stages than one ambiguous one.
The name must speak to the whole team
The name must speak to the whole team
Prefer labels everyone understands (“Confirmed”, “Shipped”) rather than internal jargon (“Phase 4”, “Stage B”).
Frequently asked questions
Can I have different stages per store?
Can I have different stages per store?
The pipeline applies to all your connected stores. If you have radically different flows, contact support to discuss your case.
What happens to orders when I delete a stage?
What happens to orders when I delete a stage?
They are automatically moved to the closest stage (generally the previous one). No order is lost.
Can I duplicate a stage?
Can I duplicate a stage?
Yes, by creating a new stage and giving it the same standard state (and same reason if applicable). Useful to manage several queues of the same nature.
What’s next?
Adjust a stage
Change a stage’s standard state without breaking your indicators
Kanban view
See your pipeline in action
