Pizzeria POS: from toppings to collection

Start with a pizza order that changes

A guest orders two pizzas, changes the size of one and removes an ingredient from the other. Then they add a sauce. Can staff enter this clearly, and does the kitchen see exactly which change belongs to which pizza?

That is a better test than choosing solely by the label “pizzeria POS”. A restaurant system can fit well if its menu handling and order flow support your operation.

Make options clear to guests and the kitchen

Distinguish sizes, added ingredients and removals. State which options cost extra and which combinations you actually offer. If you sell half-and-half pizzas or particular packages, test that pricing logic specifically.

Hypothetical menu example: a SEK 150 pizza, SEK 15 size upgrade and SEK 10 extra cheese give a SEK 175 customer price. Removing an ingredient should produce the price you have decided and communicated, without an unintended deduction.

Check that options appear correctly in the POS, kitchen order and receipt. Ask a new employee to enter the sale and observe where questions arise.

Coordinate oven work and collection

A KDS shows orders on a screen; a ticket printer produces paper tickets. Choose the approach that suits the kitchen and decide who marks an order ready.

Oldest first is not always the right cooking sequence when future collection times are mixed with immediate orders. Define the priorities. A faster POS does not create more oven capacity, so promised collection times need to reflect actual workload.

Use clear collection numbers. Separate food status from payment status, and check that the complete order, including sauces and drinks, is handed over.

Verify every ordering channel

Phone, counter and direct online orders may enter differently. If you use external platforms, establish which orders transfer automatically and which are handled another way.

Test extra toppings, sold-out items, cancellations and refunds too. An order connection does not automatically synchronise menu changes or every other event. Wolt's developer documentation, for example, distinguishes different parts of a restaurant integration. Wolt restaurant integration guidance.

Vendion Online Order uses the same system as the POS and kitchen. Request a practical review of any external connections your operation needs.

Check allergy information and VAT

A gluten-free base does not automatically make the finished pizza safe for a guest with coeliac disease. Staff need to check ingredients and kitchen handling. An option or screen flag does not replace that conversation. Swedish Food Agency guidance.

In Sweden, food VAT is temporarily 6 percent from 1 April 2026 through 31 December 2027. Restaurant services remain at 12 percent, and spirits, wine and strong beer at 25 percent. Classification depends on what the sale includes, even when the pizza itself is the same. Swedish Tax Agency VAT rates.

Agree accounts, VAT and payment methods with the person responsible for accounting. An accounting integration transfers information according to its configuration; it does not automatically establish that every item is classified correctly.

Introduce the system with clear ownership

Test menus, kitchen flow, payments and refunds before going live. Set an explicit point when sales move to the new POS so the same purchase is not recorded twice. Preserve the old records according to applicable requirements.

Vendion requires internet access. Test connectivity and the fallback routine, then compare pricing and equipment for your setup. A demo lets you work through your own menu and assess the journey from ordering to collection.