> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/channel-manager-api/use-cases/inventory-updates.md).

# Inventory updates

This use case explains the two modes by which Mews pushes inventory updates to the Channel Manager side: Full update mode and Delta update mode. Both modes use the same API operations.

## Full Inventory Update Mode

Full Inventory Update Mode sends the complete set of inventory data. In this mode, you request an inventory update for a specified time period using API Operation [Request ARI update](/channel-manager-api/mews-operations/inventory.md#request-ari-update). Alternatively, a property employee can use this mode to push the latest data manually. Data sent in this mode is always for **all** connected rate plans and space types combinations.

| 'How to' use case                      | API Operations                                                                             |
| -------------------------------------- | ------------------------------------------------------------------------------------------ |
| How to request a full inventory update | [Request ARI update](/channel-manager-api/mews-operations/inventory.md#request-ari-update) |

## Delta Inventory Update Mode

Delta Inventory Update Mode only sends changes since the last update, optimizing data transfer and ensuring efficient synchronization. In this mode, once the connection is set up, Mews automatically sends deltas or changes in inventory to the Channel Manager. Data sent in this mode is only the data that has changed since the previous update. This is a completely automated process and there is no way to trigger it manually. Delta inventory updates are sent repeatedly until they are successfully accepted by the Channel Manager.


---

# 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.mews.com/channel-manager-api/use-cases/inventory-updates.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.