Package Setup Configuration Guide

To be Reviewed

Master Reference for Package & Component Configuration

Version 29 min read | March 5, 2026 Gallery

Package Setup Configuration Guide

Master Reference for Package & Component Configuration

This guide is the master reference for configuring packages in Kaptio. Every field and setting documented here controls how packages behave across the entire platform — from how they appear in Package Search, to how they present options in the Booking Wizard, to how Package Modifications handles cancellations and transfers.

Why This Guide Matters

Package configuration is upstream of everything. A single checkbox on a Package Component can determine whether an optional service appears in the Booking Wizard Options tab, whether it is included in cancellation fee calculations, and whether its price rolls up into the package total on travel documents. Understanding these settings prevents configuration surprises downstream.

What’s Covered

  • Package Record Configuration — Record types, departure types, pricing setup, visibility, and service level modes

  • Component Configuration — Selection types, booking wizard tabs, cancellation controls, inventory, and pricing behaviour

  • Component Options — Service levels, pricelists, fare classes, and meal plans

  • Group Tours & Price Models — Configuration groups, pricing overview, and service conversion

  • Inventory & Pricing Controls — Allotment types, price points, and discount configurations

  • Admin Reference — Pilot features, permissions, app settings, and field sets

  • Downstream Impact Reference — How each setting flows into Package Search, Booking Wizard, and Package Modifications

Available In

Circle Sell Voyage Train Voyage Cruise Quest Tailormade

This guide is structured as a field-level reference. Each setting is documented with:

  • API Name — The Salesforce field API name

  • Picklist Values — All available options with their API and label values

  • What It Controls — The behaviour this setting drives

  • Downstream Impact — Which downstream systems (Search, Wizard, Modifications) are affected

This guide feeds into these downstream guides. Changes here will affect behavior documented there:

Packages have two record types that fundamentally change how the Package Editor and downstream systems behave.

Record TypeAPI NameDescriptionWhen to Use
PackagePackageStandard package with its own components, services, and pricingMost tour packages — group tours, FIT packages, rail journeys, cruise itineraries
BundleBundleA package that references other packages as components. Enables Advanced Price Rules tab in the Package Editor.Combo tours, multi-leg journeys, packages assembled from sub-packages

Field: Package__c.DepartureType__c — Controls how the package handles travel dates and which Package Editor tabs are available.

ValueLabelPackage Editor TabDescription
FixedFixedDepartures tab enabledPackage runs on specific departure dates. Each departure has a date, status, capacity. Most common for group tours.
SeasonalSeasonalSeasons tab enabledPackage is available within date ranges (seasons). Uses PackageSchedule__c records with nested time periods.
AnydayAnydayNeither tab enabledPackage is available on any date. No departure or season management needed. Common for FIT packages.

Downstream Impact

Package Search: Fixed packages only appear for dates with published departures. Seasonal packages appear within season date ranges. Anyday packages appear for any searched date. Component Behaviour: When Departure Type is Fixed, components gain departure assignment controls (DepartureMode__c). Components can be assigned to all departures or selective departures only.

Field: Package__c.SellingPriceSetupChoice__c — Determines how sell prices are calculated.

ValueLabelDescription
ChannelMarkupChannel Markup / MarginSell price derived from cost + channel-level markup/margin. Most common setup.
PackageMarkupPackage MarkupSell price derived from cost + package-level markup percentage.
PackageMarginPackage MarginSell price set to achieve a specific margin percentage on the package.
FixedFixedSell prices are manually set fixed values, independent of cost.
DynamicDynamicSell prices are calculated dynamically based on external inputs or complex rules.

Field: Package__c.NetPriceSetupChoice__c — Determines how cost prices are sourced.

ValueLabelDescription
FixedFixedCost prices are manually set. Suitable when supplier rates are contracted and stable.
DynamicDynamicCost prices are sourced dynamically from supplier rate feeds or calculated at booking time.

Field: Package__c.ServiceLevelMode__c — Controls how service levels (room types, cabin classes, etc.) are managed across the package.

ValueLabelDescription
StandardStandardDefault. Components manage their own service options independently. No package-level service level coordination.
Service LevelsService LevelsPackage defines service levels that coordinate across components. When a traveler selects “Premium”, all components upgrade to their Premium variant.
Cabin LevelsCabin LevelsSimilar to Service Levels but specifically for cabin-based products (cruise, rail). Cabin selection drives component options.

When to Use Service Levels

Use Service Levels when your package offers tiers (e.g., Classic / Premium / Luxury) and selecting a tier should automatically adjust all component options to match. This is common for rail packages with cabin classes and cruise packages with deck categories.

Field: Package__c.PhysicalInventorySelection__c — Controls whether the Booking Wizard requires physical unit (room/cabin) number selection.

ValueLabelDescription
MandatoryMandatoryDefault. Guests must select specific room/cabin numbers during booking.
NotMandatoryHiddenNot Mandatory / HiddenRoom/cabin selection is hidden. The system auto-assigns or the step is skipped.
ComponentControlledComponent ControlledEach component individually controls whether physical unit selection is required via the component’s InventoryRequired__c flag.

Downstream Impact

Booking Wizard: This setting directly controls whether the room/cabin selection step appears in the Booking Wizard flow. If set to Not Mandatory, travelers skip this step entirely.

Two fields control who can see and book a package.

Visibility Setting

Field: Package__c.VisibilitySetting__c

ValueLabelDescription
VisibleForAllVisible for AllDefault. Package appears in search for all channels and accounts.
RestrictedRestrictedPackage visibility is controlled by AccessRule__c. Only channels/accounts matching the access rule can see or book it.

Access Rule

Field: Package__c.AccessRule__c — Lookup to an Access Rule record that defines which channels and accounts can access this package. Only applies when VisibilitySetting__c = 'Restricted'.

Common Use Case

Use Restricted visibility for bundles that should not appear in consumer search results, or for packages exclusive to specific travel agent accounts or channels.

These fields control how package-level pricing calculations work.

FieldAPI NameDescription
Primary Pricing ComponentPrimaryPricingComponent__cThe main component whose pricing drives the package price. Used with PrimaryComponentAmount__c to determine base sell price.
Secondary Pricing ComponentSecondaryPricingComponent__cOptional second component contributing to package price. Used with SecondaryComponentAmount__c.
Sell Price RoundingSellPriceRounding__cDefault — applies system-level rounding. None — no rounding applied to sell prices.
Calculated as Day RateIsCalculatedAsDayRate__cLegacy (classic costings only). When checked, package pricing is calculated as a daily rate multiplied by the number of days. Only applies to fixed net rate packages from a single supplier. Not used in lightning costings.
UnpricedUnpriced__cWhen checked, the package has no automated pricing. Prices must be manually set or confirmed. Booking Wizard shows “unpriced items” warning.

These fields control commission calculations and profitability tracking at the package level.

FieldAPI NameDescription
Commission GroupCommissionGroup__cLookup to a Commission Group record. Controls which commission rates apply to this package when sold through reseller channels.
Profitability GroupProfitabilityGroup__cLookup to a Profitability Group. Used for grouping packages in profitability analysis and reporting.
Discount GroupDiscountGroup__cFor Bundle record type packages only. Links to a discount group used in the Advanced Price Rules tab.

Field: Package__c.PrepackagedBySingleSupplier__c (checkbox)

When checked, this indicates the entire package is provided by a single supplier. This changes component edit behaviour:

  • The package-level Supplier__c field is used as the default supplier for all components

  • Component option modals pre-fill supplier information from the package record

  • Simplifies setup for packages where one operator delivers everything (e.g., a single DMC providing all services)

Field: Component__c.SelectionType__c — Controls whether the component is included in the base package or presented as an option.

API ValueLabelDescriptionDownstream Impact
RequiredPre-Selected RefundableComponent is part of the package by default. It can be removed from the booking, in which case its cost/sell price is removed from the total.Included in base price. Not shown in Booking Wizard Options tab. Removable with refund.
OptionalOptionalComponent is not included by default. The traveler can choose to add it during booking.Shown in Booking Wizard Options tab (if BookingWizardTab__c is also set). Not included in base price until selected.
NonRefundablePre-Selected Non-RefundableComponent is part of the package by default. It can be removed from the booking visually, but the price is not removed — the customer still pays for it. The line appears greyed out in Costings.Included in base price. Cannot be refunded if removed. Line remains in Costings (greyed out) and documents.

Common Confusion

The API value Required maps to the label “Pre-Selected Refundable” — not “Required” in the UI. Similarly, NonRefundable maps to “Pre-Selected Non-Refundable”. The distinction matters: both are pre-selected, but they differ in refund behaviour when removed.

Example: Transfers

A transfer component set to Pre-Selected Non-Refundable means the guest can opt out of using the included transfer (e.g., they arrange their own), but the tour operator still charges for it. The component can be reinstated if needed.

Field: Component__c.BookingWizardTab__c — Controls which tab in the Booking Wizard displays this component. Only relevant for Optional selection type components.

API ValueLabelBooking Wizard Display
NoneNoneNot shown in any Booking Wizard tab. Used for background or included components.
OptionsOptionsShown in the Options tab. Standard optional services and upgrades.
Protection PlanProtection PlanShown in the Protection Plan tab. Travel insurance and protection products.
Pre StayPre StayShown in the Pre Stay tab. Hotel nights before the main package.
Post StayPost StayShown in the Post Stay tab. Hotel nights after the main package.

Most Common Configuration Mistake

If your optional component is not appearing in the Booking Wizard, the most common cause is BookingWizardTab__c set to None or SelectionType__c not set to Optional. Both must be correctly configured for the option to display.

Field: Component__c.PackageTotals__c — Controls whether this component’s price is included in the displayed “Package Total”.

API ValueLabelDescription
IncludedInPackageTotalIncluded in Package TotalDefault. Component’s price rolls up into the displayed package total.
ExcludedFromPackageTotalExcluded from Package TotalComponent’s price is not included in the displayed package total.

Critical: What Package Totals Does NOT Control

Despite the name suggesting broad control, this setting has a limited scope. Based on field testing and code verification: Area Affected? Content generation (documents/PDFs) Yes Costings hover display (package icon on optional services) Yes Cancellation fee calculations No Payment schedule generation No Itinerary rollup totals No UI total displays No Source: CancellationFeeCalculations.cls does not reference PackageTotalsSetting__c. Confirmed via field testing and code review. This is an older field with limited usage. See Cancellation Controls for the fields that actually control cancellation fee inclusion.

Two checkboxes on the Package Component control whether optional services are included in cancellation fee calculations. These are the actual controllers for cancellation fee inclusion — not the Package Totals setting.

FieldAPI NameControlsWhen Ticked on Optional Components
Is Main ComponentComponent__c.IsMainComponent__cPercentage-based cancellation feesOptional component is included in percentage-based cancellation fee calculations (e.g., 25% of package price)
Is Main Tour ComponentComponent__c.IsMainTourComponent__cFixed-amount cancellation feesOptional component is included in fixed-amount cancellation fee calculations (e.g., a flat fee)

Example: Optional Excursion

Consider a package with a fixed cancellation fee (priority 1), then percentage-based fees (25%, 50%, etc.). For an optional excursion added during booking: If IsMainComponent__c is ticked on the excursion component, the 25% fee applies to the full booking total (base package + optional excursion) If IsMainComponent__c is not ticked, the 25% fee applies only to the base package price

Technical Note

The cancellation fee engine (CancellationFeeCalculations.cls) iterates through all price lines per passenger and applies cancellation rules uniformly. These checkboxes control behaviour upstream — determining which items generate price lines that feed into the cancellation calculation. The cancellation calculator itself does not filter by component type. Source: Confirmed via field testing and code review. Verified in CancellationFeeCalculations.cls.

Field: Component__c.ComponentBehaviourChoice__c — Controls how the component handles quantity and selection in the Booking Wizard.

API ValueLabelDescription
SingleSingleComponent is selected once. One unit per booking (e.g., a hotel stay for the trip).
PassPassComponent applies as a pass across the trip (e.g., a rail pass valid for multiple days).
UnlimitedUnlimitedComponent can be added multiple times with no limit (e.g., extra excursions).
DayTicketsDay TicketsComponent is managed as day-by-day tickets (e.g., daily activity passes).

Related field: MaxTimes__c — sets an upper limit on how many times a component can be selected (only applicable for Unlimited behaviour).

Field: Component__c.PricingBehaviorChoice__c — Controls how pricing is handled for this component.

API ValueLabelDescription
StandardStandardNormal pricing — component has both cost and sell prices.
FreeComponentFree ComponentComponent has no cost and no sell price. Included at zero cost (e.g., complimentary upgrade).
NoCostRateNo Cost RateComponent has a sell price but no cost. Used when the operator provides the service at no cost but charges the customer (e.g., owned hotels).
NoSalesRateNo Sales RateComponent has a cost but no sell price. Used for internal cost tracking of services included in the package price (e.g., guide costs absorbed into the tour margin).

Field: Component__c.DepartureMode__c — Controls whether this component is available on all departures or only specific ones. Only relevant when the package DepartureType__c = 'Fixed'.

ValueDescription
All DeparturesComponent is automatically available on every departure of the package.
SelectiveComponent is only available on specifically assigned departures. Use the departure assignment modal in the Package Editor to select which departures include this component.

Use Case

Use Selective mode when an optional excursion is only available during certain seasons (e.g., whale watching only available on summer departures).

These fields control how inventory is managed at the component level.

FieldAPI NameDescription
Inventory RequiredInventoryRequired__cWhen checked, this component requires inventory contracts. Availability is checked against allotment records during booking. When PhysicalInventorySelection__c = 'ComponentControlled', this flag determines per-component whether room/cabin number selection is shown.
Allocation BehaviorAllocationBehavior__cControls how inventory is allocated: Standard (normal allocation), PreNight (allocate to the night before), PostNight (allocate to the night after). Used for pre/post-stay components.

Allotment Categories

When AppSettings__c.EnableAllotmentCategories__c is enabled, additional allocation controls appear in the component edit modal, including extra days/nights picklist values.

These fields control the day range and night behaviour of a component within the package itinerary.

FieldAPI NameDescription
Start DayStart__cThe day within the package itinerary that this component begins (e.g., Day 1, Day 3).
End DayEnd__cThe day within the package itinerary that this component ends.
Available Any DayIsAvailableAnyday__cWhen checked, this component is not tied to specific days and can be placed on any day in the itinerary.
Min Number of NightsMinNumberOfNights__cMinimum number of nights this component can be booked for (e.g., minimum 2-night stay).
Max Number of NightsMaxNumberOfNights__cMaximum number of nights this component can be booked for.
Create Item Per Night Per RoomCreateItineraryItemPerNightPerRoom__cWhen checked, the system creates a separate itinerary item for each night and each room. Used for per-night pricing models (e.g., hotel stays with different nightly rates).
Controls Departure DatesIsControllingDepartureDates__cWhen checked, this component’s dates drive the departure date of the package. Used for the primary accommodation or transport component.

These fields control the display order of components in the Package Editor, Booking Wizard, and itinerary displays.

FieldAPI NameDescription
SortSort__cControls display order of the component within the Package Editor and itinerary. Lower values appear first.
Day-by-Day DisplayDayByDayDisplay__cControls whether this component appears in day-by-day itinerary views and documents.

These fields control how commission is calculated at the component level.

FieldAPI NameDescription
Reseller Commission SettingsResellerCommissionSettings__cControls whether commission for this component follows the package-level commission group (PackageLevel) or uses its own component-level override.
Reseller Commission GroupResellerCommissionGroup__cLookup to a Commission Group. Only used when ResellerCommissionSettings__c is set to use component-level commission.

Field: Component__c.PrimaryComponent__c (checkbox) — Only applies to Fixed Departure packages (DepartureType__c = 'Fixed').

When checked, this component is flagged as a core part of the package. The system uses this flag for departure variation highlighting: if a specific departure is missing a component marked as primary, that gap is surfaced in the Package Editor so users can see which departures have incomplete component coverage.

For example, if a whale-watching excursion only runs on summer departures it would not be marked as primary — but the main accommodation would be, so its absence from any departure would be flagged.

Primary Component and Departure Mode are a paired set of fields — both appear in the component editor only for Fixed Departure packages. When a new component is created, both default to on: Primary Component is checked and Departure Mode is set to “All Departures”.

Note: Primary Component does not affect pricing calculations, date ranges, or booking wizard flow. It is purely a departure-completeness indicator.

Other Notable Component Fields

IsActive__c — Must be checked for the component to be included in the package ComponentType__cPriceCategories (standard), Live (live service), or Bundle (references another package) IsMandatoryOptional__c — Additional flag for mandatory-optional behaviour OnGroundPaymentRequired__c — Indicates payment for this component is collected on-ground rather than pre-trip TimeAvailability__c — Controls time-based availability filtering ApexClass__c — Custom Apex class for component-specific business logic

Component Options (ComponentOption__c) define the specific service variants available within a component. Each component option links a component to a specific service, pricelist, and configuration.

Component options are managed via the Component Option Edit Modal in the Package Editor, accessed by clicking the option icon on a component card.

Component Options vs Price Categories

A component links to a service, and each service has price categories (e.g., “King Bed”, “Two Twins”). Component options configure how those price categories are offered within the package — with which pricelist, pricing behaviour, and service level.

FieldDescription
Service LevelLinks this option to a package service level (when ServiceLevelMode__c is not Standard). Selecting “Premium” at booking time shows only Premium-level component options.
Price ListThe pricelist to use for this option. Determines cost and sell rates.
Pricing BehaviorOverrides the component-level pricing behaviour for this specific option.
Departure LocationStart location for transfer or transport services.
Arrival LocationEnd location for transfer or transport services.
Fare ClassFare class for rail or flight services.
Available TimesTime slots when this option is available (for time-based services).

Group Tours (GroupTravel__c) are the container for managing tour departures, price models, and the service conversion process. A Group Tour links a package to its operational configuration.

Key Fields

  • Channel — The sales channel for this group tour

  • Currency / Cost Currency — Selling and cost currencies

  • Owner — The Kaptio user responsible

  • Record Type — Supports multiple record types for different tour categories

Detailed group tour configuration (departure creation, price model linking, combo tours) will be documented in a future update.

Price Models are Itinerary records with the Price Model record type. They define the pricing structure for a group tour, including configuration groups, group sizes, and profitability strategies.

Key Concepts

  • Configuration Groups — Define occupancy options (e.g., Single, Twin, Triple) with option types and sort orders

  • Group Sizes — Start, end, and step values define the range of group sizes to price for

  • Tour Table — Shows itinerary lines with quantity behaviour, pricing behaviour, and profitability settings per group size

  • Pricing Overview — Calculates prices by departure date and configuration, with margin groups, percentage buffers, and export capabilities

  • Service Conversion Wizard — Converts price model data into live services with cost and sell prices using Banded, Fixed, or As Supplement conversion types

Detailed price model configuration will be documented in a future update.

The Pricing Overview provides a comprehensive view of calculated prices across all departures and configurations, with controls for margin management and price calculation triggers.

Key Features

  • Margin Groups — Default and override margins per service type

  • Percentage Buffer — Configurable buffer applied to calculations

  • Calculation State Monitoring — Tracks whether calculations are in progress, completed, outdated, or failed

  • Travel Dates — Manage travel date periods for seasonal pricing

  • Passenger Discounts — Child, infant, and other passenger type discounts

  • Excel Export — Export pricing data for offline review

Detailed pricing overview configuration will be documented in a future update.

Inventory is managed through inventory contracts (InventorySeasonStatus__c) that define allotment types, booking availability, fallback statuses, and release dates.

Key Configuration Areas

  • Allotment Type — Free Sale, Allotment (with capacity), On Request, Closed

  • Booking Availability — Controls when inventory becomes bookable

  • Fallback Status — What happens when allotment is exhausted (e.g., fallback to On Request)

  • Release Fallback Status — Status applied when release dates are reached

  • Scoping — Inventory can be scoped to channels, group tours, accounts, packages, tour departures, and time periods

  • Release Dates — Dates when unsold allotment is released back to supplier

Detailed inventory configuration will be documented in a future update. See the Booking Wizard Options Guide - Inventory Status for how inventory displays to users.

Pricing Controls is a standalone admin tool for managing prices across services. It provides search, filter, inline editing, and bulk operations for price items.

Key Features

  • Search & Filter — Filter by business unit, service record type, services, price categories, price points, routes, and date ranges

  • Inline Editing — Edit price values directly in the results table

  • Bulk Operations — Multi-select price items and change price points in bulk

  • Pricelist Replacement — Replace cost and/or sales pricelists on itinerary items or services

  • Discount Configurations — Manage discount groups with price groups, channels, valid from/to dates, and discount amounts

For the complete walkthrough — search filters, inline editing, batch updates, and discount configurations — see the dedicated Pricing Controls guide.

Pilot Features gate access to specific package-related capabilities. Users need the Pilot_Features permission set assigned and the relevant feature enabled.

Pilot FeatureWhat It EnablesArea
PackageModificationBooking Wizard in modification modePackage Modifications
ChangePackageOccupancyBooking Wizard in change occupancy modePackage Modifications
ChangePackageOrDepartureBooking Wizard in transfer modePackage Modifications
CancelRoomOrPackageBooking Wizard in cancellation modePackage Modifications
CreatePassengerReservationNumbersAuto-create reservation numbers from PackageDepartureDepartures
BookingFlowInventoryReserveReserve inventory items on itinerary creationBooking Wizard
AllowWaitListRequestsEnable waitlist functionality in Package Search and Booking WizardPackage Search / Booking Wizard

Key custom permissions that affect package setup and downstream behaviour.

Pricing & Cost Permissions

PermissionDescription
CanOverrideSellPriceOverride sell price on itinerary items
CanOverridePricelistsOverride pricelists on components
CanOverrideCostPricelistsOverride cost pricelists specifically
CanOverrideSalesPricelistsOverride sales pricelists specifically
CanOverrideUnitCostOverride unit cost on items
CanOverrideTaxOverride tax calculations
CanOverrideCommissionOverride commission rates
CanOverrideCancellationPercentageOverride cancellation fee percentages

Feature Access Permissions

PermissionDescription
Build_ItinerariesPermission to build itineraries from packages
Inventory_ManagementManage inventory contracts and allotments
Group_TourAccess group tour features
AccessBulkManagerAccess bulk manager for mass updates
EditAccessToVarianceBufferEdit variance buffer in tour pricing

AppSettings__c is a custom setting that controls org-wide package behaviour.

FieldDescriptionImpact
EnableAllotmentCategories__cEnables allotment category controls in the Package Editor component edit modalShows additional allocation behaviour fields and extra days/nights picklists
EnableLockSellPrice__cEnables the sell price locking mechanismPrevents sell price recalculation after initial booking
AllowLiveServicesAsOfflineServices__cAllows live service components to function as offline servicesAffects component type behaviour
CancellationRecordType__cRecord type set when an itinerary is fully cancelledPackage Modifications cancellation flow
DefaultTaxProfile__cDefault tax profile for pricing calculationsTax calculation on all price lines
RoomTypeFilterEnabled__cEnables room type filtering in the Booking WizardBooking Wizard room selection step

Field sets allow admins to customise which fields appear in the Package Editor UI without code changes.

ObjectField SetPurpose
Package__cFieldsOnPackageEditControls which fields appear on the Package Edit modal. Add custom fields here to make them editable in the Package Editor.
Component__cFieldsOnComponentEditControls which fields appear on the Component Edit modal. Custom component fields added to this field set will appear in the edit form.
ComponentOption__cFieldsOnFilteringSchemeControls filtering scheme fields for component options.

Extending the Package Editor

To add a custom field to the Package Editor UI: create the custom field on Package__c or Component__c, then add it to the corresponding field set. The UI dynamically renders fields from the field set.

This table shows how key package setup settings affect each downstream system. Use this to understand the ripple effects of configuration changes.

Package-Level Settings

SettingPackage SearchBooking WizardPackage Modifications
DepartureType__cControls date-based search behaviour (Fixed = specific dates, Anyday = any date)Determines room/cabin selection flowAffects transfer departure matching
SellingPriceSetupChoice__cAffects displayed prices in search resultsControls price calculation in wizard summaryAffects price comparison on modify
ServiceLevelMode__cFilters search by service level availabilityShows service level selector; coordinates component optionsService level preserved on modify
PhysicalInventorySelection__cNo direct impactControls room/cabin number selection stepAffects change occupancy room reassignment
VisibilitySetting__cControls which users/channels can see the packageNo direct impact (already in wizard)No direct impact
IsActive__cInactive packages excluded from searchNo direct impactNo direct impact

Component-Level Settings

SettingPackage SearchBooking WizardPackage Modifications
SelectionType__cRequired components included in search priceOptional components shown in Options tab; NonRefundable greyed if removedNonRefundable components cannot be refunded on cancellation
BookingWizardTab__cNo direct impactControls which tab displays the component (Options, Pre Stay, Post Stay, Protection Plan)Tab assignment preserved on modify
PackageTotals__cMay affect displayed total in searchAffects content/document generation onlyDoes NOT affect cancellation fees or payment schedules
IsMainComponent__cNo direct impactNo direct impactControls inclusion in percentage-based cancellation fees
IsMainTourComponent__cNo direct impactNo direct impactControls inclusion in fixed-amount cancellation fees
ComponentBehaviourChoice__cNo direct impactControls selection quantity (single pick, unlimited, day tickets)Behaviour preserved on modify
PricingBehaviorChoice__cFree components show as “Included”Controls price display (free, no cost, no sales)Pricing behaviour preserved on modify
InventoryRequired__cAffects availability status in search resultsControls inventory check and status badges (FS, AL, RQ, SO)Inventory rechecked on modify/change occupancy
DepartureMode__cSelective components only appear for assigned departuresComponent hidden for non-assigned departuresComponent availability on transfer target departure

Use this checklist when setting up a new package.

Package Record

  • Record Type selected (Package or Bundle)

  • Departure Type set (Fixed / Seasonal / Anyday)

  • Selling Price Setup configured

  • Cost Setup configured

  • Service Level Mode set (if applicable)

  • Physical Inventory Selection configured

  • Visibility and Access Rules set

  • Package marked as Active

  • Categories assigned

Components

  • Each component has correct Selection Type (Required / Optional / NonRefundable)

  • Optional components have Booking Wizard Tab set (Options / Pre Stay / Post Stay / Protection Plan)

  • Package Totals setting reviewed (Included vs Excluded)

  • IsMainComponent__c reviewed on optional components (percentage-based cancellation fees)

  • IsMainTourComponent__c reviewed on optional components (fixed-amount cancellation fees)

  • Component Behaviour set correctly

  • Pricing Behaviour set correctly

  • Inventory Required flag set where applicable

  • Start/End days configured

  • Sort order set

  • Components marked as Active

Component Options

  • Each component has at least one component option

  • Pricelists assigned to component options

  • Service levels linked (if Service Level Mode is not Standard)

  • Departure assignments set (if Departure Mode is Selective)

Pricing & Inventory

  • Prices configured for all price categories and channels

  • Inventory contracts created for components with InventoryRequired__c

  • Fallback statuses configured

Permissions

  • Pilot features enabled for users who need Package Modifications

  • Custom permissions assigned for pricing overrides (if needed)

  • Cancellation override permission assigned to managers

Downstream Guides (affected by settings in this guide)

Support

Back to Gallery