If you ask resellers what they want from operator booking systems, instant confirmation comes up in nearly every conversation. The reasons are practical: when a reseller is on the phone or in a WhatsApp conversation with a client finalizing an itinerary, the ability to confirm a tour booking immediately — rather than holding the client's attention while waiting for an operator callback — is a meaningful quality-of-service difference. The client feels taken care of. The reseller looks competent. The booking closes.
The problem is that instant confirmation is genuinely not possible for every tour product. Some experiences require guide availability checks. Some have weather-dependent departure decisions. Some require pre-purchased permits with limited daily quotas. And some operators simply don't have the operational infrastructure — the booking system connectivity, the staffing coverage, the real-time capacity management — to confirm instantly and mean it.
The conversation between operators and resellers about confirmation models is therefore not "instant confirmation good, on-request bad." It's about understanding which model fits which product, and how to make on-request as clean and fast as possible for the products where instant isn't viable.
When Instant Confirmation Works — and What It Requires
Instant confirmation is most viable for fixed-schedule products with defined capacity: daily departure city tours, regularly scheduled half-day excursions, fixed-time boat departures, cooking classes with set participant limits. For these products, the capacity question is straightforward — either there are seats available or there aren't — and a system connected to live inventory can answer it definitively without human review.
The operational requirement for genuine instant confirmation is that your available inventory count in the booking system reflects actual operational capacity. If you have 12 seats on a departure but you've mentally reserved 3 for walk-ins and you haven't reflected that in the system, your instant confirmation system will confirm seats you've actually set aside. The system is only as reliable as the human inputs feeding it.
For operators with well-maintained booking systems and consistent capacity tracking, moving higher-volume fixed-departure products to instant confirmation is achievable and worth the investment in setup time. Resellers will respond to it with more active promotion of those products — the frictionless booking experience directly reduces the hesitation that slows resellers from recommending products they're less certain about operationally.
When On-Request Is the Right Model
On-request is appropriate — and often the only honest option — for products where final confirmation genuinely requires human judgment or coordination. Private tour bookings where guide assignment matters. Expedition products with permit requirements that cap at specific daily pax numbers. Coastal or weather-dependent activities where a weather window decision is part of the confirmation process. Custom multi-day itineraries where pricing is finalized based on confirmed group size.
We're not saying on-request is inherently inferior for resellers. We're saying that a properly managed on-request process — clear response timeframes, reliable communication, and consistent follow-through — can absolutely support professional reseller relationships. The problems arise when on-request becomes a default catch-all for products that could be run on instant confirmation but aren't because the operator hasn't invested in the infrastructure.
The tell is response time. On-request products with a genuine 4-hour response window and reliable confirmations are operationally comparable to instant confirmation for most reseller use cases. On-request products that take 36–48 hours to respond, sometimes confirming and sometimes declining without clear reason, create the kind of operational uncertainty that drives resellers toward competing products that are easier to move.
The Hybrid Approach: Product-Level Confirmation Settings
Most operators with multi-product catalogs find that a single confirmation model doesn't fit all their products. The right approach is product-level confirmation settings: instant for fixed-schedule standardized experiences, on-request with defined SLA for custom or permit-limited products.
This requires that your product listing clearly communicates which model applies. Resellers need to know before they quote whether this product will confirm instantly or require a request window — not find out after they've told the client the tour is booked. Clear labeling (Instant Confirm / Request within 24 hours) at the product level is standard practice in professional B2B travel catalog systems and is a basic expectation for well-structured operator listings.
The secondary benefit of being explicit about confirmation models is that it sets correct expectations with resellers about handling time. A reseller who knows a product is on-request with 24-hour turnaround will manage their client communication accordingly. A reseller who expected instant confirmation and got a 24-hour wait has a different reaction — even if 24 hours is entirely reasonable for the product type.
Moving Products from On-Request to Instant: A Practical Path
For operators who know that their most popular fixed-departure products should be on instant confirmation but aren't yet because of system limitations, the transition path usually involves three steps.
First, centralizing capacity management: ensuring there's one authoritative source for how many seats are available on each departure, updated every time a booking is made through any channel. This might be a spreadsheet managed with real discipline, a simple booking system, or a platform like Tours Hub where inventory is managed centrally and connected to reseller bookings.
Second, defining overbooking risk tolerance: most operators don't run at 100% capacity and have some buffer between the seats they sell and the maximum they could technically carry. Understanding that buffer helps define how aggressively to set instant confirmation inventory thresholds — holding back a small reserve while allowing instant confirmation up to a safe limit.
Third, testing with lower-volume days first: moving a product to instant confirmation on less popular departure dates, validating that the system handles it cleanly, before extending to high-season departures where a confirmation error would be much more costly to fix.
The resellers who convert highest on the platform consistently favor operators who've made this transition for their standard products. The operational credibility signal of "you can confirm right now" is worth the investment in building the infrastructure behind it.
