Statuses

Define your order pipeline — custom 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 requires the Edit statuses permission.

Adding a status

Click Add in the top-right corner. Each status has:

• Name (required).
• Order — only shown when editing an existing status; controls its position among the Kanban columns.
• Type — one of New, Active, Done, or Canceled. This isn't cosmetic: the type drives the Orders Analytics funnel (which buckets orders into new/active/done/cancelled), 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 newly created order starts in.
• Default Widget — marks this as the status assigned to orders created through the public widget/embed. Separate from Default, so walk-in orders created by your team and self-service widget orders can start in different places in your pipeline.
• 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 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.

The matrix is opt-in, but once you save any rule at all, it starts being enforced project-wide. With an empty matrix, every status can move to every other status. The moment you check even one cell and save, Configo switches to matrix mode: any status that has no explicit outgoing rule becomes a dead end — orders can enter it but can no longer be moved anywhere 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.

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 project-wide, 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 directly from this list, in the order you've set here.
• The Orders Analytics funnel groups by status type, not by individual status name.
• Default Widget status is what a configurator's public embed assigns to orders it creates — see Widget embedding & iframe API.