Skip to content

Front-office screens

Status: Composition — no new primitive needed

A front-office screen — a hotel reception, a bank branch counter, a service desk — is where an operator works a queue of people through tasks with money involved. It needs everything at once: who is next, who am I serving, what step am I on, what do I sell, what do I charge, and are the automations behind it healthy.

Mateu covers this with a family of high-level components that compose into one dense screen; each is documented on its own page.

ConcernComponent
Work queue rail (arrivals / departures / in-house)Task queue
Context banner of the current guestEntity header
Check-in stepsWizard
Room assignmentResource grid
Upgrade offerOffer card
Priced extrasAdd-on picker
Side-effects checklist / incidentsStatus list
Pax registered N of MTask progress
Folio breakdown at check-outLedger
Method + chargePayment picker
Balance vs preauthorizationMeter
Stay-history KPIsStat
Automations healthProcess monitor
┌────────────┬─────────────────────────────────────────────┬──────────────┐
│ TaskQueue │ EntityHeader — María Fernández · PLATINUM │ StatusList │
│ Llegadas ├─────────────────────────────────────────────┤ 🌡 A/C ruido │
│ ▸ 1108 ● │ Wizard: Datos → Habitación → Extras → Firma │ 🔑 Grabar │
│ ▸ 1204 │ TaskProgress pax 1/4 [Añadir pax →] │ ✓ SES auto │
│ Salidas │ ResourceGrid 1201 1204★ 1206 1208 ├──────────────┤
│ ▸ 901 │ OfferCard Master Suite + € 65/noche │ Meter │
│ │ AddOnPicker 🍹 🅿 🕕 Añadidos: € 383 │ ████░ 69% │
│ ├─────────────────────────────────────────────┤ Stat · Stat │
│ │ Ledger € 1.710,50 · PaymentPicker [Cobrar] │ │
├────────────┴─────────────────────────────────────────────┴──────────────┤
│ ProcessMonitor ● Facturación a Crédito ⚠ 6 [Solucionar] · ● Comercial. │
└──────────────────────────────────────────────────────────────────────────┘

Arrange the panels with the usual layout primitives — @Zones for the columns, @Compact for density, @Section(sticky=true) to pin the queue or the header — exactly like a Workspace. The queue’s actionId loads the selected guest into the central panels (component communication handles the refresh); the wizard’s completion action confirms the check-in.

  • Preserve context — the guest banner and the queue never leave the screen
  • Minimize navigation — check-in, upsell and check-out happen without a page jump
  • Workflow over screens — every panel exists for a step of the operator’s job