> 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/set-the-expected-turnaround-for-a-service-type-at-a-store.md).

# Set the expected turnaround for a service type at a store

Set this store's own expected turnaround for a service type, in business days. It wins over the figure the service type carries for the tenant, for this store alone and for no other. Send null to clear the override, after which the service type's figure applies to this store again. Clearing is the only way back to the tenant figure; there is no delete. The resolved turnaround is returned, exactly as the read returns it, so what now applies and the level it resolves at are known without asking again.

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":{"ServiceTypeTurnaroundResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceTypeTurnaroundResponseSchema"}}}}},"schemas":{"ServiceTypeTurnaroundResponseSchema":{"title":"ServiceTypeTurnaroundResponseSchema","description":"The expected turnaround that applies to one service type at one store, together with the level it was found at. A figure set for the store wins over the tenant's figure on the service type, so this is what intake reads rather than either one on its own.\nestimatedBusinessDays is the effective figure: the store's own where the store has one, and the service type's otherwise. readyAtEstimate is the date core computes from it for a service order registered now, so the client never does the business-day arithmetic itself. Both are null when neither level carries a figure, and nothing is prefilled. readyAtEstimate is also null, and nothing is prefilled, when no day of the week can be one of the store's working days (its openDays hold only Saturday and Sunday and serviceCountWeekendsAsWorkingDays is false).","type":"object","required":["tenantUid","storeUid","serviceTypeUid","estimatedBusinessDays","readyAtEstimate","resolution"],"properties":{"tenantUid":{"$ref":"#/components/schemas/UID"},"storeUid":{"$ref":"#/components/schemas/UID"},"serviceTypeUid":{"$ref":"#/components/schemas/UID"},"estimatedBusinessDays":{"type":"integer","nullable":true,"description":"The expected turnaround that applies here, in business days. null when neither the store nor the service type carries a figure. The date it yields is readyAtEstimate on this response: the client reads the prefilled date off the response rather than computing it, and staff adjust that date case by case."},"readyAtEstimate":{"type":"string","format":"date-time","nullable":true,"description":"The date intake prefills the service order's readyAtEstimate with: the day of this request in the tenant's timezone plus estimatedBusinessDays of the store's working days (serviceCountWeekendsAsWorkingDays), at 23:59:59 on that day in the tenant's timezone, which reads as the end of the day with no time picked, as readyAtEstimate on the service order response states. Counting starts on the day of the request, or on the next working day when the request falls on a non-working day, so 0 business days answers that starting day. Core does the arithmetic; the client never counts days itself.\nnull when estimatedBusinessDays is null, or when no day of the week can be one of the store's working days (its openDays hold only Saturday and Sunday and serviceCountWeekendsAsWorkingDays is false), and nothing is prefilled. The client shows the day and time on the intake form and sends the day and time the staff kept, adjusted or cleared as readyAtEstimate on the service order create; the create never prefills a date on its own."},"resolution":{"description":"The level the figure was found at. STORE when the store has an override of its own, TENANT when it falls back to the service type's figure — including when that figure is itself null.","allOf":[{"$ref":"#/components/schemas/ServiceTurnaroundResolutionENUM"}]}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"ServiceTurnaroundResolutionENUM":{"title":"ServiceTurnaroundResolutionENUM","description":"The level the expected turnaround was found at.\nSTORE: the store has an override of its own for this service type — a store figure always wins. TENANT: the store has no override, so the service type's own figure applies, which may itself be none.","enum":["STORE","TENANT"],"type":"string"},"ServiceTypeTurnaroundUpdateRequestSchema":{"title":"ServiceTypeTurnaroundUpdateRequestSchema","description":"The store's own expected turnaround for a service type, in business days. It wins over the figure the service type carries for the tenant, the same precedence intake forms follow.\nSend null to clear the override, after which the service type's own figure applies to this store again. Clearing the override is the only way back to the tenant figure — there is no separate delete.","type":"object","required":["estimatedBusinessDays"],"properties":{"estimatedBusinessDays":{"type":"integer","nullable":true,"minimum":0,"maximum":365,"description":"How long work of this type is expected to take at this store, in business days: 0 to 365, anything outside that range is refused with a 400. null clears the store's override and leaves the service type's figure to apply."}}}},"requestBodies":{"ServiceTypeTurnaroundUpdateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceTypeTurnaroundUpdateRequestSchema"}}}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/types/{serviceTypeUid}/turnaround":{"put":{"summary":"Set the expected turnaround for a service type at a store","operationId":"put-serviceorders-types-turnaround","description":"Set this store's own expected turnaround for a service type, in business days. It wins over the figure the service type carries for the tenant, for this store alone and for no other.\nSend null to clear the override, after which the service type's figure applies to this store again. Clearing is the only way back to the tenant figure; there is no delete.\nThe resolved turnaround is returned, exactly as the read returns it, so what now applies and the level it resolves at are known without asking again.\n\nRequired permissions: SERVICE_STORE_CONFIG, SERVICE_CONFIG","responses":{"200":{"$ref":"#/components/responses/ServiceTypeTurnaroundResponse"}},"tags":["Service"],"requestBody":{"$ref":"#/components/requestBodies/ServiceTypeTurnaroundUpdateRequest"}}}}}
```


---

# 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/set-the-expected-turnaround-for-a-service-type-at-a-store.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.
