POS Reorder Points Guide 2026: Reduce Stockouts

You have seven units left, sell about three a day, and your supplier usually takes four days to deliver. An alert that arrives when stock reaches zero is too late. A useful POS replenishment setup must give someone enough time to act, not merely document that an item is already unavailable.

This 2026 buying guide compares low-stock alerts, reorder points, desired stock levels, and purchasing workflows. It is for retailers choosing a POS or deciding whether an inventory upgrade is worth paying for. The goal is a buying decision grounded in your delivery schedules and item data, not a promise that automation eliminates stockouts.

POSadvice.com helps you compare POS systems; we do not sell or install them. Product examples below come from official documentation reviewed October 6, 2026. They are documentation-based comparisons, not hands-on performance tests. Confirm the exact subscription and product edition before relying on any feature in a proposal.

Low-stock alert vs reorder point vs purchasing automation

These capabilities can coexist, but they are not interchangeable. A low-stock email is not a purchase order. A suggested purchase order is not evidence that a supplier received it. Ask the salesperson to follow one item through the entire process until receiving updates the available stock.

Two documented products to put on the demo list

Square documents low-stock alerts triggered when an item’s in-stock count falls below a set threshold. Its current help page says low-stock alert emails are sent 90 minutes after each location’s configured closing time, with separate emails for multiple locations. It also says alerts are created from Square Dashboard.

That schedule matters if your buyer needs to order before a supplier’s midday cutoff. An after-closing email may still suit the shop, but it is not an immediate replenishment notification. Request a demonstration of other monitoring options if your operation needs earlier action, and confirm which are included in the quoted plan.

Lightspeed Retail R-Series documents reorder points and desired inventory levels, with calculated quantities used in purchase orders, transfers, and a Reorder List report. Its documented calculation considers in-stock units, incoming transfers, and on-order quantities, including specified purchase-order statuses. It also addresses box stock and notes that assemblies are not factored into those calculations.

Lightspeed’s page distinguishes these settings from demand forecasting available with a Lightspeed Analytics subscription. Ask the vendor to identify what is included and what is extra. This is not a declaration that one brand is universally better: the useful difference is between a notification workflow and a demonstrated replenishment calculation that matches your stock model.

Calculate a starting threshold without confusing it with order size

For a simple item reviewed continuously, a practical starting model is: expected demand during replenishment lead time, plus a chosen safety-stock buffer. This is a planning example, not a forecast or a guarantee. The buffer should reflect the uncertainty your business is willing and able to carry.

Suppose, hypothetically, that you expect to sell three units each day, delivery takes four days, and you choose a six-unit buffer. The starting reorder point is three times four, plus six: eighteen units. The six-unit buffer is an assumption for this example, not a universal recommendation.

Now choose a desired level of thirty units. If the system’s qualifying inventory position is sixteen units and there are no incoming orders or transfers, a simple top-up calculation suggests fourteen. That is a different question from why the replenishment review started at eighteen.

If you review inventory only once a week, the continuous-review example is incomplete. Your process may need to cover the time until the next review as well as supplier lead time. Likewise, a purchase placed after a cutoff can have a longer effective lead time. Record those constraints before copying a formula across the catalog.

Define which stock counts before evaluating recommendations

Ask what the software means by on hand, available, allocated, incoming, and on order. Names can hide important differences. Ten units physically present do not necessarily mean ten units are available for a new customer if six are reserved for pickup or a special order.

Open purchase orders deserve particular attention. A stale draft can look like incoming supply in a calculation even though nobody sent it to the supplier. Lightspeed’s documented treatment of Open purchase orders makes checking status definitions especially important when evaluating that workflow. Demonstrate your actual process instead of assuming that every open document represents confirmed supply.

Transfers create another distinction. Stock at a second store is not automatically available at the first store today. Ask how the recommendation handles an approved transfer, an in-transit shipment, and a failed transfer. Our POS stock-transfer guide provides a separate checklist for that movement.

Also test returns awaiting inspection, damaged goods, bundles, and items sold both individually and in cases. If the system excludes a stock type from its calculation, determine whether a separate process is acceptable. Do not compensate for an unclear calculation by silently inflating every threshold.

Run a six-scenario replenishment demo

1. Cross the threshold by one unit. Make a test sale and inspect the low-stock view. Check whether the trigger is below or at the threshold, and when the responsible person learns about it.
2. Add an existing purchase order. Show an unsent draft, a submitted order, and a partially received order. Explain the effect of each status on the recommended quantity.
3. Use different rules at two stores. Give the same item different sales patterns and delivery schedules. Verify that the buyer sees the correct location rather than an unhelpful chain-wide total.
4. Order an item sold in case packs. Ask how a fourteen-unit need is handled when the supplier sells cases of twelve. Check the extra inventory and cost before approving twenty-four units.
5. Cancel or delay incoming supply. Confirm how the buyer finds items that looked covered yesterday but are now at risk. A stock threshold alone may not capture the timing problem.
6. Receive less than ordered. Check the remaining order, stock availability, and the next recommendation. Repeating the same workflow should not create accidental duplicate purchases.

Bring examples from a fast seller, a slow seller, and an item with irregular deliveries. Record each result as passed, failed, or dependent on another tool. A single smoothly replenished demonstration item is not enough to judge the whole catalog.

Pros and cons of simple alerts and advanced planning

Threshold alerts with human review

Pros: Easy to explain, straightforward to audit, and often enough for a shop with a manageable catalog. The buyer can account for promotions and supplier conversations that the system does not know about.

Cons: Thresholds require maintenance, notifications can arrive after an ordering cutoff, and someone still has to calculate and place the order. Alerts become noise when they lack an owner or include items the store deliberately stopped buying.

Reorder points with suggested purchase quantities

Pros: Can reduce repetitive calculations and make location-level purchasing more consistent. A visible target helps managers explain why an order contains a particular quantity.

Cons: Inaccurate stock, stale orders, or incorrect case quantities can produce precise-looking but unsuitable recommendations. Staff still need permission and time to review exceptions, not just an approval button.

Forecast-assisted replenishment

Pros: Worth evaluating where patterns change and manual analysis consumes substantial time. It can provide another input for a buyer managing a large catalog.

Cons: It may cost more and depend on assumptions the buyer needs to understand. Sales history from days when an item was unavailable can understate demand. A new product has little history. Ask how the model handles those situations instead of accepting an accuracy claim without context.

Price the work that remains after the alert

Get line items for inventory tools, purchasing, forecasting, additional locations, training, data cleanup, and support. Include the time required to maintain supplier lead times, item costs, and case packs. A cheaper package can be the right choice if the remaining work is small and clearly owned.

Use the same purchasing scenario for every proposal. Our POS purchase-order guide helps you compare approval, receiving, and partial deliveries after a reorder suggestion is created. The handoff from recommendation to actual order is part of the cost, not an optional detail.

Ask for an export of item thresholds and purchasing data before signing. Determine who can change targets and whether a bulk update can be reviewed before it affects multiple locations. Export access matters when you need to audit a recommendation or change systems later.

Pilot a small catalog before enabling broad automation

Choose a representative set of items and record the starting stock, recent sales, supplier lead time, pending orders, and assigned buyer. Inspect every recommendation during the trial. Write down why staff override a suggestion; repeated overrides can reveal a setup problem or a mismatch between the product and your process.

Measure stockout incidents alongside excess inventory and purchasing time. Fewer stockouts achieved by buying far more than you can store are not an unqualified improvement. Use the same observation period and note promotions or supplier disruptions that affect the comparison.

Buy the level of automation your team can explain and operate. A reliable alert with a clear owner can outperform a sophisticated recommendation nobody trusts. Conversely, a growing retailer should not keep paying for hours of manual calculations if a demonstrated workflow handles them well.

Frequently asked questions

What is the difference between a reorder point and a desired stock level?

A reorder point identifies when to review replenishment. A desired stock level is the target used to calculate how much to buy or transfer. The two settings should not be treated as interchangeable.

Does a low-stock alert automatically place a purchase order?

Not necessarily. An alert may only notify a person that stock crossed a threshold. Ask the vendor to show whether the quoted product suggests quantities, creates a draft order, or submits an order.

How can I estimate a starting reorder point?

For a simple continuously reviewed item, estimate expected daily demand multiplied by replenishment lead time, then add a chosen safety-stock buffer. Adjust for your review schedule, seasonal demand, and data quality.

Should every store use the same reorder settings?

Not automatically. Sales patterns, delivery schedules, shelf capacity, and transfer options can differ by location. Set and test thresholds against each location's operating conditions.