Quick Answer
A vending machine assortment review should evaluate every SKU by customer need, sales velocity, contribution margin, stockout hours, expiry, refill burden, package and dispensing compatibility, price position, daypart, and venue role. The output should identify which products to keep, expand, test, reprice, reposition, or remove, with controlled planogram and software updates.
This is the working method I would use with an operator, distributor, or category manager who has real sales data but is not sure what to change next. It works for a single machine, although it becomes much more valuable once several locations start behaving differently.
Start With the Job the Machine Has to Do
Before opening a sales report, ask a simpler question: what job is this machine supposed to do for the person standing in front of it? Convenience snacks, frozen meals, workplace PPE, travel fragrance, helmet cleaning, electronics, gifts, and health products solve different needs. Define target users, purchase occasion, operating hours, average transaction value, service level, and venue promise before comparing individual SKUs.
That answer needs some commercial boundaries around it, including target gross margin, minimum contribution, acceptable expiry, maximum refill frequency, capacity constraints, payment price points, brand obligations, and restricted products. A bestseller that conflicts with safety, venue, package, or service requirements may not belong in the machine.
Get the SKU Data Straight First
The unglamorous part comes next: clean up the SKU master. One product should have one code and one agreed record covering its name, brand, category, dimensions, weight, cost, selling price, tax, supplier, case pack, shelf life, storage condition, compliance fields, dispensing method, slot and image. Keep warehouse, dashboard, payment, planogram, and finance records aligned.
Packaging changes deserve more suspicion than they usually get. A supplier may change bottle height, bowl rim, wrapper friction, glass weight, barcode, or case quantity without changing the consumer name. The revised package should pass dispensing and capacity checks before it replaces the approved version.
Not Every Product Is There for the Same Reason
That distinction matters. Otherwise the slow but useful product is removed, while three near-identical bestsellers quietly compete with one another.
Give each SKU a reason for occupying space. It may bring traffic, build margin, cover a basic need, offer a premium step-up, anchor an entry price, serve a season, represent a local favorite, support a bundle, or simply be a measured experiment. Product roles explain why a slower SKU may still deserve space and prevent the team from selecting only by unit sales.
Too much overlap is where the shelf begins to look busy without becoming useful. If five nearly identical products compete for the same customer and daypart, they may fragment demand and create stockouts in the best item while slow units expire. Measure incremental value when a new SKU is added, not only its isolated sales.
Fast Sellers Can Still Be Misread
Look at units per active day and sales or contribution per slot, but keep days of supply and stockout hours beside them. Refill quantity and demand by weekday or daypart often explain what the topline hides. A high-velocity product with frequent stockouts may need more facings, a larger lane, or a different refill threshold rather than removal.
Pick a period that was genuinely operational. Promotions, venue closures, payment failures, temperature alarms and late refills all need to be marked; otherwise the comparison is fiction with tidy decimals. Low recorded sales during poor uptime do not prove weak demand. Compare adjusted results at target availability when making permanent decisions.
Margin Looks Different Once the Route Is Included
Now follow the money further than gross margin. Product cost matters, of course, but so do payment fees, venue share, spoilage, refunds, promotions, refill labor, route insertion and category-specific consumables. A bulky low-value item may consume capacity and labor that could support a smaller, stronger product. A high-margin item may still be weak if it creates service claims.
Compare profit per slot, per cubic unit of capacity, per refill minute, and per active day where useful. The correct measure depends on the constraint. Space-limited machines need capacity productivity; remote routes need labor and visit productivity; premium sites may prioritize transaction value and presentation.
Slow Stock Is Usually Trying to Tell You Something
Expiry, spoilage, damage, temperature loss, returns and markdowns should be visible by SKU and location. Lumping them together as waste is convenient and not very helpful. Separate poor demand from overloading, weak forecasting, supplier minimums, and route timing. Slow products may be profitable at smaller quantities even when a full lane creates waste.
Use first-expire-first-out rules, lot visibility, loading limits, and risk-based refill quantities. Frozen, refrigerated, fresh, fragrance, liquid, hygiene, and high-value products require different controls. Inventory tied inside a slow machine also has a financing cost and redeployment risk.
The Package Has to Work in the Real Machine
We have seen projects lose time here. The product looked right, the capacity calculation looked right, and the package still leaned, jammed or arrived damaged.
Use the package that will actually be sold and run it repeatedly through the real spiral, belt, elevator, locker, robotic pickup, nozzle, bowl or controlled-release mechanism. A CAD dimension is not a vend test. Check dimensions, center of gravity, friction, stiffness, leakage, breakage, orientation, label interference, and customer pickup ergonomics across repeated cycles.
Record approved parameter ranges and reject uncontrolled package substitutions. Glass fragrance bottles, frozen bowls, soft pouches, irregular PPE, and fragile electronics may require elevator or no-drop delivery. Product decisions and machine engineering must remain connected.
One Planogram Rarely Fits Every Venue
A product does not perform in a vacuum. Venue type, audience, daypart, climate, local habits, price sensitivity, language and nearby alternatives all change the result. A product can be strong in a factory and weak in a hotel, or successful at an airport departure zone and irrelevant at arrivals. Avoid forcing one national planogram onto every context.
Create controlled location clusters with a common core plus local flexibility. Define which SKUs are mandatory, which are selected by cluster, and which require approval. This preserves operational simplicity while allowing meaningful localization.
Watch What Customers Buy Instead
Where multi-item purchase is possible, review products bought together, order sequence, bundle response, and average transaction value. For single-vend systems, examine whether stockouts transfer demand to another SKU or cause customers to leave. This distinguishes true category demand from one-product loyalty.
When adding a premium or promotional item, compare total category contribution before and after. New-product sales may merely replace an existing product. Keep a product when it increases total value, reaches a new customer, protects availability, or serves a clear strategic role.
Test New Products Without Muddying the Result
For a product test, write down the locations, baseline, duration, slot count, price, loading quantity, promotion, success measure and stop rule before anybody sees the result. Change one main variable at a time when possible. Testing a new product, new price, new screen message, and new placement simultaneously makes attribution weak.
Use enough operating days to cover weekday and daypart patterns, but stop early for safety, package, quality, or dispensing problems. Record test configuration and software version so results can be reproduced before wider rollout.
Make a Decision, Then Put a Date on It
Leaving a weak SKU under review for six months is also a decision; it is just an expensive and undocumented one.
Keep stable core products; expand facings or capacity for profitable constrained demand; fix products affected by price, availability, placement, package, or machine issues; test uncertain opportunities; and remove structurally weak products. Every decision should include evidence, owner, effective date, and review date.
One bad week is not a verdict, especially when the machine was half empty or unreliable. The reverse is also true: an old favorite should not keep its slot forever on reputation alone. Likewise, do not keep a slow item indefinitely because it once sold well. Use rolling evidence and explicit exception approval.
Keep the Screen and the Physical Machine in Sync
Changing a product touches more than the tray. Slot parameters, screen image, name, allergen information, price, tax, low-stock threshold, promotion, payment amount, refund record and reporting may all move with it. Use a controlled change request and confirm the physical load matches the digital setup.
For multi-location fleets, schedule effective dates and version identifiers. Train refill staff, update pick lists, verify stock availability, and test dispense and payment after the change. Rollback instructions should be available for failed packages or incorrect configuration.
Let Field Evidence Shape the Next Machine
When the next machine is specified, bring the awkward field evidence into the room: actual dimensions, fast and slow movers, stockouts, refill effort, failed packages and what customers chose when their first option was gone. Evidence may justify larger frozen bowl capacity, adjustable belts, elevator delivery, secure high-value compartments, more fragrance channels, or flexible industrial drawers.
Share approved package samples with the OEM and preserve them for testing. Capacity claims should be based on the intended product mix, not theoretical maximum slots. The right assortment and the right dispensing architecture should be designed together.
A Review Rhythm That People Will Actually Use
The rhythm does not need to be elaborate. Check stockouts, expiry, failed vends and live tests each week; look at SKU and location economics monthly; reserve the wider discussion about roles, suppliers, prices, capacity and machine changes for a quarterly review. Seasonal categories may need a separate calendar.
A good review ends with names and dates, not another deck nobody opens. Track whether changes improved category contribution, availability, waste, customer experience, and field cost. Feed the result into location renewal, route planning, inventory control, and fleet expansion decisions.
Assortment Decision Table
| Decision | Typical evidence | Next action |
|---|---|---|
| Keep | Healthy contribution and role | Protect availability |
| Expand | Profitable demand constrained by capacity | Add facings or capacity |
| Fix | Demand exists but execution is weak | Correct price, package, payment, or refill |
| Test | Promising but insufficient evidence | Run a controlled pilot |
| Remove | Structurally weak with no strategic role | Sell through and replace |
Related Buyer Resources
- Inventory shrinkage and reconciliation checklist
- Pricing and promotion governance checklist
- Route planning and refill cost checklist
- Dashboard specifications buyer guide
- Custom vending machine RFQ template
- Custom vending machine prototype cost guide
- Custom vending machine dispensing methods guide
- Custom vending machine factory acceptance test checklist
- Custom vending machine engineering change control guide
- Custom vending machine pilot data and scale guide
- Vending machine payment API integration guide
- Vending machine shipping import planning guide
- Vending machine testing checklist before mass production
Customer Incident and Product Recall Resources
- Vending machine customer complaint and failed-vend response playbook
- Vending machine product recall and traceability checklist
Continuity and Security Resources
- Vending machine business continuity and disaster recovery plan
- Vending machine cybersecurity and fraud incident response checklist
Platform and Payment Migration Resources
- Vending machine software platform migration checklist
- Vending machine payment provider and terminal migration checklist
Software Release and API Monitoring Resources
- Vending machine software and firmware release checklist
- Vending machine API integration monitoring checklist
FAQ
How often should a vending assortment be reviewed?
Monitor exceptions weekly, review SKU performance monthly, and run a strategic category review quarterly or before seasonal changes.
Which metric is most important for vending products?
Use contribution after operating cost together with availability, stockouts, expiry, slot productivity, refill burden, and strategic role.
Should every location carry the same products?
Use a standardized core with controlled variation by venue, audience, daypart, climate, and local demand.
How should a new vending product be tested?
Define locations, baseline, price, capacity, duration, success metrics, package test, and stop criteria before launch.
How can OBO support assortment planning?
OBO can review product dimensions, capacity, dispensing, sensors, refrigeration, software fields, payment, and machine configuration.
Request a Quote
Privacy respected. No spam. Ever.