Business Problems and Recommended Smart Stock Workflows

Start from the business problem, then use the narrowest control that represents it. Do not force every exception into a global setting or a manual purchase override.

We order from a supplier only every 30, 60, or 90 days

Create a recurring Ordering Profile with the real interval, anchor date, and preparation window. Link it through the matching Planning Rule. The recommendation then protects the lead time, interval until the following review, and safety days before deducting timely supply.

We consolidate factory or container orders

Use one Ordering Profile to align the vendor review date. Use Vendor Order Review to review the complete vendor/profile/date group. Add a Purchase Schedule Profile only when the approved quantity should arrive in separate batches.

A storm, tender, promotion, or wholesale order created a spike

If the period is already known, create and confirm Demand Events before the next sync. If the sync discovered it, review the flagged lines in bulk and run one follow-up sync. Do not use Planner Purchase Quantity as the historical correction.

Low sales may be caused by out-of-stock days

Open Demand History for the product and warehouse. Compare recorded demand with monthly out-of-stock days. Use Flag only for visibility, Estimate constrained demand only with dependable evidence and backend support, or Ignore availability when unmet demand is already captured elsewhere.

Another warehouse has stock

Enable internal rebalancing, define legal warehouse relationships through the global scope or Transfer Networks, and use Planning Rules for product and warehouse exceptions. Create timely transfers first, then buy only the uncovered balance.

The recommendation is decimal or ignores case packs

Keep demand forecasts decimal. Configure stock-UoM rounding, purchase UoM conversion, Order Step, Case Pack, MOQ, and supplier minimums so the executable RFQ is valid. Internal transfers use stock-UoM precision and do not inherit supplier pack rules.

The buyer wants to order more, less, or zero

Set Planner Purchase Quantity and enter the business reason. The value survives later forecasts, including an explicit zero. Reset it when the system suggestion should become active again. A confirmed PO is never silently changed.

The line says Setup Required

Open Readiness & Setup or the Control Tower exception drawer. Correct the named source: vendor, Planning Rule, ordering dates, transfer route, warehouse role, UoM, forecast horizon, or linked document. Run a new forecast only when the correction affects the planning snapshot.

The required planning window exceeds the forecast horizon

The sync requests the largest horizon required by active Planning Rules, capped by the service plan. Use Show Lines on the Control Tower warning, correct accidental lead-time or cadence settings, or arrange a supported longer backend horizon. Dashed run-rate projection is visual context, not a purchase quantity.