When we started building Voyazio Book, we looked at the major itinerary tools on the market. They were all built for international travel patterns: one airport per city, predictable train schedules, hotels that confirm in seconds. None of them held up against the messiness of real Indian itineraries.
Edge cases that became core features
Two-airport cities
Mumbai has two operating terminals. Bengaluru has KIA. Delhi has T1, T2, and T3, with very different drive times. The itinerary has to know which terminal a flight uses and route ground transport accordingly. We model terminal as a first-class field, not a free-text note.
Festival blackout windows
Holi week in Pushkar, Diwali in Jaipur, Onam in Kochi — hotels go off-grid for confirmations, ground transport doubles in price overnight, and last-minute cancellations spike. Voyazio Book surfaces a soft warning on any itinerary that crosses a known festival blackout, with operator-specific notes.
Monsoon reroutes
The Konkan railway floods. Roads in the Western Ghats wash out. Coastal flights divert. We track historical reliability per route per month, and the builder nudges away from segments with sub-80% on-time records during monsoon.
Midnight train arrivals
Indian Railways routes a lot of long-distance trains to arrive between 1 AM and 4 AM. The hotel does not have a 24-hour check-in. The pickup driver has not been told the train number. Voyazio Book auto-flags any segment that lands in this window and prompts the operator to reconfirm late check-in or pre-pay one extra night.
What we learned
Every edge case above started as a complaint from an operator. We added it because they could not work without it. That is the only filter that ever matters in a product roadmap — does anyone actually need this, today.