Pizza POS system: a Thursday night from six until close

A demo happens in a quiet room. Your shop is not a quiet room at half past eight on a Thursday, and that is the only time a pizza pos system can really be judged.

So this article is one evening, in order. Each section is a moment that comes for every pizza shop, and what has to already be true when it does.

Read it with your own shop in mind. If a supplier cannot tell you what their product does at each of these points, the demo did not cover your business.

Why Thursday

If you are new to Kuwait, the week runs differently from the one most software is designed around. The US commercial guide for Kuwait records that Friday and Saturday are the official weekends, and that some private companies work a split schedule, from 9 in the morning until 1, then from 4 or 5 until 7 in the evening.

Two consequences. Thursday evening is your Saturday night. And the split schedule gives you a real second peak just after seven, when people finish the later half of their working day. A rush hour here is two rushes.

17:30, before anybody orders

The work that saves the evening happens before it starts.

Set what you have. Counts per item and per option should be entered while the shop is calm, so the system can take them down as orders arrive rather than a member of staff remembering at nine.

Check tonight's prices are the prices on the page. If a supplier put your mozzarella up on Sunday and the menu still charges Sunday's price, every pizza tonight loses the difference.

Confirm your hours. If the page keeps accepting orders after the oven is off, somebody is going to ring a customer back and apologise.

18:00, the first orders

The early orders are the easy ones, and they are where you check the plumbing.

An order comes in from your own ordering page. A confirmation should reach the customer within about 2 seconds, so nobody phones to ask whether the order went through. A kitchen ticket should land where your team already looks, which for most shops here is a WhatsApp group rather than a screen somebody has to remember to check. Kitchen display system covers the case for a screen if you would rather have one.

The ticket has to be readable by a cook holding a peel. Sizes and options listed as lines, not described in a sentence.

19:30, the counter is the bottleneck

This is the moment shops discover they bought the wrong thing.

There is a queue at the counter, and the phone is ringing, and both want the same member of staff. Every order that arrives on the customer's own phone, priced and addressed by the customer, is an order that never joins that queue.

If your system needs a person to type an order in, it does not reduce the bottleneck. It moves it.

20:30, something runs out

Nine times in ten it is one topping, not a whole pizza.

A system that only tracks whole items has to take four pizzas off sale when the buffalo runs out. Counts per option take away the option and leave the pizzas. At zero, the choice greys itself out with nobody watching, and if an order is cancelled the count comes back.

This is the single most useful thing a busy pizza shop can automate, because the alternative is a member of staff phoning customers back.

21:15, the drivers

Now the evening's real risk. Food that waits is food that gets worse, and the World Health Organization estimates that 866 million people, almost 1 in 9 in the world, fall ill each year after eating contaminated food. Nobody is claiming a late pizza is a public health event, but the principle is the same one your kitchen already works to: the clock starts when the food leaves the oven.

A driver should get a link with the map pin the customer dropped at checkout, plus the building and flat picked from a list rather than described. It should open without an account, because your Thursday driver may not be your Sunday driver, and one tap marks the order delivered so the customer is told without anyone at the shop doing it.

22:00, where is my order

Somebody always asks. The good answer is a status page for their own order that needs no login, sent to them when they ordered, so the question answers itself and your counter stays free.

23:00, closing

Two things are worth reading before the lights go off.

The message log, which shows every message sent and whether it arrived. A failed message is a customer who was never told anything, and you want to see that tonight rather than in a review on Sunday.

The day's sales, by item, so you know which pizza actually carried the evening. POS food point of sale covers what else a counter system reports.

"Every shop we visit is calm when we visit. So we ask one question instead: what happened last Thursday at half past eight? The answer is always specific, always about the phone, and always about somebody standing still because a screen was busy." — Agha Shah Zaman, co-founder of Get Menu

The next morning

The evening is not over when the door shuts.

Regulars earn stamps automatically, and nobody has to mark an order delivered for a stamp to count. Tiers your regulars grow into can carry an automatic discount. Their card sits in Google Wallet and updates itself with no app to install, and Apple Wallet is built and waiting on a certificate.

If you want to send an offer, there is a cap per customer per week so nobody is pestered, and overlapping campaigns are held for you to approve rather than both going out. Your menu lives on your own address on getmenu.ae, included in every plan, and you can upload the whole thing from a spreadsheet. Invoices carrying your tax registration number are available as a PDF, and old order details are cleared automatically after 120 days.

What this evening does not include

There are no online payments, so every pizza tonight is settled in cash or on your card machine at the door. No card details exist anywhere in the system.

There is no collection order type, so a customer who wants to walk in and pick up is handled the way you handle it today. There is no scheduled ordering and no pre-order, so nothing tonight was booked yesterday.

And we do not print receipts at the counter or report to a tax authority. Your register keeps doing that. Restaurant POS system comparison helps if you are choosing one of those too.

Try it on one Thursday

Do not switch the shop over. Take delivery orders only, on one Thursday, through your own ordering page.

Count three things at close: orders that arrived without a phone call, orders that went out with a correct address first time, and minutes your counter staff spent typing other people's orders.

Then decide. The trial runs 15 days, needs no card details to begin, and takes 0% of what you sell, so a single Thursday costs you nothing but the setup.

Frequently asked questions

Does the kitchen need a screen?

No. Tickets arrive in the WhatsApp group your team already uses. A screen is an option if you prefer one, not a requirement.

What happens if a topping runs out mid-service?

The option is taken away at zero and the pizzas that use other toppings stay on sale. Cancel an order and the count returns.

How do drivers get the address?

As a link carrying the map pin dropped at checkout and the building and flat details, opening with no account and no app. One tap marks it delivered.

How do customers pay?

Cash or your own card machine at the door. There are no online payments, so nothing is charged before the pizza leaves.

Can customers order before we open?

No. Orders run inside your opening hours, and there is no scheduled ordering or pre-order.