Static reorder point and max-quantity cap
Two optional unit-level fields give you direct, manual control over the floor and ceiling of RevoStock's reorder suggestions: Static reorder point and Maximum quantity cap. Neither field is required — they exist to accommodate specific buying constraints that the automatic forecast cannot account for on its own.
Both fields can be set at the Global, Vendor, or SKU layer and follow the same precedence rules as every other replenishment field.
Static reorder point
Static reorder point (SRP) is a fixed unit threshold. Its role depends on which trigger mode is active for that SKU:
| Trigger mode | What Static reorder point does |
|---|---|
| SmartDays | Ignored entirely |
| ManualQty | Acts as the exact trigger threshold — a reorder fires when stock falls to or below this value |
| Hybrid | Acts as a minimum trigger threshold — a reorder fires when stock falls to or below this value, OR when the SmartDays condition is met, whichever comes first |
| Disabled | Ignored entirely |
Setting a Static reorder point
- Decide which layer is appropriate (Global, Vendor, or SKU).
- Open the corresponding tab on the Replenishment Config page.
- Enter a positive integer in the Static reorder point field.
- Click Save changes.
Leave the field blank if you are using SmartDays mode exclusively — a blank SRP on a SmartDays SKU has no effect and is not a problem.
If a SKU is set to ManualQty mode and its Static reorder point is blank at every layer, no reorder will ever trigger for that SKU. Check the Live SKU Config tab to confirm the resolved value.
Maximum quantity cap
Maximum quantity cap is a hard ceiling on the suggested order quantity. After RevoStock calculates how much to order, it applies this cap:
Final order quantity = min(calculated quantity, maximum quantity cap)
Leave this field blank to impose no ceiling. A blank cap means RevoStock can suggest any quantity the forecast demands.
When to use a maximum quantity cap
- Warehouse space constraints — you cannot physically receive more than a certain number of units per order.
- Cash flow limits — you want to cap the dollar exposure on any single purchase order.
- Supplier allocation limits — your supplier restricts how many units you can order per period.
- Slow-moving SKUs — you want to avoid over-buying on products that move unpredictably.
How MOQ and the cap interact
MOQ (minimum order quantity) and Maximum quantity cap are applied in sequence:
- RevoStock calculates a raw suggested quantity from the forecast and trigger logic.
- MOQ is applied as a floor: if the raw quantity is below the MOQ, it is raised to the MOQ.
- The cap is applied as a ceiling: if the MOQ-adjusted quantity exceeds the cap, it is reduced to the cap.
Step 1: raw_quantity = (forecasted daily sales) x (days of supply)
Step 2: moq_adjusted = max(raw_quantity, MOQ)
Step 3: final_quantity = min(moq_adjusted, max cap) ← only if cap is set
Worked examples
Example A — cap limits a large order
| Setting | Value |
|---|---|
| MOQ | 5 units |
| Maximum quantity cap | 50 units |
| Forecast-calculated quantity | 80 units |
Calculation:
- After MOQ: max(80, 5) = 80 units
- After cap: min(80, 50) = 50 units (final suggestion)
The cap reduces the order from 80 to 50 units.
Example B — MOQ raises a small order
| Setting | Value |
|---|---|
| MOQ | 5 units |
| Maximum quantity cap | 50 units |
| Forecast-calculated quantity | 3 units |
Calculation:
- After MOQ: max(3, 5) = 5 units
- After cap: min(5, 50) = 5 units (final suggestion)
The MOQ floor raises the order from 3 to 5 units, and the cap is not reached.
MOQ vs. cap conflict
If MOQ is greater than the Maximum quantity cap, the cap can never be respected without violating the MOQ — an impossible situation. RevoStock surfaces a warning in the Live SKU Config tab and on the Global Defaults and override forms when this condition is detected.
To resolve the conflict, either:
- Lower the MOQ to be at or below the cap, or
- Raise the Maximum quantity cap to be at or above the MOQ, or
- Clear the Maximum quantity cap (set it to blank) to remove the ceiling entirely.
The warning is informational — RevoStock will still generate a suggestion. In a conflict, the MOQ takes precedence and the cap is effectively ignored for that SKU, which is why it is important to resolve the conflict deliberately rather than leave it.