Replenishment suggestions (auto buy advice)

Daily computed buy suggestions: suggested qty = daily sales × (lead time + safety days) − on hand − in transit. One click drafts a PO.

Replenishment answers "what should I buy and how much" every day, so you stop eyeballing spreadsheets. It looks at how fast each product sells (average daily sales over the last 30 days), how many days the goods take to arrive (lead time), and how many days of safety stock you want to keep — then subtracts what you already have on hand and what is already in transit. The result is a suggested purchase quantity. Suggestions below safety stock are marked "Urgent"; the rest are "Reorder advised".

How each suggestion is calculated (plain language)#

• Suggested qty = daily sales × (lead time days + safety stock days) − on-hand qty − in-transit qty. Daily sales is the 30-day average for that product in that warehouse.
• On hand below safety stock (daily sales × safety stock days) → "Urgent".
• On hand below the reorder point → "Reorder advised".
• Neither condition met → no suggestion is generated. The system does not nag you about products that are fine.

Set the parameters first (two places)#

• Product form (Master Data → Products → open the product): reorder point (suggest a reorder when on hand falls below it), safety stock days (default 7), lead time days (default 14 — product-level wins over vendor-level), preferred vendor (if empty, the vendor of this product’s most recent PO is used).
• Vendor page (Purchase → Vendors): lead time days (default 14) — used when the product has no lead time set.

Working the list (Purchase → Replenishment)#

• Recompute: recalculates everything from the last 30 days of sales, current inventory and lead times. In phase 1 this is a manual button — scheduled auto-compute is next.
• Filter by urgency or vendor to work the list in batches.
• Create PO: a popup confirms quantity (defaults to the suggested qty rounded up), unit price and vendor — then creates a draft PO you continue in the PO page (approval flow as usual).
• Dismiss: hides the suggestion. Once a suggestion becomes a PO, its status flips to "ordered" and the PO number is recorded on it.