> 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/store-operations/orders/fulfillment/troubleshooting.md).

# Troubleshooting

Confirm the selected facility and order status before changing an order. Use the guide that matches the problem.

| Problem                                             | What to check                                                                                                                                                                                                                                                                                                                                                            |
| --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| A user can open Launchpad but cannot fulfill orders | Check facility assignments in [Unable to Login](https://docs.hotwax.co/documents/store-operations/orders/fulfillment/troubleshooting/unable-to-login.md) and permissions in [Troubleshoot application access](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/users/troubleshooting/application-access-issue.md). |
| An order is missing from the fulfillment queue      | Use [Order Lookup](https://docs.hotwax.co/documents/store-operations/orders/fulfillment/order-lookup.md) to review the order's status, facility, and items. Then check the corresponding Open, In Progress, or Completed page.                                                                                                                                           |
| A shipping label cannot be generated                | Review the prerequisites and generation steps in [Shipping Label Generations](https://docs.hotwax.co/documents/store-operations/orders/fulfillment/shipping-label-generation.md).                                                                                                                                                                                        |
| An item cannot be fulfilled                         | Review [Rejection](https://docs.hotwax.co/documents/store-operations/orders/fulfillment/rejection.md), including the reason and the items affected, before confirming the action.                                                                                                                                                                                        |
| The interface uses the wrong language               | Follow [Change Language](https://docs.hotwax.co/documents/store-operations/orders/fulfillment/troubleshooting/change-language.md).                                                                                                                                                                                                                                       |

After correcting the cause, verify the affected order or shipment. Keep the order ID, shipment ID, facility, and exact error together when recording an unresolved issue.


---

# 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/store-operations/orders/fulfillment/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.
