Retail & ecommerce / Inventory

Retail replenishment: compare min-max and reorder-point policies

By Vikasraj YadavPublished 5 min read

For replenishment planner · Compare approaches

TL;DR — what you’ll learn

  • Compare replenishment policies using inventory position, not on-hand alone.
  • Make the review interval, lead time, safety allowance and order quantity explicit.
  • Apply pack multiples after calculating need and show the resulting excess.
  • Treat a late inbound delivery as an exception before issuing a duplicate order.

Topics: retail replenishment · retail reorder point · min max stock · store replenishment rules

All quantities, amounts, product codes and events are illustrative teaching examples.

A store sells about eight units a day and buys in packs of twelve. The buyer sees 40 on hand and wants another 60. The ERP says 24 are already on order. Both figures matter, but neither answers whether those units arrive before the shelf runs empty.

Separate the order trigger, order size and receipt timing. Min-max and reorder-point policies can use similar stock positions while making different decisions. Compare them with the same demand assumptions and explicitly dated inbound commitments.

Establish the position before the policy

Use an illustrative continuous-review calculation with 40 eligible units on hand, 24 confirmed inbound units and eight backordered units. Future demand of eight units per day excludes those eight backorders, so the example does not subtract them twice.

Inventory position = 40 + 24 − 8 = 56 units. This counts confirmed replenishment commitments for the trigger calculation. A separate projected-stock schedule checks when receipts arrive. If an inbound order is cancelled or no longer credible, resolve that status before including it as reliable supply.

Oracle's min-max documentation describes minimum and maximum quantities, netting choices and order modifiers. The exact demand and supply included depend on configuration. Name the fields used in your calculation instead of assuming every system means the same thing by “available”.

Compare two explicit policies

Assume a three-day replenishment lead time and an illustrative safety allowance of 16 units. The reorder point is 8 × 3 + 16 = 40 units. This is a planning assumption, not a statistically estimated service-level guarantee.

Scroll horizontally to see all columns.

Policy Trigger and order-size rule Result at position 56
Continuous reorder point Order a fixed 48 when position is 40 or less No new order
Min-max review If position is below 60, replenish towards 108 Need 108 − 56 = 52; round up to 60

With twelve-unit packs, ceiling(52 ÷ 12) × 12 = 60. The min-max order would take position to 116, eight above the nominal maximum. Show that overshoot for approval rather than pretending the ordered quantity was 52.

These are different policies, not evidence that one is wrong. The min-max thresholds may reflect a longer coverage objective. If the store orders only twice weekly, a continuous-review reorder point cannot simply be checked twice a week without considering demand between reviews. A periodic order-up-to design generally needs to cover the review interval as well as replenishment lead time. Set those assumptions with the planner.

A replenishment suggestion needs a quantity check and a timing check
  1. Net the position40 on hand + 24 inbound − 8 backorders = 56.
  2. Apply the chosen policyROP 40: no order. Min 60/max 108: 52 units needed.
  3. Respect the packTwelve-unit packs round 52 to 60; position becomes 116.
  4. Check arrival datesVerify supply arrives before projected stock is exhausted.

Exception: A delayed or uncertain PO enters an exception queue; do not both retain its supply and replace it silently.

Stress a delayed delivery

After serving eight backorders, 32 on-hand units remain for future demand. At eight units daily they cover four days. If the 24-unit inbound receipt moves from day three to day five, demand through the end of day five is 40 units. With no other supply, the store faces an eight-unit shortfall before that receipt, depending on the precise arrival time.

The inventory position can still be 56 because the order remains open. That is why a position-based trigger alone does not prove near-term availability. The planner can consider an expedited receipt, a verified inter-store transfer, an earlier new order or a changed customer promise. Each alternative needs its own cost, timing and approval.

If the original 24 units are cancelled, position becomes 40 − 8 = 32. The continuous policy now triggers its fixed order of 48, bringing position to 80. If they are merely delayed, do not delete the commitment to make the formula produce an order. Preserve it and record the approved exception action; otherwise both supplies may arrive later and create excess.

Keep planning separate from sellable stock and budget

An inbound PO is not stock that can be promised for immediate dispatch. The available-stock guide separates physical, reserved and unavailable quantities. Replenishment may consider future receipts while the channel promise remains bounded by fulfilment eligibility.

Likewise, a sensible item-level suggestion can exceed a category's buying budget. Open-to-buy planning provides a separate commitment constraint. Apply the approved budget and supplier minimums before release; do not automatically place every generated suggestion.

Native min-max configuration is often sufficient for stable items with reliable lead times. A richer planning tool helps when demand, supply dates and shared stock require time-phased decisions. More sophisticated modelling does not compensate for duplicate open POs or an incorrect pack conversion.

Test the delayed receipt before automating orders

Run normal demand, a pack overshoot, a cancelled PO, a delayed PO and a promotion scenario. Keep forecasts for new or unavailable items labelled as assumptions. Sales observed during stockouts are not a complete measure of demand.

Accept the pilot when a planner can reproduce the suggestion, identify every included commitment and explain the expected stock path. Require approval for uncertain supply, unusual order quantities and policy overrides. Review fill rate, stockouts and excess together; reducing one metric can worsen another.

Choose a policy the team can explain

The useful policy is the one whose trigger, quantity and timing match the operation. Its exceptions should remain visible when the assumptions fail.

  1. Define position, demand exclusions and eligible inbound supply.
  2. Set review cadence, lead time, trigger and order-size rules.
  3. Test pack rounding and the five-day delay scenario.
  4. Pilot suggestions with planner approval before enabling automatic release.

Discuss this workflow

Compare your current replenishment rules on one stable SKU group, including pack multiples, open orders and a delayed-delivery test.

START A CONVERSATION

Let’s talk about your next build.

Prepare your brief below, then review and send it in your email app to sales@nextlabsonline.com.

SELECTED INDUSTRYRetail & ecommerce

Article: Retail replenishment: compare min-max and reorder-point policies · Inventory

THE FIRST CONVERSATION

Your product idea, AI opportunity or automation challenge—and a useful first milestone.

All fields are required.

A few sentences about the problem, your users and timing are enough.

We’ll use your details to respond to your enquiry. Please don’t include patient records, passwords or confidential information. Privacy Policy · Website Terms.

References

Sources checked 15 October 2026. Vendor documentation supports platform facts; the worked examples and diagrams are original.

About the author

Vikasraj Yadav writes about operational decisions, software and automation for NextEdge Labs.