> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/api-reference/stock-availabilities.md).

# Stock Availabilities

## Check whether one location can fulfill a set of items

> Determines whether a single active stock location holds enough stock to\
> cover every requested item, optionally restricted to locations in a\
> given country. Backorderable stock is not counted; only on-hand counts\
> are compared.<br>

```json
{"openapi":"3.0.0","info":{"title":"OMS API","version":"1.1"},"tags":[{"name":"Stock availabilities"}],"servers":[{"url":"https://{host}/api","description":"Chord OMS instance","variables":{"host":{"default":"plant-staging.assembly-api.com","description":"Your tenant host, as configured in Chord OMS. The default is a Chord staging sandbox: replace it with your own host before making real requests."}}}],"security":[],"paths":{"/stock_availabilities/fulfillability":{"post":{"summary":"Check whether one location can fulfill a set of items","description":"Determines whether a single active stock location holds enough stock to\ncover every requested item, optionally restricted to locations in a\ngiven country. Backorderable stock is not counted; only on-hand counts\nare compared.\n","operationId":"create-stock-fulfillability","tags":["Stock availabilities"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"$ref":"#/components/schemas/fulfillability-input"}}}},"responses":{"200":{"description":"","content":{"application/json":{"schema":{"$ref":"#/components/schemas/fulfillability"}}}}}}}},"components":{"schemas":{"fulfillability-input":{"type":"object","required":["items"],"properties":{"country":{"type":"string","description":"ISO 3166-1 alpha-2 country code used to narrow the candidate stock\nlocations. Locations with no country assigned are always considered.\nOmit to consider every active stock location.\n"},"items":{"type":"array","items":{"type":"object","required":["sku","quantity"],"properties":{"sku":{"type":"string","description":"A variant SKU, or a variant ID."},"quantity":{"type":"integer"}}}}}},"fulfillability":{"type":"object","properties":{"fulfillable":{"type":"boolean","description":"True when a single stock location can cover every requested item at\nthe requested quantity.\n"},"location_id":{"type":"integer","nullable":true,"description":"The stock location that can fulfill the whole request, or null when\nno single location can.\n"},"items":{"type":"array","items":{"type":"object","properties":{"sku":{"type":"string"},"quantity":{"type":"integer"},"ok":{"type":"boolean","description":"True when the available count covers the requested quantity.\n"},"available":{"type":"integer","description":"Count at the fulfilling location, or the highest count across\ncandidate locations when no single location can fulfill the\nrequest. Only present when the store has the stock\navailability count feature enabled.\n"}}}}}}}}}
```


---

# 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.chord.co/chord-oms/api-reference/stock-availabilities.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.