Let’s talk

Back to writing

Development

The part of online booking that the customer never sees

Working on Trailoka taught me to follow the booking all the way from the date picker to the owner’s calendar.

Trailoka’s old WordPress site helped travellers find tours. When somebody wanted to go, the owner worked out the dates and details with them over WhatsApp. When I worked on the online booking flow, it was easy to focus on the part you can see: a tour page, a date picker, and a confirmation.

Then I thought about what the owner sees the next morning. If a traveller books a Saturday hike and a Monday tour in one checkout, what does the owner need to plan? One order is useful for finding the customer and invoice. The two trips still need their own dates.

Follow the date through the system

I used WooCommerce for the order and kept the travel dates with the individual tour items. I also worked on the admin workflow for bookings and invoicing, reporting in Google Sheets, and a Google Calendar integration designed around the booked tour dates. The date the order was placed still matters for reporting. The travel date is the one the owner needs when planning the trip.

I’d test the ordinary booking first, then try two tours in one order and see what happens if a reporting or calendar request has to be sent again. Can the owner spot a missing entry? Does a retry create a duplicate? These are the questions I want to answer before calling the flow done.

A traveller wants to know their tour is booked. The owner wants to know what they need to prepare. I think the work is most useful when both can get their answer from the same booking.

Have something in mind?

Let’s talk.

Tell me what you’re building. Let’s find the right way to bring it to life.