Statuses
Set up your order funnels — their statuses, allowed transitions, required contact fields, and loss reasons.
Overview
Statuses are the stages of your sales/production pipeline — the columns on the Orders Kanban board. Configo doesn't ship a fixed pipeline; you define your own statuses, their colors, and (optionally) which statuses can follow which. Open Settings → Statuses in the project sidebar. Managing statuses and funnels requires the Edit statuses permission.
Every status belongs to one funnel. A new project has a single funnel — Main funnel — and all statuses live in it. If you run several independent processes (say, retail and wholesale), give each one its own funnel with its own statuses.
Funnels
A funnel is a separate set of statuses with its own order and its own transition rules. An order is in whichever funnel its current status belongs to. Contacts, members, warehouses and permissions are shared across the whole project — funnels don't split them.
Click the funnels icon in the toolbar to open the project's list of funnels:
- Type a name and click Add to create a funnel. A new funnel is empty — add statuses to it.
- Click a funnel's name to rename it; drag it by the handle to reorder the list.
- The star marks the default funnel. Click another funnel's star to make it the default — the previous one loses the mark. There is always a default funnel; you can only move the mark, not remove it.
- The trash icon deletes a funnel together with its statuses. You can't delete the project's last funnel, nor a funnel that still has orders (deleted ones don't count) — move those orders to another funnel or delete them first. If you delete the default funnel, the next one in order becomes the default.
Once there is more than one funnel, a switcher appears next to the icon: the status table, new statuses and the transition matrix all apply to the funnel selected there. The selection is shared with the Orders page and remembered per project.
Adding a status
Click Add in the top-right corner. The status is created in the funnel selected in the switcher. Each status has:
- Name (required).
- Order — only shown when editing an existing status; controls its position among the Kanban columns within its funnel.
- Type — one of New, Active, Done, or Canceled. This isn't cosmetic: the type decides how an order counts in Orders Analytics (funnel stages, the forecast pipeline, cancellations), and the Canceled type specifically triggers the loss-reason prompt described below.
- Color — a badge color, purely visual, used consistently across the Kanban board, the transition matrix, and order lists.
- Default — marks this as the status a new order created in this funnel starts in. Each funnel has one such status: marking another one removes the mark from the previous one.
- Default Widget — marks this as the status assigned to orders created through the public widget/embed. There is one such status per project — marking another status, even in another funnel, removes the mark from the previous one. If none is marked, widget orders get the Default status of the default funnel, or its first status if it has none. This way walk-in orders created by your team and self-service widget orders can start in different places — even in different funnels.
- Required contact fields — a list of your project's custom contact fields. Any field toggled on here must already be filled in on the linked contact before an order is allowed to move into this status — Configo blocks the move with an error naming the missing fields rather than letting the order enter incomplete. If your project has no custom contact fields yet, this list is empty; add some in Contacts first.
Click Save. Edit or delete an existing status with the icons on its row.
Transitions
By default, an order can move between any two statuses freely. Click the transitions icon (the two-way arrow) in the toolbar to open the transition matrix of the selected funnel and restrict this.
The matrix is a grid: rows are the current status, columns are the target status. Check a cell to allow moving from that row's status into that column's status; the diagonal (a status "transitioning" to itself) is always disabled since it's not a transition. Click Save to apply the whole grid at once. Saving only changes this funnel's rules — other funnels' matrices are left untouched.
The matrix is opt-in, but once you save any rule at all, it starts being enforced across the funnel. With an empty matrix, every status in the funnel can move to every other one. The moment you check even one cell and save, the funnel switches to matrix mode: any of its statuses that has no explicit outgoing rule becomes a dead end — orders can enter it but can no longer be moved anywhere within the funnel from there. If you want to restrict only some transitions, make sure every status you still want to move orders out of has at least one checked box, not just the ones you're trying to lock down.
This is what stops an order from jumping straight from Quote to Shipped, skipping production in between, once you've defined a proper pipeline.
The matrix only covers movement within a funnel. Moving an order into a status of another funnel is a separate action and is always allowed, regardless of any matrix (see Orders).
Loss reasons
Click the loss reasons icon (the tag) in the toolbar to manage the list of reasons an order can be marked lost for. This list is shared by the whole project and all its funnels, not per-status.
- Type a name and click Add to create a new reason.
- Click a reason's name to rename it inline; drag it by the handle to reorder the list.
- Click the trash icon to remove one.
Loss reasons only matter if you've added at least one. As soon as your project has one or more, moving an order into any status of type Canceled requires picking a reason (and optionally a note) before the move is allowed — Configo prompts for it right in the order panel. With an empty list, orders can move into a Canceled status with no reason required at all, since there's nothing to pick from. This is what makes the loss-reason breakdown in reports meaningful instead of a pile of unexplained cancellations.
Where this shows up elsewhere
- The Kanban board columns and the status filter on Orders are built from the statuses of the selected funnel, in the order you've set here.
- The Funnel report in Orders Analytics builds its stages from one funnel's statuses in their order; the other reports go by status type and can be filtered by funnel.
- In the "Order status changed" automation condition, statuses are grouped by funnel — see Automations.
- Default Widget status is what a configurator's public embed assigns to orders it creates — see Widget embedding & iframe API.