Demo business - no real orders or payments. This is a fictional sales demo, not an operating restaurant.

Regular customer preview

Regular customer preview

Show how favorites, reorder-style cards, and app-like convenience could feel for a future repeat customer flow while this public demo stays fake-data-only.

Loyalty-style preview

Loyalty-style status: 3 of 5 demo visits

Static convenience preview only; no real loyalty record exists.

This illustrates future scoped work only. No real reward, customer profile, or remote loyalty record exists.

App-like preferences

Static preference chips

Favorite sauce
White sauce with green herb sauceFuture adapter: privacy-reviewed saved preference after account scope is approved.
Spice
Medium spiceFuture adapter: preference enum attached to a customer-owned profile only if approved.
Base
Yellow rice with saladFuture adapter: default modifier selections with deletion/export support.

Static favorites preview

Favorite items from the demo menu

Generated demo chicken over rice platter with grilled chicken, yellow rice, salad, pickled onions, and white sauce

Platters

Chicken Over Rice

$11.95
Rice onlyWhite sauce on the sideMild spiceExtra white sauce cup

Future adapter: customer-owned favorite with explicit consent and retention rules.

Reorder-style demo

Recent fake order cards

Demo T-2 visits

HHP-DEMO-1042

Combo Over Rice, white sauce, medium spice, warm pita, bottled drink

Fake ready-for-pickup previewThis is a seeded reorder-style card, not stored order history.Future adapter: order history read model with customer authorization.
$17.45

Demo T-5 visits

HHP-DEMO-1038

Chicken Over Rice, rice only, sauce on the side

Fake completed previewThe card is deterministic static data and does not identify a person.Future adapter: reorder action would rebuild a cart from item snapshots.
$12.70

App-like convenience

Future scoped value

  • Favorites and reorder cards can explain regular-customer convenience without creating accounts.
  • A future production build would need explicit scope for identity, consent, retention, deletion, and support.
  • Home-screen install plus menu favorites can be shown as app-like value before real ordering exists.

Future database-backed account feature

What would be required later

  • A real regular-customer feature would need authenticated access or another privacy-reviewed identity model.
  • Saved favorites and preferences would need server validation, customer controls, retention rules, and deletion/export support.
  • Loyalty-style progress would need terms, fraud controls, support policy, and clear owner approval before launch.
  • Reorder behavior would need immutable order item snapshots so old orders are not rewritten by menu changes.