Blog›Connectivity

Agoda YCS Child Policy Setup: Getting Occupancy Pricing Right

Setting up a child policy in Agoda's YCS extranet affects how occupancy and pricing are calculated for every booking on that room type, and this covers how to set it up correctly.

The Prime Host Partners team13 Nov 2026 · 7 min read

A child policy in Agoda's YCS extranet controls how children of different ages are counted against your room's occupancy and what, if anything, they're charged, and getting the setup wrong doesn't throw an error — it just quietly produces bookings that don't charge or count the way you intended. This covers how to set the policy up correctly for a room type and how to confirm it's actually working.

Full guide on this topic
What a child policy actually controls

In YCS, a child policy defines age bands and decides, for each band, whether a child counts toward your room's maximum occupancy and whether they're charged as an additional guest, a reduced rate, or free. The policy is set per room type, which means the same property can have different child rules for a family room versus a standard double, and that's deliberate rather than an inconsistency to fix.

Where this goes wrong is usually not the policy itself but a mismatch between what you intended when you set it and what it's actually doing for live bookings, which only becomes visible once a guest with children actually books.

Why the setup is easy to get subtly wrong

Age bands in YCS are defined by cutoff ages, and a child who falls right on a boundary can land in a different band than you expected if the cutoffs aren't set the way you pictured them. Occupancy counting is separate from charging — a child can be set to count toward your max occupancy without being charged anything, or the reverse, and conflating the two settings is a common source of rooms that look overbooked by occupancy even though no extra charge was applied. The policy also has to be set per room type individually, so a correct setup on your standard rooms doesn't carry over to a new room type you add later unless you configure it again.

Where child policy setup commonly goes wrong
1Age band cutoffs set differently than intendedA child right at a boundary age lands in a different band than you expected, changing both occupancy count and price.
2Occupancy counting and charging conflatedA child can count toward max occupancy without being charged, or be charged without counting — these are separate settings.
3Not replicated to new room typesThe policy is per room type, so adding a new room later starts without any child policy unless you set one explicitly.
How to verify the setup is doing what you intended

Open the child policy settings for the specific room type in YCS and read the age bands and their occupancy and charging rules exactly as configured, rather than from memory of when you first set it up. Run a test search on Agoda's guest-facing site with a sample booking that includes a child at an age near one of your cutoffs, and check how it's priced and counted. If a recent real booking with children looks wrong, pull up that specific reservation and compare its occupancy and charge against the policy as currently configured, since the policy may have changed since you last checked.

A child policy doesn't fail loudly — it just quietly applies exactly what you configured, which is only a problem if what you configured wasn't what you meant.
Setting it up correctly and keeping it that way
Read the current age band cutoffs for the room type directly in YCS, rather than assuming they match what you originally set.
Confirm separately whether each age band counts toward occupancy and whether it's charged — these are two different settings.
Run a test search with a sample child age near each cutoff to confirm the pricing and occupancy behave as intended.
Set a child policy explicitly on every new room type you add, since it doesn't carry over automatically.
Spot-check a real recent booking with children against the current policy whenever something about a reservation looks off.
How Prime Host stops this from happening again

Read-back verification applies to occupancy and rate structures as much as to plain rates — when a room type's settings, including occupancy rules, are pushed or confirmed, the system reads back what Agoda actually has configured and checks it against what was intended, catching a mismatch before it reaches a live reservation. If child policy setup across multiple room types has been a source of quiet errors, that verification step is the structural fix. You can see it on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Does a child always count toward my room's maximum occupancy?
Not necessarily — whether a child counts toward occupancy and whether they're charged are two separate settings in the child policy, and either can be configured independently.
Why would two of my room types have different child rules?
Child policy is set per room type in YCS, so this is normal and often intentional — a family room may have different rules than a standard double.
How do I confirm a child policy is actually working as intended?
Run a test search on Agoda's guest-facing site with a sample child age near each of your age band cutoffs and check the resulting price and occupancy.
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