Review how a future owner setup area could organize brand readiness, service windows, QR/PWA setup, and fulfillment constraints while this public demo remains fully read-only.
Demo business - no real orders or payments. Read-only fake settings only. No business profile, contact details, owner session, storage, delivery workflow, or production fulfillment exists.
Harbor Halal PlattersFictional demo display name for the public preview.Future adapter: storefront_settings.display_name.
Brand status
Demo brand assets readyLogo, mark, icons, and warm palette are committed demo assets.Future adapter: approved brand asset registry.
Operating status
Preview-only normal serviceStatic label only; no live open/closed control exists.Future adapter: service_status plus audit events.
Business contact data
None shownNo owner name, phone, email, street address, tax setting, or legal profile is represented.Future adapter: privacy-reviewed business profile fields if approved.
Brand and app readiness
QR/PWA setup shape
Logo and markDemo-ready
Current committed brand assets are enough for a polished fictional preview.
Future adapter: brand_assets table with review status.
Menu imageryDemo image set ready
Prepared 4:3 menu images support the customer menu and owner menu preview.
Future adapter: media library with licensing review.
App iconPWA-ready
Demo app icons and manifest metadata can support install guidance.
Future adapter: storefront manifest settings.
QR menu pathCurrent origin + /menu
The QR story points to the public menu route without encoding customer data.
Future adapter: approved public menu URL and QR notes.
Install guidancePWA preview ready
The install route explains browser add-to-home-screen behavior without app-store claims.
Future adapter: platform-specific install copy.
Regular customer storyStatic preview ready
Favorites, reorder, and loyalty-style concepts remain fake and non-account-based.
Future adapter: customer identity only after privacy scope.
Hours and service windows
Static schedule preview
Weekday lunch window
11:00 AM-2:00 PM demo label
Illustrative service window only, not a real business hour.
Future adapter: weekly_hours rows with timezone policy.
Evening window
5:00 PM-8:00 PM demo label
Static example for discussing future owner setup.
Future adapter: schedule exceptions and public closed messaging.
Closed-day handling
Future scoped rule
No live storefront availability or ordering cutoff exists.
Future adapter: store closures, holidays, and ordering cutoff policy.
Fulfillment-readiness preview
Service modes, future scoped
Preview-only
Pickup-style demo readiness
Customer routes can show pickup handoff language without reserving food.
Demo-only today
No kitchen ticket, prep promise, pickup reservation, or staff queue exists.
Production discovery
Define prep windows, customer lookup policy, staff workflow, and support rules.
Future adapter: fulfillment_method = pickup plus status events.
Discovery only
Delivery workflow future scope
A future delivery concept would require policy, coverage, pricing, and support decisions.
Demo-only today
No delivery dispatch, live coverage area, driver workflow, address collection, or routing exists.
Production discovery
Define coverage rules, handoff responsibility, fees, availability, and incident handling.
Future adapter: delivery settings after legal and operations review.
Discovery only
Catering/family tray future scope
Family tray and catering interest can be discussed without collecting lead details.
Demo-only today
No catering request form, deposit, scheduling queue, or owner follow-up workflow exists.
Production discovery
Define lead intake, minimums, notice windows, deposits, and staffing expectations.
Future adapter: catering inquiry model only after scope approval.
Fulfillment policy preview
What is demo-only today
Prep-time policy
Current labels are illustrative and never promise a real preparation time.
Production would need prep-time settings, busy-mode rules, and exception handling.Future adapter: prep_window_minutes and busy mode.Tax and fee boundary
The demo has no taxes, fees, payment setup, payment collection, receipts, refunds, or reconciliation.
Production would need provider choice, tax logic, fee display, refund rules, and support policy.Future adapter: payment and tax settings after provider selection.Customer handoff policy
The fake status flow does not identify customers or route messages.
Production would need lookup tokens, privacy review, notification policy, and staff training.Future adapter: customer-safe status lookup and event log.
Future database-backed settings editor
What must be scoped later
A real settings area would require authenticated owner/staff access, role checks, and audit events.
Store profile fields would need validation, privacy review, and owner-approved public display rules.
Hours and service modes would need database-backed schedules, exception handling, and customer-facing closed states.
Delivery, catering, taxes, fees, payments, uploads, and fulfillment policies remain future scoped work, not demo behavior.
Customer flow pairing
Where this setup story connects
Pair this static setup preview with the menu, regular-customer preview, fake status route, and owner console to explain what a real production build would need before accepting orders or managing fulfillment.
