Six package types. Three departure models. One platform.
How QUEST powers the full spectrum of FIT travel products.
Everything you need to know about QUEST FIT package configuration
Interactive matrix of all departure × pricing combinations
Anyday, Seasonal, and Fixed departure models compared
Single-price vs Service Level pricing modes
Bundle, PriceCategories, and Live component types
How multi-item availability drives effective capacity
Step-by-step setup guides and technical references
Every combination of departure model and pricing mode is fully supported. Click any cell to learn more.
Any-date flexibility with tiered pricing — letting guests upgrade accommodation class, cabin type, or experience level.
From fully flexible to tightly controlled — choose the departure model that fits each product.
Book any day
The most flexible departure model. Guests choose their own start date and the system prices dynamically from individual component costs. No fixed schedule or capacity cap at the package level.
Book within seasons
Availability defined by date ranges and day-of-week rules. Price seasons control rates across high, shoulder, and low periods. Combines structure with flexibility.
Book a specific departure
Named departures on specific dates with capacity tracking, status management, and booking eligibility controls. Purpose-built for premium, date-specific products.
The upcoming Seasonal Package Setup Guide will cover time period and price season configuration in detail.
Every package operates in one of two pricing modes. Service Levels unlock upsell opportunities and differentiated experiences.
Single pricing tier
One price point per package. All guests receive the same service level. The simplest configuration for products without tiered options.
Multi-tier pricing
Multiple pricing tiers (e.g., Standard Class, First Class, Premium) assigned to the package. Guests choose their tier and component prices adjust accordingly.
Every package is assembled from components. Each component type handles pricing and inventory differently.
City stays and grouped experiences
A container that groups a hotel stay with local activities and transfers into a single bookable unit. Bundles represent a destination segment of the journey.
Individual bookable items with structured pricing
A single supplier item priced through price categories — the most common component type. Covers activities, transfers, excursions, and similar services.
Dynamic pricing from external systems
Components priced in real-time from cached external data. Used when fares fluctuate based on demand, route, and booking date.
A typical package with 12 components across 4 destinations
Inventory is managed at the supplier item level, not the package level. Each item independently tracks per-date availability through allotment days.
A complex package may have 15+ items each with their own inventory. The effective availability for any date is the intersection of all items — the most constrained item becomes the bottleneck. Hotels, premium trains, and exclusive experiences typically drive the constraint.
A booking requires availability across all items. The most constrained item is the bottleneck.
Effective availability: 3 units — constrained by the Luxury Train Cabin
Step-by-step setup guides, troubleshooting playbooks, and technical references for every aspect of FIT package configuration.
The shared foundation for all package types — components, options, sort order, defaulting, categories, access rules, and package-level fields.
Managing content across packages and services — the Content Archive, content assignments, media, itinerary content, and departure variations.
How to clone packages, services, promotions, and discounts — what gets copied, what doesn't, and post-clone validation steps.
Configuring deposit rules, final balance schedules, dynamic deposits from supplier invoices, and per-passenger payment calculations.
How to configure component-level pricing for dynamic-date packages, including bundle construction, item assignment, and price category setup.
Departure lifecycle management — creating named departures, managing status transitions, capacity tracking, and component overrides per departure.
Setting up multi-tier pricing with service level assignments, configuring search API integration, and enabling upsell flows during booking.
Setting up cabin-category pricing for cruise and rail packages — creating cabin types, enabling Package Levels mode, and configuring per-room cabin selection in the Booking Wizard.
Creating time periods and day-of-week rules, configuring price seasons, and how seasonal packages interact with service levels. Covers the PackageSchedule and PriceSeason models.
How pre and post stay components work — allocation behaviour (PreNight/PostNight), shared inventory across rooms, inventory statuses, and per-night pricing during the booking wizard.
The foundation layer — creating items, defining price categories, configuring inventory seasons, managing allotment day availability, and setting stop sale controls.
Day-to-day inventory management — allotment setup, stop sale flags, release day tiers, reading availability statuses, and auditing allotment days across a large product portfolio.
Why packages don't appear in search results — service_level_ids filtering, inactive packages, departure status, date range mismatches, and inventory constraints.
How Kaptio Connect bridges external supplier systems into the packaging layer — rate loading, availability sync, and booking confirmation flows.
Net and sales price setup across all five sales price modes (Channel Markup, Package Markup, Fixed, Package Margin, Dynamic), price season configuration, markup chains, and how to verify margins are correct.
These guides are part of the QUEST enablement programme.
Contact your Kaptio delivery team for questions or feedback.