Partners & suppliers
For the people who sign with us
This page is written for three readers: a supplier assessing an API access request, a travel agency considering running the platform, and anyone who needs to know exactly who contracts with whom before signing.
Two sides, stated plainly
Rahlio is not only a consumer site and not only an agency tool. These are two front ends onto one system, and they differ in exactly one respect: who sells.
For travellers — rahlio.com
Planning is open to anyone, no sign-up. The traveller describes the trip, receives three complete packages within budget, and sees where every price came from and when it was checked.
- A whole budget, not just flights and a hotel: food, transport, attractions and a contingency
- An itinerary checked for feasibility — travel times, opening hours, pace and weather
- Every price with its source, the time it was checked, and a stated confidence level
- Booking and payment take place with a licensed travel agency
For travel agencies — the portal
The agency connects its own supplier accounts and its own payment account, and gets an engine that prices, builds and books under its name and its licence.
- The agency is the Merchant of Record: payment settles into its account directly
- The contract, credit line and supplier invoicing all stay in the agency’s name
- Pricing, margin and cancellation policy are set by the agency and enforced by the system
- The agency’s terms are snapshotted onto every order that closes
The commercial model
What a supplier needs to confirm before granting production credentials: who the debtor is, who the merchant is, and who answers to the end customer.
The contract belongs to the agency
Rahlio does not seek a distribution contract in its own name for inventory it does not sell. Each agency enters its own contract credentials, and the system calls the supplier under them.
The supplier bills the agency directly
The supplier invoices the agency against the credit line or payment terms agreed between them. Rahlio does not intermediate payment to suppliers and does not aggregate billing.
Revenue from software, not from margin
Rahlio’s revenue is a platform fee charged to the agency, collected as an application fee on top of the agency’s own settlement. We do not earn on the spread against supplier rates.
Ranked by fit
Commercial compensation does not change display order. Packages are ranked by fit to the request and the budget, and any compensation is disclosed in the terms of use.
What the platform does
These are implemented and covered by tests. They are what a new integration rests on the day it is switched on.
The full booking lifecycle
Search, re-price before commitment, hold, book, status retrieval and cancellation — each step against the supplier’s API, not against a local inventory cache.
Idempotency and compensation
Every booking attempt carries a unique key, a retry never creates a second booking, and a late-stage failure automatically releases what was already held.
Prices that expire
A price is stored with its source and the time it was checked. Once stale, the system refuses to claim “within budget” and re-checks with the supplier before committing.
Resilient to supplier failure
Timeouts, rate limits and a single supplier failing do not bring a search down: the result is built from what responded, and suppliers that did not answer are shown to the user explicitly.
A complete audit trail
Every supplier call, price change and status transition is stored with a timestamp, so what was shown to a customer and when can be reconstructed exactly.
Tenant isolation
Supplier credentials belong to the agency that entered them, are stored encrypted, and do not cross between agencies on any read path.
Integration status
A current picture, by category. What is written here is what exists in the code — not what is planned.
| Category | What we need from the supplier | Status |
|---|---|---|
| Flights | Search, re-pricing, ticketing and cancellation over an API | Adapter written and test-covered — awaiting production credentials |
| Accommodation | Search, pre-booking availability check, booking and cancellation | Adapter written and test-covered — awaiting production credentials |
| Transfers | Route-based pricing and flight-linked booking | Being mapped — within the accommodation supplier’s scope |
| Activities & attractions | Catalogue, availability and sourced opening hours | Affiliate links today; direct booking to follow |
| Payments | A connected account per agency, with a platform fee | Implemented against Stripe Connect — awaiting account activation |
Flights
- What we need from the supplier
- Search, re-pricing, ticketing and cancellation over an API
- Status
- Adapter written and test-covered — awaiting production credentials
Accommodation
- What we need from the supplier
- Search, pre-booking availability check, booking and cancellation
- Status
- Adapter written and test-covered — awaiting production credentials
Transfers
- What we need from the supplier
- Route-based pricing and flight-linked booking
- Status
- Being mapped — within the accommodation supplier’s scope
Activities & attractions
- What we need from the supplier
- Catalogue, availability and sourced opening hours
- Status
- Affiliate links today; direct booking to follow
Payments
- What we need from the supplier
- A connected account per agency, with a platform fee
- Status
- Implemented against Stripe Connect — awaiting account activation
Adding a supplier is a catalogue entry, an adapter against the booking interface, and its registration — the agency’s connection screen builds itself from those. A further integration is therefore days of work, not a quarter.
Considering working with us?
Whether you are a supplier assessing an access request or an agency wanting to see the system, we are glad to answer due-diligence questions, supply integration detail and arrange a demonstration.
Talk to us