Setting up occupancy-based pricing in Expedia Partner Central has a few sync pitfalls specific to how per-guest pricing maps to your PMS, and this walks through avoiding them.
Occupancy-based pricing lets you charge differently depending on how many guests are in the room, which is useful for small hotels with mixed leisure and group demand, but it adds a layer of structure that has to map correctly between Expedia Partner Central and your PMS. This covers the setup and the specific points where that mapping tends to go wrong.
Instead of one flat rate per room type regardless of how many guests are staying, occupancy-based pricing sets a different price depending on the number of adults, and sometimes children, booked into that room. In Expedia Partner Central, this is configured at the rate plan level, and the structure has to be mirrored correctly in your PMS for the final booking to reflect the right price for the actual occupancy a guest selected.
This is a different setup from a simple per-room-type rate, and it's worth treating it that way rather than assuming your existing rate plan mapping will handle it without changes.
The most common failure is a PMS rate plan that only has a single price configured per room type, with no equivalent per-occupancy structure, so when Expedia sends a booking at a lower two-person rate or a higher four-person rate, the PMS either defaults to its single stored price or misreads the occupancy entirely. A second common issue is that occupancy pricing set up after the rate plan was first mapped doesn't automatically retrofit into that existing mapping — it needs to be added deliberately. A third is that the number of adults Expedia allows for a room type doesn't match the maximum occupancy configured in your PMS, which can cause a booking to arrive with an occupancy count your system doesn't expect.
In Expedia Partner Central, open the specific rate plan and note exactly how occupancy pricing is structured — the price per occupancy level and the maximum guests allowed. Then check the equivalent rate plan in your PMS and confirm it has the same occupancy tiers configured, not just a single price. Run a test booking at more than one occupancy level if your PMS allows it, and confirm each one arrives with the correct price rather than defaulting to the base rate.
Read-back verification covers rate plan changes including occupancy structure — when a rate plan is pushed to Expedia Partner Central, the system reads back what was actually stored and compares it field by field against what was intended, catching a mapping gap before it reaches a guest's booking. If occupancy pricing keeps producing mismatched totals, that verification step is the structural fix — the public demo at try.primehostpartners.com is open to try without signing up.