> 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/orders/additional-oms-order-workflows/troubleshooting.md).

# Troubleshooting

Find the order and confirm its Product Store, identifiers, item status, and fulfillment location before changing it. These guides cover OMS and integration procedures; some actions take place outside the Order Manager app.

| Problem                                                       | What to check                                                                                                                                                                                                                    |
| ------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| An order is missing from an Order Manager list                | Start with [Find orders](/documents/retail-operations/orders/order-management/find-sales-orders.md) and review the active search and filters.                                                                                    |
| A Shopify order is missing from OMS                           | Check the connection, import scope, and run history in [Manage Shopify Order Sync](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/company/manage-shopify-order-sync.md). |
| An order remains in Created status                            | Review [Order Approval Errors](/documents/retail-operations/orders/additional-oms-order-workflows/troubleshooting/order-approval.md) and the approval requirements configured for the order.                                     |
| A required order attribute is missing                         | Follow [Order Attribute Missing](/documents/retail-operations/orders/additional-oms-order-workflows/troubleshooting/order-attribute-missing.md) to inspect the source value and its import path.                                 |
| Search results show a different status from the order details | Follow [Order Status Discrepancy](/documents/retail-operations/orders/additional-oms-order-workflows/troubleshooting/order-status-discrepancy.md).                                                                               |
| An order is absent from a search index                        | Follow [Order Indexing Discrepancy](/documents/retail-operations/orders/additional-oms-order-workflows/troubleshooting/order-indexing-discrepancy.md), using the affected order ID to limit the operation.                       |

Record the HotWax order ID and Shopify order ID separately. After a correction, reopen the order and repeat the original search to confirm the result. Check whether an order already exists before retrying its import.


---

# 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/orders/additional-oms-order-workflows/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.