-
Multi-Tenant Restaurant Management
One installation serves every restaurant you sign. Each tenant gets its own subdomain, menu, staff, orders and customer records, isolated at the framework level rather than by convention, so no restaurant can ever see another's data.
Adding a restaurant is an admin action, not a deployment. You create the tenant, pick a plan and hand over the owner login; the platform does the rest.
-
Restaurant Directory
Every restaurant on your platform in one list, with its plan, status, outlets and activity. Suspend one, move it to another tier or look into a support question without leaving the screen.
This is the view you will live in once you have more than a handful of customers, so it is built for scanning rather than for admiring.
-
Restaurant Types
Classify tenants by the kind of business they run — fine dining, quick service, cloud kitchen, cafe — and use that to shape defaults and reporting.
Useful the moment your customer base stops being uniform, which happens earlier than most operators expect.
-
Branch Management
Restaurants that operate several locations manage them from one account. Each branch keeps its own menu, stock, staff and reporting while the owner sees the whole group together.
How many branches a restaurant may open is governed by its plan, and the limit is enforced by the platform rather than trusted to the customer.
-
Subdomains & Custom Domains
Each tenant is reachable on its own address, which is what makes the platform feel like their software rather than a page inside yours.
Tenancy is resolved from the domain on every request, so a restaurant's staff and customers only ever see that restaurant's data.
-
Subscription Plans
Define the plans you sell: what each tier costs monthly and annually, which modules it unlocks, and the limits that apply. Plans are data, so you can change your pricing without touching code.
Free tiers and paid tiers work the same way, so you can run a free plan as an acquisition channel and upgrade restaurants into revenue later.
-
Usage Limits & Module Gating
Every plan carries hard limits — branches, menu items, online orders, moderators — and the platform enforces them. A restaurant on a two-branch plan cannot open a third until it upgrades.
Module access is gated the same way: a tier without the POS module simply does not show it, so your pricing page and your product always agree.
-
Stripe Subscription Billing
Billing runs through Laravel Cashier and Stripe. Recurring charges, upgrades, downgrades, proration, cancellations, failed payments and card updates are already handled.
This is the part most source-code buyers underestimate: weeks of work that produces nothing a restaurant will ever see, and it ships finished.
-
Subscription Invoices
Every charge produces an invoice against the restaurant, stored and retrievable rather than living only in Stripe.
Business customers ask for invoices constantly, and "log into our payment provider" is not an answer that survives contact with an accountant.
-
Billing History & Payment Methods
Restaurants see their own charges, update their card and manage their subscription from their dashboard, without emailing you.
Self-service billing is the difference between a platform that scales and one where every renewal is a conversation.
-
Subscription Payment Gateways
The gateway that collects your subscription revenue is configured separately from the gateways your restaurants use to take customer payments.
Keeping the two apart matters: your money and their money follow different rules and often different providers.
-
Subscriber List
Everyone who has signed up, what they are on and where they are in their lifecycle, from trial through to cancellation.
The list you work from when you want to know who to call before a renewal rather than after a cancellation.
-
Role-Based Access Control
Eight roles ship preconfigured: Super Admin, Restaurant Owner, Customer, Delivery Boy, Waiter, Chef, Moderator and Staff. Each sees only the screens its job requires.
Permissions run through Spatie Permissions, so you can add roles or change what an existing one may do without rewriting the authorisation layer.
-
Per-Role Permission Editing
Chefs, waiters and moderators each have their own permission screens, so access can be tightened or loosened per restaurant rather than only per role.
Hospitality staffing is rarely uniform, and a permission model that cannot bend is a permission model people work around.
-
Administrator Accounts
Platform-level staff with their own logins and scoped access, separate from the restaurant owners who use the system day to day.
Your support team can help a customer without holding the keys to everyone's billing.
-
Moderator Accounts
Restaurant owners delegate day-to-day administration to moderators without handing over billing, plan changes or anything else that belongs to the owner alone.
How many moderators a restaurant may create is a plan limit, which gives you another honest reason for a customer to move up a tier.
-
Employee Management
Staff records, roles, addresses and logins managed from the admin panel. Chefs, waiters and delivery staff each get credentials scoped to the app they actually use.
Removing an employee revokes their access everywhere at once, including the mobile apps — which matters more in hospitality than in most industries.
-
Audit Logs
Significant actions are recorded with who did them and when. When an order total changes or a menu price moves, there is a trail rather than an argument.
For a platform you are selling to other businesses, this is often the feature that closes a deal with a larger customer.
-
Default Access Profiles
New staff of a given role start with a sensible permission set instead of nothing or everything.
Removes the step where somebody is given admin "just for today" and keeps it for a year.
-
Dashboard Overview
The dashboard opens on live numbers: orders today, revenue, order status spread and recent activity, so an owner knows the state of the business at a glance.
Each figure links through to the underlying records, so a number that looks wrong can be checked rather than merely doubted.
-
Sales Reports
Revenue by period, by branch and by order type, with the breakdowns a restaurant owner actually asks for rather than a generic chart.
Reports read the same data the POS and online orders write, so the floor and the back office never disagree about what was sold.
-
Item Performance Reports
Which dishes sell, which sit on the menu earning nothing, and how that changes across the week. Menu engineering becomes a decision rather than a guess.
Useful to the restaurant, and useful to you: a concrete answer when a prospect asks what they get beyond order-taking.
-
Billing Report
What your restaurants owe you, what has been collected and what has failed, across every plan you sell.
Your revenue, separate from theirs, which is the distinction that gets blurred in platforms that bolt billing on late.
-
Subscription Report
Plan distribution, upgrades, downgrades and churn over time.
The report that tells you whether your pricing is working, which is a different question from whether you are being paid.
-
Credit Balance Report
Customer credit tracked in one place: what has been issued, what has been spent and what remains outstanding.
Keeps store credit from becoming an untracked liability, which is exactly what it becomes when it lives in a spreadsheet.
-
Transaction History
Every payment that passes through the platform, across all gateways, in one searchable list with its order, method and status.
When a customer disputes a charge, the record is one search away instead of a reconciliation exercise.
-
Configurable Analytics
Which metrics appear, and in what order, is configurable rather than fixed by whoever wrote the dashboard.
A pizza counter and a fine-dining group do not watch the same numbers, and neither should have to ignore half the screen.
-
Data Export
Reports and lists export for accountants, investors or whatever system a customer already runs on, with sample files to import against.
Because the database is yours, anything the export does not cover is a query away rather than a support ticket.
-
Menu Item Management
Build the menu with categories, descriptions, photos, pricing and availability. Items can be turned off the moment the kitchen runs out rather than disappointing a customer at checkout.
How many items a restaurant may list is a plan limit, enforced by the platform, which gives tiering a meaning beyond marketing copy.
-
Categories
Organise the menu the way guests read it rather than the way it was entered, with ordering you control.
The same structure drives the storefront and the QR menu, so a well-organised menu immediately makes ordering better.
-
Variations
Sizes and versions of the same dish — small, medium, large; half, full — each with its own price and stock.
Priced correctly everywhere: the POS, the storefront and the QR flow all read the same variation.
-
Add-ons
Reusable add-on groups such as toppings or sides, attached to the items that offer them.
Change a sauce list once and every dish offering it updates, instead of editing item by item.
-
Extras
Chargeable extras on top of an order — extra cheese, a second dip — handled as priced options rather than free-text notes.
Free-text notes are where kitchens lose money; priced extras are where they recover it.
-
Attributes & Dietary Tags
Tag items as vegetarian, spicy, halal or whatever your market cares about, and group the menu by attribute.
Guests filter by what they can eat, which is a better experience than scrolling and guessing.
-
Featured Items
Promote specific dishes to the top of the storefront to push margin or clear stock.
The simplest revenue lever on the whole platform, and the one restaurants use most often.
-
Taxes
Tax rates and rules configured per restaurant, applied consistently across POS, online orders and invoices.
Tax that is right in one channel and wrong in another is worse than no tax handling at all.
-
Bulk Import & Sample Files
Import a menu from a spreadsheet, with a sample file to match, instead of typing a hundred dishes by hand.
Onboarding a restaurant with a large menu is where most platform trials quietly die.
-
Online Ordering Storefront
Each restaurant gets a branded ordering site: menu, cart, checkout, payment and order tracking, working in a phone browser with no app to install.
Orders placed here carry no marketplace commission, which is usually the clearest argument a restaurant hears all year.
-
Four Order Types
Delivery, takeaway, POS and dining table are first-class order types, each with its own rules for charges, timing and fulfilment.
One pipeline, four doors: a restaurant reconciling separate systems at closing time is a restaurant that will leave you.
-
QR Table Ordering
Guests scan the code on the table, browse the menu on their own phone and order without waiting. Orders arrive tagged with the table they came from.
No app download for the guest and no extra hardware for the restaurant, which is why QR ordering outlived the period that popularised it.
-
Dining Tables & Floor View
Table layout, occupancy and open tabs in one view. Staff see what is seated, what is waiting on food and what is ready to clear.
Table, QR and POS orders land in the same place, so the floor is never run from two screens.
-
Table Sessions & Split Bills
A table session holds everything ordered across a visit, and the bill can be settled as one or divided between guests.
Group dining is where weaker POS products fall over, usually in front of the whole table.
-
Call-a-Waiter
Guests request service from the QR menu, and the call appears on staff screens instead of an arm in the air.
Small feature, disproportionate effect on how attentive a restaurant feels to its guests.
-
POS Orders
Walk-in orders taken at the counter flow into the same pipeline as online and table orders, with the same menu, pricing and reporting.
One source of truth is the point. Anything else means somebody reconciles numbers at midnight.
-
Nine-Stage Order Lifecycle
Orders move through pending, accepted, preparing, prepared, out for delivery, delivered, and the exceptions: cancelled, rejected and returned.
The exceptions matter as much as the happy path, because that is where money and goodwill are actually lost.
-
Active Order Board
A live board of everything in progress, ordered by urgency rather than arrival — during a rush, the only screen anyone has time for.
The kitchen works to the right priority without being told, which is what keeps tickets moving.
-
Order Rules & Setup
Minimum order values, preparation times, scheduling windows and which order types a restaurant accepts, all configurable.
Rules enforced at checkout prevent the orders a kitchen cannot actually fulfil.
-
Kitchen Display System (KDS)
Orders appear on a kitchen screen as tickets, grouped and timed, replacing printed dockets that get lost, smudged or missed.
Chefs mark items started and ready, which updates the floor and the customer automatically rather than by shouting.
-
Kitchen Order Tickets (KOT)
Each order produces a ticket carrying its items, modifiers and notes, printed or displayed, and tracked to completion.
The KOT is the record that settles "we never got that order" without anyone having to be believed.
-
Multiple Kitchens & Stations
A venue can run more than one kitchen or station, with tickets routed to the right one. Drinks go to the bar, grills go to the grill.
Essential for anything larger than a single counter, and the detail that separates a real platform from a demo.
-
Order Status Screen (OSS)
A customer-facing display showing which order numbers are preparing and which are ready — the screen you see in a food court.
It clears the crowd at the counter, a real operational gain in takeaway and quick-service venues.
-
Chef Accounts
Kitchen staff log in with their own credentials and see the kitchen display and their tickets, and nothing else.
Giving the kitchen a screen should not mean giving the kitchen the revenue figures.
-
Waiter Accounts
Floor staff take orders on their own login, with their tables and tabs, and send them straight to the kitchen.
Orders carry the waiter who took them, which makes service questions answerable after the fact.
-
Delivery Management
Assign orders to delivery staff, track them to completion and keep the customer informed on the way.
Works whether a restaurant employs its own riders or runs a small shared pool across branches.
-
Delivery Areas & Charges
Define the areas served and what delivery costs in each, including minimum order values per zone.
Orders outside the zone are refused at checkout rather than accepted and then cancelled — the version customers forgive.
-
Customer Accounts & Addresses
Customers keep saved addresses, order history and reorder in a tap. For the restaurant it is a list of people who have actually bought something.
That customer list belongs to the restaurant, not to a marketplace — the asset most operators give away without noticing.
-
Ratings & Reviews
Customers rate orders and leave reviews, visible to the restaurant and, where it chooses, on the storefront.
Feedback that belongs to the restaurant rather than sitting on a platform that charges for the privilege.
-
Coupons
Codes with percentage or fixed discounts, minimum spend, usage caps and expiry dates, validated at checkout.
Coupon usage appears in reporting, so a restaurant can see whether a campaign brought revenue or gave margin away.
-
Offers & Promotions
Scheduled promotions across chosen items, run without a developer and switched off the same way.
Restaurants run promotions constantly; a platform that makes it a support ticket is a platform they resent.
-
Time Slots & Opening Hours
Opening hours, preparation times and delivery windows per restaurant and per branch, including different hours on different days.
Orders cannot be placed for a time the kitchen is closed, removing an entire category of complaint.
-
Cash Register & Shifts
Open and close the register per shift, record cash in and out, and reconcile against what the system expected.
Cash still matters in hospitality, and a POS that ignores it leaves the hardest part of the day unsupported.
-
Customer Messaging
Order-related messages between restaurant and customer, kept with the order rather than scattered across personal phones.
When a substitution is needed mid-order, this is what stops it becoming a refund.
-
Theme & Branding
Logo, favicon, footer mark and brand colours per restaurant, applied across the storefront and the panels.
White-label means the restaurant's customers see the restaurant, not your product and not ours.
-
Sliders & Hero Content
Banners and promotional slots on the storefront, managed by the restaurant rather than by you.
Every change a customer can make themselves is a support request you never receive.
-
CMS Pages
About, contact, policies and other pages edited in the panel, so a restaurant's site is complete without a developer.
Legal pages in particular cannot wait on your release schedule.
-
FAQ & Content Blocks
Question-and-answer content and reusable blocks for the storefront, maintained by the restaurant.
Answers the questions that would otherwise arrive by phone during service.
-
Cookie Notice
A configurable cookie notice, which is not optional in several of the markets this platform is sold into.
Shipping it means your customers are not left solving a compliance problem you handed them.
-
Incoming Order Alerts
New orders arrive with a push notification and an audible alert, so nothing sits unacknowledged while the counter is busy.
Owners accept or reject from the phone, so running online ordering does not need somebody stationed at a desk.
-
Order Tracking on the Move
The full order pipeline on a phone: preparing, ready, out for delivery, done.
An owner covering two branches can see both without being in either, which is the normal case rather than the exception.
-
Menu & Availability Control
Mark an item unavailable the moment it runs out, adjust prices and toggle categories from the phone.
The change reaches the storefront, the QR menu and the POS at once, so the menu guests see is the menu the kitchen can cook.
-
Sales at a Glance
Today's revenue, order count and busiest items, without opening a laptop.
Deliberately a summary: the phone answers "how are we doing", the desktop answers "why".
-
Staff & Shift Visibility
See who is on, which orders they are handling and how the floor is covered.
Scoped by role like everywhere else, so a manager sees their branch and an owner sees the group.
-
Push Notifications
Order events, low stock and platform messages reach the right person through Firebase rather than waiting on a refresh.
Notifications are the difference between an order that moves and one that waits for somebody to look.
-
Counter Billing
Take walk-in orders and bill them on a tablet or phone. No proprietary terminal to buy, no lock-in to one hardware vendor.
Orders ring up against the same menu and tax rules as every other channel, so figures reconcile without adjustment.
-
Fast Category Navigation
A POS-specific category layout tuned for speed at the counter rather than for browsing.
Seconds per order matter at a lunch rush in a way they never do on a website.
-
Table Orders & Tabs
Open a tab against a table, add to it through the service, settle it once at the end.
The same tab is visible to the waiter app and the floor view, so whoever is nearest can add to it.
-
Multiple Payment Methods
Cash, card, mobile banking, bank transfer and due accounts, chosen at the counter when the bill is settled.
Due lets a regular run a tab across visits — normal practice in many markets and missing from most POS products built elsewhere.
-
Kitchen Order Tickets
Confirmed orders go straight to the kitchen display or ticket printer, with modifiers and notes attached.
Removes the handwritten docket, which is where most kitchen errors begin.
-
Receipts & Order Records
Printed or digital receipts carrying the restaurant's branding, tax details and order reference.
Every POS sale lands in the same order history as online orders, so a refund weeks later is a lookup rather than an investigation.
-
Register Shifts
Open and close the drawer per shift with recorded cash movements, reconciled against what the system expected.
Gives an owner a defensible number at the end of the night instead of a disagreement.
-
Assign a Delivery Rider
A counter order destined for delivery can be handed to a rider from the POS without switching screens.
Keeps takeaway and delivery on one counter workflow rather than two.
-
Order Assignment
Riders receive assigned orders with a push notification carrying the pickup, the drop-off and what is in the bag.
Assignment is visible to the restaurant too, so a dispatcher always knows who has what.
-
Active Orders
What the rider is carrying right now, in the order it should be delivered.
Prevents the common failure where the furthest order goes first and the other two arrive cold.
-
Delivery History
Completed deliveries with dates, orders and earnings, available to the rider without asking the office.
The same record settles payment questions on the restaurant's side.
-
Address Mapping & Navigation
Delivery addresses open in the rider's maps application with the route already set.
Google Maps is configured per installation, so you use your own key and control that cost.
-
Delivery Status Updates
Picked up, on the way, delivered — each update reaches the customer and the restaurant as it happens.
Most "where is my order" calls disappear once the customer can see the answer themselves.
-
Customer Contact
Call or message the customer from inside the app when an address is unclear, without exchanging personal numbers.
Protects the rider's privacy and keeps the conversation attached to the order record.
-
Cash on Delivery Collection
Orders paid in cash are marked collected on the doorstep and recorded against the rider.
Cash on delivery remains dominant in many markets, and ignoring it rules those markets out entirely.
-
Profile & Addresses
Riders manage their own details, photo and addresses rather than filing a request with the office.
Less administration for the restaurant, which is the whole reason staff apps exist.
-
Delivery Earnings
Delivery fees and tips recorded against each completed order, so a rider sees what they have earned.
Both sides read one history, which is what stops earnings becoming a weekly argument.
-
Delivery Statistics
Orders delivered, over what period, and how that compares with before.
Gives a restaurant something factual to base rider scheduling on.
-
Payment Gateways
Stripe, PayPal, Flutterwave and SSLCommerz are wired up, alongside cash on delivery and store credit, enabled and keyed per installation.
Because you hold the code, adding a gateway your market needs is a development task you can scope, not a feature request someone else prioritises.
-
Test & Live Modes
Each gateway runs in test or live mode, so a restaurant can be set up and rehearsed before it takes real money.
Onboarding without this means every new customer's first transaction is also their first test.
-
Currencies
Currency and decimal handling configured per restaurant, with a global currency list behind it.
What makes a single platform workable across regions rather than only in the one it was built for.
-
SMS Gateways
Twilio, Clickatell, Nexmo and BulkSMSBD are supported for order notifications and OTP delivery, configured per installation.
SMS pricing and deliverability vary enormously by country, and being locked to one provider is expensive.
-
OTP Verification
Phone and email verification for customer sign-up and password reset, with the gateway of your choice behind it.
Cuts fake accounts without adding friction to the people who actually want to order.
-
Push Notifications
Firebase push for order updates to customers, new orders to merchants and assignments to delivery staff.
Managed per installation, so your notifications come from your project rather than ours.
-
Notification Rules
Which events notify whom, by which channel, configured rather than hard-coded.
Every restaurant has a different view on what is worth a phone buzzing at 11pm.
-
Email Setup & Templates
Transactional email configured in the admin, with templates you control.
You decide what your customers receive and how it is worded, which matters when the platform carries your brand.
-
Four Languages, RTL Included
The interface ships in English, Arabic, Bengali and German, and Arabic runs properly right-to-left rather than as mirrored English.
Adding another language is a translation file, not a code change, so a new market does not need a new release.
-
Timezones
Each restaurant runs on its own timezone, so reports, opening hours and order timestamps mean what the staff think they mean.
The bug that bites every platform selling across borders, handled before it is yours to debug.
-
Country Codes & Phone Formats
Phone input and validation that accept the formats your markets actually use.
A sign-up form that rejects a valid local number is a customer you never hear from again.
-
A Landing Site, Built in Nuxt
A separate front end from the platform itself: the public site where restaurants find you, read what the software does, and decide whether to sign up. Built in Nuxt 3 with server-side rendering, so pages arrive fast and search engines can read them.
It means you are not commissioning a website before you can sign your first customer. The site is in the box, under your brand, the day you deploy.
-
Every Word Comes From Your Admin
The landing site reads its content from the platform over an API. Headlines, features, pricing, FAQ answers, blog posts, testimonials — all of it is edited in the same admin panel you use to run the business.
Change a plan price once and it updates on the site, because both are reading the same record. Nobody has to redeploy a website to correct a typo.
-
Where Restaurants Sign Up
Restaurants browse your plans on the landing site, then follow the sign-up link into the app to create their account. Payment and subscription happen inside the platform, where billing lives.
The split is deliberate: the landing site is for reading and deciding, the app is for accounts and money. One job each.
-
Hero
The opening pitch: headline, supporting copy and the call to action that sends a restaurant into sign-up.
Edited from the admin, so you can change how you position the product without touching the site.
-
Features
What the platform does, drawn from the feature records you maintain in the admin, with images and descriptions.
Add a feature to the platform and it can appear on your landing site the same day.
-
Pricing
Your plans, their prices and what each tier includes, with a monthly and annual toggle. The same plan records the platform bills against.
Restaurants compare tiers here and click through to register. They cannot buy on the landing site itself — the purchase happens once they have an account.
-
How It Works
The steps a restaurant goes through, from signing up to taking their first order.
The question every prospect has before they commit, answered on the page rather than by email.
-
Who It Is For
The kinds of venue the platform suits — cafes, quick service, cloud kitchens, multi-branch groups — each described separately.
A restaurant owner wants to see their own kind of business on the page before they believe the software fits.
-
Overview
A fuller explanation of the platform for visitors who want more than the headline before deciding.
Content is managed in the admin like everything else, so this grows as your pitch sharpens.
-
Reviews
Testimonials from restaurants already on your platform, with names and photographs.
The section is there from day one and stays empty until you have real customers to quote, which is how it should work.
-
Partners
Logos of partners or integrations you want to show.
Useful once you have payment providers, aggregators or resellers worth naming.
-
FAQ
Questions and answers maintained in the admin, rendered as an accordion.
Answers the objections that would otherwise arrive as support tickets before anyone has even signed up.
-
Blog
A blog with listing and article pages, written in the admin. Posts carry images, categories and full article bodies.
How a restaurant platform gets found. Searches like "QR menu for cafes" are answered by articles, not by a pricing page.
-
About and Contact
Your story and a contact page with a working enquiry form, both edited in the admin.
Restaurants check who they are buying from. An empty About page costs you deals you never hear about.
-
CMS Pages
Any additional page you need — policies, terms, a guide — created in the admin and served on the landing site at its own URL.
Legal pages in particular cannot wait on a release schedule.
-
Your Branding
Logo, colours, contact details and social links come from your settings, so the landing site carries your brand rather than ours.
Nothing in the code names us. It is your site from the first deploy.
-
SEO and Social Previews
Server-side rendering with per-page titles, descriptions and Open Graph tags, so pages are indexable and links preview properly when shared.
A client-rendered site that search engines cannot read is a marketing site that does not market.
-
Works on a Phone
The whole site is responsive, which matters because most restaurant owners will first see it on a phone.
The sign-up path works the same on a small screen as on a desktop.
Ready to own your restaurant platform?
Pay once for the full source code. No monthly fees, no commissions, and we deploy it on your servers within 3 days.