A family searches Booking.com for two adults and two children, but your Greek apartment either disappears, shows no suitable room, or prices one child as an adult. The problem may not be demand or your nightly rate. It may be the way child policies, occupancy limits, age bands, and bed options are configured.
These settings are easy to treat as housekeeping details. In practice, they shape whether Booking.com can match a family to a room and calculate an appropriate total. A policy that says children are welcome does not automatically create child prices. A cot does not automatically increase the number of guests a room can accept. And a room’s physical capacity is not always the same as the number of children eligible for a special rate.
This audit is for Greek apartment, villa, and small-accommodation operators using the Booking.com extranet, a channel manager, or another connectivity provider. Exact controls vary by property type, account, contract, and software, so verify the final result in your own live search flow.
How Booking.com separates children policies from pricing
Booking.com’s official children-policy documentation separates several decisions that hosts often combine in their minds:
- Whether children are allowed at the property.
- The minimum guest age, if a restriction applies.
- The total, adult, and child occupancy of each room type.
- Age-based child rates for children using existing beds.
- Availability and charges for cots or extra beds.
The important operational point is that these elements must agree. Booking.com says child policies are reflected at room level, because different room types can accommodate different family combinations. A villa, a studio, and a family suite should not inherit the same assumptions simply because they belong to one property.
Mistake 1: Children are allowed, but no child rates exist
“Children allowed” answers an eligibility question; it does not necessarily answer a pricing question. Booking.com’s documentation states that when a property does not expose child-rate bands, children can be treated as adults for pricing. That can be a deliberate commercial choice, but it should not happen by accident.
For each room, write down what you actually intend:
- All children pay the adult price.
- Children in specified age bands stay free in existing beds.
- Children receive a fixed or percentage-based price.
- Only a limited number of children receive the child price; additional children are priced differently.
Then search the property using the exact ages. Do not test only “two adults and one child,” because age is part of the request. A four-year-old and a sixteen-year-old may legitimately produce different results.
Mistake 2: Physical capacity and child-price eligibility are confused
A room can physically hold four guests without offering a child price to all four. Booking.com’s occupancy examples distinguish the total number of guests the room can accept from the number of children eligible for child pricing.
Consider a Greek island apartment with one double bed and one sofa bed. The operator may intend a maximum of four guests: up to two adults and two children. If the room-level configuration allows four total guests but only one child-rate slot, a search for two adults and two children may price the second child as an adult. That is not necessarily a platform error; it can be the result of the configured limits.
Audit three numbers for every room type:
- Maximum total guests physically permitted.
- Maximum adults permitted.
- Maximum children permitted and, separately, how many qualify for child rates.
Do not inflate capacity to appear in more searches. The configured occupancy must remain consistent with real beds, safety, licensing, insurance, building rules, and the guest experience.
Mistake 3: Age bands leave gaps or create unintended adult pricing
Child pricing can be divided into age bands. Booking.com’s connectivity guidance says age ranges are inclusive and should not overlap. For example, a host might use 0–3, 4–12, and 13–17, with different pricing in each band.
Review the boundary ages, not only the middle of each band. Test ages 3 and 4, 12 and 13, and 17. If the commercial policy says children up to age five stay free, confirm exactly what happens on the child’s fifth and sixth birthdays. Clear boundaries reduce disputes at check-in and prevent the booking total from contradicting the property’s message.
Do not advertise “kids stay free” without stating the qualifying ages, number of children, room type, and bed arrangement. Booking.com notes that a free-stay indicator is distinct from the broader child-rate setup and still interacts with occupancy limits.
Mistake 4: Cots and extra beds are treated as ordinary occupancy
Cots, rollaways, and sofa beds are not interchangeable fields. Booking.com lets properties state whether cots and extra beds are available, whether they are free or paid, and how many can be provided. Child rates described in the official guidance apply to children staying in existing beds, not automatically to cots or extra beds.
For every family room, verify:
- Which sleeping surfaces count as existing beds.
- How many cots and extra beds can genuinely fit.
- Whether advance confirmation is required.
- Whether the fee is per night, per stay, or included.
- Whether the bed description, room photos, and guest messages say the same thing.
A small Athens studio may technically have a cot available but lack safe circulation space when it is installed. A Halkidiki villa may have several sofa beds but need clearer room allocation. Configure what the room can deliver consistently, not the highest theoretical headcount.
Mistake 5: Minimum-age and adults-only rules contradict the listing
A property can allow children generally while imposing a minimum guest age, or it can operate as adults-only. Booking.com’s official examples identify the minimum-guest-age policy as the reliable indicator for adults-only eligibility in its accommodation data.
Check for contradictions across the property description, house rules, room policies, and booking flow. If a property does not accept young children because of an unfenced pool, steep stairs, or another genuine constraint, state the rule accurately without implying a level of safety that has not been professionally assessed. If families are welcome, make sure an outdated minimum-age field is not silently excluding them.
The five-search family pricing test
After reviewing the extranet or connectivity settings, test the guest-facing result. Use future dates with normal availability and search the same room using at least these combinations:
- Two adults and one infant.
- Two adults and one child at the highest free-stay age.
- Two adults and two children in different age bands.
- One adult and two children.
- The maximum intended family occupancy for the room.
Record whether the room appears, the total price, the room allocation, the child-policy wording, and any cot or extra-bed charge. Compare the result with the property’s intended policy. If the room disappears, do not assume the platform is suppressing the listing; first check age restrictions, adult/child allocation, total capacity, bed rules, and availability.
Booking.com’s troubleshooting guidance warns that allocation mismatches and guest limits can affect recommendations or booking previews. A channel manager may also be involved, so capture the test dates, guest ages, room, rate plan, and screenshots before asking support to investigate.
Check how child pricing interacts with promotions
Once the base family price is correct, inspect promotions separately. Genius, mobile rates, country rates, and campaigns can change the final amount depending on eligibility and setup. Do not use a discount to compensate for a broken occupancy configuration.
Start with the base scenario, then repeat one or two family searches under the active promotional conditions. Our Booking.com discount-stacking audit for Greek hosts provides a framework for checking the combined revenue effect. If you are evaluating Genius specifically, use the Booking.com Genius decision guide to separate visibility questions from net-rate questions.
Channel managers need a source-of-truth decision
Decide where child policies are maintained: the Booking.com extranet, the property-management system, or the channel manager. Editing the same field in multiple systems without understanding the connection can cause overrides or stale values.
Ask the software provider which child-policy, room-occupancy, cot, extra-bed, and age-band fields it sends to Booking.com. Booking.com’s current connectivity documentation says properties can manage policies through the extranet when their integration does not implement the relevant API. It also notes that a legacy content endpoint is scheduled to be fully sunset on December 31, 2026, so connectivity providers using it should be migrating to newer modular APIs. That technical change matters to software providers more than individual hosts, but professional managers should confirm their system’s roadmap.
After any mapping change, repeat the guest-facing test. A successful synchronization message is not proof that a family sees the intended room and total.
A monthly Booking.com child-policy audit
Add these checks to the revenue and content calendar:
- Confirm whether children are allowed and whether a minimum age applies.
- Review every room’s total, adult, and child occupancy.
- Verify child-rate slots and every age-band boundary.
- Check cot, rollaway, and sofa-bed availability and charges.
- Run the five family searches and record the displayed totals.
- Test active promotions only after the base price is correct.
- Confirm which connected system owns each setting.
- Update room descriptions and guest messages when the policy changes.
This audit complements a broader listing review. If the configuration is correct but family searches still convert poorly, work through the 30-day Booking.com improvement plan for Greece, focusing on accurate content, availability, pricing, and operational reliability rather than promises of guaranteed ranking.
Accurate family pricing is a conversion and trust issue
A Greek property does not need the cheapest child rate to compete for family bookings. It needs a result families can understand and a room that matches what they selected. The adult count, child ages, room capacity, age bands, beds, and fees must tell one coherent story.
Fix the policy before adding the promotion. Test real family combinations before peak dates. And when the displayed result differs from the intended price, diagnose occupancy and allocation before blaming demand. That discipline protects revenue while giving guests a clearer, more dependable booking experience.
