> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/retail-operations/inventory/troubleshooting.md).

# Troubleshooting

Trace inventory discrepancies for a product, facility, and sales channel.

Compare the same product and location in each system. Record the product identifier, facility, time, and quantity being compared: Quantity on Hand (QOH), Available to Promise (ATP), or online ATP.

| Problem                                       | What to check                                                                                                                                                                                                                                                                          |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A quantity changed unexpectedly in OMS        | Open [View Inventory Log](https://docs.hotwax.co/documents/retail-operations/inventory/troubleshooting/view-inventory-log.md), filter by facility, and inspect the event and quantity differences.                                                                                     |
| OMS and Shopify show different inventory      | Follow [Inventory Synchronization Errors](https://docs.hotwax.co/documents/retail-operations/inventory/troubleshooting/inventory-synchronization-errors.md) to trace the mapped location or channel, event batch, and delivery result.                                                 |
| An inventory file did not update OMS          | Check the import status, record counts, and errors using [Troubleshoot file imports](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/troubleshooting/file-imports.md).                                              |
| Physical stock exists but online ATP is lower | Review [inventory and online ATP](https://docs.hotwax.co/documents/retail-operations/inventory/available-to-promise/inventory.md) and the [sourcing concepts](https://docs.hotwax.co/documents/retail-operations/inventory/available-to-promise/concepts.md) that affect availability. |

An inventory log's `ATP diff` or `QOH diff` is the change recorded by that event, not the final balance. For example, releasing one reserved unit adds 1 to ATP and leaves QOH unchanged.

After resolving the cause, check the resulting OMS quantity and, when applicable, the mapped Shopify quantity. Confirm which records already applied before retrying an import or resetting inventory.


---

# 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.hotwax.co/documents/retail-operations/inventory/troubleshooting.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.
