A site reports that a consumable is nearly empty. The supervisor places an order, then another cleaner reports the same shortage on the next shift. A second order is raised because the first is not visible. When both deliveries arrive, the store cupboard is full but the records still say the item is low.
Replenishment software needs to represent the work between a shortage report and usable stock. That includes approval, ordering, delivery and receipt. A low stock alert connected directly to a purchase action can repeat the same mistake faster unless pending work is part of the model.
Decide what the count means
Define an item and its unit of measure. A count of three could mean individual bottles, packs or cartons. Store purchase units and usage units explicitly, with an approved conversion where the business uses both.
Keep similar products distinguishable. A familiar label may cover different sizes or formulations, and a supplier substitution is not automatically an approved equivalent. The catalogue should carry the references staff need to identify the item, while approved usage instructions remain controlled by the organisation.
Do not turn this inventory system into technical advice about chemical use. Record the products and approved procedures the business supplies. Compatibility, handling and safety decisions need the appropriate review outside an automatic reorder rule.
Separate a count from a movement
A physical count is an observation at a time. A delivery, transfer or recorded use is a movement. Keeping them separate lets the system explain why an expected balance differs from what someone found in the cupboard.
If the site does not record every small use, avoid displaying a precise live quantity that the data cannot support. Show the last count, subsequent known movements and the age of the observation. A simple low, adequate or review needed state can be more honest than an exact number inferred from incomplete records.
Let staff report an unavailable count. A locked cupboard or an unclear package quantity should not force a guessed value. Create a follow up task if that information is needed before approving replenishment.
Pending supply changes the decision
Before suggesting an order, inspect open requests, approved orders and deliveries in transit. Those quantities are not on hand, but they explain whether another purchase is necessary. Show the expected supply alongside the shortage so a supervisor can decide whether the timing is acceptable.
Deduplicate reports against the same unresolved replenishment need. A new low stock report can update the existing request's evidence rather than creating another independent order. Keep reports from different sites separate even when they concern the same catalogue item.
Use a stable operation reference when submitting a purchase to another system. If the response is lost, retrieve or reconcile the existing order before sending a new one. A local status of unknown should not be treated as proof that the supplier received nothing.
Approval depends on the site's arrangement
Some contracts may let a supervisor order within agreed rules; others may require client approval or a central purchasing team. Model that decision explicitly. The replenishment workflow should not infer commercial authority from the fact that someone can submit a count.
Show the proposed quantity, destination and reason at approval. If any material detail changes afterwards, record the revision and recheck the approval requirements. A previously approved request for one site should not silently become a delivery to another.
Keep rejected or deferred requests visible with a reason. Otherwise the next low stock report can reopen the same request without anyone seeing why purchasing paused it.
Delivery is not receipt
A supplier dispatch notice means goods have left a source, not that the site can use them. Record receipt separately, including partial deliveries, damaged items and a different product arriving. The stock available to crews should change only according to the approved receipt process.
If deliveries go to a central store first, model the later transfer to the site. A total across the organisation can be sufficient while a specific building remains short. Staff need location level availability, not only a consolidated number.
Retain delivery and transfer references so a discrepancy can be investigated without searching unrelated messages. A site supervisor should be able to identify whether the open issue is purchasing, transport or receipt confirmation.
Review differences without hiding them
When a count differs from the expected balance, create an adjustment with a reason and the original observation. Do not overwrite the balance until the history appears to have always matched. Repeated differences may indicate an unclear unit, unrecorded transfers or a counting process that needs revision.
Restrict adjustments appropriately without making ordinary reporting difficult. A cleaner can report what they found; an authorised role can approve the stock correction. Those actions can happen close together while remaining distinct in the record.
Use replenishment history to review thresholds cautiously. A site with occasional events may need different stock arrangements from a steady occupancy site. Base changes on observed usage and approved operational knowledge, not a universal prediction applied to every building.
Test the repeated report and the partial delivery
Run a scenario with two low stock reports, one pending order and a partial delivery to the wrong location. Verify that the system does not purchase twice, does not call the site fully stocked and gives the supervisor a clear next action.
Then simulate a supplier timeout after order acceptance. Confirm that recovery finds the existing order or leaves a visible uncertain state for review. The success criterion is a replenishment trail that staff can explain from the first shortage report to the goods available at the right site.