NoPOS

The till keeps ringing when everything else goes down.

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.

Store network 6/6 Internet connected Uber Eats and Mr D live

Every sale saved on the till and shared with the other devices.

Built for the Friday you've already had.

If you run stores, you've seen these. NoPOS was designed around each one.

The back-office server dies and the kitchen screens go blank.
There is no server to die. Every till and kitchen screen holds the whole day's orders and talks to the others directly. Lose any device and the rest carry on.
The internet drops and the tills start numbering orders differently.
Order numbers are made on the till by the same rule, online or offline. Nothing switches when the line goes down, so nothing changes.
Uber Eats and Mr D orders come through twice, or have to be captured by hand.
Aggregator orders arrive straight on the till and kitchen screen. A repeated delivery merges into the same order, and an order is only accepted once a device in the store actually has it.
Load shedding cuts the power mid-sale.
Each sale is written to disk before the screen confirms it. When the power comes back, the till picks up where it left off and catches up from its neighbours.
Rural stores on LTE that's working one minute and gone the next.
The store trades on its own network and syncs when it can. If the link stays down, delivery apps pause automatically and resume once it's stable, without flapping.

One system from the counter to the customer's door.

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.

Kitchen screens

Tickets per station showing how to build each pizza. Fired by promised time, not arrival. Tap to bump, recall in one tap.

Oven pacing

NoPOS knows what's in the oven, quotes honest ready times, and raises delivery-app prep times before the kitchen falls behind.

Menu boards

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.

Online and WhatsApp ordering

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.

Your own drivers

A driver app with dispatch from the kitchen, live tracking for the customer, proof of delivery and cash-up per driver.

Run 200 stores from one screen.

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.

Runs on the hardware you already own.

Windows tills

Including Windows 10 IoT tills with 2 GB of RAM. Installs offline, starts on boot, runs full screen.

Android POS

Kitchen screens, waiter handhelds and menu boards on affordable Android devices, with built-in printers.

Epson printers

Network receipt and kitchen printers. If a till dies before printing, another device prints the ticket once.

Your card terminals

NoPOS is payment-neutral. Keep your acquirer and your rates; a timed-out card payment is checked, never charged twice.

Tested well past a busy Friday.

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.

Pull the cable in your own store.

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 demo

Or email hello@nopos.co.za