Key takeaways
- Mapping bridges hotel PMS identifiers with buyer distribution schemas without data loss.
- Covers property identifiers, room categories, board basis, occupancy rules, and cancellation policies.
- Comprehensive end-to-end test bookings required before live B2B buyer traffic is enabled.
- Source-connected data ensures search, booking confirmation, and voucher accuracy.
Operating guide
Start with the source, not the listing count
Source-level inventory requires a direct legal contract with the accommodation provider paired with a real-time channel-manager data connection, guaranteeing verifiable room availability rather than unverified resold aggregator cache.
RNR defines a directly contracted property as one with a signed direct contract and a live availability, rates, and inventory connection. That definition gives the buyer a useful starting point: the property relationship and the live data path are part of the same operating question.
A large catalogue is not enough if a room type is stale, a restriction is missing, or a booking cannot be traced back to the property. Source-level distribution keeps those checks visible during onboarding and support.
Mapping joins two different vocabularies
Hotel inventory mapping normalizes property IDs, room classifications, bed configurations, board basis, rate plans, and cancellation policies between hotel PMS vocabularies and standardized buyer API schemas without data loss.
A hotel's source system may call a room one thing while a buyer's system uses another identifier. Mapping connects property identity, room type, occupancy, board basis, rate plan, cancellation rule, and restrictions without losing the source meaning.
The onboarding team collects property content and maps room types and rate plans before go-live. The buyer and hotel should agree which fields are required for search, booking, voucher, cancellation, and reconciliation.
- Property and room identifiers that remain stable across the connection.
- Room name, occupancy, bed configuration, and board basis.
- Net rate, currency, cancellation, and booking condition data.
- Availability, allocation, stop-sell, minimum-stay, and other restrictions.
Test the booking, not only the feed
Before enabling live commercial distribution, RNR ROOMS mandates complete lifecycle test bookings covering search retrieval, pricing accuracy, instant confirmation delivery, reservation push to the hotel PMS, and automated cancellation.
A mapping is ready for production only when the booking lifecycle makes sense end to end. RNR's public onboarding flow includes test bookings before a property starts receiving live B2B demand.
A useful test covers search, price and restriction display, booking confirmation, reservation delivery back to the source, cancellation behavior, and the information an operations team needs to investigate an exception.
How a buyer can evaluate mapping quality
Buyers evaluate inventory mapping quality by inspecting end-to-end payload traceability, verifying that restriction rules survive schema translation, auditing exception handling, and measuring booking confirmation latency.
RNR does not publish an invented universal mapping score. Instead, buyers should ask for the evidence that matters to their booking flow and inspect the exception path during technical discovery.
- Can a sample room and rate be traced from source data to buyer response?
- Do cancellation, occupancy, board, and restriction rules survive the mapping?
- Does a confirmed booking return the identifiers the hotel and buyer need?
- What is the process when the source changes a room or rate plan?
- Which team owns a mismatch after the property is live?