Multi-mapping lets one physical room type sell under several different OTA room or rate plans at once, and understanding it prevents a surprising number of pricing mistakes.
A single room type in your PMS can be sold on an OTA under more than one listing — a standard rate, a non-refundable rate, a breakfast-included rate — each mapped separately even though it's the same physical room. This is called multi-mapping, and not understanding how it works is behind a lot of confusing rate and inventory behavior that looks like a sync bug but isn't.
Most OTAs let a property offer the same room type under multiple rate plans or sub-listings — one with free cancellation, one discounted and non-refundable, one bundled with breakfast. Each of those is usually a separate rate plan ID on the OTA's side, but they all draw from the same physical inventory of that room type. Multi-mapping is the configuration that ties every one of those rate plan IDs back to a single room type in your PMS.
This is a deliberate and common setup, not an error. The confusion comes from forgetting that several mappings are all pulling from one shared pool of rooms, not several independent pools.
Because every rate plan tied to the same room type is drawing from one inventory count, selling a room under the non-refundable rate reduces availability for the standard rate too, and vice versa — they're not independent. If your PMS or channel manager doesn't apply every change consistently across all the mapped rate plans, you can end up with one rate plan showing available while another, mapped to the identical physical rooms, shows sold out. A stop-sell applied through one rate plan's settings also needs to close every other rate plan mapped to that same room type, or the room stays sellable through the one you forgot.
In your channel manager's mapping screen, list every rate plan ID currently mapped to a given room type and confirm it matches the full list of rate plans you actually offer on that OTA for that room — a rate plan you created recently on the OTA side but never mapped will simply not receive your updates. Test a stop-sell on one rate plan and verify in the OTA's own extranet that every other mapped rate plan for the same room type also shows closed, not just the one you changed. Check pricing relationships between mapped rate plans periodically, since an update to the base rate should flow through to any rate plan defined as a percentage or fixed discount off it.
Read-back verification checks that an availability or rate change actually landed on the channel after it's sent, which matters even more with multi-mapping, since one update is supposed to affect several rate plans at once and a partial failure is easy to miss. At the database level, a physical no-double-booking guarantee protects the shared inventory pool directly, so overlapping bookings across mapped rate plans for the same room aren't possible by construction. You can see how mapped rate plans behave on the public demo at try.primehostpartners.com, without signing up.