Static report preview

Owner insights preview

Show how future owner reporting and promotion planning could feel after the menu, status, and owner operations previews, while this demo stays fully disconnected from analytics, customer records, and campaign systems.

Back to owner console Preview store setup Customer status preview Regular customer preview Review promo readiness

Fake reporting period

Demo report period: sample weekday lunch window

Static report preview generated from seeded mock data

Demo insightNo live data source

Future database-backed report

What this preview can safely show

Data source: Seeded mock rowsNo tracking events, customer profiles, or order records.
Reporting style: Illustrative metric cardsStatic percentages are used only for founder discussion.

Review fake report

Popular item report preview

ItemMock trendIllustrative share

Combo Over RicePlattersDemo insight based on seeded menu story, not order history.

Mock trend: steady lunch favoriteFuture adapter: aggregate immutable order item snapshots by reporting period.

36% Illustrative item mix

Chicken Over RicePlattersStatic report preview only; no customer or sales data is collected.

Mock trend: reliable baseline itemFuture adapter: menu item snapshot grouping with category joins.

28% Illustrative item mix

Falafel Over RicePlattersMock trend label for founder conversation, not live reporting.

Mock trend: plant-forward optionFuture adapter: item mix report with allergen and modifier context.

21% Illustrative item mix

Mango Lassi Demo CupDrinksStatic add-on signal used to discuss future menu planning.

Mock trend: drink pairing opportunityFuture adapter: add-on attachment report from order line snapshots.

15% Illustrative add-on mix

Menu and photo readiness

Static readiness report

Illustrative metric

Menu photo readiness

Demo image set ready

Prepared 4:3 menu images are enough to show the owner how a real photo review could be organized.

Future adapter: media asset review status by menu item.

Static report preview

Modifier mapping

Core platters mapped

Sauce, spice, base, and extra groups are represented by seeded menu data only.

Future adapter: modifier groups, option rules, and validation state.

Demo insight

Store setup readiness

Future scoped

Hours, service modes, promo terms, and policies still need owner-approved production decisions.

Future adapter: storefront setup checklist with audit history.

Repeat-customer signal

Mock reorder signal

Repeat-order signalstatic-seed

Mock reorder interest

Shows where future reports could summarize repeat-item behavior without exposing customer identities.Future adapter: privacy-reviewed customer identity or guest token rule.

Regular customer previewbrowser-local

Browser-local story

Pairs with local favorites and reorder cards, not real customer history.Future adapter: consented favorites and retention controls if approved.

Privacy boundarystatic-seed

No profiles

No customer names, phones, emails, addresses, cohorts, or profiles exist in this preview.Future adapter: data minimization and deletion policy before reports.

Operations insight panel

Mock trend cards

Prep window signalMock trend

15-20 min preview

Illustrates how prep-window labels could be reviewed after real status events exist.

Future adapter: status timestamps and service-mode settings.

Ticket readinessFuture database-backed report

Read-only shape

Connects the prep ticket concept to future staff workflow requirements.

Future adapter: authorized ticket read model and audit events.

Settings readinessStatic report preview

Discovery needed

Flags production decisions needed for hours, policies, service modes, and promo terms.

Future adapter: owner setup tasks with role-based updates.

Promo readiness preview

These static offer concepts help discuss what could be planned later. They do not create coupon codes, apply discounts, message customers, or change menu prices.

Needs pricing and terms approval

Lunch special concept

Static offer concept: platter plus drink pairing

Audience label: Walk-up lunch crowd
Configurable later: Eligible menu items, Service window, Display copy
Required dependencies: Owner-approved pricing rules, Expiration and availability policy, Order/payment integration decisions, Compliance and support review

Future adapter: promotion rule draft with eligibility and terms fields.

Needs menu and fulfillment scope

Family platter highlight

Static offer concept: family tray feature placement

Audience label: Group meal planning
Configurable later: Featured item, Prep notice language, Availability window
Required dependencies: Menu approval, Prep capacity rules, Pickup/catering policy, Support wording review

Future adapter: campaign planning row tied to menu availability.

Needs privacy and consent scope

Regular reorder nudge

Static offer concept: favorite-item reminder

Audience label: Returning guest concept
Configurable later: Eligible favorite items, Customer-facing wording, Frequency limits
Required dependencies: Consent and retention policy, Customer identity model, Message policy if ever approved, Abuse and support rules

Future adapter: consented communication plan only after privacy scope.

Preview future reporting scope

What would be connected later

Future database-backed reports would need order item snapshots, menu history, and owner-authorized reporting access.
Real customer or repeat-order reporting would need consent, minimization, retention, deletion, and support policies.
Promotion planning would need approved terms, pricing, expiration rules, order/payment integration decisions, and compliance review.
No tracking scripts, analytics keys, export files, coupon redemption, campaign delivery, or live discount behavior exists in this preview.