SVSFood runs three food outlets in Madhya Pradesh. They were paying a vendor for kiosks, paying another template for online ordering, and could not see one inventory across either. When the vendor had a bad day, the counter had a bad day. This is the story of removing that dependency, documented in the SVSFood case study.
The real cost of a kiosk subscription
The invoice is the visible part. The hidden part is control. You cannot reorder the menu flow, run your own coupon logic, or fix a bug on your timeline. Every improvement is a feature request in someone else's backlog. For a restaurant, where the counter is the product, that is a strategic risk.
One vendor out, four products in
- Kiosk app: touch-first React Native for 10-inch tablets, with customisation, add-ons, coupons, QR receipts, and kitchen tickets.
- Admin console: Next.js dashboard for menu, inventory, coupons, live orders, roles, audit log, and analytics across outlets.
- Ordering website: branded Next.js storefront on the same menu, with live order tracking.
- Rider app: React Native with order assignment, maps navigation, and status updates that sync to the console and the customer.
One source of truth
The architectural decision that mattered: every client talks to the same API and the same PostgreSQL database. A coupon created in the console works at the kiosk and on the website. A sold-out item disappears everywhere. The deeper write-up is in One Fastify Backend, Four Clients.