Draft purchase orders from low-stock signals
When stock falls below a reorder point, the system calculates the quantity, picks the supplier and price from your agreements and drafts a purchase order for a buyer to approve. For distributors and retailers whose reordering depends on one person's spreadsheet.
Function: Operations · Industry: Any industry
Draft purchase orders from low-stock signals
6 steps
At a glance
- Trigger
- An item's available stock falls below its reorder point.
- Typical inputs
- Inventory levels and open purchase orders
- Sales history and forecasts you already use
- Supplier lead times and minimum order quantities
- Price agreements
- Systems it usually connects to
- NetSuite
- Shopify
- Google Sheets
- Slack
- How the work splits
4 rules, 1 model, 1 person steps
How it runs, step by step
6 steps, each tagged by what does the work. Rules are fixed logic, a model reads or drafts, and a person decides.
- Rules Fixed logic in code
- Model AI reads or drafts, with a confidence score
- Person A named person decides
- 1
Detect the trigger
RulesAvailable stock, including open orders and inbound shipments, is checked against the reorder point each day.
- 2
Calculate the quantity
RulesOrder quantity is computed from your formula: lead-time demand, safety stock and supplier minimums or case sizes.
- 3
Flag unusual demand
ModelA model compares recent sales with history and flags items where the formula may over or under order, such as a spike from a one-off sale.
- 4
Draft the purchase order
RulesLines are grouped by supplier, priced from the agreement and assembled into a draft with delivery dates.
- 5
Approve and adjust
PersonA buyer reviews the draft, changes quantities where they know something the data does not and approves.
- 6
Send and track
RulesApproved orders go to the supplier, and confirmations or delays are logged against the order.
Where people approve
The decisions that stay with your team, whatever the confidence score says.
- A buyer approves every purchase order.
- Orders above a value limit need a second approver.
- New suppliers are added by procurement, not by the system.
KPIs to track
What to measure, before and after. Targets come from your own baseline.
- 01Stock-outs on reorder-point items
- 02Excess stock beyond your cover target
- 03Buyer hours spent on routine orders
- 04Purchase orders changed after approval
Questions about this workflow
Is a model necessary for this?
Mostly no. The reorder math is rules. The model's job is narrow: noticing that demand has changed shape and telling the buyer. We do not hand it the ordering decision.
Does it forecast demand?
It uses the forecast you already trust, or a simple method you agree on. If you need a forecasting model, that is a separate project with its own testing against your history.
Which steps use rules, a model and a person?
Rules: detect the trigger; calculate the quantity; draft the purchase order; send and track. Model: flag unusual demand. Person: approve and adjust. Rules are fixed logic in code. A model reads or drafts and reports its confidence. A named person decides.
What do we need to start?
Typically: inventory levels and open purchase orders; sales history and forecasts you already use; supplier lead times and minimum order quantities; price agreements. You also need read access to NetSuite, Shopify, Google Sheets and Slack, or the equivalents you use. A workflow audit measures your volumes and past cases first, then gives a fixed price for the build, so you can decide with real numbers.