> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/inventory/inventory-api/concepts/decision-tables.md).

# Decision Tables

Decision tables for choosing between the GET and POST Inventory Availability endpoints.

## Choosing between GET and POST

| Characteristic   | GET                                     | POST                   |
| ---------------- | --------------------------------------- | ---------------------- |
| Use case         | Retrieve all applicable SKUs            | Retrieve selected SKUs |
| SKU list         | Not required                            | Required               |
| Request body     | None                                    | Required               |
| Delivery country | Not required in the documented contract | Optional               |
| Response         | SKU and ATS quantity                    | SKU and ATS quantity   |

{% hint style="success" %}
**Simple rule:** use GET for the complete inventory availability set. Use POST when availability is needed for specific SKUs.
{% endhint %}

## Which call for which situation

| Situation                                                   | Use                                         |
| ----------------------------------------------------------- | ------------------------------------------- |
| Pull a complete availability feed for all applicable SKUs   | `GET`                                       |
| Check availability for the SKUs in a basket or product list | `POST` with `skus`                          |
| Check availability for a shopper's delivery market          | `POST` with `skus` and `deliveryCountryIso` |
| Refresh availability for a single SKU                       | `POST` with one SKU in `skus`               |

## Handling the response

| Response                  | Treat as                               |
| ------------------------- | -------------------------------------- |
| `200` with `quantity > 0` | Available-to-sell stock                |
| `200` with `quantity: 0`  | A valid zero-ATS position              |
| Any non-`200` response    | A failed request, never zero inventory |

See [Response Codes](/inventory/inventory-api/response-codes.md) for what to do for each status.


---

# 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://developer.esw.com/inventory/inventory-api/concepts/decision-tables.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.