A new product may sell better or worse than the one it replaced. A simple test gives the answer.
- Why Test Instead of Just Adding
- Where New Product Ideas Come From
- Does the Product Fit the Machine
- Choosing a Slot for the Test
- One Change at a Time
- How Long to Test
- Watch Out for Seasons and Events
- Letting People Know
- What to Measure
- Comparing With the Product It Replaced
- User Feedback
- The Decision After the Test
- When the Product Stays
- When the Product Goes
- The Site's Role in Testing
- Example: An Office and Sugar-Free Drinks
- What to Check Before a Test
- Snack Machines
- FAQ
Someone on the team brings a new drink they saw at the store into the office and asks whether it could go in the machine. The office manager passes the request to the operator. The operator puts the drink on one spiral, and two weeks later it turns out only the person who suggested it bought it, twice. Does that mean the product failed? Not necessarily. Maybe nobody noticed it was there, maybe it sat on the bottom shelf, or maybe the test was too short. This article shows how to test a new product in a machine sensibly: how to choose it, where to place it, how long to test, what to measure, and how to decide. We won't give a sales threshold that means success, because that depends on the place and the operator.
Why Test Instead of Just Adding
A machine has a limited number of slots. Every new product takes space that used to belong to another. If the new item doesn't work out, it occupies a spiral for weeks while a product that did sell was unavailable. Add expired units and disappointed customers looking for their favorite candy bar. A test limits that risk. Instead of changing the offer permanently right away, the operator checks the new product in a controlled way, in one slot, for a set time. Then they decide based on data, not a hunch or one person's enthusiasm.
Where New Product Ideas Come From
Ideas for new products come from different sources. User suggestions, which are worth asking for regularly. Watching what people bring in from outside, for example from the store nearby. New items from suppliers who propose products proven elsewhere. Trends, such as growing interest in sugar-free or plant-based products. The operator's experience at similar sites. Each source has value, but none guarantees success. A product that sells great at a gym may sit untouched at an accounting firm. That's why every idea is worth checking at the specific place.
Does the Product Fit the Machine
Before a product goes into a test, check whether it fits the machine at all. Will it fit on a spiral and dispense properly? Some packages are too big, too soft, or shaped in a way that jams. Does it need refrigeration, and if so, can the machine provide the right temperature? Is its shelf life long enough given the pace of sales at that site? Is its price within what customers will accept? The answers let you rule out products that wouldn't work anyway, before they take up space in the machine.
Choosing a Slot for the Test
A new product has to go somewhere, which means something has to make room. Ideally, the new item replaces the weakest seller, not regular customers' favorite. Also think about where in the machine it will sit. A product at eye level is more likely to be noticed than one near the floor. If the new item lands in the worst slot, the test may go badly not because the product is bad, but because nobody saw it. A good slot during the test gives the product a fair chance.
One Change at a Time
A common mistake is testing several new items at once while also changing prices or the machine layout. Then it's hard to tell what worked. Maybe the new drink sells well because it sits next to a popular sandwich? Maybe the old candy bar stopped selling because it was moved lower? It's better to test one or two new items at a time and leave everything else alone. Then the results are readable. It's a slower approach, but it gives firmer conclusions. A machine isn't a lab, but a little testing discipline saves a lot of wrong decisions.
How Long to Test
A test has to run long enough for the results to mean something. The first days can mislead: curiosity may inflate sales, and lack of awareness may deflate them. Ideally, a test covers several full weeks and the site's typical working days. If the place has a clear weekly rhythm, such as a hybrid office with peak days, the test should cover several of those cycles. On the other hand, a test can't run forever, or it stops being a test. Set the length in advance and write it down, so the decision isn't postponed indefinitely.
Watch Out for Seasons and Events
Test results depend on when the test happens. A cold drink tested in winter will do worse than in summer. A snack tested at a school right before vacation won't stand a chance. An event in the building, such as a conference or an open day, can temporarily inflate sales. That's why it's worth remembering what was going on during the test when judging the results. If possible, move the test to a more typical period. If not, factor those circumstances into reading the data and don't treat the result as final.
Letting People Know
People rarely look closely at a machine they know. They walk up, pick the same thing as always, and leave. A new product can go unnoticed for a week. That's why it's worth announcing. A simple "new" sticker by the slot, a short message in the company chat, or a note from the office manager can make a big difference. If the product appeared at users' request, mention it. People are more willing to try something they asked for themselves or that a coworker recommended. Agree on the rules for posting information on the machine with the operator and the building manager.
What to Measure
The basic measure is sales: how many units of the new product sold during the test. But it's worth looking wider. How did sales change week by week? Did they grow as people found out, or drop after the first burst of curiosity? How many units had to be pulled past their date? Did sales of other products change? Maybe the new item didn't attract new customers but just took sales from a similar product. It's also worth collecting feedback: did anyone praise it or complain? Together, this information gives a fuller picture than the unit count alone.
Comparing With the Product It Replaced
A good reference point is the product whose slot the new item took. If the new drink sells better than the old one in the same slot, that's a good sign. If worse, it may be better to go back. Comparing with the whole offer helps too: is the new item near the top, in the middle, or at the bottom of the list? Data from the operator's other sites can be useful, but carefully, because every place is different. What matters most is the comparison in the same machine, over a similar period, with the same people.
User Feedback
Sales data is one thing, but user feedback adds context. Maybe the product sells poorly because it's too expensive, and people would gladly buy it at a lower price. Maybe the taste is great but the package is hard to open. Maybe someone bought it once and didn't come back because it was warm. You can gather that through a short chat with a few people, a note by the machine, or the office manager. No big survey needed. A few specific comments often explain more than a sales chart.
The Decision After the Test
At the end of a test, there are usually three options. The product worked and stays permanently, perhaps in the same slot. The product has potential, but something needs to change, such as the slot, the price, or the flavor variant, and the test is repeated. The product didn't work, and the previous one comes back or another new item gets a try. Each decision is fine if it rests on data. Write down the test result, so in six months nobody tests the same product all over again because someone suggested it once more.
When the Product Stays
If the new item worked, consider whether it got the right spot. Maybe it deserves a second spiral because it runs out before every visit? Maybe it can move lower, and the good slot can go to the next test item? It also helps to tell users the product is staying, especially if it appeared at their request. A successful test is also information for the operator about what people at that site look for. Maybe similar products would work too? Every test teaches something about the site, not just about one product.
When the Product Goes
Dropping a new item is a normal part of testing, not a failure. Not every product fits every place. What matters is doing it efficiently and without waste. Remaining units can be sold until their date or moved to another site where they may do better, according to the operator's procedures. It's also worth telling the person who suggested the product why it didn't stay. A short explanation that the test went poorly beats a quiet disappearance. People are more willing to suggest new ideas when they know their suggestions are taken seriously.
The Site's Role in Testing
The site can help a lot with testing new products. The office manager or shift supervisor can collect suggestions from staff, announce new items, and pass on feedback. They can also tell the operator about events and changes that may affect the test results. They don't need to understand sales data. It's enough to be the link between people and the operator. Many successful new items in machines appeared because someone on the site side passed on a simple suggestion and made sure people heard about it.
Example: An Office and Sugar-Free Drinks
In an office, several people ask for sugar-free drinks. The office manager passes the request to the operator. The operator picks two drinks, checks that they fit the spirals, and swaps them in for the two weakest sellers. It places them at eye level. The office manager sends a short message to the team. The test runs for several weeks, outside vacation season. One drink sells clearly better than the product it replaced, the other about the same as its predecessor. The operator keeps the first one permanently and uses the second slot to test the team's next suggestion. The test result goes into the site notes.
What to Check Before a Test
A short checklist:
- Does the product fit the spiral, the storage conditions, and the pace of sales?
- Which product will make room for it?
- Which slot will the new item go in?
- How long will the test run, and when will the decision be made?
- Does the test overlap with an unusual period?
- How will users find out about the new item?
- What will we measure, and who will collect feedback?
With answers like these, the test gives results you can rely on.
Snack Machines
You can read more about the machines where new snacks and drinks are most often tested in the description of snack vending machines (publisher's site).
FAQ
How long should a new product be tested in a machine? Long enough for the curiosity effect to fade and for the test to cover several typical weeks. Set the length in advance.
Can several new items be tested at once? You can, but one or two is better, with no other changes to the machine. Then the results are clearer.
What if a new item doesn't sell? Check whether it was clearly visible and whether people knew about it. If so, go back to the previous product or try another new item.
Can users suggest new products? Yes. Pass suggestions to the operator through the contact person on the site side.