Anyday Package Setup Guide

Overview

Anyday is the most flexible departure model in Kaptio. Unlike fixed or seasonal departures where guests choose from predetermined dates, an Anyday package lets the guest pick any start date within a valid range. Each component in the package is priced independently for the selected date, and the total price is the sum of all component prices.

This model is ideal for FIT (Fully Independent Travel) products such as city breaks, self-drive holidays, and multi-destination itineraries where there is no fixed group schedule. Because availability is checked per service rather than per package, Anyday packages can accommodate highly customizable trips without requiring batch inventory management at the package level.

This guide walks through the complete setup process: creating the package record, building the component structure, assigning services, configuring pricing, and validating that everything works end to end.

Prerequisites

Before configuring an Anyday package, ensure the following are in place:

• Business Unit and Sales Channel configured (Organization Structure Guide)
• Supplier accounts created for all hotels, activity providers, and transport operators you will reference
• Supplier services set up with relevant Price Categories, Price Seasons, and pricing (Supplier & Service Setup)
• Currency and tax configuration complete for the Business Unit (Currency & Tax Configuration)
• Service Levels defined (if you plan to offer multiple pricing tiers) (Service Level Configuration)
• Admin or Product Manager access in Kaptio

Note: For Anyday there is no capacity cap at the package level. Availability is On Request — each supplier is contacted to confirm availability at the time of request.

---

Part 1: Understanding the Anyday Model

How Anyday Pricing Works

In an Anyday package, there is no single package-level price. Instead, each component carries its own cost and sell price. When a guest selects a date:

1. The system checks availability for every service assigned to every component
2. Each service returns its price for the requested date (based on the active price season)
3. The component price is derived from its assigned services
4. The package total is the sum of all component prices

This means price can vary from day to day depending on seasonal pricing and supplier rate changes.

Key concept: The package is a container for components. The components hold the pricing logic. The package itself has no price field.

When to Use Anyday

Anyday is the right departure type when:

Criterion	Anyday Fit
Guests choose their own travel dates	Yes
No fixed group departures or set schedules	Yes
Products are multi-destination with independent segments	Yes
Pricing varies by date (seasonal rates)	Yes
You need per-component availability checking	Yes
Short getaways, city breaks, self-drive tours	Yes
High-volume FIT products with flexible dates	Yes

Anyday is not the right choice when you need fixed departure dates with group capacity (use Fixed), or when you sell a single bundled price that does not break down by component (use Seasonal with a flat price).

For a side-by-side comparison of all three departure types, see Three Ways to Sell Dates.

---

Part 2: Creating the Package Record

Step 1: Create the Package

Navigate to Packages in the Kaptio app and click New.

Set the following fields:

Field	Value	Notes
Record Type	Package	A Package that can contain multiple components including Bundles and Live components
Name	Descriptive package name	e.g., “Classic City Explorer”
Departure Type	Anyday	This cannot be changed after creation
Duration	Total trip duration in nights	e.g., 8
Categories	Package type category	e.g., “FIT”, “Self-Drive”

Important: The Departure Type field is locked after the package is saved. Double-check that “Anyday” is selected before saving.

Step 2: Configure Package Settings

After saving the package record, configure these additional settings:

Field	Description	Recommendation
Active	Makes the package available for search and booking	Leave unchecked until setup is complete
Visibility Setting	Controls which channels can see the package	Set to “Open” for all channels, or “Restricted” with Access Rules

Tip: Keep the package inactive (Active = false) while building components and configuring pricing. Activate it only after completing the validation checklist at the end of this guide.

Adding Service Levels (Optional)

If your package supports multiple pricing tiers (e.g., Standard, Superior, Luxury), you can assign Service Levels at the package level. Each Service Level maps to a different set of services within components, allowing the same package structure to offer different hotel grades or activity tiers.

Service Level setup is covered in detail in the Service Level Configuration guide. For a single-tier Anyday package, skip this step.

---

Part 3: Building the Component Structure

Understanding Component Types

An Anyday package is composed of components. Each component represents a segment of the trip. There are three component types:

Type	Purpose	Example
Bundle	Groups multiple services (hotel + activities + transfers) into a single bookable destination segment	”City A — 2 Night Stay”
Component	A single supplier service with structured pricing	”Guided Landmark Tour”, “Premium Transport”
Live	Real-time pricing from an external system (dynamic fares)	“Dynamic-Fare Transit”

A typical multi-destination Anyday package might look like this:

#	Component	Type
1	City A — 2 Night Stay	Bundle
2	Evening Entertainment	Component
3	Guided Landmark Tour	Component
4	Premium Transport to City B	Component
5	City B — 2 Night Stay	Bundle
6	Cultural Walking Tour	Component
7	Dynamic-Fare Transit to City C	Live
8	City C — 1 Night Stay	Bundle
9	Historic Site Excursion	Component
10	Dynamic-Fare Transit to City D	Live
11	City D — 3 Night Resort Stay	Bundle
12	Day Excursion	Component

Step 3: Create the Bundle

Bundles represent destination segments. Each bundle groups the accommodation and associated activities/transfers for one location.

Navigate to Components on the package record and click New.

Set the following fields:

Field	Value	Notes
Record Type	Bundle	A Bundle Component that can be added to Packages or sold independently
Name	Descriptive bundle name	e.g., “City A — 2 Night Stay”
Departure Type	Anyday	This cannot be changed after creation
Duration	Segment duration in nights	e.g., 2
Categories	Package type category	e.g., “FIT”, “Self-Drive”

Repeat for each destination segment in the itinerary. For the example above, you would create four Bundle components (City A, City B, City C, City D).

Tip: Use a consistent naming convention for bundles. Including the city/destination name and duration makes it easier to manage packages with many components.

Configure the Bundle

After saving the bundle, configure its settings:

Field	Description	Recommendation
Duration	Number of nights for this destination segment	Should match the accommodation stay length
Position	Controls display order in the itinerary	Use increments of 10 (10, 20, 30…) to leave room for insertions
Included	Whether this bundle is included by default	Set to checked for standard itinerary segments

Assign services to the bundle using Component Options — see Step 6 for details.

Adding Service Levels (Optional)

If your bundle supports multiple pricing tiers (e.g., Standard, Superior, Luxury), you can assign Service Levels at the bundle level. Each Service Level maps to a different set of services within the bundle, allowing the same bundle structure to offer different hotel grades or activity tiers.

Service Level setup is covered in detail in the Service Level Configuration guide. For a single-tier bundle, skip this step.

Step 4: Add Components

Components represent individual bookable services with structured pricing — activities, transfers, excursions, and similar services.

1. Click New Component on the bundle (or directly on the package for non-bundle components)
2. Set Component Type based on the Record Type (e.g., Accommodation for hotel)
3. Enter the Name (e.g., “Guided Landmark Tour”)
4. Set the Position to place it in the correct itinerary sequence
5. Set the Start Day to indicate which day of the trip this component falls on. For Accommodation, this is replaced by Check In and Check Out fields.
6. Save the component

Repeat for each standalone activity, transfer, or experience in the package.

Field	Description
Name	Descriptive activity or transfer name
Position	Sequence in the itinerary (integer)
Start Day	Which day of the trip (mandatory). For Accommodation: Check In and Check Out
Included	Whether this is included by default

Step 5: Add Live Components (Optional)

Live components pull real-time pricing from an external system (e.g., a flight or rail booking engine). They are used for segments where the price is not managed in Kaptio inventory.

1. Click New Component on the package
2. Set Component Type to Live
3. Enter the Name (e.g., “Dynamic-Fare Transit to City C”)
4. Configure the External Source settings as required by your integration
5. Set the Position for itinerary ordering
6. Save the component

Note: Live components require a working integration with the external pricing source. Coordinate with your technical team to ensure the integration is configured before adding Live components.

Component Ordering

The Position field on each component controls the display order in the itinerary. Components are rendered in ascending position order.

Best practices for position numbering:

• Use increments of 10 (10, 20, 30…) to leave room for insertions
• Bundle components typically anchor the major segments
• Place related components immediately after their parent bundle
• Live components slot in wherever the transit segment occurs

---

Part 4: Service Assignment and Pricing

Step 6: Assign Services to Components

Each component needs at least one service assigned to it. Services are the supplier offerings that fulfil the component (a specific hotel, a specific tour, a specific transfer route).

For each component:

1. Select New Component Option
2. Search for and select the Supplier
3. Search for and select the Service
4. Select the required Price Categories as well as Add-ons and Meal Plans if needed
5. If using Service Levels, assign the Price Category to the appropriate level

Important: Every component must have at least one service assigned. A component with no services will cause the package to show an error.

Step 7: Verify Component Pricing

Before activating the package, verify that each component returns a price for a sample date. For the full verification walkthrough — including the checklist, example margin table, and troubleshooting tips — see Spot-Check Component Margins for Packages in the Cost & Pricing Architecture guide.

---

Part 5: Availability

How Availability Works for Anyday

Anyday packages use an On Request availability model. There is no capacity management at the package level — each supplier is contacted to confirm availability at the time of request.

When a guest selects a date:

1. The system checks each component’s assigned services
2. A component is available if at least one of its assigned services is active
3. The package is available if all components have active services

If all services on a component are inactive, the package will show as unavailable for that date.

Key concept: Package availability = the intersection of all component availability. One component with all inactive services blocks the entire package.

---

Validation Checklist

Before activating the package, verify each item:

Package Record

• Departure Type is set to Anyday
• Duration matches the total trip length in nights
• Visibility Setting is appropriate for your channels

Components

• All destination segments have a Bundle component
• All standalone activities/transfers have a Component
• All external-fare segments have a Live component (if applicable)
• Position values are set and produce the correct itinerary order
• No duplicate or orphaned components exist

Services and Pricing

• Every component has at least one service assigned
• Default services are marked for components with multiple options
• Service Level assignments are correct (if using tiers)
• Price seasons cover the full valid date range with no gaps
• Cost and sell prices are populated
• Costings / Builder returns valid prices for low season, high season, and boundary dates

End-to-End Test

• Create a test itinerary using the package
• Select a date and confirm all components are priced
• Verify the total matches the sum of component prices
• Confirm availability returns correctly for dates with and without inventory

---

Common Issues and Solutions

Package Not Appearing in Search

Cause	Solution
Active is false	Set Active = true on the package record
Visibility Setting is Restricted with no Access Rules	Add Access Rules granting channel access, or set to “Open”

Package Shows Errors

Cause	Solution
A component has no services assigned	Assign at least one service (Component Option) to each component
Service is inactive	Verify the supplier service is active

Pricing Shows as Zero

Cause	Solution
Service has no price season for the requested date	Create a price season covering the date range
Cost/sell prices not populated	Update the service pricing
Component has no services assigned	Assign at least one service to the component

Availability Showing as Unavailable

Cause	Solution
All services on a component are inactive	Activate at least one service on each component
Date gap between price seasons	Ensure price seasons are contiguous with no missing days

Price Varies Unexpectedly Between Dates

This is usually expected behavior for Anyday packages. Each date pulls pricing from the applicable price season. If you see unexpected variation:

• Check that price seasons have the intended rate structure
• Verify that season date boundaries are correct (a one-day overlap or gap can cause the wrong rate to apply)

---

Related Schema Objects

Object	API Name	Purpose
Package	KaptioTravel__Package__c	Top-level product container
Component	KaptioTravel__PackageComponent__c	Segment within a package (Bundle, Component, Live)
Component Option	KaptioTravel__PackageComponentItem__c	Links a supplier service to a component
Service	KaptioTravel__Item__c	Specific supplier service offering
Service Level	KaptioTravel__ServiceLevel__c	Pricing tier (Standard, Superior, etc.)
Package Service Level	KaptioTravel__PackageServiceLevel__c	Junction linking a package to a service level

---

See Also

• Package Fundamentals — core package structure, components, and pricing foundations
• QUEST FIT Package Types — Three Ways to Sell Dates
• Seasonal Package Setup Guide
• Fixed Departure Management
• Service Level Configuration
• Supplier & Service Setup
• Cost & Pricing Architecture