Answers before you ask.

Ownership is a one-time licence: you run the platform as your own asset with no per-booking share. SaaS is a subscription: we host, maintain and upgrade it, and you pay monthly or per booking. Custom development is a build to your specification, delivered to your repository as your IP. The engagement models page compares cost, timeline, hosting and roadmap control side by side.

Yes, and many agencies do exactly that. You prove the market on subscription, then buy the licence once volume makes ownership cheaper than the per-booking share. Your data, configuration and agent base carry across — there is no rebuild and no migration weekend.

No. Start on Rezofy's consolidated content and switch to your own credentials whenever your contracts come through. Many agencies run both at once and let the rule engine decide which source to show for a given route or agent tier.

Three to seven working days from the moment you hand over test credentials and documentation. That covers search, booking, cancellation and refund, plus certification if the supplier requires it. Suppliers with long sandbox provisioning or mandatory certification cycles take longer, and we tell you which those are before you commit.

All of them. Currency, language, payment rails, tax rules and supplier content are configured per point of sale, so one instance can run an Indian B2B desk, a GCC consumer site and a European corporate portal at the same time. Right-to-left layouts, local tax formats and regional payment methods are part of the platform, not a customisation.

Yes. They share one supplier layer, one wallet and one back office, but each has its own front end, pricing rules and reports. A fare loaded once is available to all three channels at whatever price each is meant to see.

You load a seat block with sector-wise pricing and validity. It then sells through your agent portal, consumer site and apps without a GDS booking, and the system tracks utilisation, deadlines and unsold seats. You can restrict a block to selected agents or open it to every tier.

It reads your live booking data, so it can confirm a PNR, quote a date change, explain a refund status, capture a new enquiry, update a traveller's contact details, and offer add-ons such as seats, baggage or insurance. Anything outside its scope is transferred to a human with the transcript and booking already on screen.

Yes. We set up your WhatsApp Business account, get your message templates approved, apply for the verified badge, and connect the number to your booking data so replies carry real availability and real ticket documents.

They are. The apps carry your name, icon and design, and go live on the App Store and Play Store under your developer account. We handle the build, the submission and any review responses.

Agent ledgers, receipts, credit notes, supplier and bank reconciliation, and tax-compliant invoicing with your own numbering series are all built in. Data exports to Tally and other accounting systems, and tax behaviour is configured per jurisdiction rather than hard-coded for one country.

A standard SaaS configuration goes live in 24 hours. Ownership deployments take two to six weeks depending on where they are hosted. Custom development is set by scope, with phased releases usually starting around week six. Each supplier API adds three to seven working days, run in parallel rather than in sequence.

It depends on the model and your product mix. Ownership is a one-time licence with optional maintenance; SaaS is monthly or per booking; custom development is quoted against scope. Tell us your volumes and the markets you sell in, and you will get a written quote — not a callback loop.

Yes. You can run real searches and test bookings on your own routes before any money changes hands, so the evaluation is done on your fares and your agent structure rather than on a demo dataset.