> 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/analytics/reports/reorder-limit.md).

# Reorder Limit

This document details the Reorder-Limit feature, allowing clients to automatically generate reports for items requiring inventory replenishment.The feature utilizes a pre-configured `Reorder Channel` with customizable threshold rules. Clients can adjust these rules to define the minimum inventory level **(reorder limit)** at which they'd like to be notified for stock replenishment.

## Setting Reorder Limits

Here's how to set the reorder limit for products by tag:

1. Navigate to **Launchpad** > **ATP App** > **Threshold** page.
2. Click the **"+"** symbol to create a new rule.
3. Enter a descriptive name for the rule, such as "Reorder Limit - \[Tag Name]".
4. In the **Threshold** field, enter your desired reorder level (e.g., 5).
5. Under **Channels**, select the **Configuration Facility**.
6. Under **Products by Tag**, use the filter options to include or exclude products based on their tags.
7. Click **Save** to create the rule.
8. Schedule the rule to run daily at midnight. You can also click **Run Now** for immediate execution from the Job scheduler pinned on the top of the page.

### Additional Steps (Optional)

1. Open `Job Manager` from the Launchpad.
2. Open `Catalog` and search for `Import Product Facility`.
3. Open the job and schedule it for the required frequency, or select `Run Now` for an immediate execution.
4. Return to `Catalog` and search for the bulk imported file processing job used by the instance.
5. Open the job and configure its required schedule, or select `Run Now`.

See [Manage a job](https://github.com/hotwax/oms-documentation/tree/user-guides-pub/documents/system-admin/administration/job-manager/jobs/job-details.md) for current scheduling instructions.

### Setting Different Reorder Limits (Optional)

If you require different reorder limits for various product categories, create separate rules using the same process mentioned above. Utilize the `Products by Tag` section for filtering products within each rule.

## Verifying Reorder Limits

After setting the reorder limits, verify the configuration by navigating to the product's inventory details within the OMS product page. You should see a new reorder channel with the corresponding reorder limit threshold. Products belonging to the designated tag and having an Available-To-Promise (ATP) level that falls below this reorder channel threshold, along with no upcoming purchase orders (POs), will be considered eligible for inclusion in the Reorder Eligible Products report.

## Report Delivery

The scheduled report will be delivered to your inbox at a predetermined time slot, assuming there are products meeting the reorder criteria. The report frequency can be adjusted upon request.


---

# 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/analytics/reports/reorder-limit.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.