Blog›Connectivity

Diagnosing an OTA Rate Plan Mapping Mismatch Before It Reaches a Guest's Bill

A reservation arrives tagged to the wrong rate plan, or the wrong price, and this walks through how to diagnose a rate plan mapping mismatch between an OTA and your PMS step by step.

The Prime Host Partners team16 Nov 2026 · 7 min read

A booking lands in your PMS under the wrong rate plan — breakfast included when it shouldn't be, or a non-refundable rate showing as flexible — and the first instinct is to fix the one reservation. The actual problem is usually the mapping between that rate plan on the OTA and its counterpart in your PMS, and fixing only the symptom leaves every future booking on that rate plan exposed to the same error.

Full guide on this topic
What a rate plan mapping mismatch looks like

The booking itself arrives — a guest, dates, a price — so nothing about the connection looks broken. What's wrong is which rate plan the reservation gets attached to once it lands in your PMS: a breakfast-included rate shows as room-only, a non-refundable booking shows as flexible and cancellable, or the price doesn't match either rate plan's actual value. Staff usually catch this at check-in or during a cancellation request, when the terms the guest expects don't match what the PMS is enforcing.

Because the reservation exists and looks superficially normal, this kind of mismatch can run for a while before anyone notices, unlike a missing booking that announces itself immediately.

Why rate plans map incorrectly in the first place

Every rate plan on an OTA has its own identifier, and your channel manager has to hold a correct, one-to-one link between that identifier and the matching rate plan inside your PMS. That link is usually set up once, manually, when the room type or rate plan is first connected, and it stays correct only as long as neither side changes without the other being updated. If a new rate plan is added on the OTA side — a new promotion, a new meal-plan variant — and nobody updates the mapping, the new rate plan can silently inherit the wrong PMS-side counterpart, or fall back to a default that doesn't match its actual terms.

The usual sources of a mapping mismatch
1A new rate plan added on the OTA without updating the mappingThe extranet now has a rate plan with no deliberately configured PMS-side match, so it defaults to whatever the mapping table falls back to.
2Two similarly named rate plans mapped to the same PMS entryA flexible and a non-refundable version of the same room type, both pointing at one PMS rate plan by mistake.
3A mapping that was correct once but never revisitedThe property's rate structure changed over time and the mapping table wasn't updated alongside it.
How to diagnose it methodically

Start with the affected reservation and open it in the OTA extranet directly, noting the exact rate plan name, its meal inclusion, and its cancellation terms as the OTA has them. Then open your channel manager's mapping table for that room type and find exactly which PMS rate plan that OTA rate plan is linked to — this is usually a dedicated settings screen, not something visible from the reservation itself. If the mapped PMS rate plan's terms don't match what the OTA extranet shows, you've found the mismatch; if they do match but the reservation still came through wrong, check whether the booking was made under a newer rate plan variant that isn't in the mapping table at all.

One wrong booking is a symptom. The mapping table is where the actual mistake lives, and it will keep producing the same wrong booking until someone opens it.
Fixing the mapping, not just the reservation

Correct the specific guest's reservation in your PMS by hand so their stay reflects the terms they actually booked under — that's the immediate, guest-facing fix. Then go back to the mapping table and correct the link itself, pointing the OTA rate plan at the right PMS rate plan rather than leaving the table as it was. Check whether any other recent reservations came through under the same incorrect mapping while it was live, since a mapping error rarely affects just the one booking you happened to notice.

Keeping rate plan mappings accurate going forward
Open the specific reservation in the OTA extranet and note its exact rate plan name, meal inclusion and cancellation terms.
Check the mapping table in your channel manager for that room type, not just the reservation, to see what it's actually linked to.
Correct the affected guest's reservation in your PMS by hand first, since that's the part a guest will notice.
Fix the mapping link itself, then check recent bookings on the same rate plan for the same error.
Re-check mappings whenever you add a new rate plan or promotion on any connected OTA, not only when something goes visibly wrong.
How Prime Host stops this from happening again

Read-back verification covers rate plan pushes the same way it covers availability — when a rate or rate plan configuration is sent to a channel, the system reads back what the channel actually stored and compares it field by field against what was intended, catching a mapping gap before it has a chance to attach to a real guest's reservation. If mapping mismatches have shown up at check-in before, that verification step is the structural fix — you can see it on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Why did only some bookings on this room type come through with the wrong rate plan?
Most likely only a specific rate plan variant — a new promotion or meal-plan option — has an incorrect or missing mapping, while the main rate plan for that room type is mapped correctly.
Should I fix the reservation first or the mapping first?
Fix the guest-facing reservation first, since that affects what the guest experiences. Then fix the mapping itself so the same error doesn't repeat on the next booking.
How often should rate plan mappings be reviewed?
Any time a new rate plan, meal-plan variant or promotion is added on an OTA, and periodically alongside a routine inventory or pricing review.
Want to see all of this working for real?
Walk through the actual system in read-only mode. Nothing to fill in.

Read next

© 2026 Prime Host Partners
Privacy PolicyTerms of Service