> 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/service-sales-products.md).

# Service sales products

Saving the Service extension creates the products that service sales are booked on, one pair per VAT code.

**When a service order is billed, its parts and work are booked on service sales products: two per VAT code, created for you when you save the Service extension.**

The products are ordinary products. You can rename them to your own names.

***

## Which products are created?

For every VAT code in the tenant's country, two products:

| Product        | Name (English tenants) | SKU                    | Carries                                   |
| -------------- | ---------------------- | ---------------------- | ----------------------------------------- |
| Goods          | Goods                  | `SERVICE-PARTS-{rate}` | Parts that are stock products             |
| Work and other | Work and other         | `SERVICE-WORK-{rate}`  | Work, and goods you do not track in stock |

`{rate}` is the VAT rate, such as `SERVICE-WORK-25`. If two VAT codes share a rate, the later one gets `-2`, then `-3`. The names follow the tenant's language, for example **Varer** and **Arbeid og øvrig** in Norwegian.

The products get the brand **Service** and a product group **Service**, and are created as <kbd>No Stock</kbd> products with **Allow order-specific cost** on. No price is set: the price comes from the service order.

Every VAT code gets products with the same two names. The SKU is what tells them apart, so you will likely want the rate in the name, such as **Work and other 25%**.

***

## When are they created?

When you save the Service extension as active in Flow Admin: **Settings → Extensions**, the Service card, **Active**, **Save**. See [Get started](https://docs.flowretail.com/docs/service/get-started.md).

* **Every active save fills what is missing** and changes nothing that exists. A VAT code added later gets its pair the next time you save.
* **Nothing is created** when the extension is first added, when you switch it off, or when you save it for a single store.
* **If the save is refused,** nothing is created. Fix what the message says and save again.

You need the **Extension Management** permission.

***

## Can I rename the products?

Yes. Flow Service finds the products by a link kept for each one, never by name or SKU, so a new name, SKU, brand or product group changes nothing. New sales order lines take the product's current name.

{% hint style="danger" %}

#### Do not change the type, order-specific cost or VAT code

If you change the product from <kbd>No Stock</kbd>, turn off **Allow order-specific cost** or give it another VAT code, every later save of the Service extension is refused, even one that only changes the portal address. Change it back to save again.
{% endhint %}

* **A product that has been used cannot be deleted.** Once it has order lines or service orders, it stays.
* **An unused product that you delete is created again** the next time you save the extension.
* **If you rename the Service brand or group,** a product created later gets a new **Service** brand and group.

***

## What happens when a service order is billed?

Flow Service books the case's items on a sales order: parts that are stock products on the Goods product of their VAT code, everything else on the Work and other product. That gives at most two lines per VAT code, each with quantity 1 and the summed price. The sales order is then confirmed.

If a product is missing, billing stops with <kbd>…is missing for this tenant. Saving the Service extension creates it.</kbd> Save the extension to create it.

These are not the products staff add to a service order. Those are your normal products, such as a spare part or the hour product for billing time.

*Last updated 19.10.2026*


---

# 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/service-sales-products.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.
