A restaurant system
with no hardware to buy

A busy restaurant whose system was a Google Form and memory

A real restaurant in Chiang Mai taking weekly tiffin-box meal orders faced the classic SME problems:

• Customers didn't know what time the food would arrive → they kept messaging to ask, and the food risked spoiling while it waited
• Orders lived in a Google Form → data was scattered, not connected to the kitchen, no customer profiles
• Dishes were ready one at a time → customers had to be notified one by one, by hand

The alternative on the market was a POS system that requires buying hardware — a cost a small restaurant shouldn't have to carry

Design the workflow first — the software follows

• Zero hardware — the whole system is a PWA that opens instantly from a link / QR / LINE, with no app to install and no devices to buy
• Three roles, one system — customers (order + track) · kitchen staff (kitchen board) · owner (manage menu/orders), each on their own phone
• Real-time kitchen board — the kitchen taps a button to move the status forward → the customer is notified instantly via LINE
• Per-dish notifications — when a dish is ready, the system notifies only the customers who ordered it — no one has to chase people with messages
• Weekly subscriptions — customers set a plan (days + meals + dishes) and the system creates the orders automatically every week
• Multi-tenant from day one — the architecture is ready to grow into SaaS for other restaurants without a rebuild

Software doesn't create the system — the system decides what the software should be

What we actually built

11 end-to-end modules — from customer intake · food allergy management · weekly menus · automatic subscriptions · real-time kitchen display · delivery with ETA notifications · notification engine · all the way to the owner's admin panel

Every module has passed end-to-end testing and is deployed in production

Live in production — used by a real restaurant

The system has been in production since August 2026 and is the testbed for the SME patterns Faberic builds on with other clients — lessons from a real restaurant became knowledge that can be passed on

SMEs don't lack technology — they lack systems designed from real work

The restaurant's problem was never "no AI" or "no POS" — it was a workflow that had never been designed. Once the workflow is clear (who orders → who makes it → who knows when), the software that follows is simpler and cheaper than anyone expects

And the engineering lesson: be precise about where you need flexibility — we used ports & adapters only at the 3 points that truly need to change (auth · notification · payment); everything else uses a standard structure — simplicity is something you have to design