A destination booking system can look inexpensive until the DMO accounts for integrations, payment processing, supplier onboarding, refunds and staff time. It can also look expensive while creating valuable bookings and reducing manual work. The useful question is not “What is the monthly price?” It is “What does this operating model cost for our visitor and merchant mix, and what verified value does it create?”
Evaluating a planning-led option? See Loop's AI Trip Planner for its current destination pricing and the booking journey it offers. Confirm which booking functions and integrations are included in your proposed setup.
Start with the role the DMO will play
A DMO can refer visitors to a merchant's own booking system, operate a regional booking marketplace, or manage a fuller reservation service with payments and commission settlement. Each role has a different cost profile. A referral approach may require less finance work but deliver less proof of completed bookings. A central service may produce better transaction data and income, but needs contracts, customer support and reconciliation. Define the role before comparing vendor quotes.
For a first estimate, write down expected monthly visitors, participating businesses, product categories and bookings. Identify how many operators already use software and how many need a booking tool. Include the visitor centre if staff handle in-person or phone reservations. A pricing model that suits a website-only DMO may not suit a VIC with hundreds of counter transactions. Our region-wide booking guide explains these operating choices.
Eight cost lines to request in every proposal
1. Platform subscription and setup
Ask for monthly or annual platform fees, one-time setup, training and support. Clarify whether pricing depends on the number of operators, locations, users, products or bookings. If a low introductory price changes after a trial, model the first full year and the following year separately. Ask what happens when the DMO adds another town or category. A package quote should name the modules included, not merely the parent brand.
2. Merchant onboarding
Creating profiles, products, rates, images and terms takes time. Some vendors include onboarding; others charge or expect DMO staff to do it. An operator with an existing booking system may need connection work, while a business without one needs product setup and training. Estimate staff hours per merchant and check whether seasonal changes require repeat work. A low software fee can be outweighed by manual supplier administration.
3. Integration and maintenance
Ask for the named merchant systems included in standard connections and the cost of any custom work. A connector may need ongoing maintenance when either system changes. Determine who pays to fix failures and who monitors availability sync. Count the cost of a broken handoff as well as the development invoice: it can lose bookings and undermine trust. The integration checklist shows the tests to require.
4. Transaction and payment fees
Separate platform transaction charges from card processing and third-party booking fees. Ask whether the fee applies to gross booking value, net value, deposits or only confirmed transactions. Determine whether it is charged again when a booking changes. For a simple model, multiply expected completed bookings by the average value, then apply each percentage and fixed per-booking fee. Use realistic category mixes because hotel rooms and restaurant reservations have very different values.
5. Commission and revenue sharing
A commission may fund the DMO's work, the platform, a distribution partner or all three. Ask who sets the rate, who collects it, when it is paid and what happens after cancellation. A merchant who already pays an OTA may resist another charge unless the destination channel brings distinct value. Show a sample statement from visitor payment to merchant payout. Do not combine commission revenue with gross visitor spending in board reports.
6. Refunds, chargebacks and customer support
Changes and disputes are part of bookings. Ask who answers the guest, who authorizes a refund, who bears the payment fee and whether the DMO staff have to intervene. Include peak-season support in the budget. A platform that handles the first transaction but leaves every exception to the DMO can create substantial hidden work. Test one cancellation and one partial refund before signing.
7. Website and content work
The booking system may need new landing pages, operator records, accessibility fixes, search filters, itinerary content and analytics. Some vendors provide a site; others embed in the DMO's existing site. Compare the actual project scope. A destination with good content may only need a clear planning and booking layer. A destination with outdated listings will need editorial cleanup regardless of platform choice.
8. Data, reporting and export
Ask whether reports, API access or exports cost extra. Check whether the DMO can see supplier-level outcomes, cancellations and net value, not just clicks. Determine what data the merchant receives and what happens if the DMO changes providers. Data portability is part of total cost because a closed reporting system can make future changes expensive. Read our booking measurement guide for event definitions.
Build a simple first-year cost model
Create one row for each fee and one for staff time. Use a conservative scenario, an expected scenario and a busy-season scenario. For example, a DMO may start with 30 merchants, 10 of whom need a new booking setup. Estimate integration work for the other 20 individually rather than assuming one connector covers them all. Forecast bookings by category, average value, cancellations and fees. Calculate DMO income separately from operator revenue and platform expense.
The model should show cost per confirmed booking and cost per participating business, but those are not the only outcomes. A planner may also help visitors discover businesses they would otherwise miss, save a trip or lengthen a stay. Report these as separate visitor and member measures. Do not assign an invented dollar value to every itinerary view. Use verified reservations and a clearly labeled estimate for any indirect effect.
Ask vendors to price the same scenario
Send every vendor the same brief: existing website, operator count, booking-system mix, product categories, expected volume, visitor-centre needs and required reports. Ask for the first-year cost, recurring cost, transaction fees, integration work, merchant onboarding and support. If a vendor proposes a broader suite, ask which modules are mandatory and which can wait. A fair comparison is impossible if one quote includes finance operations and another only includes a website widget.
Request a written example of one hotel booking, one activity booking and one cancellation. For each, identify the visitor price, merchant payout, DMO commission if any, payment processing, platform fee and staff action. This exposes differences that headline percentages hide. Also ask whether the DMO can keep a merchant's existing booking system, and what it costs to add a merchant without one.
When a lower fee is not a better deal
Suppose a low-cost referral tool sends traffic to suppliers but cannot confirm what was booked. It may be appropriate for a DMO whose goal is simple member exposure. It may be inadequate for one that must show room nights and commission to fund a visitor centre. Conversely, a full reservation system could be excessive for a small destination that wants visitors to build a useful trip and book directly with operators. Match expenditure to the outcome and operating responsibilities.
A platform with a higher subscription but less manual reconciliation could save staff time. A commission model with no subscription could be expensive at volume. Run both cases through the same expected booking mix. The destination booking platform guide helps identify which models to compare.
A worked comparison without invented promises
Consider two bids for the same pilot. One charges a fixed monthly amount and sends visitors to each operator's checkout. The other charges per confirmed booking and handles payments and settlement. Neither can be called cheaper until the DMO specifies expected volume, average booking value, cancellation rate, staff hours and what the report must prove. If the first bid cannot identify confirmed bookings, do not give it the same revenue-attribution score as the second. If the second requires substantial supplier contracting and finance administration, include those hours. This kind of scenario is more useful than comparing one advertised headline price with another vendor's full-service quote.
Review the contract's practical details
Before signing, check minimum term, price changes, support hours, uptime commitments, integration ownership and data export. Clarify whether the DMO can pause a merchant, refund a guest and access historical records after termination. Ask how changes to local tax or payment rules will be handled. A procurement decision affects visitor trust and merchant relationships, not just software expenditure.
Frequently asked questions
Is a commission model cheaper than a subscription?
It depends on booking volume, average value and the work included. Model both with your own numbers, including payment fees and staff time.
Should a DMO earn commission on every booking?
That is a policy and commercial choice. Some destinations prioritize revenue to support services; others prioritize direct operator relationships. Make the terms transparent to merchants.
Can we estimate impact before launching?
Yes, as scenarios. Keep projected bookings separate from confirmed results, and revise the model after a small pilot.
Next step: Explore Loop's AI Trip Planner and ask for a quote tied to your merchants and booking paths.