The Reorder Point That Belongs to No Warehouse
Each warehouse carries its own minimum and maximum, and the Reorder screen reads them. But the low-stock alarm, safety stock and lead time live on the item, and the alarm compares the national total. A distribution centre can be at zero for a fortnight while the number on the dashboard stays green.
The short version
The low-stock alarm compares one reorder point per item against total stock across every warehouse you own. If you run one store, this is correct and you can stop reading. If you run regional distribution centres two thousand kilometres apart, the alarm is measuring the wrong thing — so give each centre its own minimum and maximum, and replenish from the Reorder screen one centre at a time, because that is where the per-site figures are read.
A distributor with centres in São Paulo, Recife and Manaus does not have one stock position. It has three, and the distance between them means they are, for practical purposes, three businesses that share a purchasing department.
Our system knows exactly how much is in each. It holds stock per warehouse and per bin location, moves it with a full history, and will report the balance at any site you ask about. What it will not do is raise an alarm about any of those numbers individually — the per-site figures are read when somebody asks, on the Reorder and balancing screens, not pushed at anyone.
One number, one alarm
An item carries a reorder point. It also carries a safety stock figure and a lead time, with organisation-wide defaults behind them. Each warehouse can also carry its own minimum and maximum for the item, set on the item's Stock tab on the web or in the mobile app.
Those per-warehouse levels are read in two places. The Reorder screen, with a warehouse chosen, offers every item at or below that warehouse's minimum and suggests filling it to the warehouse's maximum. Stock balancing uses the same minimum to decide which site is short. Everywhere else — the low-stock alert, the reminders, the dashboard tile, the count of items needing attention — the comparison is total stock across all warehouses, against the item's single reorder point.
The system can be told where you need stock. The alarm only hears the total.
The failure has a shape, and it is not random
It always fails the same way: the site that is short is invisible while the network is long. Which is the common case, because stock accumulates where it lands and demand happens where the customers are.
One item, three centres, one reorder point
Nothing here is a defect in the arithmetic. 460 is genuinely more than 300. The problem is that 460 is not a quantity anybody can sell, because the units are in the wrong cities and the freight between them takes days. Give São Paulo a minimum of 150 and Reorder for São Paulo lists the item at once — but only when somebody opens it for São Paulo.
Now run it in the other direction and it is just as bad. Set the reorder point high enough that São Paulo never runs dry — say 900 — and every one of your items is permanently in alarm, on every screen, for the whole network. An alarm that is always on is an alarm that gets turned off. That is why the per-site figure belongs on the warehouse, not on the item.
Why the distances make this a Brazilian problem specifically
Not because the software behaves differently here, but because the cost of being wrong scales with the distance between your sites, and few distribution networks in the world are stretched further.
Rebalancing between two warehouses in a small country is an inconvenience — a van, an afternoon. Rebalancing between the south-east and the north is a decision with a freight cost, a transit time measured in days rather than hours, and in some corridors a river. A system that lets a site drift to zero without saying anything is not costing you a phone call; it is costing you the difference between replenishing from your own network in time and buying locally in a hurry.
The discipline that works instead
-
Give each centre its own minimum and maximum
On the item's Stock tab, set what São Paulo, Recife and Manaus should each hold. Start with your fast movers. A centre left blank falls back to the item's reorder point, so the levels can go in a line at a time.
-
Run Reorder per centre on a fixed day, every week
Choose the warehouse on the Reorder screen and it lists every item at or below that centre's minimum, with a quantity that fills it to its maximum. Nothing pushes that list at you, so make it a standing item with a named owner rather than something somebody remembers.
-
Treat rebalancing as a scheduled activity, not an exception
Stock balancing suggests transfers from a centre above its minimum to one below it, and transfers between your own warehouses are fully built — dispatch, receipt, partial receipt, shortfall, return to source. Put a weekly rebalancing review in the calendar and use the suggestions as its agenda, deciding each one against the freight it costs.
-
Do not let the dashboard tile be your replenishment process
It is measuring the network. If your business is regional, it is answering a question you are not asking, and it is answering it with a green tick.
Four questions about replenishment, for us or anybody else
Show me the reorder point for this item at this warehouse.
A good answer sounds like
A field, on the warehouse-item combination, with its own value.
What it actually means
Ours is a minimum and maximum per warehouse on the item's Stock tab, read by Reorder and balancing. Then ask the next question, because the alarm may not read it — ours does not.
Which stock figure does the low-stock alert compare against?
A good answer sounds like
A named figure — total, on-hand at a site, or available after allocations.
What it actually means
Three different answers, three different products. The word "available" is doing a lot of work in most demonstrations.
Does anything suggest a transfer between my own sites?
A good answer sounds like
A rebalancing suggestion, or an honest no.
What it actually means
Suggestion engines are rarer than vendors imply. Ours suggests a transfer from a site above its minimum to one below it, and leaves the decision to send the vehicle with you.
Can lead time differ by supplier and by destination?
A good answer sounds like
Yes, held on the supply relationship.
What it actually means
Ours is one figure on the item, with an organisation-wide default behind it — so a two-day delivery and a six-week import share a number.
Per-site replenishment is a dimension, not a new module
The stock is already held per warehouse, and each warehouse can already carry its own minimum and maximum. What remains is having the alarm and the rest of the replenishment inputs read that same dimension. That is a well-shaped piece of work rather than an open-ended one, and it is worth describing precisely so you can judge the size of it.
A low-stock alert per warehouse
The alert and the reminders comparing each site's own balance with its own minimum, so a centre at zero is pushed at you rather than found on a screen.
Safety stock per warehouse
A buffer set per site, so a centre a week's freight away can hold more cover than one a van ride from the supplier.
Lead time on the supply route
The smallest of the three and the one that quietly improves every other number, because a single item-level lead time cannot describe a network with an import and a local supplier in it.
We put scope on a public page and dates in a written quote. Describe your network — how many sites, how far apart, and which one hurts when it is empty — and we will come back with a written scope, timeline and cost before you commit.
Scope per-site replenishmentWhat AWRA OpsHub does today
- Stock held, valued and reported per warehouse and per bin location, with complete movement history.
- A reorder point, a safety stock figure and a lead time on every item, with organisation-wide defaults behind the last two.
- A minimum and maximum per warehouse, overriding the item's reorder point — the Reorder screen for a chosen warehouse offers items at or below that warehouse's minimum and fills to its maximum, and balancing reads the same minimum.
- Stock balancing suggestions between your own sites, from a warehouse above its floor to one below it, advisory rather than automatic.
- Low-stock alerts, reminders, a dashboard tile and a low-stock report, all driven from the item's own reorder point against total stock.
- Automatic requisition raising against a department when an item falls below its point, through the workflow engine.
- Transfers between warehouses with dispatch, receipt, partial receipt, recorded shortfall and return to source.
- A blended 30/90-day consumption velocity per item with a suggested reorder quantity built from lead time and safety stock.
More we can add to your workspace
- Safety stock and lead time per warehouse, so a distant centre can carry more cover than one beside the supplier. Commission it
- Low-stock alerts and reminders per warehouse, comparing each site's own balance with its own minimum and pushing the result at the person who owns that site. Commission it
- Supplier selection on an automatic replenishment — the rule raises a requisition against a department and sourcing stays manual. Commission it
- Order sizing beyond a fixed configured quantity or the difference between the reorder point and current stock: pack sizes, price breaks and demand shaping. Commission it
Where we point you to a specialist
- One reorder point is the right design for a single-site business, and most businesses are single-site. This page is about the ones that are not.
- While the alarm reads the network total, setting the item's reorder point for your largest site keeps that site's alert honest. It does over-order for the network on the alert's terms, and you should know that you are choosing it.
- This is market-neutral. It is the arithmetic of a spread-out network; Brazil is where the distances make it expensive fastest.
Size the reorder points with somebody
The hour that pays for itself is the one where you decide what each site should hold, and type it in as that warehouse's minimum and maximum. Bring your three biggest centres and your top hundred lines.
Set the points properlyFrequently asked questions
Can I set a reorder point per warehouse?
Yes. Each warehouse can carry its own minimum and maximum for an item, on the item's Stock tab on the web or in the mobile app. The Reorder screen and stock balancing read them. The low-stock alert and reminders compare total stock with the item's reorder point, so the per-warehouse levels are the place to hold a site figure — a custom field would not change the alert either.
Does the automatic requisition know which warehouse is short?
It fires on the item-level comparison, so it knows the item is below its point across the organisation. It raises a requisition against a department, and it does not select a supplier or a destination site — sourcing and routing stay with your buyer.
Is a per-warehouse balance report available today?
Yes. Stock is held per warehouse and per location and can be reported that way, over any period, and the item page shows each warehouse as at or below its minimum, within its levels, or above its maximum. What remains is pushing a short site at you as an alert rather than waiting for somebody to look.
What should I set the item's reorder point to, when warehouses have their own?
Set each centre's minimum and maximum on the warehouse, and set the item's reorder point for the alarm — to the requirement of the site whose stockout costs you most, not to the sum of the network. The alert reads the total, so you will stop discovering an empty distribution centre from a customer at the cost of a slightly early warning for the network.