> 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/customs-catalog-api/fulfillment-api/core-concepts/inventory.md).

# Inventory

The inventory model is SKU-level, FC-scoped, and status-driven. Each sync call replaces the platform's known state for the included SKUs — it is a snapshot, not a delta.

### Key model properties

<table data-view="cards"><thead><tr><th>Property</th></tr></thead><tbody><tr><td><strong>FC-scoped</strong><br>Inventory is per fulfillment centre.</td></tr><tr><td><strong>Snapshot semantics</strong><br>Each call replaces known state.</td></tr><tr><td><strong>Multi-status per SKU</strong><br>Same SKU can exist in multiple statuses.</td></tr><tr><td><strong>Provider-scoped</strong><br>Stock can be segmented by 3PL provider.</td></tr></tbody></table>

### `ArticleStatus`

| Status       | Allocation to orders | Typical trigger                                                 |
| ------------ | -------------------- | --------------------------------------------------------------- |
| `Expected`   | No — earmarked only  | Inbound delivery confirmed by retailer buying system            |
| `Active`     | Yes                  | Put-away complete; cycle count verified; replenishment received |
| `Quarantine` | No                   | Damage found; regulatory hold; pending QC assessment            |
| `Suspended`  | No                   | QC assessment: irreparable damage; written off                  |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/customs-catalog-api/fulfillment-api/core-concepts/inventory.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.