Limiting Sales by Channel with Channel Ticket Caps

Cap how many tickets your online widget and resellers can sell from a timeslot, while keeping front-desk sales uncapped.

Channel Ticket Caps let you control how many tickets each sales channel can sell from a timeslot. If your direct bookings are picking up and you want to hold back seats from your online widget or your resellers, you can now set those limits right in TripWorks — no more phoning each reseller to throttle them by hand.

How It Works

All of your channels sell from the same pool of tickets. A channel cap is a ceiling on how many of those tickets a given channel is allowed to sell — it is not a reserved set-aside. Because they're caps and not allocations, they don't need to add up to your total capacity.

There are two channels you can cap:

  • e-Commerce — online bookings through your own booking widget.
  • Resellers — all OTAs (Viator, GetYourGuide, Klook, Expedia) and private partners combined, as a single number.

Your direct sales — walk-up, phone, and point of sale — are never capped. You can always sell from your own front desk right up to full capacity.

Turning On Channel Limits

Channel caps live inside the Capped Per Timeslot capacity type:

  1. Open the activity editor and go to Capacity Settings.
  2. Find the Enable Channel Limits toggle and switch it on.
  3. Set your default e-Commerce and Reseller caps. These defaults apply to every timeslot unless you override an individual slot.
Note: Channel limits aren't available on resource-based capacity types, since dynamic capacity and fixed caps don't mix.

Reading the Channel Pills

Each capped channel shows a pill on the timeslot in the format booked / cap. Say a timeslot has a total capacity of 15, with a 10-ticket cap on e-Commerce and a 5-ticket cap on Resellers. As bookings come in, you might see pills like e-Commerce: 10 / 10 and Resellers: 0 / 5. When a channel reaches its cap but seats still remain overall, you'll see a badge like:

Good to Know

  • Holds count. An unpaid cart in progress counts against the cap, just like a confirmed booking does against total capacity.
  • No-shows don't free up the cap. A no-show check-in status doesn't release capacity, consistent with how no-shows behave today.
  • Turning it on mid-season is safe. When you first enable a cap on an activity that already has bookings, those existing bookings are counted toward the cap automatically — the counter starts from your real numbers, not zero.
  • You can set a cap below what's already booked. We'll warn you before you save, but we'll let you do it if that's your intent.
  • Caps can't exceed total capacity. If you try to save a cap higher than the slot's total, or lower the total below an existing cap, you'll get a clear prompt to adjust one or the other.
  • Turning the toggle off keeps your work. Per-timeslot overrides are preserved and simply go inactive; switch the toggle back on and they return.