> 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/job-types.md).

# Job types

Job types split a service type into kinds of work, each with the checks made before handover and the products suggested when the work is priced.

**A job type is a kind of work under a service type, such as a screen replacement under phone repair. It carries the checklist staff answer before handover and the products Flow Service suggests on the service order.**

{% hint style="info" %}
**What you need:** the **Service configuration** permission, and at least one service type that is not deprecated. Only users with the permission see **Job types** in the settings menu. See [Permissions and roles](https://docs.flowretail.com/docs/service/permissions-and-roles.md) and Service types.
{% endhint %}

## Summary

|              |                                                                                              |
| ------------ | -------------------------------------------------------------------------------------------- |
| Where        | **Settings → Job types**, in the **Service orders** group                                    |
| Who can edit | Users with the **Service configuration** permission                                          |
| Layout       | Grouped under each service type, both sorted by name. Types without job types are not shown. |
| Each row     | Name, <kbd>Deprecated</kbd> when it applies, number of checkpoints and products              |
| Used by      | Intake, the service order, the order list's **Job type** filter, Statistics **By job type**  |

![Settings → Job types with two service type groups, rows showing checkpoint and product counts, one deprecated row](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FfVtUzbrIQAFLU3OaMAxM%2Fservice-job-types-list.webp?alt=media)

Click a row to edit it. The three-dot menu has <kbd>Deprecate</kbd> (or <kbd>Reactivate</kbd>) and <kbd>Delete</kbd>.

***

## Edit job type

<kbd>New job type</kbd> and clicking a row open the same dialog. <kbd>New job type</kbd> is hidden until a service type is active.

![the Edit job type dialog with a checklist of three checkpoints and two suggested products, one with a note](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FEE2KC2nPQYm5TLiSrzq8%2Fservice-job-type-editor.webp?alt=media)

| Field                  | Meaning                                                                                                                                                                                    |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Name**               | Required. Shown when staff pick job types.                                                                                                                                                 |
| **Service type**       | Required. Where the job type is offered. Only active types can be picked. Cannot be changed after the job type is created.                                                                 |
| **Checklist**          | Checks made before handover, asked in this order. <kbd>Add checkpoint</kbd> adds one; drag to reorder. Each needs text, and no two can read the same. No checklist means nothing is asked. |
| **Suggested products** | Offered as one-tap additions on orders with this job type. <kbd>Add product</kbd> searches the whole catalogue; <kbd>Add a note</kbd> says what it covers. Each product only once.         |

To move a job type to another service type, create it there and deprecate the old one.

***

## How job types reach a service order

* **At intake**, staff tick none, one or several job types of the order's service type. Deprecated ones are not offered.
* **On the service order**, staff change them under **Job types**. A deprecated job type the order has stays.
* **Suggested products** appear in **Parts and work** under **Suggested for (job type)**, for staff who can add lines. A tap opens the add dialog with the product picked; nothing is added by itself.

***

## The checklist before handover

![a service order moved to a Ready for pickup status, the Checklist before (status) dialog with one job type section, Pass and Fail per checkpoint, and Skip checklist](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2F4SiDj1OuDVflwMN1IyXZ%2Fservice-order-checklist-prompt.webp?alt=media)

While the work is under way (**In progress**, **Waiting for customer**, **Waiting for supplier**), staff can answer checkpoints on the service order's checklist card.

When staff move the order to a status in the **Ready for pickup** or **Complete** state, Flow Service first opens **Checklist before (status)**, one section per job type still owing its checklist:

| In the dialog                     | Meaning                                                                                                                                      |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| <kbd>Pass</kbd> / <kbd>Fail</kbd> | The answer per checkpoint. Ones answered on the card are shown, not asked.                                                                   |
| **Note**                          | Optional, saved with the entry.                                                                                                              |
| <kbd>Save and continue</kbd>      | Enabled when every checkpoint has an answer. Writes **Checklist completed** on the log with every result.                                    |
| <kbd>Skip checklist</kbd>         | Asks **Skip the checklist for (job type)?**, warning that the log will say nothing was tested. <kbd>Skip</kbd> writes **Checklist skipped**. |

When every section is saved or skipped, the status change continues, through any confirmation the move needs. If the card already answered every checkpoint, the checklist is recorded without the dialog. Both entries are not shown to the customer and name who saved or skipped. Moving to a cancelled status never asks.

A job type's checklist is asked once per order, even after the job type is deprecated.

***

## Deprecate, reactivate and delete

| Action                | What happens                                                                                                                                                      |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <kbd>Deprecate</kbd>  | One click. No longer offered at intake or on orders. Orders that have it keep it.                                                                                 |
| <kbd>Reactivate</kbd> | One click. The job type is offered again.                                                                                                                         |
| <kbd>Delete</kbd>     | Asks you to confirm. Cannot be undone. Refused while an order has the job type or its checklist is on a log; the dialog then offers <kbd>Deprecate instead</kbd>. |

***

## Good to know

* A changed checklist applies to checklists saved afterwards. On open orders, a reworded checkpoint reads as unanswered and a removed one's answer disappears. Entries already on the log never change.
* A service type turned into a job type brings only its name. Add the checklist and products here.


---

# 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/job-types.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.
