> 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/developers/api-documentation/service/update-a-stores-service-settings.md).

# Update a store's service settings

Change this store's service settings, for this store alone. Every field is optional and a field left out keeps its value, so a client sends only what it changes; the full settings are returned, exactly as the read returns them. A serviceBannerExpiresAt that is not later than the server's clock when the update is handled is refused with a 400, and nothing is saved, unless serviceBannerText is or becomes empty. This is store-level service configuration and asks for SERVICE\_STORE\_CONFIG held at this store, at its organization or at the tenant, or SERVICE\_CONFIG, which is held at the tenant only — the same permissions the store's turnaround takes. A tenant-wide ADMIN grant counts as every permission. A caller holding neither at this store is refused with a 403, and a storeUid naming no store of the tenant with a 400.

Required permissions: SERVICE\_STORE\_CONFIG, SERVICE\_CONFIG

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Service","description":"Service"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"responses":{"ServiceStoreSettingsResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceStoreSettingsResponseSchema"}}}}},"schemas":{"ServiceStoreSettingsResponseSchema":{"title":"ServiceStoreSettingsResponseSchema","description":"The service settings of one store: the finish confirmation, the due-day nudge, the default service warehouse, whether open weekend days are working days, and the store's own banner for its service staff. They are store-level service configuration — written under SERVICE_STORE_CONFIG or SERVICE_CONFIG through the store's service settings operation, never through the store itself — and read under any service permission reaching the store, by whoever works service there or configures it.\nThe first two are the client's own: they change nothing on the server. The server acts on the next two — the default service warehouse decides which warehouse a stock part is taken out of when a line names none, and serviceCountWeekendsAsWorkingDays decides the store's working days. The banner is shown and nothing more, and the server ends it at serviceBannerExpiresAt.","type":"object","required":["tenantUid","storeUid","serviceWarnOnFinish","serviceDueDayWarningCount","serviceDefaultWarehouseUid","serviceCountWeekendsAsWorkingDays","serviceBannerText","serviceBannerExpiresAt"],"properties":{"tenantUid":{"$ref":"#/components/schemas/UID"},"storeUid":{"$ref":"#/components/schemas/UID"},"serviceWarnOnFinish":{"type":"boolean","description":"When it is on, the client asks the user to confirm before a service order is moved into a terminal state — COMPLETE or CANCELLED. It is the store's own guard against a slip, and it is the store manager who decides whether to have it: finishing a case is final, deleting its secrets and starting the clock on the customer's portal link, and a store that would rather be stopped once than undo that can ask to be. It changes nothing on the server — the confirmation is the client's, and the finish itself is refused or allowed on the same terms either way."},"serviceDueDayWarningCount":{"type":"integer","nullable":true,"description":"When at least this many service orders of any kind are already due on one day at this store, the client nudges the user who is putting a due date on a service order. null means the store has no such nudge.\nIt is the backstop across service types: a service type's own dueWarningCount only sees the service orders of that type, and this one sees the whole day whatever types the work is spread over.\nIt changes nothing on the server: the count is taken by the client through the service order counts endpoint the moment a due date is set or edited, and again whenever the date changes. Nothing is computed from this number, no submit is ever blocked by it, and no worker watches for a day that fills up later — that is what the due-today and overdue notifications and the due-sorted workspace lists are for."},"serviceDefaultWarehouseUid":{"type":"string","nullable":true,"pattern":"^[A-Za-z0-9_-]+$","description":"The warehouse a stock part is taken out of when a line added to a service order at this store names none. It names one of the warehouses the store owns, as it stood when the setting was written, or null when the store has chosen none; the fallback is then the store's own defaultWarehouseUid, used only when the store owns that warehouse too — a defaultWarehouseUid naming a central warehouse another store owns is skipped rather than used. A stock line that resolves to nothing is refused with a 400 and the client asks the technician to pick a warehouse. The read serves the uid as stored and never re-checks it.\nThis is the workshop's parts store, and it is the reason the setting exists: the drawer the technician reaches into is usually not the warehouse the shop floor sells from, and a store that keeps them apart sets this so that nobody has to name a warehouse on every part.\nUnlike the finish confirmation and the due-day nudge, this one changes what the server does. A part booked out of the wrong warehouse is a stock correction in two places, so the setting is not a quiet default: when the warehouse it names has been deleted, or has stopped belonging to this store, the next stock line is refused with a 400 naming this setting rather than falling back to the store's default warehouse. The refusal is the signal to fix the setting."},"serviceCountWeekendsAsWorkingDays":{"type":"boolean","description":"Whether a Saturday or Sunday the store is open counts as one of the store's working days. False when never set. The store's working days are the days of the week it is open — all seven when its openingHours has no openDays — less Saturday and Sunday unless this is true, and less the active days of the tenant's holiday calendar that apply to the store; they are the business days estimatedBusinessDays counts. This is what \"the store's working days\" means wherever readyAtEstimate, estimatedBusinessDays and avgWorkOpenDays are described."},"serviceBannerText":{"type":"string","description":"A notice for the service staff of this store alone, written by whoever configures the store's service settings, such as that the workshop closes early on Friday. It is shown beside the tenant's banner, serviceBannerText in the tenant's service settings, on the service screens worked at this store, and nowhere else. An empty string means the store has no banner, and it is what is served once the banner has ended (serviceBannerExpiresAt).\nIt is plain text and is to be rendered as plain text: no markup, no links, no formatting. Nothing follows from it beyond being shown — it filters nothing, blocks nothing, and never reaches the customer."},"serviceBannerExpiresAt":{"type":"string","format":"date-time","nullable":true,"description":"The moment the store's banner stops being shown, or null when it is shown until somebody takes it down. It is null whenever serviceBannerText is empty. A moment that reads 23:59:59 in the tenant's timezone is the end of that day and is shown as such, as readyAtEstimate is; any other moment is shown as its day and time.\nIt ends the way the tenant's banner does: a read at this moment or later serves serviceBannerText as an empty string and this as null, and a client drops an ended one at its next read or may take it down when its own clock reaches this moment."}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"ServiceStoreSettingsUpdateRequestSchema":{"title":"ServiceStoreSettingsUpdateRequestSchema","description":"The store's service settings to change. Every field is optional: a field left out keeps its value, so a client sends only what it changes.","type":"object","properties":{"serviceWarnOnFinish":{"type":"boolean","description":"Send true to have the client ask the user to confirm before a service order is moved into a terminal state — COMPLETE or CANCELLED, and false to let it finish without asking. It is the store's own guard against a slip, and it is the store manager who decides whether to have it: finishing a case is final, deleting its secrets and starting the clock on the customer's portal link, and a store that would rather be stopped once than undo that can ask to be. It changes nothing on the server — the confirmation is the client's, and the finish itself is refused or allowed on the same terms either way."},"serviceDueDayWarningCount":{"type":"integer","nullable":true,"description":"When at least this many service orders of any kind are already due on one day at this store, the client nudges the user who is putting a due date on a service order. Send null to switch the nudge off for the store.\nIt is the backstop across service types: a service type's own dueWarningCount only sees the service orders of that type, and this one sees the whole day whatever types the work is spread over.\nIt changes nothing on the server: the count is taken by the client through the service order counts endpoint the moment a due date is set or edited, and again whenever the date changes. Nothing is computed from this number, no submit is ever blocked by it, and no worker watches for a day that fills up later — that is what the due-today and overdue notifications and the due-sorted workspace lists are for."},"serviceDefaultWarehouseUid":{"type":"string","nullable":true,"pattern":"^[A-Za-z0-9_-]+$","description":"The warehouse a stock part is to be taken out of when a line added to a service order at this store names none. It must be one of the warehouses this store owns — the warehouses the store's own warehouse list returns — and any other value is refused with a 400, the empty string among them. Send null to clear the setting — that is the only way to clear it — after which a stock line that names no warehouse falls back to the store's own defaultWarehouseUid, but only when the store owns that warehouse too; when the store has none, or its defaultWarehouseUid names another store's central warehouse and is skipped, the line is refused with a 400 so the technician picks one. Left out, it keeps its value.\nUnlike the finish confirmation and the due-day nudge, this one changes what the server does: it decides which warehouse the stock actually leaves when nobody names one. A warehouse this store merely has access to is refused here, even though a line may name one explicitly — what a technician chooses deliberately and what the server picks on their behalf are held to different scopes on purpose, because the part a service order takes by default is the part on the bench."},"serviceCountWeekendsAsWorkingDays":{"type":"boolean","description":"Send true to have a Saturday or Sunday the store is open count as one of the store's working days, and false to leave Saturday and Sunday out of them. Left out, it keeps its value."},"serviceBannerText":{"type":"string","description":"A notice for the service staff of this store alone, shown beside the tenant's banner on the service screens worked at this store, and nowhere else. Send an empty string to take it down, which also clears serviceBannerExpiresAt. Left out, it keeps the value the read serves; an update applies to the banner as the read serves it (serviceBannerExpiresAt).\nIt is plain text and is rendered as plain text: no markup, no links, no formatting. Nothing follows from it beyond being shown — it filters nothing, blocks nothing, and never reaches the customer."},"serviceBannerExpiresAt":{"type":"string","format":"date-time","nullable":true,"description":"The moment the store's banner is to stop being shown. The client turns the day and time the user picks, in the tenant's timezone, into this moment: 12:00 today to have it shown until noon. A day picked without a time is sent as 23:59:59 on that day in the tenant's timezone, as for readyAtEstimate, to have it shown for the whole of that day. The tenant's timezone is timezone on the tenant, Europe/Oslo when none is set, as readyAtEstimate on the service order states. Any UTC offset is accepted and means the same moment. Send null to have it shown until somebody takes it down. Left out, it keeps its value.\nA moment that is not later than the server's clock when the update is handled is refused with a 400 and nothing is saved, unless serviceBannerText is or becomes empty: a moment that is not kept is not judged. The client's clock picks the moment and the server's clock judges it, so a moment a browser running behind still sees ahead can be refused.\nAn update applies to the settings as the read serves them. A serviceBannerText sent without serviceBannerExpiresAt keeps the moment the read serves: a banner edited while it is shown still ends at its moment, and a text sent after the banner has ended is shown until it is taken down rather than ending at once at the old moment. A moment sent while serviceBannerText is or becomes empty is not kept: the update is accepted and serviceBannerExpiresAt is served as null. After the banner has ended, an update that sends serviceBannerExpiresAt without serviceBannerText, null included, leaves the banner down; the ended text never comes back. An update that sends serviceBannerText or serviceBannerExpiresAt saves both, exactly as the response then serves them, so nothing of an ended banner stays behind to come back."}}}},"requestBodies":{"ServiceStoreSettingsUpdateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceStoreSettingsUpdateRequestSchema"}}}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/settings":{"put":{"summary":"Update a store's service settings","operationId":"put-serviceorders-settings-store","description":"Change this store's service settings, for this store alone. Every field is optional and a field left out keeps its value, so a client sends only what it changes; the full settings are returned, exactly as the read returns them.\nA serviceBannerExpiresAt that is not later than the server's clock when the update is handled is refused with a 400, and nothing is saved, unless serviceBannerText is or becomes empty.\nThis is store-level service configuration and asks for SERVICE_STORE_CONFIG held at this store, at its organization or at the tenant, or SERVICE_CONFIG, which is held at the tenant only — the same permissions the store's turnaround takes. A tenant-wide ADMIN grant counts as every permission. A caller holding neither at this store is refused with a 403, and a storeUid naming no store of the tenant with a 400.\n\nRequired permissions: SERVICE_STORE_CONFIG, SERVICE_CONFIG","responses":{"200":{"$ref":"#/components/responses/ServiceStoreSettingsResponse"}},"tags":["Service"],"requestBody":{"$ref":"#/components/requestBodies/ServiceStoreSettingsUpdateRequest"}}}}}
```


---

# 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/developers/api-documentation/service/update-a-stores-service-settings.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.
