> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/service/statuses.md).

# Statuses

Statuses are your names for where a service order stands, and each one maps to one of nine fixed states that decide what Flow Service does with the order.

{% hint style="info" %}
Name statuses in your own words and map each to a state. The state decides what Flow Service does; changing it moves every order on the status.
{% endhint %}

Every service order has one of your statuses, and each status maps to one of nine fixed states. Filters, the portal, confirmations and turnaround figures follow the state, not the name.

Open **Settings → Statuses**. It needs the **Service configuration** permission (see [Permissions and roles](https://docs.flowretail.com/docs/service/permissions-and-roles.md)).

![Settings → Statuses with several state cards, one state showing 'No status maps to …', one deprecated row, message badges on a row](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FPAUItoAw6rC3wfiPoAXS%2Fservice-statuses-list.webp?alt=media)

***

## The nine states

| State                           | Meaning                                                                  | What it changes                                                                                                                                                                                                                               |
| ------------------------------- | ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <kbd>Awaiting product</kbd>     | Registered, but the device hasn't arrived.                               | Can be the start status.                                                                                                                                                                                                                      |
| <kbd>Not started</kbd>          | The device is here and the work is queued.                               | Can be the start status.                                                                                                                                                                                                                      |
| <kbd>In transit</kbd>           | On its way between locations.                                            | —                                                                                                                                                                                                                                             |
| <kbd>In progress</kbd>          | The work is being done.                                                  | With **Customer must accept before work starts** on, an order can't enter this state until the terms are accepted (see [Terms and conditions](https://docs.flowretail.com/docs/service/terms-and-conditions.md)). Checklists can be answered. |
| <kbd>Waiting for customer</kbd> | Waiting for an answer from the customer, never for the device.           | Checklists can be answered. The portal highlights the status.                                                                                                                                                                                 |
| <kbd>Waiting for supplier</kbd> | Waiting for parts or a supplier's answer.                                | Checklists can be answered.                                                                                                                                                                                                                   |
| <kbd>Ready for pickup</kbd>     | The outcome is ready to hand over.                                       | Asks for unanswered job type checklists. The portal shows "Ready to collect at …" instead of the estimated date.                                                                                                                              |
| <kbd>Complete</kbd>             | The customer has the device back. This is the handover, not the payment. | **Closed.** Asks for checklists, warns about lines not billed or not paid, and confirms if the store asks to.                                                                                                                                 |
| <kbd>Cancelled</kbd>            | Ended without a completed repair.                                        | **Closed.** Confirms if the store asks to.                                                                                                                                                                                                    |

A **closed** order can't be edited, sent to another store, reassigned or quoted until it gets an open status, which reopens it. Closing deletes its secrets and sensitive form answers and makes the portal page read-only; **Portal link works after the service order is finished** in General settings sets how long the link lasts.

None of the prompts blocks the move. The store's switch is **Ask for confirmation before a service order is finished** (see [Stores](https://docs.flowretail.com/docs/service/stores.md)).

***

## The statuses list

One card per state, with its status count. Statuses are sorted by name within a card; you can't reorder them.

| Element                                   | Meaning                                                                                             |
| ----------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Status chip                               | The name in its colour. Click it to edit.                                                           |
| Second column                             | The customer-visible label, or <kbd>Same as the name</kbd>.                                         |
| <kbd>SMS</kbd> / <kbd>E-mail</kbd> badges | Messages the status sends. A crossed-out badge marked <kbd>Off</kbd> is switched off.               |
| <kbd>Deprecated</kbd>                     | Kept for the orders that already have it, but no longer offered when changing status.               |
| "No status maps to …"                     | No active status covers this state, so no order can be moved there.                                 |
| <kbd>Edit mapping</kbd>                   | Opens **Status mapping** (see below).                                                               |
| <kbd>New status</kbd>, row menu           | Create (on a card: in that state); <kbd>Deprecate</kbd> / <kbd>Reactivate</kbd>; <kbd>Delete</kbd>. |

If the start status sends no message, the page warns "Customers get no portal link: … sends no message." Its message is what carries the portal link.

***

## Status editor

![Edit status dialog with the four fields on the left and the Messages column on the right](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FLYMwtRsVasyE9fTh0ByQ%2Fservice-status-editor.webp?alt=media)

| Field                      | Meaning                                                                                                                                                                                            |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**                   | Required. What staff see. No two statuses can share a name.                                                                                                                                        |
| **State**                  | Required. The state the status maps to. Changing it moves every order on the status; see Changing or removing a status.                                                                            |
| **Color**                  | <kbd>No color</kbd> or one of 16 swatches. On a new status, picking a state fills in that state's colour until you choose one yourself. Changing the state of an existing status keeps its colour. |
| **Customer-visible label** | What customers read on the portal and in messages. Leave it empty to show the name.                                                                                                                |

On an existing status, the **Messages for …** column sets what the customer gets when an order reaches it: an SMS row and an E-mail row, each with **Text**, <kbd>On</kbd>/<kbd>Off</kbd> and <kbd>Delete</kbd>, plus **Attach paper** on e-mail. Rows save as you change them. See [Message texts](https://docs.flowretail.com/docs/service/message-texts.md).

The start status is not set here but under **Start status for new service orders** in General settings.

***

## What customers see

Customers see the customer-visible label, or the name if it is empty, on the portal and in messages. The portal badge is tinted by state, not your colour.

***

## Changing or removing a status

| Change                                                   | What happens to existing orders                                                                                                               |
| -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| Name, colour, customer-visible label                     | Shown everywhere straight away, past messages excepted.                                                                                       |
| State                                                    | Every order on the status moves to the new state. The statistics are recounted, past periods too. No message is sent and no terms check runs. |
| State into <kbd>Complete</kbd> or <kbd>Cancelled</kbd>   | Every order on it is closed at once, with the deletions described above.                                                                      |
| State out of <kbd>Complete</kbd> or <kbd>Cancelled</kbd> | Every order on it is reopened.                                                                                                                |
| <kbd>Deprecate</kbd>                                     | Orders keep the status. It is no longer offered.                                                                                              |
| <kbd>Delete</kbd>                                        | Only possible while no order, log entry or message rule uses the status. Otherwise you're offered <kbd>Deprecate instead</kbd>.               |

{% hint style="danger" %}
Moving a status into **Complete** or **Cancelled** closes every order on it and deletes their secrets and sensitive answers. Moving it back reopens the orders, but the deleted data doesn't come back. Flow Service doesn't ask for confirmation, in the editor or on Status mapping, so check the state before you save or drop.
{% endhint %}

The start status can't be deprecated or deleted, and its state must stay **Awaiting product** or **Not started**. Choose another start status, or clear the setting, in General settings first.

***

## Mapping old statuses

<kbd>Edit mapping</kbd> opens **Status mapping**: one panel per state with its statuses, a count of how many states have a status, and an info icon explaining each state. Use it to sort statuses carried over from before and fill any empty state.

| Control                 | What it does                                                                               |
| ----------------------- | ------------------------------------------------------------------------------------------ |
| <kbd>Move to</kbd>      | Moves the status to the state you pick and saves at once. Dragging the chip does the same. |
| <kbd>Add a status</kbd> | Shown on a state without an active status. Opens the status editor for that state.         |

A move here is the same as changing the state in the editor, with the same effect on orders. Deprecated statuses can't be moved, and a state with only deprecated statuses counts as empty.

![Status mapping with the coverage line, one empty state showing 'Add a status', and a Move to menu open](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FM2wFTTNScLM1Ls4czJV6%2Fservice-status-mapping.webp?alt=media)

***

## Good to know

* New tenants start with one status per state, named after it (Complete's is "Completed"). Rename them freely.
* If no start status is set, new orders start on your one active **Not started** status. With none, or several, registering a service order fails until you set a start status in General settings.
* When staff change an order's status, the choices are grouped by state. Deprecated statuses and the current status are left out.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flowretail.com/docs/service/statuses.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
