> 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/order/ask-the-supplier-what-it-can-confirm-for-a-product.md).

# Ask the supplier what it can confirm for a product

Ask the supplier's own system how much of a product it can confirm for this store, and for when. Answers the question a salesperson has before promising anything to a customer: is this actually coming, and when.

The lookup goes out to the supplier live, so it costs a round trip. Ask for the products you need in one call rather than one call per product.

Every product in one call shares its fate. If the supplier rejects any one of the article numbers, the whole call fails and no forecast comes back for the others.

Only available to tenants configured for it. A tenant without the integration gets an error rather than an empty list, so a client can tell "not available here" apart from "nothing is coming".

Required permissions: SALES\_ORDER

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Order","description":"Order"}],"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":{"SupplyForecastSearchRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/SupplyForecastSearchSchema"}}}}},"schemas":{"SupplyForecastSearchSchema":{"title":"SupplyForecastSearchSchema","type":"object","description":"The products to ask about. All quantities are in hundredths (100 = 1 unit), matching\nthe rest of the API.","required":["products"],"properties":{"products":{"type":"array","minItems":1,"items":{"$ref":"#/components/schemas/SupplyForecastProductSchema"}}}},"SupplyForecastProductSchema":{"title":"SupplyForecastProductSchema","type":"object","required":["productUid","quantity"],"properties":{"productUid":{"$ref":"#/components/schemas/UID"},"quantity":{"type":"integer","description":"How much to ask about, in hundredths (100 = 1 unit)."},"deliveryDate":{"type":"string","format":"date","description":"The date to ask about. Left out, the supplier is asked about a default a couple of days out — so a plain \"can I get this soon\" needs nothing here. Set it when the customer has named a date."}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"SupplyForecastItemSchema":{"title":"SupplyForecastItemSchema","type":"object","description":"What the supplier will confirm for one product. Every product in the request comes back\nhere, in the same order, so a client can walk request and response side by side. A\nproduct the supplier recognises but will not confirm any quantity for comes back with\nquantity 0 and no date rather than being left out.\n\nAn article number the supplier does not recognise at all behaves differently: it fails\nthe whole request instead of coming back as a zero row, and it fails it for every other\nproduct in the same call. Send article numbers the supplier knows.","required":["productUid","confirmedQuantity","confirmedDate"],"properties":{"productUid":{"allOf":[{"$ref":"#/components/schemas/UID"}],"description":"The same value that was asked about, echoed back so the entry can be matched to the request without relying on order alone."},"confirmedQuantity":{"type":"integer","description":"How much the supplier commits to, in hundredths (100 = 1 unit). Can be less than was asked for, and is 0 when the supplier commits to nothing."},"confirmedDate":{"type":"string","format":"date","nullable":true,"description":"When the confirmed quantity is available. Null when there is nothing to confirm, which is the only case where it is null — so a non-zero confirmedQuantity always carries a date."}}}},"responses":{"SupplyForecastListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","required":["items"],"properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/SupplyForecastItemSchema"}}}}}}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/supply-forecast":{"post":{"description":"Ask the supplier's own system how much of a product it can confirm for this store, and\nfor when. Answers the question a salesperson has before promising anything to a\ncustomer: is this actually coming, and when.\n\nThe lookup goes out to the supplier live, so it costs a round trip. Ask for the\nproducts you need in one call rather than one call per product.\n\nEvery product in one call shares its fate. If the supplier rejects any one of the\narticle numbers, the whole call fails and no forecast comes back for the others.\n\nOnly available to tenants configured for it. A tenant without the integration gets an\nerror rather than an empty list, so a client can tell \"not available here\" apart from\n\"nothing is coming\".\n\nRequired permissions: SALES_ORDER","operationId":"post-tenants-stores-supply-forecast","requestBody":{"$ref":"#/components/requestBodies/SupplyForecastSearchRequest"},"responses":{"200":{"$ref":"#/components/responses/SupplyForecastListResponse"}},"summary":"Ask the supplier what it can confirm for a product","tags":["Order"]}}}}
```


---

# 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/order/ask-the-supplier-what-it-can-confirm-for-a-product.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.