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