The pipeline is the central piece of Sendocki. It’s the personalized sequence of stages an order goes through, from creation to delivery (or cancellation).Documentation Index
Fetch the complete documentation index at: https://help.sendocki.io/llms.txt
Use this file to discover all available pages before exploring further.
Why a customizable pipeline?
Every merchant has their own operational flow:- A COD store wants a “Call queue” stage between reception and confirmation
- A prepaid store skips directly from “Received” to “In preparation”
- A store with an internal fleet can add an “Assigned to driver” stage
- A drop-shipping store adds “Waiting for supplier”
Configure your pipeline — 3 modes
On first launch of Sendocki, or by going to Pipeline from navigation, you access the setup wizard. You have 3 options:- Mode — Choose a template (recommended)
- Mode — Customize (custom)
- Mode — Hybrid (template + adjustments)
Sendocki offers ready-to-use templates matching the most common use cases in Morocco:
- Standard COD e-commerce: Received → To confirm → Confirmed → In preparation → Shipped → Delivered → Collected
- Prepaid e-commerce: Received → Confirmed → In preparation → Shipped → Delivered
- Drop-shipping: Received → Confirmed → Waiting for supplier → Shipped → Delivered
- Internal fleet: Received → Confirmed → Prepared → Assigned to driver → On route → Delivered
Anatomy of a stage
Each stage of your pipeline contains:| Property | Description | Example |
|---|---|---|
| Name | Label shown in Kanban and badges | ”To confirm” |
| Color | Badge color — useful for visual scanning | 🔵 blue |
| Order | Position in the flow (1, 2, 3…) | 2 |
| Associated system state | What it represents for Sendocki | ”Awaiting confirmation” |
The associated system state ensures your KPIs, carrier automations, and revenue tracking work properly (e.g., only orders associated with the “Delivered” state count in your revenue).
Stock — link stages to stock movement
Sendocki can automatically decrement / increment your stock based on order progression in the pipeline.Best practices
- ✅ Start with a template: it covers 80% of cases — only customize after a few weeks of real usage
- ✅ No more than 7-8 stages: a too-long pipeline confuses the team and slows processing
- ✅ Distinct colors: facilitate quick Kanban reading
- ✅ Map ALL critical system states: otherwise the dashboard will be partially broken
- ❌ Avoid adding stages “just because” without real operational use case — each stage must have a concrete action associated
Modify your pipeline later
You can return to Pipeline anytime to:- Rename a stage
- Change a color
- Add a new stage
- Remove an unused stage
Frequently asked questions
Can I have multiple pipelines (one per store)?
Can I have multiple pipelines (one per store)?
Currently, Sendocki applies the same pipeline to all your connected stores. If you have radically different flows, contact support to discuss your case.
What happens to existing orders when I modify the pipeline?
What happens to existing orders when I modify the pipeline?
Existing orders stay at their current stage. If you delete a stage where orders are active, they’re automatically moved to the closest stage.
Does the pipeline impact my carrier integrations?
Does the pipeline impact my carrier integrations?
Yes — it’s the system state associated with each stage (not its name) that determines when Sendocki triggers carrier actions (package creation, label, tracking). As long as the association is correct, your integrations work.
What’s next?
Connect your store
Your pipeline is ready — time to connect your order source