RentonSoft POS Restaurant POS & SaaS
A restaurant point-of-sale system that runs live in two cafés and as a multi-tenant SaaS edition.
Interactive example · runs in your browser
Take one order from table to till
The waiter's tablet, the kitchen and bar screens, the till and the stock all work at once. Pick a table to start.
- 1Pick a table
- 2Add items and send
- 3“Ready” in kitchen and bar
- 4Split and pay at the till
- 5Check the stock
Pick a table first.
No open orders
No open orders
No tables to pay
Stock · by recipe
- Coffee beans1.000 g
- Milk5.000 ml
- Tea500 g
- Lemons40 pcs
- Toast bread40 pcs
- Cheese2.000 g
- Cheesecake12 pcs
- 0:00socket · waiter tablet · kitchen · bar · till
This is an example: it runs in your browser and sends no data anywhere. In the real RentonSoft POS the same flow runs on the tablet, the kitchen screen and the till at once, with your own menu, prices and recipes.
One order, many hands: waiters, kitchen, bar and cashier working from the same live state.
Who it’s for
For restaurants with table service, cafés that sell over the counter and places running take-away. Waiters enter orders on a tablet, the kitchen and bar see them on their own screens, and the cashier closes the same check.
Problem
Restaurant service is split across tables, the counter, the kitchen, the bar and the cash desk. Every handoff needs the same order state, clear permissions and payment logic that never double-charges or loses a line — on tablets, in a hurry.
Approach
A typed monorepo: NestJS and Prisma on PostgreSQL, React and Vite on the front. Role-based realtime rooms push each change to the kitchen, bar, cashier and waiters. Payments are transactional and idempotent — split by items or evenly, discounts, manager-PIN refunds and shift reconciliation. Branding lives in settings, so one codebase serves different cafés; the SaaS edition isolates every business in its own PostgreSQL schema.
Result
In daily use at Castor Coffee, and open to new businesses as a SaaS with a seven-day trial that turns read-only — never deleted — when it ends.
What’s inside
- Table service, counter sales and take-away in one flow
- Kitchen and bar screens with late-order warnings
- Split payments, discounts, manager-PIN refunds and Z reports
- Recipe-based stock: every sale consumes raw ingredients
- Schema-per-tenant SaaS with trials and safe suspension
Stack
Under the hood
The code layer of this project — modules and moving parts.
apps/api NestJS · Prisma · PostgreSQL 16 realtime/ Socket.IO rooms → kitchen · bar · cashier · waiters · display checks/ Check → Order → OrderItem, tax-inclusive totals payments/ split · discount · refund (idempotency keys, manager PIN) stock/ recipes (BOM) → ingredients consumed per sale tenancy/ schema-per-tenant, routed through AsyncLocalStorage apps/web React · Vite · TanStack Query · Zustand deploy Docker Compose · reverse proxy · nightly backups
Common questions
Does it suit a small café?
Yes. It runs every day at Castor Coffee. If you have no table service, counter sales and take-away work from the same screen.
How does the free trial work?
You get seven days free. When the trial ends the account isn’t deleted: it turns read-only, so you can still see your records.
What devices does it run on?
It runs in the browser, so a tablet or a computer is enough.
Does it track stock?
Yes. You set a recipe for each item, and every sale deducts the raw ingredients it used.
Can a check be split or refunded?
A check can be split by item or evenly. Discounts are supported, refunds need a manager PIN, and you close the day with a Z report.
Ready software
Table service, kitchen and bar screens, split payments and recipe-based stock — as SaaS or on your own server.