Blog›Pricing

How to Set Up Multiple Occupancy Rates (OBP) Without Breaking Channel Sync

Setting rates per number of guests sounds simple until the structure fails to map correctly to a channel, and this walks through setting up occupancy-based pricing without that breaking.

The Prime Host Partners team20 Nov 2026 · 7 min read

Occupancy-based pricing — charging a different rate depending on whether one, two or more guests are staying — is a reasonable way to price a room, but it's also one of the more common places where a rate structure maps correctly in your PMS and incorrectly on a channel. Setting it up well means thinking about the mapping from the start, not fixing it after a wrong booking arrives.

Full guide on this topic
What occupancy-based pricing actually requires

Instead of one flat price per room type, occupancy-based pricing (OBP) sets a base rate for a standard occupancy — often double — and then a defined adjustment, usually a surcharge or discount, for each additional or fewer guest. That structure has to exist both in your PMS's rate plan and, separately, in the configuration each connected channel uses, and the two don't automatically stay in agreement just because they were both set up correctly on their own.

Done well, a guest booking for one person pays less than the double-occupancy base, and a guest adding a third person pays the defined surcharge — consistently, across every channel the room is sold on.

Where OBP setups commonly go wrong

A rate plan can be built with occupancy adjustments in your PMS, then mapped to a channel that either doesn't support the same granularity, or supports it but needs it configured separately on its own side rather than inheriting the PMS structure automatically. If a channel's occupancy increments don't match what your PMS expects — for example your PMS allows single, double and triple, but the channel's rate plan is only built for double — the mismatch either gets flattened to the nearest supported occupancy or silently dropped on that reservation.

Where the OBP mapping usually breaks
1Mismatched occupancy incrementsYour PMS supports more occupancy tiers than the channel's rate plan was actually built to handle.
2Channel-side config not mirroredThe occupancy adjustment exists in your PMS but was never separately configured in the channel's own extranet rate plan.
3Base occupancy assumption differsYour PMS assumes a double-occupancy base while the channel's rate plan defaults to single, shifting every calculation by one tier.
How to verify the setup before it goes live

After configuring OBP in your PMS, open the equivalent rate plan directly on the channel's extranet and check that the same occupancy tiers and adjustments exist there, not just that the mapping is pointed at the right rate plan ID. Then run test bookings at each occupancy level you actually offer — single, double, triple, however many you support — and confirm the price shown to the guest matches what you configured, not just that a booking goes through without an error.

An occupancy structure that's correct in your PMS and unconfirmed on the channel is only half built — the channel doesn't inherit logic it was never separately told about.
Keeping the OBP setup correct over time
Build the occupancy-based rate structure in your PMS, then separately confirm the same tiers exist in the channel's own rate plan configuration.
Check the channel's base occupancy assumption matches your PMS's, since a one-tier mismatch shifts every calculation.
Run a test booking at every occupancy level you offer and confirm the guest-facing price matches your intended structure.
If a channel doesn't support the same number of occupancy tiers, decide deliberately how to collapse them rather than letting it happen by default.
Recheck the mapping any time you add a new occupancy tier or change an existing surcharge.
How Prime Host stops this from happening again

Read-back verification covers rate plan structure the same way it covers a simple rate change — when an occupancy-based rate plan is pushed, the system reads back what the channel actually stored, tier by tier, and compares it to what was intended, instead of assuming a successful push means the full structure landed correctly. If OBP mismatches have produced a wrong price at the front desk before, that verification step is the fix — the public demo at try.primehostpartners.com is open to try without signing up.

Frequently asked
Why did a single-occupancy booking come through at the double-occupancy rate?
Most likely the channel's rate plan either wasn't configured with the same occupancy tiers as your PMS, or its base occupancy assumption didn't match, shifting every calculation by one tier.
Does every channel support the same level of occupancy-based pricing detail?
No — some support finer tiers than others. Check each channel's own rate plan configuration rather than assuming it will mirror your PMS automatically.
What's the fastest way to catch an OBP mapping error before a guest does?
Run a test booking at every occupancy level you actually sell and compare the guest-facing price against your intended structure before relying on it for real reservations.
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