Check seven stock replenishment mistakes, from demand shifts to bulk alerts, before you place a shop order.
Key takeaways
Check these five areas before placing a shop order to avoid common replenishment errors:
- Review demand shifts and overflow warnings. In one documented example, a warning reduced a purchase by 30, from 90 to 60, to keep projected inventory at 100 according to the overflow level, according to Microsoft Learn.
- Verify box math for incoming stock. If a box item includes 10 units, you have no boxes on hand, and one box on order, the Need quantity will be zero, according to Lightspeed.
- Confirm assembly exclusions. Assemblies are not factored into reordering calculations, according to Lightspeed.
- Set maximum stock levels. The Maximum Stock Level defines the maximum quantity that you can keep in stock to avoid overstocking, according to Zoho.
- Check bulk alert conditions. The "At or Below Min Level" condition will overwrite the min level on every item you've selected, according to Sortly.
Use these checks to verify that your proposed order quantities match current stock and incoming deliveries.
Stock replenishment mistakes: the checks before ordering
The seven checks to make before placing a shop order are:
- Ignoring changed customer demand: A customer can change a sales order from 70 to 40 pieces between two planning runs, according to Microsoft Learn.
- Confusing inventory projections: Distinguish projected inventory from projected available inventory when reviewing quantities.
- Overlooking boxes on order: Verify how many units each box holds and how many boxes are already ordered to adjust the need quantity.
- Assuming assemblies are included: Confirm whether your tool excludes assemblies from reordering calculations.
- Ignoring replenishment order settings: Check if the order is a purchase or transfer order and the maximum stock quantity.
- Overwriting individual minimum levels: Ensure bulk alerts do not overwrite specific item minimums.
- Leaving alert fields empty: Fill required fields before setting any bulk alert conditions.
Check changed demand and distinguish inventory projections
Demand shifts between planning runs can alter the quantity your system proposes to buy. In one documented scenario, a customer changes a sales order from 70 to 40 pieces between two planning runs Microsoft Learn. In a separate documented example, the system may create a warning planning line to reduce the purchase by 30, from 90 to 60, to keep the projected inventory at 100 according to the overflow level Microsoft Learn. Without the overflow feature, no warning is created if the projected inventory level is above the maximum, which could cause an extra supply of 30 Microsoft Learn.
Understanding how these warnings work requires distinguishing between two types of projected figures. The projected inventory level increases to +4, while the projected available inventory becomes -1 Microsoft Learn. These two metrics do not always move in the same direction or by the same amount. For instance, the projected inventory level increases (A: +0 => +4 or B: +2 = +6) when supply changes Microsoft Learn. Additionally, the planning system adds the decrease reminder of -3 reminder to the projected inventory level, either A: +4 -3 = 1 or B: +6 -3 = +3 Microsoft Learn.
When reviewing your own replenishment settings, check whether your tool distinguishes between these projected values. If your system uses an overflow level, verify that the warning line correctly reduces the purchase quantity to match that level. This distinction matters because the projected inventory level and the projected available inventory can differ, as shown by the +4 and -1 example Microsoft Learn.
To apply this check, look at the specific item you are reordering. Confirm the current sales orders and see if any have changed since the last planning run. If a customer reduced their order, compare the new sales quantity with the last planning run before you buy. Verify that the adjusted quantity keeps the projected inventory at the intended level. If your tool shows both projected inventory and projected available inventory, note the difference between them. A positive projected inventory does not necessarily mean positive available inventory, as the -1 example demonstrates Microsoft Learn.
Account for boxes on order and excluded assemblies
Incoming boxes reduce the quantity you need to order. If a box item includes 10 units, you have no boxes on hand, and one box on order, the Need quantity will be zero, according to Lightspeed. The on-order quantity includes purchase orders in the Open, Ordered, and/or Check-In statuses, according to Lightspeed.
When a single item is part of a box, the system accounts for stock quantity in boxes, according to Lightspeed. It also counts the on-order quantity in boxes if the single item is part of a box, according to Lightspeed. Verify that your box contents match the unit count in your inventory records. If a box contains 10 units, the system uses that figure to adjust the need quantity.
Assemblies are not factored into reordering calculations, according to Lightspeed. Check your item types to confirm which items are classified as assemblies. If you rely on assembly components for production or display, you must manage their stock separately from the parent assembly.
Review the status of every open purchase order. Ensure that your purchase orders are updated to the correct status before reviewing replenishment suggestions.
Shelf counts are covered in Count shop stock: 4 apps compared for small retailers.
Check the order route and maximum stock setting
Before finalizing a replenishment quantity, verify the order type and vendor settings to ensure the stock arrives at the correct location. In the Replenishments | User Guide | Zoho Inventory, the system allows you to manually create the necessary orders to replenish stock once the initial parameters are set, according to Zoho. This manual creation step is where you define how the stock moves.
You must choose between two specific order types for these replenishments. The documentation states that you can create either a Purchase order or Transfer order, according to Zoho.
If you select a Purchase Order, the system provides a specific field for vendor selection. You can choose a preferred vendor to whom the replenishments should be created, according to Zoho. This setting ensures that the generated order is directed to the supplier you intend to use for that specific item.
To prevent overstocking, review the maximum stock level setting. This field represents the maximum quantity that you can keep in stock to avoid overstocking, according to Zoho. Check this value against your current inventory levels before confirming the order.
Action Step: Open the replenishment settings for one item in your tool. Confirm whether the order type is set to Purchase or Transfer, verify the preferred vendor is correct for a purchase order, and check that the proposed quantity does not exceed the maximum stock level.
Reorder fields are listed in Reorder settings: 9 fields for retail inventory.
Review bulk minimum changes and missing alert fields
Before applying a bulk quantity alert, verify that the selected items have complete data and understand how the chosen condition affects their minimum levels. In Sortly's Quantity Alerts, if a field isn't filled in on some of the selected items, those items won't be eligible for the bulk alert Sortly. Check each item in your selection for missing values before proceeding.
The specific condition you choose determines how the alert interacts with existing minimum levels. The "At or Below Min Level" condition will overwrite the min level on every item you've selected Sortly. This means the tool does not preserve each item's current minimum when this specific condition is applied. If your shop relies on distinct minimum levels for different products, applying this bulk alert will replace those individual settings with the new value.
To avoid unintended changes or excluded items, follow the sequence documented by Sortly. Fill in that field first, then set the alert Sortly. This order ensures that all selected items are eligible for the bulk operation and that the overwrite behavior applies to a complete set of data.
Action step: Open the list of items you intend to include in a bulk alert. Confirm that the relevant field is populated for every item in that list. If any item lacks the value, complete the field before applying the alert condition.
Low-stock warnings are compared in Low-stock warnings compared across 4 retail apps.
Replenishment mistakes reference table by publisher
| Mistake | Key Check | Documented Behavior |
|---|---|---|
| 1. Ignoring changed customer demand | Overflow Warning | The system creates a warning planning line to reduce the purchase by 30, from 90 to 60, to keep the projected inventory at 100 according to the overflow level, according to Microsoft Learn. |
| 2. Confusing inventory projections | Projected Inventory | The projected inventory level increases to +4, while the projected available inventory becomes -1, according to Microsoft Learn. |
| 3. Overlooking boxes on order | Boxes on Order | If a box item includes 10 units, you have no boxes on hand, and one box on order, the Need quantity will be zero, according to Lightspeed. |
| 4. Assuming assemblies are included | Excluded Assemblies | Assemblies are not factored into reordering calculations, according to Lightspeed. |
| 5. Ignoring replenishment order settings | Maximum Stock Level | Maximum Stock Level is the maximum quantity that you can keep in stock to avoid overstocking, according to Zoho. |
| 6. Overwriting individual minimum levels | Bulk Alert Condition | At or Below Min Level will overwrite the min level on every item you've selected, according to Sortly. |
| 7. Leaving alert fields empty | Bulk Alert Condition | If a field isn't filled in on some of the selected items, those items won't be eligible for the bulk alert, according to Sortly. |
Illustrative example of a single item check
Suppose you practice on one item with round illustrative figures only. Demand moves from 70 to 40. A separate warning moves a purchase from 90 to 60 and shows projected inventory at 100. Projected inventory on a second line shows 4, and projected available inventory shows 1. One box holds 10 units, 1 box is on order, and the need quantity shows 0. The maximum stock level shows 50. You mark the order as a purchase, fill the alert field, and only then set the bulk alert. No supplier or product is named here.
Check one item before you order today
Review one item's proposed replenishment in the tool you use, checking the documented quantity inputs and order settings before placing the order.
FAQ: reviewing stock before placing an order
What stock replenishment mistakes should I check before ordering?
Review changed customer demand, distinguish inventory projections, verify incoming boxes, confirm excluded assemblies, check replenishment order settings, watch for bulk minimum changes, and fill missing alert fields. These seven checks cover the specific planning warnings and order settings relevant to your shop's replenishment process.
How does Lightspeed handle a box already on order?
On-order quantity in boxes contributes to the calculation, so a box on order can reduce the Need quantity to zero, according to Lightspeed.
Does Lightspeed include assemblies in my shop's reordering calculations?
No. Assemblies are not factored into reordering calculations, according to Lightspeed.
Which replenishment order types can I choose in Zoho?
You can create either a Purchase order or Transfer order, according to Zoho. These are the two available order types for replenishments in that system.
What happens to item minimum levels when I apply a Sortly bulk alert?
The "At or Below Min Level" condition overwrites the min level on every item you've selected, according to Sortly. This behavior applies to bulk alerts using that specific condition.