If your lodge houses your own departures, releasing surplus rooms to a bedbank adds revenue — but only if your trip calendar and room inventory never promise the same bed twice.
A lodge owner running multi-day treks can find themselves in an awkward position. The accommodation exists primarily to house confirmed departures, but unused beds remain outside peak trip dates. A wholesaler or online travel agency then asks for those rooms, promising additional revenue through a hotel bed extranet.
The opportunity is real, but the operational risk is easy to underestimate. The lodge's trip calendar and the room-distribution portal are usually separate systems. If both offer the same bed and neither knows about the other, a room can be sold to an outside guest just when a confirmed group needs it.
Three terms create most of the confusion.
A hotel bed extranet is the secure supplier portal used by an accommodation provider to manage one distribution relationship. The lodge or guesthouse logs in to update rates, availability, room details, photos, descriptions, restrictions, special offers, and reservations. In wholesale arrangements, the portal may also contain contract rates, discounts, supplements, and allocation controls. The best-known example is the portal the wholesaler Hotelbeds gives its suppliers, MaxiRoom, which is a working reference for what a hotel bed extranet lets a supplier control — from the availability calendar to room content.
A bedbank, also called a wholesaler, is the commercial partner on the other side. It buys or contracts room inventory at a net rate, then resells that inventory through its own marketplace or to travel sellers. The bedbank controls the resale relationship, while the accommodation provider controls the information and inventory supplied through the portal.
A channel manager is software that distributes availability, rates, and booking information across several channels. Instead of editing multiple portals by hand, the accommodation provider connects a property-management system or channel manager to the relevant marketplaces. A channel manager can reduce duplicate entry, but it doesn't remove the need for clear allocations and operating rules.
These systems perform different jobs:
A tour operator who owns a camp may use all three, but they aren't interchangeable. The extranet doesn't automatically become a channel manager because it contains a calendar. A bedbank doesn't become the operator's reservation system because it sends booking notices.
The same principle applies to the physical product. A well-presented lodge still needs accurate room information, clear sleeping arrangements, and consistent housekeeping standards, but presentation won't solve an allocation error. The commercial listing and the operational bed plan must agree.
The hotel bed extranet became important because it gave suppliers a manageable interface without requiring every small property to build a direct system integration. It remains useful, but it should be treated as one operational control panel, not as the source of truth for every bed the business owns.
A hotel bed extranet usually starts with a property profile. The supplier enters the accommodation name, location, room types, occupancy rules, facilities, photographs, descriptions, and policies. Those details shape what the distribution partner can sell and what a guest expects on arrival.
The more important work happens in the availability and rate screens, the day-to-day availability management that keeps a channel accurate. The supplier normally sets:
A supplier may update these fields manually in the portal. Alternatively, a property-management system or channel manager may exchange information through an API, FTP connection, CSV import, or another connectivity method. Those technical methods are useful only when the connected systems have matching room types, date rules, and ownership of the data.
Manual entry can work for a small lodge with limited external inventory and a disciplined daily process. It becomes fragile when several people edit the calendar, when bookings arrive by phone, or when a trip manager blocks rooms in a separate spreadsheet.
Connected distribution reduces repeated data entry, but it introduces setup work. Room names, occupancy rules, cancellation policies, and availability statuses must match across systems. A connection can transmit the wrong information efficiently if the underlying configuration is wrong.
Tour operators should also separate the trip system from the accommodation system. A trip booking platform may manage departures, participant records, payments, and capacity without managing room inventory. Guidance on OTA integration can help clarify the difference between connecting booking channels and controlling accommodation availability.
The safest process assigns ownership to each field. One person should control room allocations, another may manage descriptions and photos, and the trip operations lead should approve any change affecting confirmed departures. Rate plans and cancellation policies shouldn't be edited casually after bookings are live, because a small change can alter the promise made to guests.
The central risk is simple: the same bed appears in two operational plans.
A trek operator may reserve rooms for a confirmed departure in a spreadsheet, trip-management system, or internal booking record. The accommodation extranet may still show those rooms as available to a bedbank or OTA. If an outside booking arrives, the room has effectively been sold twice, even though each system appears correct on its own.
The problem becomes most dangerous when both channels sell the last available room during the same period. Manual management across two channels fails at exactly that point. There is no shared, real-time buffer between the departure plan and the room-distribution portal, so the second booking can arrive before anyone has updated the other system.
An allotment is the quantity released to an external partner. It doesn't need to equal the property's total capacity. A lodge with several beds may release only the surplus, while holding the remaining capacity for its own confirmed trips.
A stop-sell closes a room type or date to new external bookings. It should be used when the released allotment has been consumed, when an upcoming departure requires the remaining rooms, or when the team can no longer monitor the channel safely.
Practical rule: The allocation held back for confirmed departures matters more than the speed of a portal update.
A conservative allocation with a clear buffer is usually safer than releasing every apparently empty bed. The buffer protects against late trip bookings, room moves, maintenance closures, cancellations that have not been reconciled, and simple human delay. It also gives the operator time to apply a stop-sell before an outside reservation consumes essential capacity.
The reconciliation is between two systems that don't know about each other:
That process is administrative work, not a software feature. A tour business should document who checks it, when the check occurs, and what happens when the records disagree.
A human should review this boundary before publication or implementation. The distinction between trip capacity and accommodation inventory needs to remain exact, because treating a trip platform as a room channel can create an avoidable overbooking incident.
Accommodation distribution generally uses one of two commercial structures.
With a net-rate agreement, the bedbank receives rooms at a contracted wholesale price. It then resells those rooms at a price determined by its own commercial arrangement. The supplier gets the agreed net amount, but may have less visibility into the final selling price and less control over how the room is packaged.
With a commission model, the accommodation provider sets a published rate and pays the distribution channel a commission after a booking. The supplier retains more direct control over the displayed price, but the final margin depends on the commission, taxes, payment costs, promotions, refunds, and any extras included in the reservation.
| Model | Supplier controls | Main trade-off |
|---|---|---|
| Net rate | The contracted amount and released allocation | Simpler wholesale economics, but less control over resale pricing |
| Commission | The published rate and rate-plan structure | More price visibility, but commission and reconciliation require care |
| Direct sale | The guest relationship, payment flow, and public price | Stronger control, with responsibility for demand, support, and collection |
A parity clause can restrict the supplier from offering a lower public rate on its own website than the rate shown through a contracted channel. That clause should be read before setting a direct rate below an OTA or bedbank rate. A cheaper direct price may appear attractive, but it can breach the agreement or trigger a dispute.
Rate consistency starts with one published base rate. Each channel's rate should be derived from that figure by working backwards from the required commission or net margin. The same logic should apply to cancellation terms, meals, transfers, taxes, and supplements. Otherwise, the reservation team may sell two apparently similar rooms with different financial outcomes.
Operators who need a deeper explanation of the calculations can review net-of-commission pricing for operators. For teams monitoring public rates across multiple channels, automated rate-monitoring tools can flag parity gaps, but data freshness and agreed checking responsibilities still matter. Monitoring isn't a substitute for contract knowledge or accurate inventory.
Payment terms deserve the same attention. The contract should state who collects the guest's money, when the supplier is paid, how refunds are processed, and whether commissions apply to cancelled or refunded reservations. Local taxes and invoice requirements should be checked with the operator's accountant or relevant authority.
A lodge attached to a tour business has three practical choices: release surplus rooms to a bedbank, list them through an OTA marketplace, or sell them directly. The right choice depends less on the promise of extra bookings and more on whether the team can protect its core departures while handling the added administration.
A bedbank suits an operator with predictable surplus inventory and a willingness to trade some price control for wholesale reach. The operator supplies contracted rates and allotments, then manages the relationship through an extranet or connected workflow.
The attraction is volume without building a direct guest-acquisition process for every booking. The cost is less control over resale, additional contract terms, and the need to reconcile bookings that may arrive through a distribution chain rather than through the tour company's own sales process.
An OTA can expose a lodge to individual travelers looking for accommodation. It may be appropriate when the property has genuine availability outside tour departures and the team can answer guest questions, manage payment rules, handle cancellations, and maintain room content.
The workload is broader than uploading rooms. Guest messages, reviews, policy exceptions, arrival details, and changes all become part of the accommodation operation. A channel manager may reduce manual calendar work, and this channel manager definition provides useful terminology for evaluating that software. It still won't decide which beds must remain reserved for a trek.
Direct sales give the operator control over the guest relationship, price presentation, cancellation wording, and payment process. They also leave the operator responsible for demand generation, customer support, payment reconciliation, taxes, and any distribution work that a marketplace would otherwise provide.
Before uploading the first room, three fields deserve priority:
The second field is the operator-specific safeguard. It prevents the worst outcome, selling a bed that a confirmed departure already needs.
The practical guidance on OTA versus direct booking is useful when comparing guest ownership and channel costs. Any operator working with an external accommodation partner should also put inventory ownership in writing. The agreement should identify who can release rooms, who can stop sales, who reconciles bookings, and who pays when a room isn't available.
A tour operator may need one system for trip departures and another for accommodation distribution. That isn't a weakness if the boundary is clear.
Samba manages trip departures and the seats on them. It supports online checkout, deposits, installment schedules, participant information, departure capacity, booking status, invoices, refunds, and finance workflows. It connects to the operator's Stripe account, and Samba states that it doesn't hold the operator's funds.
Samba does not manage hotel room inventory, connect a lodge to bedbanks, or synchronize room availability between extranets. It isn't a hotel channel manager. An operator using Samba for trek bookings still needs a separate accommodation workflow for room types, allotments, stop-sells, cancellations, and external reservations.
The separation can make responsibilities easier to audit:
Samba's published pricing includes no setup fee and no contract, with the first $10,000 in bookings fee-free, followed by a flat 2% per booking on direct and OTA bookings, according to its pricing page. The operator can absorb that fee or pass it to the traveler at checkout. Offline and bank-transfer payments can be recorded without a platform fee, while the operator's own Stripe account receives payouts directly.
Samba also states that refunded bookings return the Samba fee with the booking refund, so the operator isn't charged a booking fee on money returned to the traveler, as described in its terms. Those mechanics apply to trip and activity bookings, not to hotel-room distribution.
The safe operating model is therefore straightforward. The departure system records the beds a confirmed group requires. The accommodation workflow releases only the surplus. A named team member reconciles the two before opening dates or changing an allotment.
Listing rooms makes sense when the accommodation has reliable surplus capacity, the operator can assign someone to maintain it, and the additional revenue justifies the reconciliation work. It isn't automatically worthwhile because an extranet makes publication easy.
A lodge built primarily for the operator's own departures has a different economics from a hotel designed to sell rooms every night. Its most valuable inventory may be the beds that protect a confirmed trek, even if those beds appear empty on a particular date. Releasing them can create a sale today and a much larger operational problem later.
A cautious yes is reasonable when the following conditions exist:
A no is sensible when the rooms are almost always required for departures, availability changes frequently, or the team has no reliable reconciliation routine. Listing a small amount of surplus inventory isn't passive income. It creates content maintenance, rate administration, payment checks, guest communication, and exception handling.
The initial upload should begin with the three fields that prevent the most serious mistake:
Rates should be set once as the published base, then derived for each channel according to commission, net margin, taxes, and included services. Direct rates shouldn't be lowered casually until parity clauses have been checked. A lower direct price may conflict with a distribution agreement and can confuse guests who have already booked through another channel.
Manual management across two systems will eventually face a badly timed booking window. The protection isn't a promise that updates happen faster. It is a conservative allocation, a visible buffer, and a stop-sell procedure that someone can execute without asking who owns the decision.
The final question is operational rather than technical: can the business sell surplus rooms without putting confirmed departures at risk? If the answer is yes, begin with a small, clearly separated allotment and review the workload. If the answer is no, keep the rooms for the core trips and avoid turning essential capacity into a side business.
Samba gives multi-day tour operators a system for managing trip departures, participant records, payments, and balances, while room distribution remains in the accommodation workflow. Visit Samba to review the trip-booking and payment tools, then keep the lodge's allotments and stop-sells under a separate, clearly owned process.
Founder & CEO
Related posts
Channel Manager for Tours: How OTA Sync Works (2026)
Channel managers keep your inventory aligned across OTAs and your own site — but for tour operators, distribution is only half the job. Here's what to evaluate and what to watch out for.
Availability Management for Tour Operators
A guide for tour operators on keeping every seat, departure, and channel in sync — covering capacity rules, booking statuses, payment gates, and manifest readiness.
OTA Integration: Sync Tours Inventory and Bookings
OTA bookings now outpace direct sales for many operators. This guide covers how inventory and reservations flow between your booking system and marketplaces—and how to avoid oversells.
Keep the 20–30% you would hand an OTA
Samba gives tour and activity operators direct bookings on their own website, so you stop paying a marketplace 20–30% of every booking.