Web Point: a restaurant POS built for the floor
A touch-first point of sale and back office for sit-down restaurants with delivery. Used in 5 restaurants in Egypt.
Role
Co-founder, lead frontend developer

5
restaurants used it
~100
orders a day per restaurant
1
touch screen per hall, plus one printer each for the kitchen and the bar
10
management reports
Before and after
Before
A busy restaurant runs a hall, a takeaway counter and a delivery desk at once, each with its own prices, tax and service. Before Web Point, these restaurants ran on paper or on another POS, depending on the place: handwritten tickets, totals added by hand, and cash gaps that showed up the next morning.
After
Web Point runs in the browser on a touch screen in each hall, while the kitchen and the bar have just a printer. The cashier opens a table on a floor plan that matches the real room and adds dishes with a double tap, and each item prints at its own station right away. Payment, shift close and day close follow the same flow, and the owner reads ten reports from the same data.
Key features
See the whole room at a glance
Each hall has its own floor plan with real table sizes. A table's colour tells you if it's free, busy, waiting for payment or reserved.
Each item prints at its own station
A juice prints at the bar and a grill dish in the kitchen, as soon as the order is taken. Kitchen slips can use a different item name from the customer check.
Three channels, one menu
Every item has its own dine-in, takeaway and delivery price, and each channel has its own tax and service rules.
Delivery handled end to end
Find the customer by phone with their saved address and delivery fee, hand the order to a driver, and settle each driver's cash.
Cash that adds up
Day and shift close, numbered checks per terminal with gap detection, void and transfer logs, and per-user discount limits.
Ten reports for the owner
Sales by item, waiter, shift and channel, plus discounts, voids, transfers, cost and cost of sold items.
See it in action

01Dine-in order: from the table to the kitchen
Screens
Desktop
01/ 06
Floor plan: each table's colour shows its state
Screens in this case study use invented demo data (a fictional restaurant, names and prices). No client data is shown.
Mobile
Order screen on a phone
01 / 02
My role
Co-founder, lead frontend developer
Co-founder. I led the frontend: the POS screens (login, floor plan, order and payment, delivery, options) and the control-panel and report interfaces. The backend logic was not mine.
Status
Delivered. Used in 5 restaurants in Egypt, and at least one still runs it today. Not in active development.
Under the hood
Architecture: one Laravel application split into three areas: /menu (the POS), /admin (control panel) and /Reports. Shared business rules for days, shifts, serials, tax and service live in one place and every screen uses them. Most actions are AJAX calls, so terminals never reload during service.
Decisions in the system design (team work):
- Live day vs. history. Orders sit in small "live" tables during service. When the day ends, everything moves to history tables in one step. The screens waiters use stay fast, and reports read from a separate set.
- Printing goes through a queue. The app doesn't talk to printers. It writes print jobs to a queue table, and a print agent on the restaurant network sends each item to its station. Printing never holds up the cashier's screen.
- Built for touch, not a mouse (my part, in the interface). Login is a user picker plus a PIN pad. There's an on-screen keyboard with English and Arabic layouts, items are added by double tap (so a stray touch doesn't add a dish), and ticket lines open their actions with a swipe.
Stack
- Laravel 6
- PHP
- MySQL
- Blade
- jQuery
- AJAX
- Bootstrap 4
- DataTables
- jQuery UI (touch)
- mPDF
- Spatie Permission
Architecture
Next project
Warehouse Management System
One system linking all the warehouses, replacing paper and Excel
Let's start your project
Message me on WhatsApp or by email, and I'll reply within 24 hours.
You can also find my work and experience on

