Price decisions
in context
UX and interface design for fuel pricing, connecting network signals with station-level comparisons, proposed changes and operating conditions.
- Design lead
- Lorenzo Rogante
- Design scope
- UX architecture · Interaction design · UI design
- Collaboration
- Management and development team
- Designed for
- Pricing analysts and network operators
Pricing decisions combine network priorities with local conditions. The design connects the overview to station detail while preserving the selected station and fuel, so the investigation can deepen without repeating the initial selection.
or explore the workspace
Key decisions
Overview into investigation
Network indicators lead into the stations and fuels behind the totals.
Comparable exposure
A station-by-fuel matrix combines values and labels with colour to support comparison.
Visible assumptions
Expected impact, missing inputs and price limits remain explicit before a proposal can be assessed.
Volume and revenue at risk
Exposure = daily volume × churn probability; revenue exposure also includes the current €/L price. Illustrative prioritisation, not a validated forecast.
Make the overview a starting point
Volume, margin and recent changes sit together in the dashboard, with a route into the stations behind the totals. Summary indicators support choosing an investigation rather than becoming an isolated report.
A price worth investigating
Current → Proposed · €/L · A synthetic estimate
Compare stations and fuels on a shared basis
The station-by-fuel matrix organises exposure across the network. Volume and revenue views use distinct units, with values and labels supporting the colour scale. Each cell leads into a specific station and fuel.
A price worth investigating
Current → Proposed · €/L · A synthetic estimate
Keep the selection as detail opens
Current price, proposed price and difference appear together. Station and fuel remain selected through the transition, preserving the context of the comparison.
A price worth investigating
Current → Proposed · €/L · A synthetic estimate
Expose the trade-off and missing inputs
A price increase can affect sales volume as well as margin per litre. The comparison shows both, including a synthetic unfavourable scenario and an example where missing cost data prevents an estimate.
Read the conditions
Current → Proposed · €/L · A synthetic estimate
Keep the market comparison available
Nearby competitor prices and recent movements sit alongside the proposal. The operator can inspect the local context before assessing a response. Locations and market records in this reconstruction are invented.
Read the conditions
Current → Proposed · €/L · A synthetic estimate
Make the operating limits explicit
Price limits, discounts, market references and approval settings remain close to the proposal. Conditions can be adjusted locally in this reconstruction; they do not update a real station.
Read the conditions
Manual approval · Price limits · Market reference
A proposal stays connected to its assumptions
This case study presents professional product design work. Interfaces have been recreated for the portfolio using synthetic records and generic names. Interactive sequences illustrate design decisions rather than record the original application. The figures are examples, not measured project outcomes.