Example: restaurant-pro

restaurant-pro is the canonical installable SDK application for hospitality (ADR-003): reservations, takeaway, menu, kitchen, floor plan, orders, payments, and a light CRM. Current package version: 1.10.3.

Scaffold vs reference

warehouse-pro is the CLI scaffold id (qefro create-app warehouse-pro). restaurant-pro is the reference vertical proving the same surface in production. Start with Build your first app unless you are studying this package.

widget / WhatsApp / staff UI
  → runtime → tool invoker → restaurant-pro /qefro
  → restaurant.* → ctx.storage.* → storage-service → MongoDB
  → ctx.customer (Customer Hub) · app.marketing · app.organization

connectors: [] — no POS pool dependency. The app is the connector for its own domain (hosting: managed, endpoint: http://restaurant-pro:8080).

What’s in 1.10.x

Area	Behavior
Booking bridge	Static form + booking_form_url; WhatsApp digits from workspace channel (?n=)
Time slots	Configurable service_start / service_end / slot_interval_minutes
Marketing	Audiences, Book Table CTA attribution (campaign_id / offer_id)
Organization	Opaque workflow capabilities for Internal Inbox
Pilot hardening (1.10.3)	No hardcoded booking fallback; optional seed_demo; ?brand=

Package layout

restaurant-pro/
├── manifest.yaml
├── src/                 # required SDK app (@qefro-ai/backend)
├── package.json
├── Dockerfile
├── assets/
├── booking/             # static WhatsApp bridge
├── onboarding/
├── workflows/           # optional — tool: restaurant-pro/restaurant.*
├── prompts/
└── ui/                  # optional — sources → restaurant-pro/restaurant.list*
    ├── theme.yaml
    ├── navigation.yaml
    ├── pages.yaml
    ├── layouts.yaml
    ├── widgets.yaml
    └── sources.yaml

Collections (via ctx.storage)

Logical	Purpose
reservations	guest, phone, covers, time, status, marketing attribution
tables	name, capacity, floor x/y, status
orders	order number, items, total, status (channel: takeaway)
menu_items	name, price, category, available
payments	amount, method, order_id, status
customers	name, phone, email, vip, visits, notes
offers	title, message, audience, status

Physical Mongo collections: restaurant_pro__{logical}.

Staff UI

Page	What you can do
Menu	Add / update dishes (forms → staff workflows → app tools)
Tables	Floor plan + add/update tables
Customers	List / VIP filter, upsert, queue offer
Orders	Readable dates, order number, totals
Offers	Platform campaign send + sent/failed counts

Portal: /app/solutions/ui/restaurant-pro/{page}
Subdomain: https://restaurant-pro.portal.qefro.com/…

Brand & booking settings

Installation settings overlay ui/theme.yaml and booking behavior:

Key	Type
business_name	string
booking_form_url	url
service_start / service_end	string (HH:MM)
slot_interval_minutes	number
logo_url	url
background_image_url	url
primary_color / secondary_color / accent_color / background_color	color
reservation_lead_time	number
seed_demo	boolean (optional onboarding seed)

Configure under Installed solutions → Configure. WhatsApp business digits come from the workspace channel, not install settings.

Workflow example — book a table

workflows/reservation.yaml (excerpt)

- id: create_reservation
  type: tool
  tool: restaurant-pro/restaurant.createReservation
  params:
    guest_name: "{{ variables.reservation_input.guest_name }}"
    phone: "{{ variables.reservation_input.phone }}"
    email: "{{ variables.reservation_input.email }}"
    covers: "{{ variables.reservation_input.covers }}"
    date: "{{ variables.reservation_input.date }}"
    time: "{{ variables.reservation_input.time }}"
    channel: "{{ variables.channel }}"

Staff flows (staff-reservation-create, staff-menu-create, …) call the same app tools so chat and the portal share one document plane.

Do not use

tool: storage/insert (or any storage/*) from workflows — deprecated.

ui/sources.yaml (excerpt)

ui/sources.yaml

- id: reservations
  type: connector
  target: restaurant-pro/restaurant.listReservations
  params:
    limit: 50
    sort:
      created_at: -1
- id: customers_vip
  type: connector
  target: restaurant-pro/restaurant.listCustomers
  params:
    filter:
      vip: true
    limit: 100

Own-app sources are gated on runtime.query. Do not target storage/find.

Local SDK app

cd restaurant-pro   # or platform docs/examples/restaurant-pro
npm install
export QEFRO_SIGNING_SECRET=dev-secret
export QEFRO_STORAGE_URL=http://localhost:8108   # optional if runtime injects platform.storage
npm run dev

Build, publish, install

qefro solution build .    # requires src/
qefro solution publish
qefro solution install restaurant-pro
# upgrade: POST /installations/restaurant-pro/upgrade
#   { "target_version": "1.10.3" }  (+ workspace_id)

Source of truth in the platform repo: docs/examples/restaurant-pro/.

Related topics

• Build your first app — primary third-party path
• Managed apps
• Marketing
• Organization workflows
• Customer Hub
• Managed storage