Do I need to support time zones in a booking flow?

Yes—if your booking flow can be used by people in more than one location, you should support time zones.

When you definitely need time zones

• Customers and staff are in different regions
• Bookings can be made across countries
• You show times to users in their local time
• You schedule future events where daylight saving time could change the actual clock time
• You send notifications/reminders that need to be correct for the recipient

When you might not need much timezone complexity

• Everything is strictly local to one city or one facility
• All users are in the same timezone
• Appointments are always tied to a single physical location

Even then, it’s still wise to store timestamps in a timezone-safe way.

Best practice

• Store times in UTC
• Also store the relevant timezone for the booking/location
• Display times in the user’s or location’s local timezone
• Be explicit in the UI:
  • “10:00 AM PT”
  • “10:00 AM local time”
• Handle daylight saving time carefully

Common pitfalls

• Assuming “3 PM” means the same everywhere
• Converting only on display but not when storing
• Ignoring DST, which can make a 1-hour difference
• Using the browser timezone when the booking should follow the venue’s timezone

Simple rule of thumb

If a user could reasonably ask “3 PM where?” then you need timezone support.

If you want, I can also help you decide the minimum timezone design for your booking system.