// the find
faizaldevs/RestoPOS
RestoPOS is a cloud-based SaaS solution designed for restaurants, cafés, and food businesses to streamline billing, order management, inventory tracking, and more. Built with Laravel and Vue.js, it supports multi-tenancy, allowing multiple restaurants to operate independently on a single platform.
RestoPOS is a self-hosted, multi-tenant restaurant POS built on Laravel (API) and Vue (frontend), covering billing, KOT routing, recipe-based inventory deduction, and payroll/expense tracking. It's aimed at small dev shops or agencies who want to white-label a POS for restaurant clients rather than build one from scratch, and are comfortable running their own Laravel/Postgres stack.
Multi-tenancy is handled through Stancl Tenancy rather than a bolted-on tenant_id column, so each restaurant actually gets isolated data. The domain modeling goes deeper than a typical POS clone: KOT tickets route to kitchen printers, recipes auto-deduct ingredient stock on sale, and it supports split payments and multiple order types (dine-in/takeaway/delivery/pre-booking). Laravel Passport for API auth is a reasonable fit for a Vue SPA talking to a multi-tenant backend. Docker Compose, an nginx config, and an Azure Pipelines file are included, so there's an actual deployment story instead of just 'clone and pray'.
The repo has committed scratch/debug files that should never have been pushed: `SaleController - Copy.php`, `BarcodeGenerate_old.vue`, `BarcodeGenerate_backup_value_mart.vue`, `package_bcp.json`, plus stray `test.pdf`, `test.txt`, and `filename.pdf` in `public/` — a sign of no .gitignore discipline or review gate. The README hands you default login credentials (admin@admin.com / 123456789) as the documented first-login path with no mention of forcing a reset, which is a real liability if someone deploys this without reading the fine print. phpunit.xml exists but there's no visible test suite backing a system that touches billing and inventory. Last push was March 2025, so anyone adopting it now is taking on over a year of drift against current Laravel/PHP point releases with no changelog to tell you what, if anything, still needs fixing.