Showing price where the buyer chooses the date
Some events on TicketMax charge different prices on different dates. An amusement park is the clearest case: a Tuesday and a Saturday cost different amounts, and for a family choosing when to go, that difference is often the deciding factor.
The date picker didn't show it.
The problem
The calendar showed day numbers on grey squares. Buyers picked a date, and only then found out what it cost. To compare two dates, they had to select one, read the price, go back, select another, and hold both numbers in their head.
The information the buyer needed to decide existed in the system. It just wasn't at the point of the decision.
What I changed
Each date now carries its price. A marker highlights the lowest-price dates, with a legend explaining what the marker and the selected state mean, so the cheapest options are findable at a glance rather than through comparison.
The panel states that more than one date can be bought in a single order, which the previous layout left buyers to discover. Below the calendar, an empty state says what happens next — choose a date to see the tickets — instead of showing an empty area, and checkout stays disabled with an explicit reason until there is something in the cart.
This is a producer-side option, not a default. Showing prices in the calendar only helps when prices actually vary; for a single-price event it's noise. So producers turn it on for their event. That decision connects to the event creation flow, where producers also choose how buyers pick a date at all — date buttons for a handful of dates, a monthly calendar for many, or grouping by weekday for recurring events.
Designing both sides of that meant treating the producer's configuration and the buyer's experience as one system rather than two screens.
Where it stands
Live on the platform since July 2026.