Vending Machine Restocking Schedule: Routes, Par Levels and Stockout Control

18/11/2026

VENDING OPERATIONS · FIELD GUIDE

Build a restocking schedule from demand, not habit

A fixed weekly visit is easy to remember, but it can leave a high-selling machine empty while sending a driver to a slow location too often. A useful restocking plan connects sales velocity, usable shelf capacity, delivery lead time, product shelf life, route travel and the service promise made to the venue. This guide turns those inputs into a repeatable schedule with clear exceptions.

01 · Forecast
Daily sales by SKU and site
02 · Protect
Par levels and safety stock
03 · Execute
Routes, proof and review

Start with a reliable site and SKU baseline

Export at least four recent weeks of sales by machine, product and day when available. Mark holidays, site closures, promotions, stockouts and outages. A zero-sales day during a stockout is missing demand, not proof that demand vanished. Record the machine's usable capacity rather than a brochure maximum: different packaging, lane settings and temperature zones change how much can actually be stocked. Confirm minimum order quantities and supplier lead times for every fast-moving item.

Group products by operating risk. Ambient packaged snacks can often tolerate a longer interval, subject to their dates and local rules. Chilled meals, milk and other short-life goods need tighter temperature, date and waste controls. High-value products may need a different security and reconciliation process. Use the product-mix guide to decide which SKUs deserve a lane before optimizing delivery frequency.

Calculate a starting par level

For each SKU, estimate average daily units sold over a clean period. Set a target number of days of supply based on route access and shelf life. Add safety stock for plausible demand variation and supplier delay, but never exceed physical capacity or usable life. One practical starting formula is:

Target par (units) = expected daily sales × coverage days + safety stock.
Suggested refill quantity = target par − saleable units on hand − confirmed inbound units.
Round only to the pack size that the machine can hold. Reduce the target if expiry would occur before the next visit.

Illustrative example: a drink sells 8 units per day. The planned interval is 4 days and the operator holds 6 extra units for variation. Target par is 8 × 4 + 6 = 38 units. If 11 saleable units remain and no delivery is already inbound, the suggested refill is 27 units, subject to lane capacity and case-pack constraints. If the lane holds only 30, a four-day interval is not feasible at that velocity. Add capacity, change the mix or visit sooner. These numbers are planning examples, not guaranteed demand forecasts.

Use a reorder point to trigger exceptions between scheduled visits: expected sales during the time until the next possible delivery, plus safety stock. A remotely reported stock count should be checked against physical counts because failed vends, misloaded products, theft and telemetry gaps cause differences. A recurring mismatch is a service problem to investigate, not a reason to inflate every par level.

Choose visit frequency by economics and service risk

Estimate the contribution margin preserved by avoiding a stockout, the cost of an extra stop, and the cost of expired or damaged goods. A high-volume office machine may merit several visits a week; a low-volume site may need fewer, provided the product life and venue agreement allow it. Avoid a blanket rule across all machines. Where a site has limited access hours, schedule inside a confirmed delivery window and keep a fallback contact. Where temperature-sensitive products are stocked, use logged temperatures and documented handling procedures, not sales alone, to set the interval.

Calculate a simple coverage signal: usable on-hand units divided by expected daily sales. Treat products with less coverage than the next feasible visit as urgent. Review machine-level and SKU-level signals; one popular drink can be empty even when the cabinet looks full. Prioritize failed-payment and cooling alarms separately from replenishment because they may require a technician rather than a delivery driver. The maintenance checklist helps distinguish these tasks.

Design routes that drivers can actually complete

Map sites by geography, access window, machine service time and loading constraints. Build a route with realistic travel, parking, security check-in, lift time, product rotation, cash collection where relevant, cleaning, test vend and documentation. Add a buffer for traffic and unexpected service work. A route that assumes every visit is a quick refill will fail as soon as a machine needs attention. Assign backup stock and a backup operator for critical sites.

Pre-pick each stop from the latest sales and on-hand data, but let the driver adjust using the physical count. Pack chilled goods in equipment appropriate to the product and local requirements; record temperatures where required. On site, rotate by date, remove damaged or expired items, check prices and labels, clean touch points, confirm payment works and record a post-service photo or checklist. Reconcile what left the vehicle, what entered the machine, what was removed and what was returned to storage. This makes shrinkage and waste visible.

Use a weekly planning table

The table is an example of the decision logic. Replace the values with site data and contractual service targets. Flag exceptions daily, then review route performance weekly.

Signal Evidence Action
Coverage below next visit SKU sales and usable on-hand Move visit forward or replenish remotely held stock
Repeated stockout Out-of-stock duration and demand trend Increase capacity or shorten interval
Rising waste Expired units and disposal log Lower par, change mix or visit later
Count mismatch Physical count versus telemetry Audit vends, loading and device events
Route overrun Actual stop and travel minutes Rebalance stops and access windows

Measure outcomes and adjust the plan

Track stockout hours for top SKUs, fill rate, expired or damaged units, sales per visit, cost per stop, route completion, count accuracy and complaint rate. Define each metric so teams calculate it consistently. A high fill rate alone can hide too much inventory and waste; fewer visits alone can hide lost sales. Compare changes against an appropriate baseline and note promotions, seasonality and site traffic. Review the first two to four weeks after launch more frequently, then adjust the plan when a clear pattern appears.

Give each venue a service contact and a simple way to report an empty lane, refund issue or machine fault. Confirm whether the operator or venue owns the product and who approves substitutions. If the agreement promises a response time, measure it from the agreed event, such as a validated alert or reported complaint, to the agreed resolution. Keep a record of exceptions and follow-up actions.

Questions to ask before scaling a route

  • Can the system export SKU-level sales, stockouts and service events by machine?
  • How are physical counts reconciled with telemetry and cashless settlements?
  • Which products need temperature logs, date rotation or special handling?
  • What is the cost of an extra visit versus the contribution lost to a stockout?
  • Who handles refunds, payment failure, cooling alarms and technical repairs?

These answers affect machine selection as well as route design. The installation checklist covers access, handover and telemetry checks that make later restocking easier.

Frequently asked questions

How often should a vending machine be restocked?

Use expected sales, usable capacity, shelf life, route access and service commitments to set the interval for each site. Recalculate when stockouts, waste or traffic change.

What is a par level?

It is a target quantity for a product at a location. Set it from demand over the coverage period plus a reasonable safety allowance, constrained by capacity and expiry.

Can telemetry replace physical inventory counts?

No. It helps prioritize visits, but loading errors, failed vends, theft and data gaps require periodic physical reconciliation.

What should the driver record after a visit?

Record quantities added and removed, dates, issues, cleaning, test transaction, temperature where required and a final count or photo. The exact record should match the operator's procedures and local rules.

Plan a maintainable vending route

Tell Micron your product mix, expected daily transactions, number of sites, access windows and payment methods. We can help identify machine capacity, telemetry and service requirements to test before rollout.

Discuss your vending project →

Methods and figures are illustrative. Validate product handling, food safety, electrical and contract requirements for your location. Last reviewed: November 2026.