Appearance
Reorder Rules
| Backlog field | Value |
|---|---|
| Story ID | INV-DASH-007 |
| Epic | Inventory |
| Story type | Dashboard |
| Review status | Draft - business analyst and business owner review required |
| Source evidence | Inventory MFE route/form, Inventory.Apis controller, application command/query handlers, validators, domain entities, and posting services |
| Last source review | 2026-07-10 |
Purpose
Maintain item/warehouse thresholds used to identify stock that needs replenishment.
User stories
- As an inventory planner, I want to define minimum, maximum, and reorder quantities by item and warehouse so that replenishment decisions are consistent.
- As a planner, I want to search and maintain existing rules so that thresholds stay aligned with demand.
- As a manager, I want the system to highlight quantities that breach a rule so that action can be prioritized.
Acceptance criteria
- A rule identifies a valid item variant and warehouse.
- Only one active rule exists for the same item-variant/warehouse scope.
- Threshold quantities are non-negative and logically ordered.
- Reorder quantity is valid for the item's unit configuration.
- Users can add, edit, delete, and act on rules only with the corresponding permission.
- Existing stock is not changed when a reorder rule is edited.
Needs confirmation
- Whether replenishment creates a purchase/transfer request automatically or only provides an alert/action.
Required and derived data
- Item variant: required and greater than zero.
- Warehouse: required and greater than zero.
- Minimum quantity: required, non-negative.
- Maximum quantity: required, non-negative, and greater than or equal to minimum.
- Current balance: derived from item-variant stock in the warehouse and read-only.
- The item-variant/warehouse combination must be unique.
Saving a rule does not reserve, receive, issue, or post stock and creates no GL effect. It only changes replenishment thresholds and any downstream alert/action eligibility.