A 100-Drink Vending Menu: Count Ingredient Paths Before Counting Recipes

01   /   BUYER NOTES

Separate menu names from physical preparation needs

A concept may propose one hundred drinks by combining bases, flavours and sizes. That is a menu idea, not evidence that a single machine can prepare every option. The equipment must support the ingredients, preparation steps and customer handover behind each selection.

Start by grouping drinks according to their actual process. A packaged beverage, a mixed powder drink and a blended fruit drink are not equivalent simply because they all end in a cup. Keep the preparation differences visible in the feasibility brief.

02   /   BUYER NOTES

Create an ingredient inventory before the recipe list

List every ingredient source and its required handling conditions. Record whether it arrives as a sealed portion, bulk liquid, powder, frozen component or another form. Include serving consumables such as cups and lids in the operating inventory.

For each ingredient, identify storage, replenishment and cleaning implications using the relevant product and equipment instructions. Do not assume two liquids can share a path or that a powder designed for manual preparation works unchanged in an automated process.

This article does not recommend recipes or processing settings. It describes how to organise a custom project so qualified technical and food-operation teams can assess it. No particular ingredient capacity or function is implied for a WEIMI model.

03   /   BUYER NOTES

Map recipes to shared and separate paths

Build a table with recipes as rows and ingredients or preparation stages as columns. Mark what each recipe uses. This reveals shared resources that may limit the menu and distinct processes that may require separate equipment.

A hypothetical set of three drink bases and four flavours creates twelve named combinations before size choices. That arithmetic does not validate flavour quality, portion delivery, ingredient compatibility or cleaning. Each proposed combination still needs an appropriate review and test.

Avoid using combinatorial menu counts as a performance claim. A screen can display many options that the physical system cannot reliably supply under the proposed operating conditions. Keep selectable options restricted to the validated and available offer.

04   /   BUYER NOTES

Treat allergens and product information as design inputs

A large menu creates more opportunities for ingredient substitutions or incorrect descriptions. Keep the recipe record connected to the customer-facing information and the actual stocked ingredients. The responsible food business should review labelling and allergen requirements for the operation.

Where shared preparation paths are proposed, have appropriate specialists assess the process and required controls. Do not make allergen-free claims merely because a recipe omits an ingredient on paper. The physical preparation and cleaning process matters.

Use controlled recipe revisions. If a supplier changes an ingredient, review both the technical process and the customer information before the new stock is used. A familiar flavour name should not conceal a changed formulation.

05   /   BUYER NOTES

Understand the bottleneck behind peak service

A menu with many options may use a common preparation stage. That stage can determine the time between completed drinks even when ingredient storage is large. Evaluate the complete order-to-handover cycle using a representative mix of the intended recipes.

Do not add the fastest individual cycle times together to create an unsupported hourly output. Record required recovery, cleaning transitions and ordinary customer actions. The appropriate test should reflect the actual operating process.

A popular recipe can also exhaust one shared ingredient and make several menu items unavailable at once. The availability logic should show the affected offers accurately. Do not assume that each menu button corresponds to independent physical stock.

06   /   BUYER NOTES

Launch with a validated menu and a controlled expansion path

A smaller approved range can make the pilot easier to interpret. Select recipes that demonstrate the important process types and customer choices, then expand only after the relevant evidence is available. This is a project-planning approach, not a fixed limit on menu size.

Record each recipe’s ingredients, process reference, serving unit, customer information and acceptance status. Keep development recipes separate from live offers. The operator should be able to identify who approved the version currently sold.

Use pilot results to assess refill work, waste, service time and customer selection. Adding recipes should solve a demonstrated customer need or commercial opportunity, not simply increase a headline count while making the operation harder to maintain.