A B2B marketplace for tour operators, charter consolidators and DMC networks selling chartered-flight allotments and fixed-departure tour packages. Manage allocations, expiry rules, releases, group bookings and per-supplier reports - everything you need to monetise pre-purchased seat blocks and pre-configured tour packages without manual chasing.
Chartered Flights & Fixed Departure Marketplace sits at the intersection of supplier connectivity, distribution and the operational tools your team actually uses every day. A B2B marketplace for tour operators, charter consolidators and DMC networks selling chartered-flight allotments and fixed-departure tour packages. Manage allocations, expiry rules, releases, group bookings and per-supplier reports - everything you need to monetise pre-purchased seat blocks and pre-configured tour packages without manual chasing.
adivaha® powers more than 2,400 travel brands across 120+ countries, with engineering teams in India and Europe and 200+ pre-integrated supplier connections. We are an Amadeus Global CAP Licence holder and ISO 9001:2015 certified. The platform you read about on this page sits inside the same connected core that powers booking engines, agent portals, mobile apps, gift cards, loyalty programs and AI automations across every product line we ship.
This page is part of adivaha®’s broader travel-tech catalogue covering flights, hotels, holiday packages, transfers, activities, gift cards, loyalty, corporate travel, mobile apps and AI automations. Customers typically start with one product and layer on the rest as they grow - everything sits on the same supplier pool, the same payment rails, the same customer wallet and the same audit log so adding a new module never means a re-platform.
The platform is built for the operational reality of travel - cancellations, refunds, credit shells, supplier reconfirmations, multi-currency settlement, GST on commission vs principal sales, ADM/ACM handling - all of it modelled as first-class concepts. Generic accounting tools and SaaS platforms weren’t built for these flows. We were. Customers tell us this is the single biggest reason their finance and operations teams stop fighting the platform and start using it.
Most adivaha® customers go from contract to first production booking in 2-3 weeks. The path is short because the hard parts are already done: supplier credentials are pre-provisioned, the booking flow is tested end-to-end, payment gateways are integrated, and the white-label theming sits behind a config flag. Your team focuses on the parts that are actually unique to your business - brand, audience, market positioning, supplier contracts - instead of rebuilding a booking engine from scratch.
Beyond the speed-to-launch advantage, customers stay on adivaha® because the platform compounds. Every supplier we add, every payment rail we wire in, every AI capability we ship lands automatically for everyone on the platform - not as a paid upgrade, not behind an enterprise tier. The roadmap moves the entire customer base forward together. That’s how a small agency in 2023 ends up with the same supplier coverage as a multi-country OTA in 2026 without ever touching the integration code themselves.
The architecture, the integration approach and the operational model behind every production deployment.
A 200+ supplier pool sits behind a single, normalised contract. Search results stream back from parallel calls so users see partial results immediately rather than waiting for the slowest provider. When a supplier ships a breaking change - an NDC update, a rate-plan reorganisation, a deprecated endpoint - we absorb it in our adapter layer so your code never has to.
Your domain, logo, colours and store-listing copy are wired in by our delivery team. The white-label storefront ships in 2-3 weeks for most customers. Custom UI work or unusual payment requirements may extend the timeline, but we’ll be upfront about exactly what changes the schedule.
Run a customer-facing site and a B2B agent portal from one platform with role-based access, separate fare displays for retail and trade, KYC for sub-agents, commission tiers and credit-shell management. Markups apply per supplier, per product, per agent, per market - with stacking rules and override priority.
Cards, UPI, wallets, BNPL and FX flow through the same checkout. adivaha Pay reconciles transactions automatically against bookings; one escrow covers every supplier so the customer payment, your markup and the supplier cost are tracked in a single ledger. UPI integration ships out of the box for Indian markets.
Conversational booking assistants, support auto-resolution, invoice generation and anomaly alerts run on top of adivaha AI. Every AI action that touches money, contracts or customers waits for human sign-off, and every action is logged with full audit trail. PII is redacted at the edge before reaching any LLM.
Native mobile apps on iOS and Android share the same backend. Public REST APIs expose everything the storefront uses, with OpenAPI 3.1 specs, Postman collections, SDKs in five languages and HMAC-signed webhooks for booking and refund events.
The features that look small on a demo but compound into real margin advantage when you’re running production traffic month after month.
API contracts stay supported for at least 12 months after the next major version ships. Suppliers churn, regulations change, but your code keeps working.
Why it matters: Without this you’d be paying engineering or operations cost every month to do the same work manually - a hidden tax that grows with your booking volume. The platform absorbs that cost so your team doesn’t have to.
Logs, traces, latency, error rates and rate-limit usage available per API key, per environment. No more guessing why a request failed yesterday.
Why it matters: This is the kind of feature most platforms charge as an enterprise add-on. It ships standard with adivaha® because it’s how a real travel business actually operates.
Sandbox keys issued within 24 hours with realistic test data. Same code as production so what you build there works in production unchanged.
Why it matters: Customers who lean on this consistently outperform peers on conversion, supplier mix and reconciliation accuracy. The compounding shows up in margin within a quarter or two.
When one supplier goes down, results from the rest still show. No blank pages for your sellers, no lost conversions during a Sabre outage.
Why it matters: It’s built around an open contract, so you can extend it without waiting for a vendor release cycle. When your business shifts, the platform shifts with you.
No hidden fees, no surprise overage charges, no per-API-call billing that turns a quiet month into a budget conversation. Pricing is published.
Why it matters: The audit trail and rollback story make it safe to use even on money-affecting flows. Compliance teams love it; finance teams stop double-checking exports.
Every AI action that touches money, contracts or customers waits for human sign-off. Full audit trail of who approved what, when and why.
Why it matters: It scales linearly with traffic - no surprise re-architecture when you 10x volume. The same API call that works at 100 RPS works at 1000 RPS.
Specialist coverage for the verticals where adivaha customers operate today, from inbound DMCs to corporate self-booking tools.
GDS, NDC and LCC content unified into one normalised search response. Sub-second median latency, smart caching and parallel calls so the slowest supplier doesn’t bottleneck checkout.
Aggregate API hotel inventory with your contracted properties through the mapping engine. Duplicates collapse, cheapest rate wins, your markups apply automatically.
Airport, intercity and chauffeur transfers with vehicle/driver allocation and a live ops console for day-of dispatch. Bookable inline with hotel or flight reservations.
Curated tours, attractions, day trips and tickets with QR voucher fulfilment. Sell standalone or bundled into dynamic packages.
Earn-and-burn points engine with tiers, expiry rules, multiplier campaigns and a built-in reward catalogue across travel and retail.
Native iOS and Android apps with biometric login, Apple/Google Pay, push notifications and offline itineraries. One backend powers web and mobile.
The same proven path we’ve walked with thousands of customers. Most go from signed contract to first revenue in 14-21 days.
A 30-60 minute call to understand your travel business, target markets and supplier preferences. We map your roadmap to our modules and produce a clean scope document - including any custom work and where it’ll add weeks to the timeline.
You receive sandbox API keys within one business day. The sandbox runs on the same code as production with realistic test data, so what your team builds and tests there will work the same way in production.
Domain, logo, colours, store-listing copy, payment gateway, currencies and supplier credentials all get wired in by our delivery team. Customers can have engineers integrating in parallel while branding work continues.
UAT sign-off, soft launch with a few sub-agents or a limited audience, then full release. Your dedicated success manager stays with you for 30 days post-launch to handle the edge cases that only appear under real traffic.
Standard support takes over with success-manager access on demand. Monthly platform releases land automatically. As your traffic grows you layer in additional modules - AI agents, mobile apps, payments - on the same connected core.
Every airline, hotel chain, bedbank and aggregator has its own contract format, response shape and breaking-change cadence. That’s a problem you don’t want to solve twice.
Travel distribution is one of the most fragmented technical landscapes in commerce. There are dozens of GDS systems, hundreds of NDC-enabled airlines, thousands of hotel bedbanks and direct-connect partners, and each one ships its own data shape, error envelope and authentication model. Building against any single one is manageable. Building against twenty of them in parallel, while keeping a normalised search response on your storefront, becomes a continuous engineering burden.
And the burden never ends. Suppliers ship breaking changes regularly. Rate-plan structures get reorganised. Endpoints get deprecated. Authentication schemes migrate. Each change requires a coordinated update across your search, hold, ticketing, voucher and reconciliation flows. Without a dedicated team, this work piles up as silent technical debt - visible only when a supplier outage causes a missed conversion or a refund miscalculation triggers a customer dispute.
The cost compounds in another way too. Even when individual supplier integrations work, the user-facing experience suffers when each supplier returns slightly different room categories, slightly different cancellation policies, slightly different fare-rule wording. Customers get confused. Conversion drops. Support tickets pile up. Your team spends time normalising data across suppliers instead of building features that actually move revenue.
adivaha® absorbs the supplier fragmentation problem at the platform level. Every integration sits behind a unified contract with normalised room types, cancellation rules, fare families and error envelopes. When a supplier ships a breaking change, our adapter layer handles it - your code never breaks. When a new supplier becomes available, all our customers get access on the same day. This is what fifteen years of focused engineering on the supplier-abstraction problem looks like in production.
Three deployment patterns we see most often - pick the one that fits your business and adapt as you scale.
One product, one currency, one supplier mix per category. Branded portal on your own domain. Sandbox for testing, production for live. Most solo agencies start here, ship in 2-3 weeks and process their first few hundred bookings within the first month.
B2C site plus B2B sub-agent portal sharing one supplier pool. Dynamic markups per agent group, credit limits, KYC, agent reports and per-agent statements. Multi-currency for cross-border markets.
Multi-tenant deployment with regional branches, local payment rails, language packs and per-market fare displays. Consolidated reporting at HQ rolls up everything automatically.
The point of these patterns isn’t to box you in - it’s the opposite. Customers move between them as their business shifts. We’ve had a Starter customer become an Enterprise customer in 18 months without ever changing platforms. The deployment model is fluid because the underlying platform is the same; you’re only ever toggling configuration, never re-platforming.
The platform sits on a foundation of independent certifications and partnership credentials - the kind that show up on procurement checklists at mid-cap and enterprise customers.
adivaha® is an Amadeus Global CAP Licence holder, the highest tier of integration partnership Amadeus offers. That gives us direct PCC provisioning rights, full API coverage including NDC, and the ability to onboard your IATA agency to fresh Amadeus content rather than waiting through a consolidator. We’re recognised as an integration partner across all the major distribution stacks - Amadeus, Sabre, Travelport, Hotelbeds, Expedia and many more.
On the quality and security side, the platform is ISO 9001:2015 certified for quality management of platform development and customer delivery, follows OWASP guidelines for application-level security, and runs third-party penetration tests annually. Customer data is isolated per tenant with strong row-level security at the database. Payment data flows through PCI-compliant tokenization layers, never touching our infrastructure in raw form. Webhook payloads are HMAC-signed so receivers can verify authenticity.
On the operational side, we commit to a 99.9% monthly uptime SLA for paid plans, with credit-back guarantees on enterprise contracts. Our support response times are SLA-backed for paid plans and Slack-channel access is included for enterprise customers. The platform processes over 50 million API calls per month at sub-second median latency, with the metrics observable per API key in your dashboard.
The reasons customers consistently cite when we ask why they picked us over the alternatives.
1. Travel-specific by design, not retrofitted. Generic SaaS doesn’t know what an ADM is or how a credit shell works. We’ve been building exclusively for travel for fifteen years, and the platform reflects that - ticketing, refunds, reconfirmations, supplier statements, multi-currency settlements, GST handling are all first-class concepts, not afterthoughts patched on top of an e-commerce engine.
2. Stable contracts, evolving features. Our API versions stay supported for at least 12 months after the next major version ships. Suppliers churn, regulations change, but your code keeps working. Non-breaking improvements land in your current version with release notes - no surprise upgrades, no “you must migrate by next quarter” emails.
3. One backend, every surface. The same engine across web, mobile app, agent portal and partner APIs. Same login, same wallet, same loyalty balance, same support thread. Customers move freely across surfaces and your team works in one place - no parallel inventory to maintain, no silos to bridge.
4. Live in days, not months. Most launches ship in 2-3 weeks. We’ve made the slow parts fast through repeatable templates, pre-integrated suppliers and a 24-hour sandbox provisioning policy. Speed-to-launch isn’t marketing - it’s a competitive advantage that lets you test markets, validate ideas and capture seasonal demand windows that slower competitors miss.
5. Transparent pricing, no surprises. Pricing is published on the site. Sandboxes are free. The move from sandbox to production is a permission flip rather than a contract negotiation. We don’t play games with hidden fees, surprise overage charges or per-API-call billing.
Series fares (also called allotments, group fares or block-seat inventory) are pre-purchased flight seats that tour operators buy in bulk from airlines at a discount, then resell. They're common on leisure routes - Bangkok, Bali, Dubai, Maldives, European cities - where tour operators commit upfront for hundreds of seats and need to fill them through agent networks.
Fixed-departure tours are similar: a tour operator pre-builds a complete itinerary (flight + hotel + transfers + activities) for specific dates, then sells those exact dates to retail agencies and direct customers. They're the backbone of group leisure - honeymoon packages, religious tours, school trips, senior tours.
Generic GDS or hotel APIs don't handle series fares well. You need allotment management, hold-and-release rules, expiry logic, group-rate handling and a B2B marketplace where retail agents can discover and book what you've loaded. adivaha® gives you that purpose-built platform.
Per-flight, per-class allocations with hold-and-release rules and seat block tracking.
Sell pre-configured tour packages with set dates, capacity and tiered pricing per category.
Auto-release unsold inventory N days before departure to avoid commitment loss.
Retail agents discover and book your allotments via the platform with built-in CRM.
Track sell-through, revenue, margin and remaining inventory per supplier and per route.
Group rates and group seat blocks with separate confirmation flows for 10+ pax.
Auto-alerts when allotments are nearing release deadlines so you can push pricing.
Dynamic pricing rules based on sell-through, time-to-departure and competitor data.
Different rates for retail agents, sub-agents, corporate clients and direct customers.
Whether you're a charter consolidator pre-buying flights or a tour operator running fixed-departure programmes, the platform fits.
Upload flight allotments, hotel blocks or pre-configured tour itineraries with dates, capacity and rates.
Configure release rules, payment terms, cancellation windows and tiered pricing per buyer type.
Push to retail-agent networks, your B2B portal and direct booking site simultaneously.
Monitor sell-through, push pricing on slow-moving inventory, release before expiry.
Chartered-flight operations follow a specific commercial pattern. A tour operator like SOTC, Thomas Cook India or Akbar Travels signs a charter agreement with an airline (typically a charter-specialist like Atlas Air or a leisure-route carrier like SpiceJet or Indigo) for guaranteed seat allocations on specific routes during specific seasons. For example: 200 seats per departure on Mumbai-Bangkok every Saturday from October to March - 26 weekly departures, 5,200 total seats. The operator pays the airline upfront for these seats at a deep discount (40-60% off published fares) in exchange for the volume commitment.
The operator now needs to fill these 5,200 seats across the 6-month season. Filling them through their own retail channel alone is hard - their direct customer base might absorb 30-40%; the rest needs to flow through other agencies. Pre-platform, this distribution was painful: the operator emailed inventory sheets to dozens of retail agencies, agencies emailed back enquiries, the operator manually confirmed seats over phone, agencies issued vouchers from the operator's ticketing pad. Errors, double-bookings, missed payments were endemic.
adivaha's Series Fares Marketplace digitises this entirely. The operator loads the 5,200 seats into the platform with per-week pricing, payment terms, cancellation windows and tier pricing (different rates for retail-agent partners vs sub-agents vs direct customers). Retail agencies log in, search available departures, book seats with their customer details, pay through their wallet, receive instant confirmation with PNR and ticket. The operator sees real-time sell-through dashboards showing fill rate per departure, agent performance, revenue per departure.
Pricing strategy becomes data-driven. Slow-moving departures (e.g., the December 15 flight at 30% sold 30 days out) trigger price drops or marketing pushes to retail-agent network. Fast-moving departures (the December 25 Christmas flight at 90% sold 60 days out) trigger price increases on remaining seats. The platform automates the yield-management decisions that operators previously made manually with spreadsheets.
For fixed-departure tour packages, the same dynamics apply. A tour operator selling a 7-day Europe tour with fixed departure dates (February 15, March 1, March 15, etc.) loads each departure with capacity (typically 30-50 pax per departure), per-pax pricing, single-supplement rates, payment schedule (e.g., 30% deposit, 50% at 60 days, balance at 30 days), cancellation policy. Retail agencies sell against this fixed inventory with named-pax confirmation; the platform manages the entire workflow from enquiry to confirmation to payment to voucher delivery.
For airline partners, allowing operators to digitise their charter sales increases overall sell-through. Operators with platform distribution typically achieve 85-95% sell-through on charter inventory vs 65-75% with manual distribution. The remaining unsold seats can be released to the airline's public inventory closer to departure, but starting from 90% sold is far better commercially than starting from 70% sold.
Religious and pilgrimage tour operations are the single largest use case for series-fares marketplaces. Hajj operators in Saudi Arabia, Umrah operators across Indonesia / Malaysia / India / Egypt / Pakistan, Char Dham operators in India (Yamunotri, Gangotri, Kedarnath, Badrinath circuits), Vaishno Devi specialists, Tirupati / Sabarimala operators, Buddhist circuit operators across Bodh Gaya / Sarnath / Lumbini - each runs structured fixed-departure programmes that fit perfectly into series-fares architecture.
The operational characteristics are specific. Religious tours typically run as fixed groups (50-200 pilgrims per departure) with named-pax registration far in advance (sometimes 6-12 months for Hajj). Documentation is intensive: passport copies, visa applications, vaccination certificates, identity proofs. Religious requirements affect logistics: gender-segregated accommodation in some operators, specific meal preparations, prayer-time considerations in routing, coordinated group movements at religious sites. Cancellation policies are strict (visa is non-refundable, religious-site permits are committed) and pricing is transparent (operators don't do dynamic pricing - the price published 6 months ago is the price the pilgrim pays).
adivaha's platform handles all of this with religious-tour-specific configurations. Document-collection workflows ensure all required papers are gathered before final ticket issue. Group-segregation rules apply to room allocation. Pre-departure briefings are scheduled and tracked. Visa-application workflows integrate with VFS Global, BLS International and other visa-processing partners. Payment schedules accommodate the typical pilgrim-payment cadence (initial deposit, partial payments over months, balance before departure). The result: religious operators can scale from 500-1000 annual pilgrims to 5000-15000 annual pilgrims using the same platform.
Industry data on chartered-flight and fixed-departure operations.
Pre-purchased flight inventory at fixed prices, typically for tour operators selling specific routes/dates. The operator buys the seats from the airline at a deep discount and resells them through retail agents. Common on leisure routes like Bangkok, Bali, Dubai and the Maldives.
You define seat blocks per flight, with hold rules (e.g., release unsold seats 7 days before departure). The platform manages it automatically - alerts you on slow-moving inventory, releases what won't sell, and reports on sell-through.
Yes - tier the same allotment to retail agents (lower rate), sub-agents (mid-tier) and direct customers (full retail). Pair with a <a href="/b2b-travel-booking-solution.html">B2B portal</a> for retail-agent distribution.
Yes - group rates with 10-50+ pax bookings, named-pax confirmation, special meal preferences and group payment workflows. Configurable group-fare rules per route.
Common use case - Hajj, Umrah, Char Dham, Vaishno Devi tour operators run fixed-departure programmes that fit perfectly. Group blocks, named-pax confirmation, document collection and visa workflows are all supported.
Yes - even though seats are pre-allocated, the actual ticket issue happens through your <a href="/amadeus-api-integration.html">Amadeus</a>, <a href="/sabre-api-integration.html">Sabre</a> or Travelport plate. The platform handles the allocation tracking and ticket-issuance trigger.
