Skip to content
ELARO

ELARO × AXO-8 · Case study

The technology behind ELARO

ELARO helps travelers arrange private transfers in Thailand with a verified local transport partner. AXO-8 designed and built the digital systems connecting that customer experience to the people, decisions and records behind each journey.

The business challenge

A journey is more than a booking form.

A traveler needs clarity before paying. A local partner needs the right trip information, a way to confirm supply and room to coordinate drivers in an established workflow. ELARO needs a reliable record of what was requested, agreed, paid and delivered.

AXO-8’s task was to bring those needs together: a customer-facing service that stays understandable at the front, with the operational and financial controls needed behind it.

What AXO-8 built

One service, connected end to end.

01

A clear journey for travelers

AXO-8 built ELARO’s public website, route guides and campaign pages around the decisions a traveler needs to make before arrival. The booking experience gathers the journey, passenger and contact details needed to organize a transfer, while preserving acquisition information from the visit. A private booking page gives the customer a place to follow the request and see relevant trip information as it becomes available.

02

Booking, supply and payment in sequence

A request becomes a booking record with server-validated details and pricing. The local team can respond with availability or an alternative and a partner quote; the customer can then review the applicable terms and payment request. The payment integration verifies provider events before updating the booking, so a return from checkout alone does not stand in for payment confirmation. This connects the commercial promise to the operational work that follows.

03

A dependable record behind the service

The platform brings booking, supply, payment, fulfillment and financial information together in a shared database, with separate states and a history of consequential actions. Business rules run on the server and in the database, keeping prices, permissions and transitions consistent across customer and operational interfaces. That gives the team a common record when a journey needs attention, a change or reconciliation.

04

Tools for the people fulfilling the ride

AXO-8 built operational interfaces for ELARO and its local partner: a control tower for bookings and exceptions, and role-specific partner views for supply and dispatch. Once a booking is ready for dispatch, the local team can assign a driver and vehicle. A restricted trip link gives the assigned driver the information and actions needed for that job, while the partner can continue coordinating through its existing LINE workflow.

05

Communication and coordination

Notification workflows and a retryable delivery queue connect important booking events to customer and operational communications. A read-only operational sheet can present a partner-safe view of the queue, while the booking record remains authoritative. These integrations support the team’s work; availability decisions, exceptions and local coordination still require people.

06

Protection designed into the workflow

The system uses server-side validation, scoped access for operational roles, multi-factor authentication for sensitive staff access and private, limited-purpose links. Payment events are verified before they affect booking records, and significant actions are recorded for review. The project also includes documented internal security reviews and targeted remediation; these are not represented as an independent external certification.

07

A foundation for discovery and partnerships

Campaign pages and travel content connect discovery to the booking experience. Consent-aware analytics and acquisition attribution are designed to help ELARO understand the journey into a request. Partner referral links and QR materials provide another route into the same booking flow, preserving the source without turning a distribution partner into the transport operator.

How it works together

From request to the person at pickup.

The platform carries the record between stages and supports notifications and operational views. People confirm supply, resolve exceptions and coordinate the ride.

  1. 01

    Request

    A traveler shares the trip details through ELARO’s booking flow.

  2. 02

    Supply

    The local team checks availability and provides the relevant quote or alternative.

  3. 03

    Payment

    After the offer is ready, the traveler can pay; verified payment updates the booking.

  4. 04

    Coordination

    ELARO and the local team manage the confirmed journey and any exceptions.

  5. 05

    Driver

    The partner assigns a driver and vehicle, and the customer receives the relevant details.

The vision · What comes next

Built to grow with the business.

ELARO begins with private transfers and a local operating node, but the ambition is broader than a single route. As the business grows, the same foundations could support additional routes and local teams, a wider distribution network and a clearer view of operations across the service.

AXO-8’s role is to evolve that infrastructure alongside ELARO: connecting more of the experience before, during and after a ride, and developing the data, coordination and automation needed as real operational needs emerge. Each next step can be shaped by the people using the service and the partners delivering it.

(Knowing us, there probably won’t be a “maximum” — we’ll keep finding ways to go further, even if we don’t yet know what all of them look like.)

AXO-8’s role

Technology shaped around how a business works.

AXO-8 brought the digital experience, data, business rules and operational processes into a system designed for ELARO’s way of working. The work continues as the business develops: improving the connections that matter today and building the foundations for what comes next.

Discover AXO-8