1. Stop the incorrect OTA offer without closing a room that is still physically available.
2. Compare meals, cancellation, payment, and final guest price with the intended PMS rate plan.
3. Keep existing bookings and guest-facing terms intact while the relationship is corrected.
4. Give technical IDs to support only when they are needed to investigate the connection.
An OTA rate plan mapping mismatch can make the correct room appear with the wrong booking conditions. The hotel may give away breakfast, accept a cancellation it did not price for, collect payment incorrectly, or sell below the intended final price.
Mapping simply means the relationship between a rate plan in your PMS and the product guests can book on an OTA. For example, the PMS plan “Non-refundable Room Only” should not point to an OTA product called “Flexible Breakfast Included.”
Start with what the guest can buy and what the hotel must deliver. Technical codes can wait until a support team needs them.
Protect Guests and Stop the Wrong Offer
Open the affected OTA product and confirm what is wrong before changing the connection. Save the room, stay dates, displayed price, meal inclusion, cancellation terms, and payment instructions.
If the offer creates an immediate financial or guest-service risk, pause or close only that rate plan through your normal PMS or channel manager process. Do not close the shared room inventory when the room itself is still available under other valid plans.
Keep all existing reservations. Do not delete or recreate a rate plan that has live bookings, because later modifications and cancellations may still depend on it. Assign one person to review reservations already created under the wrong product.
Not every price difference is a mapping error. Use the same room, dates, occupancy, currency, device, market, login status, and tax display before comparing the PMS and OTA. A mobile discount, member price, promotion, currency conversion, or tax presentation can create a valid difference.
Compare the Four Fields Guests Actually Buy
The PMS rate plan and OTA product do not need identical names. They do need to promise the same commercial stay. Compare these four fields before deciding the mapping is wrong.
Meals and Inclusions
Check whether both products are room-only, breakfast included, half board, or another package. Also compare parking, airport transfer, welcome items, resort credits, or other inclusions that cost the hotel money.
If the OTA sells breakfast but the PMS receives a room-only plan, the front desk may not see the inclusion and the hotel may absorb an unplanned meal cost. Protect the guest-facing promise while the mapping is corrected.
Cancellation Policy
Compare the free-cancellation deadline, non-refundable condition, no-show charge, modification rules, and any deposit retained after cancellation.
A flexible OTA product connected to a non-refundable PMS plan creates disputes at cancellation. The OTA confirmation is the record of what the guest bought; do not replace those terms silently with the hotel's intended policy.
Payment Method and Timing
Check whether the OTA collects payment, the hotel charges the guest, a virtual card is used, or a deposit is due before arrival. Confirm when the payment becomes available and which amount the hotel should collect.
The wrong mapping can trigger an incorrect deposit request, a second payment request, or the wrong front-desk collection instructions. Keep protected payment details out of ordinary notes and support screenshots.
Final Guest Price
Compare the total price for the same stay, not only the base nightly rate. Include occupancy charges, taxes, fees, meal supplements, discounts, derived-rate adjustments, and the currency shown to the guest.
If the four commercial fields match but the public price differs, investigate promotions, tax display, occupancy pricing, currency, and market discounts before changing the mapping. If the conditions point to a different PMS plan, the relationship is likely wrong.
When plans are managed across several channels, a hotel channel manager gives the team one place to compare the PMS rate plan with the OTA product before another price or reservation is sent.
Keep PMS Rate Plans and OTA Products Aligned
Connect each OTA offer to the intended PMS rate plan so price, booking conditions, and incoming reservations follow the same hotel workflow.
Confirm and Correct the PMS-to-OTA Relationship
What Mapping Means
In practical terms, mapping answers one question: which PMS rate plan should control and receive each OTA product? The hotel should be able to describe both sides using the same four fields even when their displayed names differ.
Choose one affected property, room, date, PMS plan, and OTA product. Confirm the physical room is correct first. Then compare the PMS plan with the OTA product using meals, cancellation, payment, and final price.
Check what changed recently. A new plan, copied room, renamed offer, channel reconnection, PMS migration, or change from a standalone price to a derived price may leave an old relationship selected.
Change One Relationship at a Time
Pause routine edits for the affected plan and save screenshots of the current setup. Select the intended PMS plan and OTA product based on commercial meaning, not the closest names.
Change only the incorrect rate-plan relationship. Leave verified property, room, and inventory connections unchanged. If changing one plan requires disconnecting the whole property or room, stop and contact the connectivity provider.
Use a low-risk future date for verification. Send one controlled price or restriction change, then check the exact OTA product and confirm that unrelated plans did not change.
Review Bookings Created Under the Wrong Plan
Correcting the mapping protects future sales. It does not automatically repair reservations already created under the wrong PMS plan.
Compare every affected OTA confirmation with its PMS record. Preserve the guest's price, meals, cancellation terms, payment instructions, stay dates, and source reservation reference. Correct internal rate codes or operational notes only through an approved process that keeps future OTA updates attached to the same reservation.
Check the operational consequences. The wrong plan may have changed meal counts, deposit tasks, automated messages, tax or package posting, commission treatment, revenue codes, or front-desk payment instructions.
Contact the guest only when a material difference requires clarification. Do not describe the hotel's internal mapping mistake as a guest error, and do not cancel a valid OTA booking merely to make the PMS record cleaner.
Information to Give Technical Support
Hotel staff can explain the commercial mismatch without diagnosing the connection. Send one support case containing:
- the property ID, PMS rate-plan ID, channel-manager rate-plan ID, and OTA offer or rate-plan ID;
- the affected room, stay dates, occupancy, currency, and sales market;
- the expected and actual meals, cancellation, payment, and final price;
- one affected reservation reference, with payment data masked;
- screenshots of the PMS plan, mapping screen, OTA product, and guest-facing offer; and
- the update time, time zone, outbound acknowledgement or delivery result, and recent configuration changes.
This is the only stage where the identifier chain is useful. Ask support to confirm which technical ID points to which product and whether the latest update reached that target. Hotel staff should not need to inspect message payloads or provider queues themselves.
Confirm the Fix and Prevent a Repeat
Do not close the case because the mapping screen looks correct. Confirm that one controlled PMS update changes the intended OTA product, while another valid plan remains unchanged.
Search the public OTA offer using the same dates, occupancy, currency, market, login status, meals, cancellation, and payment conditions. Then place an authorized cancellable test booking. Verify that it enters the PMS under the intended rate plan with the correct price and inventory change, and that an approved modification and cancellation update the same record.
Document the final PMS plan and OTA product in the hotel's rate-plan register. Repeat this business-field check whenever the team launches, copies, renames, derives, or retires a rate plan, changes channel manager, or migrates PMS.
Frequently Asked Questions
What is an OTA rate plan mapping mismatch?
It means a PMS rate plan is connected to the wrong OTA product. The room may be correct while meals, cancellation, payment, or final price are wrong.
Can the room type be correct while the rate plan is wrong?
Yes. Room inventory can update correctly while the OTA sells different commercial conditions from those assigned to the PMS plan.
Is every OTA price difference a mapping error?
No. First compare the same dates, occupancy, currency, taxes, market, login status, promotions, and derived-price rules. Mapping is the likely cause when the OTA product corresponds to a different PMS plan.
Should the hotel delete and recreate the rate plan?
Not while it has live bookings or dependent plans. Protect the offer, confirm the intended relationship, and change only the incorrect mapping through the approved workflow.
How do you verify a corrected mapping?
Check one controlled update on the intended OTA product, confirm unrelated plans remain unchanged, and complete an authorized cancellable booking, modification, and cancellation.
For hotel managers, the safest approach is to compare what the guest buys: meals, cancellation, payment, and final price. Use technical IDs only after those business facts show which PMS plan and OTA product should be connected.
