Till
Counter, tables, collection and delivery on one screen. A large pizza in two taps, half and half in five. Deals suggested when the order qualifies. Cash, card on your own terminal, split by seat.
NoPOS is a point of sale for pizza, QSR and sit-down restaurants. Every till and kitchen screen carries the whole store, so there is no server to fail, order numbers never jump, and Uber Eats and Mr D orders never go to manual capture.
Every sale saved on the till and shared with the other devices.
If you run stores, you've seen these. NoPOS was designed around each one.
Counter, tables, collection and delivery on one screen. A large pizza in two taps, half and half in five. Deals suggested when the order qualifies. Cash, card on your own terminal, split by seat.
Tickets per station showing how to build each pizza. Fired by promised time, not arrival. Tap to bump, recall in one tap.
NoPOS knows what's in the oven, quotes honest ready times, and raises delivery-app prep times before the kitchen falls behind.
Driven by the same menu as the tills. Mark ham out of stock and every ham pizza greys out on the board within a second.
Your own branded ordering site and apps, plus ordering in WhatsApp. Orders land on the till automatically, with the nearest store chosen by delivery zone.
A driver app with dispatch from the kitchen, live tracking for the customer, proof of delivery and cash-up per driver.
Head office sets the menu, prices, hours and delivery zones once. They reach the tills, menu boards, ordering site, WhatsApp, Uber Eats, Mr D and Google Business Profile. Franchisees change only what you unlock.
Including Windows 10 IoT tills with 2 GB of RAM. Installs offline, starts on boot, runs full screen.
Kitchen screens, waiter handhelds and menu boards on affordable Android devices, with built-in printers.
Network receipt and kitchen printers. If a till dies before printing, another device prints the ticket once.
NoPOS is payment-neutral. Keep your acquirer and your rates; a timed-out card payment is checked, never charged twice.
From our own load test: one store with a server, six tills and three kitchen screens, taking 10 orders a second plus a cloud order every second, for five minutes.
2,802 orders completed, none failed
0 duplicate delivery-app orders
74 ms for 99% of tills to confirm a sale
10% average CPU on a single-core till
A busy pizza store on a R120,000 Friday takes about one order every 15 seconds at peak.
We'll set NoPOS up next to your current system, unplug the internet in the middle of service, and you can watch what happens.
Book a demoOr email hello@nopos.co.za