Products identify the dish; options describe the choice
A product should answer the question: what is the customer ordering? On a restaurant menu, that might be a margherita pizza, a chicken burger or a side salad. Options then explain how that item should be served. A pizza size or an extra topping is usually easier to understand alongside the pizza than as an unrelated menu item.
The distinction is practical rather than absolute. Separate products can help when two dishes have different recipes, preparation routes or availability. Options can reduce repetition when the underlying dish stays the same. Avoid combining dishes simply because they share a name: the person taking the order and the person preparing it must both understand the result.
Decide which choices are essential and which are extras
Some choices are necessary to complete an order. If a pizza comes in two sizes and neither is assumed, the team needs a size before preparation can start. An extra topping is different: a customer should be able to order the standard pizza without choosing one. Write down that intended behaviour before configuring the menu.
Do not assume that a choice is compulsory just because its label says so. Confirm which selection rules your NeroPOS setup supports and test what happens when a choice is skipped, changed or removed. Where a default is used, make sure staff can see it and explain it to customers rather than treating silence as a clear instruction.
- Mark each choice as essential or optional on your draft menu.
- Define the intended default, if there is one.
- Confirm how those rules can be represented in your installation.
Hypothetical example: one pizza, two sizes and an extra
Imagine a restaurant offering a margherita pizza in regular and large sizes, with an optional extra mushroom topping. A sensible starting point is one margherita product, a size choice and a mushroom extra. The intended order is easy to read: large margherita, extra mushrooms. The actual configuration should be agreed against the features available in the restaurant’s setup.
By contrast, a mushroom side dish is a separate product: customers can order it without a pizza, and the kitchen prepares it independently. A gluten-free pizza may also need separate treatment if its preparation or availability differs. Do not assume an option automatically applies ingredient deductions or creates a separate preparation instruction; confirm those behaviours.
Check the total and the order the kitchen receives
A menu can look clear on screen but still produce an ambiguous order. Test a standard dish, a changed size and a dish with an extra. Compare each total with your approved menu prices, checking whether an option replaces a price or adds to it in the actual configuration. Also test changing your mind halfway through an order.
Follow each test through the receipt and the preparation workflow used by your team. Supported printing, kitchen displays and integrations depend on setup, so inspect the actual output rather than assuming every screen shows the same detail. Success means the selected dish, size and extras are unambiguous, the total matches your intended calculation, and removed choices no longer appear.
- Try continuing without an essential choice and observe the result.
- Add, replace and remove an extra, then check the total each time.
- Ask a colleague to prepare the test order from its output alone.
Make availability and online orders part of the decision
Consider what should happen when one ingredient runs out. If mushrooms are unavailable, the standard pizza may still be sellable. If the pizza base is unavailable, the whole dish may need different treatment. NeroPOS provides stock-related controls, but confirm how your product and option structure interacts with those controls rather than assuming ingredient-level behaviour.
If you also use NeroWeb, its orders can use the existing fulfilment workflow. Check the customer-facing choices and the resulting order details in your actual setup. Your next action is to trial one representative dish with the team, resolve any unclear selection or pricing behaviour, then use the agreed approach for similar menu items.
GOOD TO KNOW
Common questions
Should every size be a separate product?
Not necessarily. A size choice may suit one dish with closely related versions. Separate products may be clearer where preparation, availability or stock treatment differs. Test both the ordering experience and the resulting preparation details before deciding.
Can I make customers choose an option before continuing?
Confirm the selection controls available in your actual NeroPOS setup. Then test an order with the choice left blank. A label such as Choose your size is not evidence that the system prevents an incomplete order.
Will an extra automatically update ingredient stock?
Do not assume so. NeroPOS has stock-related controls, but the behaviour of products and options must be confirmed for your installation. Ask how your intended stock treatment is supported and verify it with a controlled test.
Does NeroPOS have an additional software subscription charge?
With an eligible NeroPay card terminal, NeroPOS software can be included without an additional software subscription charge. Terminal costs, payment processing charges, eligibility and applicable terms still apply. Confirm current availability and commercial terms with the team.