A pizza shop's menu looks short — a dozen pizzas, a few sides, some drinks. But every pizza drags along a size, a crust type and a list of toppings the customer adds, so the real figure is several hundred different combinations. On top of that the shop sells through three channels at once: guests eating in, guests picking up a takeaway, and orders delivered to the door. Pizza shop software has to carry exactly those two things; the rest is the same as any food business.
One pizza, many choices — declared once on the menu
In Ordersys an item has attributes and variants. An attribute is a choice group such as Size or Crust; each value (S, M, L; thin, thick, cheese-stuffed rim) combines with the item to form a variant with its own price. Staff pick the item then pick the size, and the system takes that size's price — nobody has to keep a price list in their head.
Toppings work differently: they are declared as topping groups attached to the item, each topping carrying an added price. A customer who wants sausage and mushrooms picks two entries and the money is added to that order line. There are also side dishes and pre-built combos, used for packages like "pizza + drink + salad".
The real value of declaring all of it shows up in the kitchen, not at the counter. When an order line carries the size, the crust and the toppings, the ticket printed in the kitchen carries those lines too — the pizzaiolo does not have to come out and ask, and the customer does not get the wrong pizza. In a shop with several kitchen stations, the ticket also goes to the station you configured.
Dine-in, takeaway, delivery: three ways of selling on one system
A dine-in order is attached to a table on the floor plan, and extra rounds pile onto that table. A takeaway order needs no table — the software marks it separately and the printed bill says "Takeaway", so the person packing it does not mix it up with a table still seated. A delivery order is an online order, storing the customer's name and phone number along with the shipping fee and the cash-collection fee if they pay on delivery.
| Channel | Attached to | Extra things to track |
|---|---|---|
| Dine-in | A table on the floor plan | Extra rounds, splitting bills, moving tables |
| Takeaway | No table, marked separately | Packing everything, bill clearly marked takeaway |
| Delivery | An online order with customer name and phone | Shipping fee, cash collected, who delivers |
One point to state plainly: the delivery partner list is something the shop declares itself in the system, to attach to orders and charge fees. The software does not push orders into a third-party ride-hailing app. Delivering yourself or hiring a driver both work; hooking directly into a particular platform is not something to expect.
Ingredients deducted from stock by recipe
A pizza is assembled from many ingredients, so if stock never moves when you sell one, nobody knows at month-end where the flour and cheese went. Ordersys lets you declare a recipe for each item: how many grams of dough, sauce and cheese a pizza takes, and how much of each topping. Selling one deducts exactly those ingredient lines.
A practical caveat: stock is tracked per menu item, not per size. A shop that wants size S and size L to deduct differently should declare each size as its own menu item rather than as a variant — a little more setup work, but far cleaner stock figures.
A few things to do in the first week
- Declare the menu the way customers order, not the way an accountant would like it: pizza name, then size, then toppings.
- Keep topping names short and non-overlapping — kitchen tickets print narrow and long names get cut off.
- Agree your delivery fees by area and enter them in advance, so staff do not each calculate their own way.
- At the end of the first week, open the best-seller report, see which sizes and toppings are actually ordered, and trim the menu.
A pizza shop does not need software built for the pizza trade; it needs sales software that understands one item with many choices and one shop with many sales channels. Have a look at the Ordersys restaurant management software and the free 7-day trial, so you can set up your own menu and sell for a few days to see where it snags. Two related articles: declaring size and topping options so orders are not mixed up, recipes that deduct stock automatically when an item is sold.
Ordersys has editions for restaurants and for retail stores: checkout, stock, reports and e-invoices, with on-site setup and training.
Other news
Managing massage therapist shifts without padded hours
A handwritten timesheet leaves nothing to check at month-end, so it gets signed anyway. Declare shifts in advance, clock in on a branch-tied QR device, then set hours beside the session count for that shift — three common discrepancy signals and how to go from timesheet to hourly payroll.
Reports on which billiards tables are busy by hour, for staffing shifts
How many staff for a Friday night, and is the table at the back worth keeping — two questions answered by reports, not instinct. The revenue-by-table screen lists even the zero tables, per-table detail carries invoice timestamps, plus three charts for reading hour bands and four things to do after reading them.
Assessing staff productivity by sales and hours worked
The highest sales figure is not necessarily the strongest performer — you still have to divide by hours worked. The two numbers you need first, three ways to turn them into productivity, three rules for comparing like with like, what to measure for roles with no sales, and why criteria must be announced before money is attached.
Per-dish gross margin in a restaurant: making the number trustworthy
What the gross margin on a plate includes and excludes, two ways to get cost into the software (a cost price field or ingredient recipes), four places the number goes wrong, and why you must multiply margin by plates sold to see which dish really feeds the restaurant.
Bubble tea chain management software: open the second shop without starting over
Opening a second bubble tea shop: import the menu from a file instead of retyping it, declare the four option groups and the recipes so the drink stays the same, use a price list for per-location price differences, then read reports combined and split by branch.
Massage bookings over Zalo: what to do once the message arrives
A chat message is not yet an appointment. How to move it into the shared schedule: pick the room, the bed and the therapist, read the appointment statuses, and let the software remind the customer before the slot.
Pet shop software: selling supplies and taking grooming bookings on one machine
A pet shop is two shops in one: stock in many pack sizes, and grooming services that need a time slot. How to declare several units of measure, take bookings with a named staff member, and put goods and services on the same bill.
Credit for billiard club regulars: record and collect debt in the software
Replacing the notebook at the counter: debt is recorded as the table is closed and must be tied to a member, revenue counts only money actually received, and the debt report shows who owes what and the total outstanding.
Restaurants with several kitchens and printers: tickets to the right station
Hot kitchen, cold kitchen and bar each with their own printer. Assign product groups to each machine and the system splits tickets by station; choosing IP or USB printers, and where to look when the kitchen loses a ticket.
