AZ Azerbaijan / AZN
MUPZA OperatorOwner accountMU
M
MUPZAOSRestaurant OS command

MUPZAOS / Daily Control

Restaurant Operations Command Center

POS, kitchen, waiter, QR, website, printer bridge and release-readiness workflows run from one local-first operator surface. Cloud services stay gated while LAN authority remains independent.

AI release forecast91%

Core restaurant signals are ready for the next QA-backed sprint chain.

LAN modePOS, kitchen, waiter and printer bridge keep working offline.
Risk actionsManager approval and audit log are mandatory.
Public ordersQR and website orders flow to all local operators.
ReleaseLocal QA evidence comes before GitHub and AWS work.
BugГјnkГј satД±Еџ
в‚ј 86.80
4 demo sifariЕџ
Yeni sifariЕџlЙ™r
1
QR vЙ™ website routing aktivdir
HazД±rlanan
1
Kitchen ticket foundation
Offline sync
1
POS Local Hub queue

Live Order Routing

Mock flow covers public, POS and local kitchen/printer routing.

QR MENU order_1241 — Masa 7Rəşad · 2 item · ₼ 33.00 · sync: synced
new
WEBSITE order_1240 — No tableUnassigned · 2 item · ₼ 23.00 · sync: synced
preparing
POS order_1239 — Masa 3Aydan · 1 item · ₼ 9.90 · sync: local_only
accepted
WAITER APP order_1246 — Masa 7Rəşad · 2 item · ₼ 20.90 · sync: pending_sync
accepted

Restaurant Setup MVP Flow

Owner setup stays separate from operator-only secrets and platform settings.

1
Restaurant profile

Logo, cover, VOEN, phone, work hours and delivery/pickup settings.

2
Domain engine

Default subdomain plus assisted custom domain request through WhatsApp/call center support.

3
Menu catalog

Category, product, modifier/add-on, combo v1, QR/POS/website visibility.

4
Order routing

QR/website/POS/waiter/kiosk orders flow into POS, admin, kitchen, printer and courier.

5
Approval guard

Risky POS buttons are integrated with manager approval guard and offline approval queue.

6
Audit log

Approved, blocked and queued risk actions are visible in POS audit log preview.

7
Communication outbox

OTP, WhatsApp, Telegram, email and in-app notifications start as audited provider contracts.

8
Notification consent templates

External sends require consent, audit and blocked secret payload fields.

9
Customer consent ledger

SMS OTP, WhatsApp, Telegram and email consent changes are audited and opt-outs block external sends.

10
Notification provider dry-run harness

OTP, WhatsApp, Telegram, email and LAN in-app sends are simulated with audit evidence.