A reminder for each store when stock is below its level
The customer asks: A reminder per store when its stock falls below a set level
- Verdict: Ready, with limits (4)
- Door: Configure · area: Stock and buying › Alerts and reorder
- Recipe: Set a shop up with no code
- Sample: none yet
- Checked: run on a sandbox 2026-10-16 · POS 2.0.0.647 · the reorder job made a submitted transfer request for one item below its level; not run: the e-mail on creation, the report Itemwise Recommended Reorder Level with sales in range (it returned no rows)
What you build
Item Reorder rows on the item (the store, the level, the quantity, the type Transfer or Purchase) and the setting for automatic requests in Stock Settings; the standard job makes the request.
Limits
- The request is submitted, never a draft (run: type Transfer made a submitted Material Transfer request, status Pending); for a draft see the card stock-and-expiry-alerts.
- Leave the row's warehouse group empty: with a group named, the level is compared with the whole group's stock and a store below its level was not reordered (run).
- The job runs once a day over the whole site, only while the automatic-request setting is on (it is off until someone switches it on: read on the sandbox); it covers every item with a reorder row.
- The quantity requested is the reorder quantity, or the shortfall when that is larger, and it compares projected stock, so an open request or an incoming order delays the next one (read from the code).
Tell the customer
Each store's low stock comes as a transfer request, raised once a day; it is a real request, not a draft.
What next
- Tell the customer the 4 limits above, and write them into the proposal.
- Follow the recipe: Set a shop up with no code.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
- Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.
Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.
Related needs
- A branch sees the stock of its own store and the head office's, no other — Ready, with limits (4)
- A coded reason when a cashier voids, returns or discounts — Ready, with limits (3)
- An e-mail at each approval step with the purchase order's PDF attached, and the uploaded CSV — Ready, with limits (4)
- Members pay less, by tier — Ready, with limits (5)
Start a project shortlist with this need · Put it in your blueprint · Every need