Say it
Hands covered in flour on the make line, or driving between deliveries. Push to talk and it happens.
Kitchen, car, anywhere your hands are busy
How we build
You have almost certainly changed how your shop works to suit a piece of software. Renamed something because the field was too short. Kept a second book because the system would not hold it. Trained everybody around a screen that was designed for a coffee chain. That is normal, and it is backwards.
The method
These are not ours alone — they are the methodology of NebusAI, the partner PizzaOS is built with, and every screen in this product is answerable to them. They are worth reading because they explain the things you will notice and the things you will not.
01
A screen should not offer every function it has. It should offer the ones that matter at this hour, in this role, in this shop, on this shift. A register at seven on a Friday and the same register at close are not the same job, and should not look identical.
Context awareness over feature complexity
02
No tutorial, no tooltip tour, no laminated card by the till. People should be able to use it the way they already think — including by simply saying what they want. A new starter on their first shift is the test.
The "no manual" rule
03
Not how it looks. Fewer taps to send an order. No dead ends. Nothing that makes somebody wait for the machine. The prettiest screen in the world is a bad one if it costs an extra press during a rush.
Design is how it works, not just how it looks
04
The system tells you what it thinks you should prep, or which deal saves the customer most. It never quietly does it for you. Every suggestion can be accepted, changed or ignored, and none of them touch money without you.
Predictive assistance, not prescriptive automation
05
If people keep cancelling the same step, or keep doing a job outside the software, that is not user error. It is a design failure and it is logged as one. Most systems treat a workaround as your problem. We treat it as the thing to fix.
Continuous learning through usage
06
Clear errors that say what to do next. Space that makes a busy screen readable. Feedback the instant you press something. The parts you never consciously see are the parts that decide whether a shift feels smooth.
Obsessive attention to detail
Three ways, one result
Most software gives you one way to do a thing and expects you to be at a keyboard when you want it. A pizza shop is not like that. The person who needs to 86 the wings has flour on both hands; the person asking what Friday cost is sitting down with a coffee. So everything is reachable three ways, and all three do exactly the same thing and leave exactly the same record.
Hands covered in flour on the make line, or driving between deliveries. Push to talk and it happens.
Kitchen, car, anywhere your hands are busy
A quiet back office and a long question. Type it the way you would text somebody who knows the shop.
The desk, the office, end of night
The screen is still a screen. Everything reachable by hand, laid out the way your shift runs.
The counter, the rush, the kiosk
This is the part nobody else has. Voice in this industry means a robot answering your phone for customers. Useful, and we do that too — but it is not the same thing as your own staff talking to the till, in every app, and having it actually do the job.
One shop or a thousand
This is the part that makes the same product work for a single pizzeria and for a brand with a thousand stores. Every setting — who may refund, what a screen is called, whether a rule applies — resolves down a ten-level chain. Each level can narrow what it inherits. None can loosen it. So head office sets a floor that cannot be undone in a store, and a store still owns the decisions that are genuinely its own.
A setting is changed by an operator, not by an engineer, and it takes effect without anybody shipping a new version of the app.
What that buys you
If your shop says "pie", the screen says pie. Categories in the order you sell them, not alphabetically. Navigation that matches the way your shift actually runs.
Layouts shift with the tempo of service — bigger targets and fewer choices when it is busy, the full picture when you are counting up at the end of the night.
A second shop, then a region, then a brand — on the same platform, with the rules you already set inherited down the chain. You do not graduate onto enterprise software; the software grows a level.
Hardware
There is no terminal you have to buy from us to get started. The software runs on ordinary Android tablets, and on the iPads and laptops already in your shop. What differs between the two paths is not whether it works — it is who you call when something stops.
It runs on the hardware in your shop right now. There is no proprietary terminal you have to buy to get started, and no box that only we can sell you.
We certify specific Android terminals, handhelds and kiosk screens — the ones we test on, keep working, and support properly. If you want somebody to call when a printer stops, this is the path to pick.
That is the honest trade and we would rather say it up front: your own device runs the software, and help with it is best-effort. Certified hardware is the tier we stand behind. Neither choice is locked — you can start on what you have and move later.
Book a demo
Everyone has one. Bring it to the call and we will either show you the setting, or write it down as something to build — and tell you honestly which of the two it is.
Book a demoAsk PizzaOS
Answers come straight off this site
Ask me anything about how PizzaOS works. I only know what is on this site, so I will not make anything up — and if you would rather talk to a person, just say so.