Blog

How to Set Reorder Points by Warehouse

VORQ Operations · 2026-05-19 · 10 min read · Low stock · Reorder points · Multi-warehouse

Pallet racking in a warehouse aisle used to plan site-level reorder points

A single reorder point for every warehouse is a blunt tool. Main DC might burn 40 cartons a week while Van 2 burns 8. If you set one Low stock threshold on company total, the van can empty while the DC still looks “fine”, or you can raise Purchase orders for the wrong destination Storage site.

This guide shows how to set reorder points by warehouse using demand and supplier lead time at two sites, then how those thresholds feed Low stock and purchasing in VORQ.

Answer first

For each SKU at each Storage site, set a reorder point (min stock / Low stock threshold) from typical demand during lead time, plus a small buffer for variability. Review by site, not only by company total. Raise Purchase orders to the site that is short, or use Transfers when another site already holds surplus.

What a reorder point means in VORQ

In VORQ, the reorder signal lives under Low stock. Products carry a minimum stock level. When on-hand falls below that level, the SKU appears on Low stock so buyers can act before a pick fails.

For multi-site teams, enable per-site Low stock where demand differs by warehouse. That way Main DC and Van 2 each get their own threshold check against on-hand at that Storage site, and open Purchase orders destined to that site count as incoming for the shortfall view.

If you still track only a company total, fix site structure first. How to track stock across multiple warehouses explains on-hand versus incoming by site.

Worked example: FLR-120 at Main DC and Van 2

Hypothetical company Apex Flooring runs two Storage sites. SKU FLR-120 is a fast mover at Main DC and a slow top-up SKU on Van 2. Supplier lead time to both sites is 7 calendar days once a purchase order is sent.

InputMain DCVan 2
Average daily demand8 cartons1.5 cartons
Lead time (days)77
Demand during lead time5610.5 (round to 11)
Buffer for spikes / late vans16 (about 2 days)4 (about 2 to 3 days)
Reorder point (Low stock threshold)7215
Current on-hand689
Low stock statusYes (4 below)Yes (6 below)

Formula used here: reorder point ≈ (average daily demand × lead time days) + buffer. Main DC needs 72. Van 2 needs 15. A single company threshold of “50” would miss the van crisis and understate Main DC risk. A single threshold of “90” would fire constantly and train the team to ignore Low stock.

Open Purchase orders matter. If Main DC already has a sent PO for 40 cartons of FLR-120 due next week, Low stock still shows the site is short today, but buyers can see incoming quantity before duplicating the order. If only 20 of 40 have landed, the PO sits partially_received and the remaining 20 still count as expected inbound for that destination.

How to choose demand and lead time numbers

  1. Demand: Use the last 4 to 8 weeks of issues from that Storage site only. Do not average Van 2 into Main DC. Exclude one-off project spikes unless those spikes are now normal.
  2. Lead time: Measure from Purchase orders moving to sent until Receive stock posts the first usable quantity. Use the supplier’s typical time, not the best case.
  3. Buffer: Add days of cover for demand noise and late deliveries. Fast movers and unreliable suppliers need more buffer than stable slow movers.
  4. Unit sanity: Keep thresholds in the same unit you pick and receive (cartons, metres, each). Mixing units is how “72” becomes meaningless.

If a site is replenished mostly by Transfers from the DC rather than supplier Purchase orders, set the van threshold against transfer cycle time, not ocean freight lead time. Otherwise Van 2 will look permanently short while Main DC holds the real buffer.

Step-by-step: set site reorder points in practice

  1. List Storage sites that hold the SKU (Main DC, Van 2, and any shed or cage that sells or fits from stock).
  2. Confirm whether the product should use per-site Low stock. Turn it on when site demand differs or when vans must not empty unnoticed.
  3. Enter the site-aware minimum (72 at Main DC, 15 at Van 2 in the example).
  4. Check Low stock the next morning. Confirm FLR-120 appears for the sites that are truly below threshold.
  5. Raise a purchase order to the short site, or transfer surplus from a fat site. Do not raise two POs “just in case” without reading open sent and partially_received lines.
  6. After Receive stock and putaway, confirm Low stock clears or shrinks as expected.

Pair this with clean locations so on-hand is believable. Thresholds on ghost stock create false calm. Use warehouse locations and bin codes if site balances still feel soft.

When company-wide thresholds are still fine

  • You have one Storage site only.
  • Secondary sites are pure overflow with no independent demand.
  • Every replenishment is a Transfer from a single DC, and you manage the DC buffer deliberately.

Even then, write the rule down. Teams grow into a second site faster than they rewrite purchasing habits.

Common mistakes

  • Copying the same number to every site. Van 2 is not a miniature Main DC.
  • Ignoring open POs. Reordering while a sent or partially_received order already covers the shortfall creates dock congestion and cash tied in excess.
  • Setting thresholds after a stock-out panic without measuring demand. Panic numbers are usually too high and stay forever.
  • Silencing Low stock instead of fixing the threshold or the late supplier. Badges only help if people trust them.
  • Forgetting Stock counts. A wrong on-hand makes every reorder point lie. Cycle-count the SKUs that trigger the most Low stock noise.

Review cadence

Revisit thresholds quarterly for top movers, and after any supplier lead time change. When Analytics shows rising overdue Purchase orders for a supplier, temporarily raise buffers for that supplier’s SKUs rather than pretending lead time is still seven days. For the overdue review itself, use how to track overdue purchase orders.

For the product walkthrough of alerts and replenishment signals, stay with Low stock reordering. To put site thresholds live, start at signup or review pricing.

Reorder points by warehouse are not a maths competition. They are honest site-level floors so Low stock points at the Storage site that will fail first, with Purchase orders and Transfers aimed at the right place.