> 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/order-routing/troubleshooting/incorrect-facility-configurations.md).

# Troubleshoot facility configuration

Check facility groups when a routing rule skips an expected location or allocates an order to the wrong location.

## Check the facility group

1. Open the **Order Routing Rules** app.
2. Confirm the Product Store shown in the app footer.
3. Go to `Routing` > `Facility groups`.
4. Search for the group used by the routing rule.
5. Confirm that its type is `Brokering`.
6. Click `Manage facilities`.
7. Select eligible facilities and clear facilities that should not participate.
8. Click the save icon.

The facility count on the group card updates after the membership change is saved.

## Check the routing rule

1. Go to `Routing` > `Order Routing`.
2. Open the routing group, then select the routing and routing rule.
3. In `Filters`, review `Group` and any excluded group.
4. Add or change the group filter when it points to the wrong facility group.
5. Review other filters that can remove a facility, including `Proximity`, `Safety stock`, `Week of Supply`, and fulfillment capacity.
6. Save the routing group's working copy.

If no facility-group filter is applied, the routing rule can consider every facility enabled for online fulfillment. Use a group filter when the rule should use a controlled set of locations.

See [Manage facility groups](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/facilities/manage-groups.md) and [Configure routing rules](/documents/retail-operations/orders/order-routing/manage-and-configure/inventory-rules.md) for the full setup.


---

# 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://docs.hotwax.co/documents/retail-operations/orders/order-routing/troubleshooting/incorrect-facility-configurations.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.