Reordering Rules - Part 3: Planning and Access Controls

Planning and Access Controls

This part explains planning behaviour such as just-in-time replenishment, forecast dates, visibility days, automatic minimum and maximum rules, and warehouse-based access.

Just-in-time logic

Just-in-time logic helps reduce unnecessary stock holding by placing replenishment actions only when they are needed to meet demand. The system uses the forecasted date to decide when replenishment should be prepared.

The forecasted date is the earliest possible date that the product can be available if the replenishment process starts immediately. This date is calculated using the lead times related to the replenishment process, such as supplier lead time, purchase delay, or manufacturing lead time.

Example: If a product has a total lead time of 5 days and the demand is required in 10 days, the system does not need to prepare replenishment immediately. It can wait until the timing is closer, so stock arrives when it is needed instead of sitting in the warehouse too early.

Important considerations:

  • If this timing feels risky, add buffer time through lead time configuration.
  • Reordering rules can still work without advanced lead time setup, but lead times provide better timing control.

Forecasted date and To Order quantity

To view forecasted replenishment information, open the replenishment screen and use the information option on the required line. The system displays the forecasted date and lead time details used for planning.

The To Order quantity represents the quantity that must be replenished based on the forecasted stock and demand within the planning window.

Important: The forecasted date is not simply the customer delivery date. It is the date calculated from the current date plus the lead times required to replenish the product.

Example: A product has a supplier lead time of 4 days, a purchase buffer of 1 day, and an internal purchasing delay of 2 days. The total lead time is 7 days. If today is November 26, the forecasted date is December 3. A confirmed sales order requiring 5 units on December 3 appears as a quantity to order now. If the sales order is required after December 3, the product may not appear as an immediate replenishment need yet.

Common confusion about forecasted quantities

Demands due after the forecasted date may not appear in the immediate forecast quantity on the reordering rule. However, they can still be visible in the longer-term forecast report.

This means a product can show no immediate quantity to order even though future demand exists. The system shows the replenishment need only when it falls within the correct planning window.

Example: Continuing the previous example, if the sales order date is moved from December 3 to December 4, the immediate Forecast and To Order values may show zero because the demand is outside the forecasted date window. The long-term forecast can still show that the 5 units will be needed later.

Visibility days

Visibility days allow the system to look ahead for additional demand when a replenishment need is already due. This helps combine immediate and near-future requirements into a single replenishment action.

Visibility days are useful when consolidating replenishment can reduce transport costs, improve supplier ordering efficiency, or avoid repeated orders for the same product.

To use visibility days, show the Visibility Days field on the replenishment or reordering rule screen and enter the number of days the system should look ahead.

Important: Visibility days do not move the forecasted date forward. The system checks extra future demand only if the product already needs replenishment on the forecasted date.

Example where visibility days is triggered

A product has a combined lead time of 30 days.

  • November 4: Current date. The forecasted date is December 4.
  • Sales Order 1: Requires the product by December 4.
  • Sales Order 2: Requires the product by December 19.
  • Sales Order 3: Requires the product by December 25.

If Visibility Days is set to 20, the system looks ahead from December 4 to December 24. Sales Order 2 can be included with Sales Order 1 in the same replenishment action. Sales Order 3 is outside the visibility window and is not included.

Example where visibility days is not triggered

Using the same product, if there is no demand on the forecasted date, visibility days do not create an early replenishment need by themselves.

  • November 4: Current date. The forecasted date is December 4.
  • No demand exists on December 4.
  • Sales Order 2: Requires the product by December 19.

In this case, the system waits until the normal planning logic determines that replenishment is required. Visibility days only extend an existing replenishment need; they do not force an earlier one.

Auto Set Min/Max

[Insert image: Warehouse Auto Set Min/Max setting]

The Auto Set Min/Max option is available on the warehouse setup. When enabled, the system can automatically create missing reordering rules for products transferred into that warehouse.

To use this option:

  1. Navigate to Inventory → Configuration → Warehouses.
  2. Open the required warehouse.
  3. Enable Auto Set Min/Max.
  4. Save the warehouse.
  5. Process an internal transfer into that warehouse.

System behaviour: If the receiving warehouse has Auto Set Min/Max enabled and the transferred product does not already have a reordering rule for that warehouse, the system creates a new rule using the transfer quantity as both the minimum and maximum quantity.

Example: Warehouse C has Auto Set Min/Max enabled. An internal transfer brings 12 units of a product into Warehouse C. If no reordering rule already exists for that product and warehouse, the system creates a new rule with 12 as the minimum quantity and 12 as the maximum quantity.

Warehouse-based replenishment access

[Insert image: Warehouse-based replenishment access]

Warehouse-based access can restrict users to the warehouses assigned to them. This helps warehouse teams work only with the replenishment and reordering records relevant to their responsibility.

Users with warehouse restrictions see and process only the allowed warehouse records. Users without these restrictions continue to work according to their normal access rights.

Example: A user assigned to the A warehouse opens the replenishment screen and sees only the replenishment records related to allowed warehouse locations. This prevents the user from accidentally working on another warehouse's planning records.