Pricing Screen (Preisgestaltung)

Context: Extracted from costing-pricing-separation ADR §4 — UI/UX safeguards. App: Workspace (Dispatcher/Planner) Entity: PriceMatrix (Backoffice) → TourOfferingPrice (Commerce read-model)

---

Design Principle

Opinionated defaults with progressive disclosure. The interface prevents cognitive overload by hiding complexity until the operator needs it.

---

Screen Layout

Read-Only Base View

The default view displays a single, read-only grid showing the Base Price Calculation (Level 1) for each variant combination (room type × age bracket).

• Prices derive from the linked CostingSheet + margin_config
• The grid is read-only by default — the operator sees what the engine calculated
• The system hides complex channel and algorithmic rules behind toggles

Manual Override Mode

Toggled explicitly. Allows the operator to override individual cells (Level 4: "Dispatcher's Veto").

• Overridden cells are visually highlighted (e.g., colored border, icon badge)
• Each overridden cell shows a "Revert to calculated" action
• Manual overrides halt automated yield adjustments for that specific cell [planned — Phase 2]

---

Micro-Views & Widgets

Margin Inspector (Popover)

A popover on individual grid cells showing the full derivation stack:

Layer	Value	Source
Base cost (from CostingSheet)	€85.00	CostingSheet.total_net_cost ÷ pax
+ Margin (18% hotel)	€15.30	PriceMatrix.margin_config
= Net selling price	€100.30
+ Tax (19% standard / margin scheme)	€19.06	CostingSheet.tax_strategy
= Gross selling price	€119.36	PriceMatrix.target_gross_price
Manual override	€109.00 ⚠️	Dispatcher
Resulting margin	-€10.36 below target	⚠️ Warning

Blended Tour Summary (Persistent Widget)

A macro-view widget visible at all times on the pricing screen:

• Total projected revenue based on the currently active PriceMatrix × expected pax
• Dynamic break-even PAX gauge — visual indicator of how many passengers are needed at current prices
• Margin health indicator — overall margin percentage vs. planned target
• Updates live as the operator changes prices

---

Alerts & Safeguards

Stale Override Alerts

When the system recalculates a CostingSheet (e.g., fuel spikes):

1. System scans all linked PriceMatrix entries for active manual overrides
2. If a cost increase drops the override's margin below the configured threshold → flag the cell
3. Dispatcher receives an alert for mandatory review
4. Alert persists until the dispatcher either updates the price or explicitly confirms the override

Publish Guards

Before a PriceMatrix transitions DRAFT → PUBLISHED:

• All variants must have valid gross prices (no zero/negative)
• Break-even PAX must be achievable at the configured capacity
• The user must resolve any stale-override alerts