A complete back-office for excursion operators, DMCs and tour aggregators - tour scheduling with time slots, guide assignment in 12+ languages, group sizes and group pricing, pickup-point logistics, branded e-vouchers and supplier inventory. Pair with the Tours Marketplace for distribution to retail agents and OTAs.
Excursion Extranet Software sits at the intersection of supplier connectivity, distribution and the operational tools your team actually uses every day. A complete back-office for excursion operators, DMCs and tour aggregators - tour scheduling with time slots, guide assignment in 12+ languages, group sizes and group pricing, pickup-point logistics, branded e-vouchers and supplier inventory. Pair with the Tours Marketplace for distribution to retail agents and OTAs.
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.
Aggregated tours, attractions and experiences with availability calendars and instant confirmation. Whether you sell direct to consumers, run a B2B sub-agent network or distribute to OTA partners through APIs, this product slots into the same booking, payments, fulfilment and reporting stack that powers every other adivaha customer.
Run your own supplier extranet so hotels, transfer operators or tour providers load their own inventory and pricing. 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 rather than afterthoughts. That’s the difference between travel-tech that scales and a generic SaaS product retrofitted for travel.
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.
Viator, GetYourGuide, Musement and Bridgify in one API with best-rate selection.
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.
Per-day, per-time-slot availability with cut-off rules from operators.
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.
Stitch multi-day tours and add-ons into a single PNR.
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.
QR-coded vouchers with your logo and booking reference.
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.
Suppliers manage rooms, rates, calendars and stop-sells themselves.
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.
Map your inventory out to OTAs and metasearch.
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.
A clear hand-off model so your team knows exactly what happens at every phase - no surprise dependencies, no vendor-side mystery work.
We map your existing flows, supplier preferences, payment requirements and target markets. The output is a scoped delivery plan with explicit timelines, deliverables and ownership boundaries between your team and ours.
Sandbox keys, API documentation access, supplier credential requests and payment gateway onboarding all kick off in parallel. Your engineering team can start building integrations immediately.
Branding, UI customisation, currency setup, tax rules, markup rules, agent tiers and policy enforcement get wired in. Most of the customer-visible work lands here.
End-to-end testing on real supplier sandboxes, payment flow validation, edge-case handling and a controlled soft launch. We catch the issues that only show up under real traffic.
Full launch, dedicated success-manager access for 30 days, then standard support. New APIs, AI capabilities and supplier integrations land automatically as we ship them - no migration projects.
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.
Direct partnerships with the GDS systems, hotel bedbanks and payment networks that handle the majority of travel transactions globally.
Our partnership network is the foundation of the platform. We hold an Amadeus Global CAP Licence with direct PCC provisioning, are recognised as an integration partner with Sabre and Travelport, and ship pre-integrated connections to Hotelbeds, Expedia, Agoda, RateHawk, GRN, Bridgify and dozens more bedbanks. Customers benefit from these relationships from Day 1 - no separate supplier negotiations, no waiting in line for credentials.
On the quality side, the platform carries an ISO 9001:2015 certification covering both platform development and customer delivery processes. Application security follows OWASP standards with annual third-party penetration testing. Payment processing flows through PCI-compliant tokenisation. Webhook payloads carry HMAC signatures. SSO and granular role-based access control are available on enterprise plans.
Operationally we commit to a 99.9% monthly uptime SLA for paid plans, with credit-back guarantees on enterprise contracts and Slack-channel access for direct support. The platform processes 50 million+ API calls per month at sub-second median latency, with per-key observability surfaced in every customer’s dashboard. None of these credentials are unusual by enterprise SaaS standards - but they’re relatively rare in travel-tech, and that’s exactly the point.
The platform-level choices that look small at evaluation time and pay back over years of running production traffic.
1. A normalised search response across every supplier. Whether the result comes from Amadeus, Sabre, an LCC partner or a hotel bedbank, your storefront sees the same shape. No supplier-specific code paths in your app, no edge cases you discover only when a new supplier ships a different format.
2. Idempotent booking confirmations from Day 1. Double-clicks, network retries and webhook redelivery never create duplicate tickets. Booking IDs are deterministic on the server. Your reconciliation always matches your customer-facing confirmations - even when something glitches mid-transaction.
3. Audit logs on every change, attributable to a user or token. Compliance teams stop asking for special exports. Disputes get resolved with the actual record of what happened. The audit log is part of the platform, not a paid add-on bolted on for enterprise customers.
4. Webhook delivery with retries, signatures and dead-letter queue. When your endpoint goes down, our retries don’t lose events. When you finally come back online, we replay the queue. HMAC signatures let you verify every payload is genuine before processing.
5. Sandbox identical to production at the code level. Not a stripped-down preview environment. Same code, same logic, same edge-case behaviour - only with test supplier credentials and isolated payment routing. What you build in sandbox works in production unchanged.
Tours, activities and excursions ("TAE" in industry parlance) carry margins of 25-40% - significantly higher than flights (1-2%) or hotels (10-15%). They're also the bookings travellers regret missing: a guest who books a hotel still wants city tours, food walks, snorkelling, museum tickets, sunset cruises and cooking classes. If your portal doesn't sell those, someone else captures the wallet share.
But excursion ops are uniquely complex. Time slots vary by tour. Guides are assigned per language. Group sizes have hard caps. Pickup points scatter across cities. Cancellation rules are stricter than hotels. And the inventory is a mix of your own contracted tours plus aggregator inventory (Bridgify, Hotelbeds Activities, GetYourGuide).
adivaha® Excursion Extranet handles all of it: time-slotted tours, multi-language guide assignment, group caps, pickup logistics, branded vouchers, automatic OTA distribution and a marketplace layer for tour aggregators reselling third-party content.
Time-slotted tours with per-slot capacity, cut-off times, waitlists and minimum-pax thresholds.
Per-tour guide assignment with multi-language support and guide profiles for customers.
Group caps and per-group pricing with separate confirmation paths and named-pax handling.
Multiple pickup options with map integration, geofencing and driver dispatch.
Branded e-vouchers with QR check-in, supplier policies and supplier contact info.
Push to tours marketplace and aggregators automatically.
Guides scan QR codes from a mobile app for fast on-site check-in.
Rich tour photo galleries to drive conversion on listing pages.
Aggregated review system with response workflow for operators.
Whether you operate your own tours, aggregate from third-party suppliers, or both - the platform handles it.
Load tour catalog with descriptions, photos, pricing tiers, time slots and capacities.
Add guides with languages and qualifications; configure pickup points with maps.
Push to marketplace, your own portal and aggregator OTAs.
Live booking, mobile check-in, voucher delivery, post-tour reviews and reporting.
Excursion operations have unique daily-operation challenges that distinguish them from hotels or flights. A tour scheduled for 9am needs guests confirmed by 8:30, transferred to the meeting point by 8:45, briefed on safety and logistics, then started promptly. A late guest at 9:05 holds up the entire group. Multiply this by 5-15 tours per day, multiple guides, multiple languages, multiple pickup points, and you get a daily operational orchestration problem that's significantly harder than running a hotel front desk.
Weather and external factors compound the problem. A snorkelling tour in Bali might be cancelled at 7am due to rough seas, requiring 30-50 customer notifications and refund processing in under 2 hours. A walking tour in Rome might run into a transit strike, forcing route changes mid-tour. A theme-park tour might face unexpected ride closures. The platform must support these real-time operational adjustments without breaking customer trust.
Guide management is its own operational discipline. Most excursion operators have a mix of full-time guides, freelance guides and seasonal guides. Each has different language capabilities, area expertise (Vatican specialist, food-tour specialist, adventure-trek specialist), pay rates, availability windows and quality ratings. Matching the right guide to each tour, on each day, with the right pax mix, is a complex constraint-satisfaction problem. adivaha's platform handles the basics (language matching, availability, qualifications) and integrates with workforce-management tools for the more complex cases.
Quality control matters enormously. Tour reviews on TripAdvisor / Viator / Klook directly affect future bookings - one bad review out of ten kills the tour's rank. Operators need real-time review monitoring, quick-response workflows, post-tour customer follow-up to encourage 5-star reviews, and analytics to identify which guides / tours / time slots / customer types correlate with bad reviews. The platform builds all of this in: post-tour SMS / email automation, review-response workflow, per-guide-per-tour rating dashboards.
Local DMC (Destination Management Company) is the most common excursion model. A DMC operates in one or a few destinations (e.g., Bali Tourism Services running tours in Bali only) with their own guides, vehicles and supplier relationships. They sell to inbound travellers via aggregators (Viator, GetYourGuide, Klook) and direct via their own portal. Margins are healthy (25-40% gross) but acquisition cost is high. The DMC model works when the operator has deep local expertise and can deliver quality at scale.
Aggregator marketplace is the next-tier model. Operators like Viator (TripAdvisor), GetYourGuide and Klook aggregate tours from thousands of local DMCs and sell to travellers globally. Margins are lower (15-25% take-rate) but volume is enormous. The aggregator model works when you have technology + scale to support thousands of suppliers and millions of customers. Hard for small operators to enter, but adivaha's platform supports white-labelled mid-size aggregators in regional niches.
Niche specialist is the third model - operators focusing on a specific tour category (food tours, adventure tours, photography tours) and serving customers globally. Examples: Devour Tours (food, multiple cities), Cookly (cooking classes globally), G Adventures (adventure travel). Margins are excellent (30-50%) when the niche is well-defined and the operator owns category leadership. This model works when the operator has a strong content / influencer / SEO presence to drive direct demand.
City walking tours with audio guides, structured routes and group leaders.
Food tours, cooking classes, brewery / winery visits, market tours.
Trekking, scuba, rock climbing, paragliding, white-water rafting.
Museum tours, heritage walks, archaeological sites, palace visits.
Disney, Universal, Six Flags, Legoland with skip-the-line tickets.
Pre-built day-trip itineraries (e.g., Pisa from Florence, Stonehenge from London).
Tours bundling transfers + activity (e.g., desert safari with hotel pickup).
2-7 day excursions with overnight stays (small-group adventures).
Boat tours, sailing, snorkelling, deep-sea fishing, jet-ski tours.
Industry data from Phocuswright, Skift and adivaha-customer averages.
Yes - tours can be offered in 12+ languages with separate guides per language. Each language can have its own description, gallery, time-slot capacity and guide profile. Common pattern: morning English tour at 9am, afternoon Spanish tour at 2pm, both for the same product.
Multiple pickup points with maps and geofencing; can integrate with <a href="transfers-extranet-software.html">transfer software</a> for door-to-door pickup. Driver dispatch built in. Common pattern: bus pickup from 5 hotel locations with timed-route ordering.
Yes - aggregator mode pulls from <a href="Bridgify-API-Integration.html">Bridgify</a>, Hotelbeds Activities, GetYourGuide Connect, Klook B2B, TourRadar and others. Apply mark-ups and resell to retail agents or direct customers. Pre-built supplier connections, just turn on what you need.
Group caps per tour with named-pax confirmation, group rates, special meal preferences and consolidated voucher delivery. Separate confirmation flow for groups of 8+ pax. Group leaders get manifest with all guests, dietary requirements and special needs.
Yes - each tour can have multiple time slots per day, each with its own capacity, cut-off time and minimum-pax threshold. The system manages waitlists and auto-cancels under-booked slots if you configure it. Cut-off times typically 1-24 hours before tour start.
Yes - our guide app supports QR check-in, manifest viewing, customer messaging, on-tour photo uploads, completion reporting and rating-collection prompts. iOS and Android, works offline for tours in poor-signal areas.
Per-tour and per-supplier cancellation rules with automatic refund calculation. Customers see policies clearly at checkout. Refund disbursement is automatic via <a href="adivaha-pay.html">adivaha Pay</a>. Weather-clause cancellations supported (auto-refund for weather-cancelled tours).
Built-in review system with verified-booking-only reviews, photo uploads, structured ratings and operator-response workflow. Per-guide-per-tour analytics show which guides drive 5-star reviews vs which need coaching.
Yes - promotions, packages, flash sales and member-only deals supported. Common patterns: 24-hour flash sale on slow-moving slots, seasonal-package deals (Christmas tours), member-discount codes via your <a href="prepaid-gift-cards-and-loyality-program.html">loyalty program</a>.
Configurable per-guide payment rules: per-tour fixed rate, per-pax variable rate, hybrid base + per-pax. Auto-payments to guides on completed tours via <a href="adivaha-pay.html">adivaha Pay</a> or your finance system. Tax-document generation for freelance guides.
