Blog›Pricing

Agoda YCS Occupancy-Based Pricing: Setting Rates per Number of Guests

Setting rates that vary by the number of guests in Agoda's YCS extranet is a different mechanism from a flat room rate, and getting it wrong affects what every booking actually earns.

The Prime Host Partners team14 Nov 2026 · 7 min read

Occupancy-based pricing in Agoda's YCS lets you charge differently depending on how many guests are staying in a room, rather than one flat rate regardless of occupancy. It's a useful way to capture extra revenue from larger groups, but the setup works differently from a standard rate plan, and a mistake here tends to show up as bookings earning less — or more — than you intended, without an obvious error anywhere.

Full guide on this topic
What occupancy-based pricing changes

A standard rate plan in YCS charges the same amount for a room regardless of how many guests, up to its maximum occupancy, actually stay in it. Occupancy-based pricing instead ties the price to the specific number of guests booked, so a room sold to two guests and the same room sold to four guests can be priced differently even though it's the identical physical room and dates. This is set per room type and rate plan in YCS, not as a global property setting.

The mechanism matters because it changes what you need to check when a booking's price looks off — the question isn't whether your base rate is correct, it's whether the occupancy tier that applied to that specific booking is the one you intended.

How the occupancy tiers actually apply

In YCS, you configure a base price typically tied to a reference occupancy, then set adjustments — usually additive per extra guest — for occupancy levels above or below that reference point, up to the room's maximum occupancy. The guest count used for pricing is whatever was actually booked, not the room's maximum, so a room with a four-guest maximum booked for two guests should price at the two-guest tier, not the maximum. If a rate plan's occupancy pricing wasn't configured for every occupancy level the room type allows, a booking at an unconfigured tier can default to the base price rather than the adjusted one, which looks like a pricing error but is actually a gap in setup.

Where occupancy pricing most often goes wrong
1Missing a tierAn occupancy level within the room's allowed range was never configured, so bookings at that occupancy fall back to the base price unexpectedly.
2Reference occupancy misunderstoodThe base price is tied to a specific occupancy level, and adjustments are calculated relative to it — not to zero.
3Maximum occupancy changed after pricing was setIf the room type's maximum occupancy was edited later, occupancy pricing tiers should be rechecked against the new range.
How to verify your occupancy pricing is actually correct

In the YCS extranet, open the specific rate plan and review the occupancy pricing table for every occupancy level the room type allows, confirming each one has a deliberate price rather than an unconfigured gap. Then check a handful of recent bookings at different occupancy levels and compare the price charged against what the table says should apply for that exact guest count. If a booking's price doesn't match its occupancy tier, check whether the room type's maximum occupancy or the rate plan's tiers were edited more recently than the booking, which can explain a mismatch that isn't actually an error.

Occupancy pricing fails quietly at the gaps, not the numbers you actually set — the tier nobody configured is the one that charges the base price by default.
Keeping occupancy pricing correct going forward
Review the occupancy pricing table for every guest count the room type allows, not just the most common ones.
Confirm which occupancy level your base price is actually anchored to before setting adjustments above or below it.
Recheck occupancy pricing tiers whenever you change a room type's maximum occupancy.
Spot-check a sample of recent bookings at different occupancy levels against the configured table.
Document your intended pricing per occupancy level outside the extranet, so a gap in the table is easy to spot against your own record.
How Prime Host stops this from happening again

Read-back verification applies to rate changes including occupancy pricing structures — when a rate plan is pushed with its occupancy tiers, the system reads back what Agoda actually stored and checks it against what was intended, catching a missing tier before it reaches a live booking rather than after. Prime Shield adds the other side of the check, comparing the rate you sent, the rate you intended and what the guest actually paid, and flagging a gap worth more than 5% in plain money. If occupancy pricing gaps have cost you revenue before, that combination is the structural fix — you can try it on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Why did a booking charge the base rate instead of an occupancy-adjusted price?
Most likely that specific occupancy level was never configured in the rate plan's occupancy pricing table, so it defaulted to the base price rather than an adjustment you intended to apply.
Is occupancy-based pricing set per property or per room type?
Per room type and rate plan — it isn't a single global setting, so each room type's occupancy pricing needs to be configured and checked individually.
Does changing a room's maximum occupancy affect existing pricing tiers?
It can — if the allowed occupancy range changes, the pricing tiers should be reviewed to make sure every newly allowed guest count has a deliberate price configured.
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