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.
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.
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.
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.
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.
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.