In short: A low on-hand quantity is not an order. Compare available stock with reservations and inbound purchase orders, then open one request a buyer can accept, change or close.
An inventory alert should not become a purchase because a cell dropped under a number in a spreadsheet. Available stock, quantities already promised and deliveries already on the way all change whether you need to buy. For most SMEs the first workflow should create a purchase request that a buyer reviews.
Choosing an inventory product is covered in the inventory management guide. Turning an accepted request into an order is the purchase order workflow. This page is the decision between those two.
Name the stock figures
Pick the system that owns stock. If a spreadsheet and an accounting file both claim to, you do not have a trigger yet. You have a data repair.
| Figure | Meaning |
|---|---|
| On hand | Physical or system quantity at a location |
| Reserved or committed | Already promised to a customer or a job |
| Available | On hand minus reserved, in your definition. Write the formula down |
| Inbound | Open purchase-order quantity not yet received |
| Suggested buy | What the rule proposes. Not an order |
Store SKU, location, unit of measure and the time the figures were read. A suggestion without a timestamp will be actioned on yesterday’s count.
Rules are assumptions
A reorder point and a lead time are inputs the business owns. They are not an industry standard this guide can hand you. Show the assumption on the request: “minimum 20, supplier lead time 14 days, pack multiple 12”. If the source balance is known to be unreliable, raise a data-quality exception instead of a purchase. Buying to correct a bad count makes the count worse.
One open request
Create a single open replenishment request for a SKU at a location. While it is open, further alerts attach to it. Define how a changed requirement revises the suggestion without opening a twin. Two low-stock events at the same moment are the acceptance test: one request, or an explicit lock that serialises them.
When a buyer closes the request with “no buy”, decide how long that suppression lasts. Forever is how you stock out. Until the next receipt, or for a stated number of days, is a rule you can explain.
The buyer still decides
The request may suggest a supplier, a quantity and a date. The buyer can change all three. Price lives on the purchase path, not in the alert. Do not let the workflow email a supplier. Release of an order is the purchase-order control, after approval, on a versioned document.
Microsoft’s error-handling guidance applies when the stock read fails. A failure is not a zero balance. Retry a transient read. Do not turn a timeout into a purchase request for the entire minimum.
Units, warehouses, returns, late receipts
A supplier that sells cartons while you count pieces will double or halve the order unless the conversion is on the SKU and the request shows both units. Multiple warehouses do not share one minimum unless you have said they do. A return and a damaged quantity change available stock only when they are posted in the stock system. A delayed receipt changes the date you need the goods; it should update the open request, not spawn another.
If stock movements support GST records, IRAS requires those records to be kept for at least five years from the end of the accounting period. The reorder suggestion itself is not the tax record. Keep the purchase order and the receipt, as the purchase order guide describes.
What to measure
Count duplicate open requests, stock events that never produced a suggestion, and the age of the balance at the time of the suggestion. Those tell you whether the trigger is safe. They are not a saving.
Prefer the replenishment feature in the inventory system you already run if it can see inbound and reserved quantities and can stop at a request. Integrate when the stock authority and the purchasing authority are different products and the identifiers do not match. That is system integration work, scoped to the identifier and the units.
Illustrative scenario, not a client engagement: a distributor’s available quantity falls through the minimum while a purchase order is already inbound. The workflow links that open order and asks the buyer whether the remainder is still short. It does not create a second order. The buyer can raise a request for the difference or close the suggestion.
Witness the twin alert, the carton-versus-piece conversion, and a delayed receipt that moves the required date. Ask who may edit the rule, and whether the trigger’s definition of available stock is written next to the button that creates the request.
To look at one item that was ordered twice, use the contact form or WhatsApp +65 9071 3976 (chat).
Frequently asked questions
Should the trigger ignore incoming and reserved stock?
No. On-hand stock that is already promised to customers is not available, and stock on an open purchase order may already cover the gap. The request should show both figures. A rule that cannot see them will double-buy.
How are overlapping alerts prevented?
One open replenishment request per SKU and location. Further low-stock events attach to that request as notes or as a revised suggestion. They do not open a second request unless a buyer closed the first.
Who may change the reorder rule?
A named inventory or purchasing owner. The rule stores its minimum, its multiple and the lead-time assumption. Changing it is a versioned edit. A spreadsheet cell with no owner will drift.
Can the workflow place the purchase order itself?
Only if you deliberately add that authority later. The safer first version creates a request. Supplier, quantity and price remain a buyer’s decision, then follow the purchase-order approval path.
