Startup
Mobile & web application

NFTECH

Sector: Food service
Delivered as: Website
Mobile app
Back office
Languages: FR / EN / AR
Live site: Visit the sitenftech.ma(opens in a new tab)

“Gérez chaque établissement et chaque commande depuis un seul écran.”

(The project)

A multi-tenant platform for fast-food and restaurant stores: customers order on a branded storefront, owners run menus, zones and staff from their dashboards, and the team works the floor from one mobile app, all synchronised in real time.

(Context)

One platform where most restaurants juggle three tools.

A restaurant usually has a website for customers, a back office for the owner, and paper tickets, phone calls or WhatsApp to coordinate kitchen, waiters and couriers. NFTECH joins all of it into one system on one database.

Customers browse and order on the storefront. Owners manage menus, delivery zones, themes and staff. On the floor, the kitchen sees tickets, waiters take orders at the table and couriers share their live position. Every order change reaches all three surfaces at once.

(Key figures)

connected applications: 3
staff modes: kitchen, waiter, courier: 3
in every app: FR / EN / AR
real-time events: 15

(The ecosystem)

The decisions that shaped it

One set of rules, on the server
Totals, delivery fees, zone checks, order numbers and permissions are computed by the back end. The storefront and the mobile app display results and never recompute money.
Single source of truth
A new store is configuration
Every store shares one isolated schema and gets its own storefront address, theme and template, applied at request time. Opening a store needs no deployment.
Multi-tenancy
Real time everywhere, push as a fallback
The same order, stock, table and courier-location events reach the storefront and the staff app over WebSockets. Push notifications cover the moments the app is closed.
No polling
Each role sees its own screen
After a phone code sign-in, staff land in the kitchen, waiter or courier mode their role allows, and the server enforces the same restriction.
Role-based access

(How it works)

A dine-in order, end to end

Scan the table
A guest scans the table’s QR code and the storefront opens in dine-in mode with the table already attached.
Order
The order is created and its totals recomputed on the server from the cart, never from the browser.
Kitchen ticket
The kitchen display receives the ticket instantly, with a sound alert, and the team starts preparing.
Serve and track
When the cook marks it ready, the waiter is alerted and the guest’s tracking page moves forward.

Inside the project

Captures of the delivered build, grouped by product. Select one to see it at full size.

Website

3 captures

NFTECH: The platform’s modules — The platform’s modules

NFTECH: Delivery, tracked to the door — Delivery, tracked to the door

Mobile app

6 captures

NFTECH: Kitchen: KDS screen — Kitchen: KDS screen

NFTECH: Waiter: ordering at the table — Waiter: ordering at the table

NFTECH: Waiter: ready to serve — Waiter: ready to serve

NFTECH: Courier: deliveries in progress — Courier: deliveries in progress

NFTECH: Courier: earnings — Courier: earnings

NFTECH: Courier: order history — Courier: order history

Back office

3 captures

NFTECH: Dashboard: orders, revenue and best sellers — Dashboard: orders, revenue and best sellers

NFTECH: Orders by status, with cancellation requests — Orders by status, with cancellation requests

NFTECH: Menu management by category — Menu management by category

Technology

Front end: Next.js 16
React 19
Tailwind CSS 4
Radix UI
Zustand
TanStack Query
Back end: Laravel
Sanctum
MySQL
Redis
Mobile: Expo 54
React Native 0.81
NativeWind
react-native-maps
Real-time & notifications: Laravel Reverb
Pusher
Laravel Echo
Expo Notifications
Firebase
Payments: Stripe
CMI
Infrastructure: Docker
Nginx
Coolify
EAS Build & Updates