Flat trip pricing hides which travelers are subsidizing others. This guide shows how to split fixed and variable costs, price add-ons fairly, and build tiered packages travelers trust.
By Valentin Fily
Activity-based pricing can mean two different things. In accounting, it builds a price from activity-based costing, while in tourism it charges separately for each activity or itinerary component. This guide uses the tour-operator meaning, with the accounting origin providing the logic underneath.
What if your advertised trek price is quietly making the travelers who skip every extra subsidize the ones who choose them all?
That question leads to the practical meaning of activity-based pricing for tour operators. A multi-day trip isn't one uniform product. It contains permits, guide days, transport, accommodation, meals, support work, and activities that some travelers choose while others skip. Pricing every booking with one flat day rate or one package total hides those differences.
The accounting meaning comes first. Activity-based pricing is rooted in activity-based costing, a method that links costs to the activities consuming resources. George J. Staubus's 1971 work Activity Costing and Input-Output Accountinghelped establish the causal connection between activities and costs, and Robert Kaplan and Robin Cooper developed the modern activity-based costing framework in the late 1980s. The approach spread from manufacturing into service businesses, including tourism, as indirect costs became harder to allocate with broad averages (historical review of activity-based costing).
Tourism uses the phrase more loosely. An operator calls it activity-based pricing when a base itinerary price is combined with separate prices for optional activities, upgrades, transfers, or other components. That is the meaning used here. The accounting discipline still matters, because it tells an operator which costs belong in the base and which should follow actual usage.
For a small trek company, the central question isn't whether every line on an internal spreadsheet should appear at checkout. It's whether the price reflects how the trip consumes resources and how travelers experience value. The same customer-facing thinking runs through the 4Ps marketing framework — product, price, and presentation deciding together how a trip is packaged and sold.
The test is straightforward. Separate costs that scale with each traveler from costs that exist for the whole departure, set the fixed block against a realistic minimum party size, then decide which optional components belong in the base price. That order gives an operator a defensible price without turning a simple trip into an accounting exercise.
A tour operator applies the method through a short costing sequence. The purpose isn't to make pricing complicated. It's to replace one unexplained markup with a small number of understandable cost relationships.
List the work required to deliver one departure. For a multi-day trek, that could include securing permits, briefing travelers, guiding each day, arranging vehicles, handling accommodation, coordinating meals, processing itinerary changes, and providing customer support.
The list should include the activities customers see and the ones they don't. A permit is visible. Rebooking a room after a date change is less visible, but it still consumes time and money.
Attach the relevant supplier, labor, and operating costs to each activity. Permit charges may relate to the departure or to each participant. Guide day rates usually relate to the departure schedule. Accommodation varies by room or lodge tier. A special activity may carry its own supplier charge and transport requirement.
The point is causal allocation. If an activity creates a cost, the pricing model should show where that cost enters rather than spreading it across every trip through a single blanket percentage. The standard service-business activity-based costing sequence runs the same way: identify the activities, assign the related costs, group similar activities into cost pools, select a driver for each pool, calculate a pool rate, and apply that rate according to usage.
A cost pool groups expenses that respond to the same driver. Guide labor and vehicle costs shouldn't automatically share a pool if one changes with guide days and the other changes with vehicle days or passenger capacity.
For a small operator, a few useful pools might be:
Each pool needs a driver that reflects usage. The driver might be a traveler, guide day, vehicle day, room night, booking, or optional activity selection. The resulting rate is then applied to the relevant booking or participant.
This mirrors the logic behind a practical job costing method. A trip is treated as a job with identifiable inputs, rather than as a product that receives an arbitrary share of overhead.
The customer price still needs a market check. Activity-based costing tells the operator what a trip consumes. It doesn't guarantee that travelers will accept every internal allocation, and it shouldn't override competitor prices or customer expectations. It also differs from demand-based pricing, which moves prices according to demand conditions rather than the cost and usage structure of the itinerary.
The most important split is not between "included" and "optional." It's between per-person costs and per-departure costs.
Per-person costs rise as more travelers join. Per-departure costs exist whether the group holds four travelers or twelve. A vehicle and driver cost the same for both groups. The guide works the same number of days. A lead vehicle is still required for the route. If the price treats those fixed costs as though they scale with passengers, a small group can consume the margin before the operator notices.
A simple departure model might look like this:
| Cost Item | Cost Type | Example Calculation |
|---|---|---|
| Permit charged for each traveler | Per-person | Permit amount × number of travelers |
| Meals charged by participant | Per-person | Meal amount × number of travelers |
| Accommodation by traveler | Per-person | Room or bed amount × number of travelers |
| Guide and driver schedule | Per-departure | Fixed departure block |
| Vehicle and lead vehicle | Per-departure | Fixed transport block |
| Departure coordination | Per-departure | Fixed preparation and delivery work |
| Optional activity | Per-person or per-booking | Supplier charge according to selection |
The accounting literature describes this logic through activities, cost pools, and cost drivers. It became relevant beyond manufacturing because service firms also carry indirect work that volume-based allocation obscures (review of the development and adoption of ABC).
Suppose a departure has a fixed operating block of $4,000. The operator's minimum party size is four travelers. The fixed cost allocation is:
$4,000 ÷ 4 travelers = $1,000 per traveler
If the same departure reaches twelve travelers, the fixed cost allocation becomes:
$4,000 ÷ 12 travelers = $333.33 per traveler
The cost hasn't changed. The number of people sharing it has. That distinction lets an operator set a minimum party size as a pricing decision, not merely an operational preference.
A trip priced around ten travelers looks healthy when ten people book, but the same price is weak at seven if the fixed block stays put. Historical fill levels from the previous season should therefore shape the minimum. The minimum has to reflect the group size that can realistically carry the departure, not only the maximum capacity.
Practical rule: Separate the fixed departure block first, divide it by the minimum viable party size, and only then decide how much margin and contingency the base price needs.
The same discipline applies when reviewing commissions and fees. An operator can use a net-of-commission pricing approach to see whether the amount retained after channel or transaction costs still covers the per-person and per-departure structure.
The most useful inputs are supplier and permit costs per departure, guide day rates, vehicle and fuel, accommodation by tier, historic take-up for each optional activity, and how full departures ran last season. Optional-activity take-up is often the missing input. Without it, an operator buries an experience in the base price even though only some travelers use it.
A single package price looks clean at checkout, but it creates two problems at once. It raises the entry price for travelers who want a simpler itinerary, while undercharging travelers who consume more of the operator's resources.
Consider one multi-day departure with a standard route and several optional experiences. Traveler A books the core itinerary and skips every extra. Traveler B selects every optional activity, needs additional transport coordination, and chooses a more expensive accommodation tier. Under one flat package price, both travelers pay the same amount.
That is cross-subsidization. The simpler booking carries part of the cost of the more complex booking. The operator may not see the problem in total revenue, because the departure still sells, but margin by traveler and package becomes unclear.
A flat price puts all components into one number. It's easy to explain, but the advertised price has to include enough room for the highest-consumption version of the trip, or accept that some selections will be underpriced.
Activity-based pricing starts with a lower base that covers the common itinerary, then charges separately for understood extras. The traveler who wants a helicopter transfer, premium lodge, or optional technical activity pays for that selection. The traveler who doesn't want it avoids carrying the cost.
The arithmetic is mechanical. Unbundling optional activities lowers the advertised entry price while letting travelers who want more spend more. The same departure can hold a wider spread of booking values without changing the departure itself.
The approach isn't automatically fair because it has more line items. Itemized pricing feels honest when the items are things travelers understand, such as a permit, a better lodge, or a helicopter transfer. It feels like nickel-and-diming when the operator separates items a reasonable traveler expected to be included, such as water or transport from the stated meeting point.
That expectation line matters more than whether a cost is technically optional. A transparent price explains what the base includes, what an add-on provides, whether the charge is per traveler or per booking, and when the selection has to be made.
A useful structure combines a clear base itinerary, optional add-ons, and two or more package levels on the same departure. The operator isn't changing the route for every traveler. The operator is letting each booking reflect the components selected.
The base package should contain what most travelers reasonably expect from the advertised trip: the core route, scheduled guide service, standard accommodation, stated meals, and the transport needed to deliver the published itinerary.
Optional activities should then be separated when they carry distinct supplier costs, require extra transport or staffing, or appeal to only part of the group. An add-on can be charged per traveler when each participant consumes it, or per booking when the group receives one shared service.
A per-traveler example is a specialist activity where every participant needs a place. A per-booking example is a private vehicle transfer arranged for the whole booking. The distinction should follow consumption, not convenience.
Tiered packages make the comparison visible. A standard package includes the core itinerary and standard accommodation. A premium package adds a better lodge tier, upgraded transport, or a more involved activity.
The entry price stays attached to the standard option. Travelers who value the additional components choose the premium option and pay more. That raises the value of selected bookings without raising the price presented to someone who only wants the standard experience.
Different travelers on one booking may also want different arrangements. One participant might choose the premium lodge or optional activity while another stays on the standard package. A booking system needs to represent those choices at participant level rather than forcing the whole group into one package.
The customer-facing description needs to answer four questions:
The item should make sense to the traveler. A permit or premium lodge is usually understandable as a separate component. A meeting-point transfer may not be, especially if the trip description implies that the operator handles arrival logistics.
Activity-based pricing should reduce confusion, not create a menu of tiny charges. A small operator keeps the structure manageable by separating only the components that materially differ in cost or customer choice.
The model becomes useful when the operator can maintain it without rebuilding the spreadsheet for every departure. A practical setup starts with a limited number of cost groups and reviews them when supplier terms, routes, or customer choices change.
The core inputs are operational, not abstract:
Optional-activity take-up deserves special attention. If it isn't tracked, the operator can't tell whether an add-on is priced too low, priced too high, or being buried in the base package.
Deposits and installment plans should follow the booking structure. The system should show the amount collected, the remaining balance, due dates, and reminders. A refund should reverse the relevant booking and payment records, including any selected add-ons or package differences.
Samba supports tiered packages priced per person and shown side by side, add-ons charged per booking or per traveler, different package choices for travelers on one booking, and a minimum party size set per trip. Offline and bank-transfer payments can be recorded without a platform fee, so the operator keeps a complete booking record even when payment doesn't run through the online checkout (Samba payment processing fees).
Implementation check: A booking record should show the departure, party size, package choice, add-ons, payment schedule, and remaining balance without a second manual calculation.
A revenue view helps the operator compare package mix, add-on selections, collections, and refunds against the original pricing assumptions. Revenue analytics for tour operators is relevant when the goal is to review what each departure produced rather than relying on the advertised price alone.
Activity-based pricing earns its complexity when itineraries contain meaningful optional activities, accommodation tiers, varied transport, and fixed departure costs that dominate the economics. It gives the operator a clearer relationship between what the traveler selects and what the business has to deliver.
Flat pricing remains sensible for short, simple, high-volume products with limited variation. If nearly every traveler receives the same service and the cost structure is easy to predict, separate components add friction without improving the decision.
The accounting heritage explains why the method works. Activity-based costing emerged in the late 1980s as businesses with varied products and complex overhead found broad allocation less useful, and its use later extended into service sectors (review of ABC's development). Tourism operators can borrow the logic without adopting an elaborate accounting system.
Demand-based pricing is a separate question. It moves the price according to demand conditions, while activity-based pricing structures the price around itinerary components and resource use. An operator can run one without the other, or layer demand adjustments on top of an activity-based base.
The next practical step is to take one upcoming departure, list its per-person and per-departure costs, and test the base package against the minimum party size.
Samba brings tiered packages, per-booking and per-traveler add-ons, minimum party sizes, deposits, installments, participant records, and Stripe-connected payments into one booking workflow, with payouts landing in the operator's own Stripe account. See whether Samba fits the way the business prices and operates multi-day trips.
Valentin Fily
Founder & CEO
Related posts
Demand Based Pricing for Tours: A 2026 Operator Guide
How to adjust departure prices by demand without breaking your payment workflows. Covers pricing models, triggers, guardrails, and keeping booked totals locked for travelers on installment plans.
Net of Commission: What Tour Operators Sign Away
When a channel pays you net of commission, your payout reflects multiple deductions — not just one rate. Here's what to check before you sign and how to reconcile accurately.
What Is a Payment Plan for Multi-Day Tours
A practical guide to structuring deposit-and-installment payment plans for multi-day tours — covering how to set a deposit floor, handle cancellations, and automate collection.
Keep the 20–30% you would hand an OTA
Samba is the booking platform built for multi-day tour operators who want to run direct bookings — not pay a marketplace 20–30% of every departure.