> 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/print-a-service-order-on-a-store-printer.md).

# Print a service order on a store printer

Print a service order on a store printer. The one thing printed here is the intake slip — the short form of the service confirmation, on the receipt roll, for the customer to take away at registration when the A4 confirmation is not printed or not wanted. Flow composes the slip and sends it to the printer named by printerUid itself, the way a sales receipt is printed, so no client ever touches a printer and there is no client-side printing path. The answer carries no body. The printer must be assigned to the store in the path, and it must list SERVICE\_INTAKE\_SLIP among its availablePrintActions; a printer assigned to another store, a printer that does not list that action, and a printerUid naming no printer are all refused with a 400. The printer is always judged against the store in the path, whichever store that is: the endpoint is served at any store of the tenant, and a counter prints on its own roll. There is no fallback printer — printerUid is required. The slip prints on request and never automatically: no store printer event triggers it. One slip covers one service order, so several units taken in together, registered as several service orders, print one slip each. The slip carries the store header a sales receipt carries, naming the store that owns the service order, wherever the slip is printed — the logo, the store's name, address, phone and organization number — the localized service confirmation title, the service number in large type and as a Code128 barcode, and the date and time of registration. Below that: the customer's name; the unit, its product name with the serial number and the IMEI where they were captured; the title of the issue as it was registered; the coverage, with the insurer, the claim number and the deductible for an insurance case, the claim number printed only where it is not empty and the deductible only where it is not 0; when the work is expected to be ready, as the day and the time, or as the day and "end of day"; and the estimated price and the max price, each printed only where it is not 0. Where there is a termsUrl, that line prints: the URL is the standing acceptance's own snapshot of it where one exists, and the service order's where none does. Where an acceptance stands, the fact of it prints; the terms text itself belongs to the confirmation and is never on the slip. Never on the slip: the answers captured on the intake form, a signature, any timeline entry, the values of sensitive fields, the secrets and their labels, the store's own cost and the margin that follows from it, the name of any person who worked on the case, and the customer's service portal link. The slip is wrapped to the printer's line width, and it is rendered in the customer's preferred language, and in the tenant's where the customer has none. This is read reach rather than a write on the case: it is served at any store of the tenant, because printing the slip changes nothing on the case; the service order record carries the whole reach rule.

Required permissions: SERVICE\_ORDER

```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"}},"requestBodies":{"ServiceOrderPrintRequest":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceOrderPrintSchema"}}}}},"schemas":{"ServiceOrderPrintSchema":{"title":"ServiceOrderPrintSchema","description":"A print of a service order on a store printer: what to print, and the printer to print it on. Both are required — there is no fallback printer, and nothing is printed on a printer nobody named.\nFlow composes the print and sends it to the printer itself, so no client ever touches a printer.","type":"object","required":["type","printerUid"],"properties":{"type":{"$ref":"#/components/schemas/ServiceOrderPrintTypeENUM"},"printerUid":{"description":"The printer to send the print to. It must be assigned to the store in the path, and it must list the print action the type needs among its availablePrintActions — SERVICE_INTAKE_SLIP for INTAKE_SLIP, which every RECEIPT printer lists. A printer assigned to another store, a printer that does not list the action, and a uid naming no printer are all refused with a 400.","allOf":[{"$ref":"#/components/schemas/UID"}]}}},"ServiceOrderPrintTypeENUM":{"title":"ServiceOrderPrintTypeENUM","description":"What a service order print request prints on a store printer.\nINTAKE_SLIP: the intake slip — the short form of the service confirmation on the receipt roll, for the customer to take away at registration.","type":"string","enum":["INTAKE_SLIP"]},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/{serviceOrderUid}/print":{"post":{"summary":"Print a service order on a store printer","tags":["Service"],"responses":{"204":{"description":"No Content"}},"operationId":"post-serviceorders-print","description":"Print a service order on a store printer. The one thing printed here is the intake slip — the short form of the service confirmation, on the receipt roll, for the customer to take away at registration when the A4 confirmation is not printed or not wanted.\nFlow composes the slip and sends it to the printer named by printerUid itself, the way a sales receipt is printed, so no client ever touches a printer and there is no client-side printing path. The answer carries no body.\nThe printer must be assigned to the store in the path, and it must list SERVICE_INTAKE_SLIP among its availablePrintActions; a printer assigned to another store, a printer that does not list that action, and a printerUid naming no printer are all refused with a 400. The printer is always judged against the store in the path, whichever store that is: the endpoint is served at any store of the tenant, and a counter prints on its own roll. There is no fallback printer — printerUid is required.\nThe slip prints on request and never automatically: no store printer event triggers it. One slip covers one service order, so several units taken in together, registered as several service orders, print one slip each.\nThe slip carries the store header a sales receipt carries, naming the store that owns the service order, wherever the slip is printed — the logo, the store's name, address, phone and organization number — the localized service confirmation title, the service number in large type and as a Code128 barcode, and the date and time of registration. Below that: the customer's name; the unit, its product name with the serial number and the IMEI where they were captured; the title of the issue as it was registered; the coverage, with the insurer, the claim number and the deductible for an insurance case, the claim number printed only where it is not empty and the deductible only where it is not 0; when the work is expected to be ready, as the day and the time, or as the day and \"end of day\"; and the estimated price and the max price, each printed only where it is not 0. Where there is a termsUrl, that line prints: the URL is the standing acceptance's own snapshot of it where one exists, and the service order's where none does. Where an acceptance stands, the fact of it prints; the terms text itself belongs to the confirmation and is never on the slip.\nNever on the slip: the answers captured on the intake form, a signature, any timeline entry, the values of sensitive fields, the secrets and their labels, the store's own cost and the margin that follows from it, the name of any person who worked on the case, and the customer's service portal link. The slip is wrapped to the printer's line width, and it is rendered in the customer's preferred language, and in the tenant's where the customer has none.\nThis is read reach rather than a write on the case: it is served at any store of the tenant, because printing the slip changes nothing on the case; the service order record carries the whole reach rule.\n\nRequired permissions: SERVICE_ORDER","requestBody":{"$ref":"#/components/requestBodies/ServiceOrderPrintRequest"}}}}}
```


---

# 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/print-a-service-order-on-a-store-printer.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.
