Logotip AXO-8AXO-8

Own product · Transport · Custom systems

From booking to completed ride.

How we connected online booking, payment and local operations for a private transport service.

ELARO is an AXO-8 product. Its first pilot corridor connects Bangkok and Pattaya.

A passenger requests a ride. The local team checks availability, confirms the cost and assigns a driver. Each step depends on the right information reaching the right people. We built infrastructure to connect these steps in one process.

A booking is only the beginning.

A form can collect trip details. It cannot on its own confirm availability, establish who approves the cost, verify payment or determine who will drive.

The passenger needs a clear offer and booking information. The local team needs data to arrange the ride. Operations need to see what is confirmed, paid and assigned, and where an exception needs attention.

Starting point

One booking. Shared information. Clear next steps.

We designed the system around a shared booking record connecting the passenger, local partner and operations team.

What we built.

We connected the customer experience and the processes behind it in a platform for handling rides.

  • 01

    Website and booking

    Service and route information, a booking flow and a private page with trip details.

  • 02

    Availability and payments

    Support for checking an offer and taking payment. Payment status is updated from a verified payment event.

  • 03

    Operations and partners

    Interfaces for reviewing bookings, assigning drivers and vehicles, and handling exceptions. A driver can receive limited access to an individual trip.

  • 04

    Data and business rules

    Booking, availability, payment and fulfilment are connected through statuses and a history of important actions.

  • 05

    Notifications and access

    Notifications for important events, failed-delivery handling, role-based access and multifactor authentication for sensitive access.

How the pieces connect.

  1. The passenger submits trip details and the system creates a booking.
  2. The local team checks availability and cost, and handles an alternative if needed.
  3. The passenger pays; a verified payment event updates the booking.
  4. The partner assigns a driver and vehicle while operations monitor status and handle exceptions.

Automation carries information between steps. Availability and local execution decisions remain with the people responsible. The project includes internal security reviews; these are not an independent external security audit.

A foundation for growth.

ELARO can grow with the service: adding routes, local teams and partners when there is an operational need.

We start by understanding how a service needs to work in practice. Then we connect the customer experience, data and the team’s work.

Where does your process stop?

If customer, payment or delivery information gets lost between tools and messages, let’s look at what makes sense to connect.

Book a conversationAll projects