What it is
The replenishment engine uses forecasts, lead times, cover, on-hand stock and open orders to calculate purchase quantities and dates for each product and location. There is no Smart Replenishment page: the engine is part of Commitments, read on the desk's Buy and Demand columns, on the Bench and on the Reorder lines, and budgeted by a commitment's envelope in season.
How Tightly decides it
The walk runs inside every sync, after the forecast. Cover is a minimum: the stock you must hold so a line does not run out before its next delivery can land, never a target to sell down to. It covers the review cycle plus the lead time in full, and it grows with how much sales swing week to week and with how inconsistent a supplier's own deliveries have run: a supplier whose lead time varies a lot earns a deeper buffer than one who always arrives on schedule, worked out from that supplier's own recent purchase-order receipts. A saved NetSuite supplier/subsidiary lead time applies to its matching warehouse first, including an explicit unknown. Otherwise lead time resolves from variant and supplier at the warehouse, supplier at the warehouse, variant and supplier, supplier default, then the variant warehouse default, then the source-owned variant default, and finally the company default. The variant warehouse default uses a Tightly override where declared, otherwise the preserved imported value. The source reads variant warehouse default or variant default; the company fallback reads from system. A line whose demand was read from a predecessor's sales rather than its own record says from a predecessor: the same predecessor the forecast reads. Where the walk runs past the end of the forecast it says so, past the forecast, and where the forecast under a line is thin the quantity carries lower confidence.
A line the engine cannot walk is refused with a word, never a zero: No stock count where nothing says what is on hand, No forecast yet where the forecast has not reached the line. In season on Tightly Pro a line inside a commitment's scope is Held until a Commitment covers it rather than ordered on its own, and a line a policy owns says Owned by that policy. When the walk finds nothing to order it writes that empty result, so yesterday's lines do not survive under today's date. Its promise follows your full-sync slot. Old inputs cannot support an Every line is covered claim; stock and forecast guards remain.
The words on the face
The run timestamp distinguishes current results from Running, Late, Stale, Partial or Failed results. Never ran means no completed calculation exists; Nothing yet means no forecast. Paused, Not on your plan and Not on the run describe availability, not zero demand.
The page says Every line is covered past its lead time. only after a completed run over current inputs. While calculating, the page does not invent a line count. Line reasons distinguish missing stock, missing forecasts, commitment coverage, policy ownership and lower confidence. Forecasts based on predecessors identify their look-alike source; dates beyond the forecast are marked separately.
What you can do about it
On Smart Replenishment, take a recommended line to an order. On Tightly Pro, Add to Bench from the desk, and the Bench turns the lines into draft purchase orders; staging on the Bench spends nothing, and the envelope moves when an order is approved. A line reading No stock count clears once the warehouse has a stock count on file; No forecast yet clears when the forecast reaches the line, which for a new product means a look-alike on Analogs. Nothing is pressed to run the engine; it follows the sync, and a Paused source is resumed on Integrations. Cover, and why cover is a minimum, carries the reading of the cover figure; Smart Replenishment and the desk articles carry each page's own.
On the Purchasing card of a product or variant, Stop new purchasing holds new supplier purchasing while retaining forecasts, sales history, physical stock and existing purchase orders. A product hold applies to all its variants. Removing it leaves independent variant holds in place; removing a variant's own hold does not remove an inherited product hold.
Glossary line
The replenishment engine works out what to order and when, from the forecast, the lead time and the cover you must hold.
Changing a commitment range or fulfilment warehouses queues a buying recalculation. Recommendation-based buying waits until both direct purchase and component requirements are refreshed. Forecasts, historical sales and physical stock are unchanged.
Versioned lifecycle policies
Lifecycle policies separate review cadence, trigger, target cover, safety stock, lot size and seasonal buying dates. Active applications apply at their declared company, commitment, product or variant scope and effective dates. A saved draft has no buying authority. Preview runs asynchronously with bounded result pages; activation requires a complete, current review and the expected application revision. Existing policy behavior remains until a new application takes ownership.
Cover uses its declared on-hand or inventory-position basis. Buying cutoffs, latest arrival, carryover and quoted supplier/warehouse supply routes remain explicit. A selected route supplies end-to-end lead time and optional incremental per-unit freight. When current funding is required, activation rechecks the approved Finance funding book and commitment limits; it does not reserve cash, place a PO or bypass later approval.