4
واجهات استخدام
customer, driver, owner dashboard, POS
SaaS · 2026
نظام متكامل لتشغيل المطعم، وكل المطاعم تعمل على نظام خلفي واحد يخدمها جميعاً (Multi-tenant): طلبات الزبائن، وتوزيع التوصيل على السائقين، ولوحة تحكّم للمالك، ونقاط البيع.
4
واجهات استخدام
customer, driver, owner dashboard, POS
51
صفحةً في لوحة التحكّم
58k
Frontend code
lines across the surfaces
Multi-tenant
Tenancy
scoped at the data layer
المشكلة
Independent restaurants take orders over messaging apps and track them on paper. Delivery platforms charge heavy commission and keep the customer relationship, so the restaurant never learns who its regulars are. Owners have no live view of orders, drivers or daily revenue, and no system that covers both delivery and walk-in trade.
الحلّ المعتمد
Built four surfaces over one multi-tenant backend where each restaurant is an isolated tenant sharing a single codebase and deployment. A customer ordering experience for browsing and checkout, a driver surface for assignment and live location, an owner dashboard covering menu, orders, drivers and analytics, and a point of sale for counter trade so both channels land in the same order model. Tenant scoping is enforced at the data access layer rather than trusted to individual queries.
بنية النظام
One API with tenant-scoped data access enforced centrally. Live order and driver events over per-tenant socket rooms. Delivery and counter orders share one order model so reporting and stock behave identically regardless of channel.
ومع كل قرار ثمنه
القرار الذي لا يُذكر ثمنه مجرّد تفضيل شخصي.
01
السبب
مجموعة خوادم واحدة، ونشر واحد، وطريقة واحدة لترحيل البيانات. وإضافة مطعم جديد تصبح مجرّد سجلّ جديد، لا مهمّة بنية تحتية.
الثمن
كل استعلام يجب أن يقتصر على بيانات مطعم واحد. لذلك وُضع هذا القيد في طبقة واحدة للوصول إلى البيانات يستحيل فيها نسيانه، بدل تكراره في كل وحدة تحكّم (controller)، حيث يصبح نسيانه مسألة وقت.
02
السبب
Reporting, refunds, stock effects and customer history are identical logic regardless of how the order arrived. Two models means writing all of it twice and watching them drift.
الثمن
A few channel-specific fields are nullable on the shared model, a far smaller cost than duplicated business logic.
03
السبب
Zero install friction for customers and drivers, one codebase per surface, and updates that ship without an app store review.
الثمن
Push notification support is weaker than native, handled through web push.
النتيجة
A restaurant goes from signup to taking online orders in under a day, keeps its full margin, and owns its customer data. Four surfaces across roughly 58,000 lines of frontend and a shared backend, with 51 dashboard pages and 27 customer pages.