Fake demo orders
18
Seeded display number only, not live order data.
Future adapter: count orders by business day.
Static owner preview
A fake owner console for the sales demo
Show a restaurant owner what a future owner/admin experience could feel like, without adding real admin access, live orders, customer data, payments, or backend services.
Today at a glance
Fake metrics for owner conversation
Top fake item
Mixed platter
Example insight based on static demo content.
Future adapter: aggregate order item snapshots.
Sample prep time
16 min
Illustrative owner-console metric, not kitchen timing.
Future adapter: status timestamps and prep settings.
Repeat signal
42%
Fake retention preview for sales conversation only.
Future adapter: privacy-reviewed customer identity rule.
Menu snapshot
Photo and item readiness
- Chicken over rice: hero item photography ready
- Lamb over rice: premium platter imagery ready
- Mixed platter: best-seller concept ready
- Falafel over rice: vegetarian option ready
- Gyro sandwich: handheld item imagery ready
- Sides, sauces, drinks, and extras: category slots ready
Popular items
Static examples only
- Chicken over rice
Fake top lunch item
- Mixed platter
Fake dinner favorite
- Falafel over rice
Fake vegetarian repeat item
- Gyro sandwich
Fake grab-and-go item
Demo status board
Fake order cards, not live management
Received preview
HHP-DEMO-1042
Mixed platter, white sauce, medium spice
Static card only; no order exists.
Preparing preview
HHP-DEMO-1043
Chicken over rice with extra white sauce
Fake status label for owner conversation.
Ready preview
HHP-DEMO-1044
Falafel over rice, green sauce
Not connected to a kitchen or customer.
Pair this static owner-side board with `/order-status-preview` to show the matching fake customer status concept, then open `/owner-console-preview` for a deeper fake operations and menu editor preview. None of these pages are connected to live orders.
Brand/app readiness
What the founder can point to
- Logo and app icon direction ready for owner branding swap
- QR menu concept ready for cart window, counter, receipt, or social profile
- Add-to-home-screen story ready for supported browsers
- Menu image slots ready for owner food photos
Future scoped work
Not live in this demo
- Future real ordering workflow
- Future payment handling
- Static operations/menu editor preview
- Regular customer/reorder insight preview
- Staff notifications
- Analytics
- Loyalty tools
- Customer list
Owner value
Why this matters in a small-food-business pitch
- Shows the owner how direct digital presence could look without starting with marketplace pages.
- Makes menu quality, photos, modifiers, and QR access easier to explain in one short meeting.
- Helps separate what is already demo-ready from what would need careful future scoping.
Database-ready later
Data boundaries before real owner tools
- Real order metrics would require a database, staff workflow, retention policy, and owner approval.
- Customer signals should be minimized and should not require accounts unless a real business case is approved.
- Menu edits, order status changes, and staff actions would need server-side authorization and audit logs.
- Payment, refund, tax, and receipt data must stay out of this mock shell until production scope is approved.
Owner preview guardrail
Do not present this page as a live dashboard. It is a static owner preview with fake examples only. A real owner/admin product would need separate requirements, authentication, authorization, data storage, privacy review, operational rules, and testing.