Grid POS
An offline-first till for the counter: staff PINs, discounts, refunds, split payments and shifts. It keeps selling when the internet doesn’t, and updates itself.
Core Mission
A restaurant group shouldn’t need a POS, an ERP, a portal for every delivery app, Excel for food cost and a payroll tool that never sees sales. Grid replaces that stack with one operating system. The till, the kiosk, the kitchen, the QR menu and the back office all write to the same typed database — so HQ sees the same numbers the counter does, the moment they happen.
Before
After
One system. Every sale, shift, ticket and employee lives in one typed database — so the numbers agree everywhere they appear.
An offline-first till for the counter: staff PINs, discounts, refunds, split payments and shifts. It keeps selling when the internet doesn’t, and updates itself.
Guest-facing ordering with brand themes, upsells and an attract screen, in English and Arabic. One build ships to the web, Android and Windows.
Orders reach the right kitchen station the moment they’re paid, and move from fire to finish without paper.
A small server inside each store. It runs the kitchen board, screens and printers over the local network — online or not.
A phone menu for every table that knows where the guest is sitting, in either language.
Where managers and HQ run the business: live sales, menus and pricing, cash and shift reports, delivery-app settlements, HR, attendance and assets.
One API behind every surface. Types run from the database to the till, so a change in one place can’t silently break another.
An AI analyst that answers sales questions in plain words, using Grid’s own reports — and writes a briefing before the doors open.
SYS_08 / Ask Grid
Managers shouldn’t need an analyst to find out why Tuesday was slow. Ask Grid answers in plain language, pulls from the same reports the back office uses, and draws the chart while it’s at it.
Tills and kitchens keep working when the internet drops. Orders sync when it’s back; nobody stops serving.
Database types flow through the API to every screen. When the model changes, the compiler finds every place that has to change with it.
Arabic and English, right-to-left and left-to-right, are built in from the first screen — not translated at the end.
Self-updating Windows installers, Android builds and web deploys all run through CI, so a fix reaches every store without a site visit.
May 2026
One monorepo, one schema, and a plan to replace every tool the group runs on.
Oct 2026
The first stores cut over. Grid starts taking real payments at the counter, the kiosk and the kitchen.
Now
Bringing each brand in the group onto Grid, store by store, until the old POS is gone.
Next
Already underway: accounting, inventory, purchasing and HR move into Grid — so the company runs on one system, not a stack of them.
“A business that runs on five tools runs on guesswork. One system runs on facts.”
Start a Project