Beispiel

Complete procedure: a guest-facing procedure that builds an order and takes payment before confirmation or sync.

Goal: One coherent purchase path — shared payment core for occupancy and menu flows.

Typical step order

1. Guest / time / elements context — as in booking-classic-occupancy, or skip occupancy for booking-menu-checkout.
2. Build the order
   • Position hinzufügen (AddPositionToOrder) — configured orderables; quantities usually FromOtherParameter.
   • Von Menü bestellen (OrderFromMenu) — guest-picked SKUs.
3. Online-Direktzahlung (PayNow) — checkout when gross total > 0; skipped when nothing is owed.
4. Persist / notify — Reservierung erstellen (SyncReservationEntry) / Bestellung erstellen (SyncOrderEntry) / Rechnung erstellen (SyncInvoiceEntry), then Gast via E-Mail informieren (InformGuestViaEmail) → Betreiber informieren (InformOperator).

Choosing order-building steps

Scenario	Prefer
Fixed or parameter-driven price list	Position hinzufügen (AddPositionToOrder)
Guest browses menu	Von Menü bestellen (OrderFromMenu)
Multi-night stay	Nächte-Position hinzufügen (AddNightsToOrder) before Online-Direktzahlung (PayNow)
Pay first, order more later	Online-Direktzahlung (PayNow) then Nachbestellungsmenü (ReOrderMenu) / Als Nachbestellung einreichen (SubmitAsReorder)

Related patterns: booking-classic-occupancy, booking-menu-checkout, booking-kiosk-tickets.

Testing split: Component guides for knobs; this pattern for chaining; Playwright for one E2E path; procedure-manager tests for Online-Direktzahlung (PayNow) edge cases.