eFood

About eFood

eFood is a single-restaurant food ordering and delivery platform in Laravel + Flutter. It is built for one restaurant brand — including multi-branch chains and cloud kitchens — that wants its own branded ordering app instead of being one of many restaurants on a marketplace.

If you want to run multiple restaurants on one platform (Foodpanda / Uber Eats style), pick StackFood. If you need an "everything app" with food + grocery + pharmacy, pick 6ammart.

Who eFood is for

• A single restaurant going digital with its own customer app and ordering site.
• Multi-branch chains (e.g. a fast-food chain with 5-50 outlets) consolidating ordering under one brand.
• Cloud kitchens that need a unified app for delivery, dine-in and pickup.
• Fine-dining establishments adding reservation + table ordering to in-person service.

What you get in the box

• Customer app (Android + iOS) — order delivery, dine-in or pickup, with live tracking.
• Waiter / table-order app — staff take dine-in orders at the table, push directly to kitchen.
• Kitchen / chef display app — kitchen sees incoming orders, marks each item ready.
• Deliveryman app — accept jobs, GPS navigation, proof of delivery.
• Laravel admin panel — menu, branches, staff, payments, analytics.
• Branch panel — per-branch dashboard for branch managers.
• Customer ordering website — branded, fast checkout, optional table reservation.

Key capabilities

• Menu, category and add-on management with item-level photos and modifiers.
• Three order types — delivery, dine-in (table), pickup.
• Dine-in via waiter app — server takes order, kitchen sees it instantly.
• Kitchen display system (KDS) — order ticket per station, mark items ready, auto-route to server.
• Live order tracking with driver assignment for delivery orders.
• Customer wallet, loyalty points, referrals and scheduled orders.
• Coupons and campaigns — flat, percentage, BOGO, free-delivery.
• Multi-branch operations — per-branch menu overrides, prices, hours, delivery zone.
• Refund and dispute handling baked into the admin.
• Push notifications + OTP login via Firebase.
• Multi-language and multi-currency localisation.

What we install, configure and test

• Server / hosting (PHP 8.1+, MySQL, queues, cron, SSL).
• Branded Customer, Waiter, Kitchen and Deliveryman apps for Android + iOS.
• Admin, branch panel and customer website on your domain.
• Firebase push + OTP, Google Maps APIs, SMTP and social login.
• Existing payment gateways and SMS providers.

Delivery is 1-3 working days once requirements are complete. Free lifetime support included.

eFood vs StackFood vs 6ammart

Frequently asked questions

Can I run a multi-branch chain (e.g. 20 outlets) with eFood?

Yes — eFood is designed for single brand, multi-branch. The admin manages all branches; each branch has its own menu overrides, hours, prices and delivery zones. The customer app shows the nearest open branch automatically.

Does eFood handle dine-in orders?

Yes — the Waiter app lets staff take orders at the table; the Kitchen app (or web-based Kitchen Display System) shows incoming orders by station and timestamps each item.

Can customers pre-book a table or schedule an order?

Yes — both. Customers can schedule a delivery / pickup for a future time, and on supported plans, reserve a table for dine-in.

Does the customer website need Node.js hosting?

The React (Next.js) customer website needs a Node.js host. If your hosting is PHP-only (cPanel-class), we deploy the Flutter web build instead — same customer experience, different runtime.

How is the kitchen display app different from the admin panel?

The Kitchen app is always-on per station — chefs see incoming orders without logging in to a full admin panel. Each item card is mark-as-ready, and the waiter app sees the status update in real time.

Do I get the source code?

Yes — Laravel admin, Flutter apps and customer website land on a private GitHub repo.

Running many restaurants on one platform? Use StackFood instead.