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

# Holidays

The days your stores are closed, which estimated ready dates skip.

The holiday calendar lists the days your stores are closed. When staff register a service order, the suggested estimated ready date skips these days and every Saturday and Sunday.

|                       |                                                                                                                                                                                                                                                                     |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Where                 | **Settings → Holidays**, in the **Company** group                                                                                                                                                                                                                   |
| What it affects       | Only the estimated ready date suggested at intake, worked out from the service type's **Expected turnaround** (see [Service types](https://docs.flowretail.com/docs/service/service-types.md) and Stores). It closes no store, holds no work and stops no messages. |
| Public holidays       | Added automatically for each active store in Norway, Sweden, Denmark, Finland or Germany, following the store's country                                                                                                                                             |
| Your own closure days | Apply to every store                                                                                                                                                                                                                                                |
| 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).                                                                         |

***

## The calendar

The calendar shows one year at a time, and opens on the current year in your company's time zone. Use the arrows beside the year in the header to step between years.

![Settings → Holidays for the current year: public holidays listed, one own day with Country 'Own', one public holiday with Closed switched off and greyed](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2Fep9I0zIjG0CyBtDdnXHQ%2Fservice-holidays-year.webp?alt=media)

| Column      | Meaning                                                                                                                                                                         |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Date**    | The day.                                                                                                                                                                        |
| **Name**    | The day's name. Public holidays come named in the country's own language, for example "Grunnlovsdag". Select the name to rename the day.                                        |
| **Country** | The country code of the public holiday, for example `NO`. **Own** for a day you added.                                                                                          |
| **Closed**  | <kbd>On</kbd>: the day is skipped. <kbd>Off</kbd>: the day counts as an ordinary working day, and the row is greyed. Turn it off for a public holiday your stores work through. |

The row menu has **Rename** for every day, and **Delete** for your own days only.

## New closure day

Choose **New closure day** to add a day of your own, such as a staff day or a stocktaking day.

![the New closure day dialog with a date chosen and a name filled in](https://593715853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0GCVniU8V4PZKEK4axWz%2Fuploads%2FNqr020aaHsEufIrJeLvx%2Fservice-holidays-new-day.webp?alt=media)

| Field    | Meaning                          |
| -------- | -------------------------------- |
| **Date** | One day. A past date is allowed. |
| **Name** | Required.                        |

The day is added with **Closed** <kbd>On</kbd> and applies to every store.

***

## Good to know

* **Public holidays are added once per year.** They are filled in the first time someone opens a year, or when an estimated ready date reaches into it. After that, your renames and **Closed** switches are kept and never written over.
* **A public holiday applies to the stores in its country.** A store's country is the **Country** set in Flow Admin under **Stores → (store) → General → Location**. A store with no country gets your own days only. Your own days apply to all stores.
* **Public holidays can't be deleted.** Switch **Closed** off instead.
* **A day's date can't be changed.** Delete your own day and add it again on the right date.
* **One own day per date.** It can share a date with a public holiday.
* **Days don't repeat.** Each own day is a single date, so add recurring closures again for each year.
* **Changes don't move existing dates.** Service orders keep the estimated ready date they were given. Staff can also change the suggested date at intake.


---

# 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/holidays.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.
