> 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/terms-and-conditions.md).

# Terms and conditions

The terms customers accept for their service order, and whether work waits for that acceptance.

Write your company's terms once, and every new service order carries them. Set **Customer must accept before work starts** to <kbd>On</kbd> if work must wait until the customer has accepted.

|                   |                                                                                                                                                                                             |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Where             | **Settings → Terms**, in the **Customers** group                                                                                                                                            |
| Applies to        | Every store and every service type. A service type can add text of its own (see [Service types](https://docs.flowretail.com/docs/service/service-types.md)).                                |
| Who can change it | Users with the **Service configuration** permission. Only they see the section in the menu. See [Permissions and roles](https://docs.flowretail.com/docs/service/permissions-and-roles.md). |

***

## Fields

![Settings → Terms with a terms text using bold and a bulleted list, a link filled in, and the acceptance switch on](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FxdnCgmeVEFK8okyraKDH%2Fservice-terms-settings.webp?alt=media)

| Field                                       | Meaning                                                                                                                                                                                                                                                     |
| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Terms text**                              | The wording customers accept. The toolbar has **Bold**, **Italic** and **Bulleted list**, and nothing else: no headings, links or numbered lists. Leave it empty for no terms text. You can also type `**bold**`, `*italic*` or `-` at the start of a line. |
| **Link to the terms**                       | For terms kept on your own website. Must be a full web address starting with `https://` or `http://`. Shown beside the text and printed on the service papers. A link on its own counts as terms.                                                           |
| **Customer must accept before work starts** | <kbd>Off</kbd> by default. While <kbd>On</kbd>, a service order with terms can't move to a status in the <kbd>In progress</kbd> state until the customer has accepted.                                                                                      |

Write the terms in the language your customers read. Every customer sees the same text, exactly as you wrote it, while the portal and the signing page around it follow the customer's preferred language, or your company's language when the customer has none.

With both fields empty, a service order has terms only when its service type has **Additional terms**, and the customer is asked to accept only those.

***

## When you save

* A save records a new version only when the text or the link has changed.
* A new service order gets the version in force when it is registered. Existing service orders keep theirs, and nobody is asked again.

## Additional terms per service type

Each service type can have **Additional terms** (see [Service types](https://docs.flowretail.com/docs/service/service-types.md)). On a service order of that type, they come after your company's terms, separated by a blank line. They have no link of their own, and they are versioned the same way.

If a service order moves to another service type before the customer has accepted, it takes the new type's additional terms. After acceptance, the terms stay as the customer accepted them.

***

## When acceptance is required

* The setting applies at once, to existing service orders as well as new ones.
* It holds every move into <kbd>In progress</kbd>, not only the first. A service order that leaves <kbd>In progress</kbd> can't come back without an accepted set of terms.
* It never takes a service order out of work. Voiding an acceptance on a service order that is already in progress leaves it there.
* Changing a status's state to <kbd>In progress</kbd> under Statuses is not held: service orders on that status move with it.
* A service order without terms is never held.
* With the setting off, the terms are still shown and can still be accepted.

While a service order is held, its **Terms** tab says "Work can't start until the customer accepts the terms."

***

## How customers accept

All three ways count the same. Each acceptance keeps a copy of the terms exactly as the customer saw them.

![a service order's Terms tab with the Record acceptance dialog open, showing the three choices](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FlnLS2adUC9QUNTJ4dyEO%2Fservice-terms-record-acceptance.webp?alt=media)

| Way            | Shown as           | What happens                                                                                                                                                                                                             |
| -------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Service portal | In the portal      | The customer opens the link in the message they were sent and taps **I accept the terms**.                                                                                                                               |
| Signature      | Signed on a screen | On the service order's **Terms** tab, staff choose **Record acceptance**. Then either **Sign on this screen**, or **Sign on a phone or tablet**, which shows a QR code that works for 10 minutes. The signature is kept. |
| In the store   | In the store       | Staff choose **Record acceptance → Accepted in the store** when the customer signed the printed confirmation or said they accept. No signature is kept.                                                                  |

* **Record acceptance** is only offered at the store that owns the service order.
* **Void** is only offered at the store that owns the service order, needs **Service configuration**, and asks for a reason. The customer is then asked to accept again.
* Changing the customer on a service order voids the acceptance and stops any QR code that is still open.


---

# 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/terms-and-conditions.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.
