Blog›Connectivity

Trip.com Extranet Child and Extra Bed Policies: Setting Them Up Correctly

Child and extra bed charges set in the Trip.com extranet are landing wrong at booking, and this covers how the policy structure works and how to set it up so the price matches.

The Prime Host Partners team17 Nov 2026 · 7 min read

A family books a room on Trip.com, and the extra bed or child surcharge you configured either doesn't show up on the reservation or shows up at the wrong amount. Child and extra bed policies sit on top of your base rate rather than inside it, and getting the structure right in the extranet is what decides whether the booking arrives correct.

Full guide on this topic
What a broken child or extra bed policy looks like

The room rate itself comes through fine, but the reservation either shows no child or extra bed charge at all when the guest clearly booked with one, or it shows a flat total that doesn't separate into the base rate plus the extra charge your PMS expects to see. Front desk staff usually catch it when the amount quoted on arrival doesn't match what the booking confirmation implies.

This is a configuration issue, not a sync failure — the booking itself arrives normally, it's the price structure underneath it that's set up incorrectly in the extranet or doesn't match what your PMS is expecting to receive.

Why these policies are set up differently from a base rate

A standard room rate is one number tied to one rate plan. A child or extra bed policy adds a conditional layer on top — an age band for children, a flat or per-night charge for an extra bed, sometimes tied to specific room types that physically have room for one. Trip.com's extranet lets you define these per rate plan, but if the policy is defined at a level your PMS's rate plan mapping doesn't mirror, the extra charge has nowhere consistent to land, and either gets dropped or folded into the base rate as an unexplained lump.

Where this usually goes wrong
1Policy set at the wrong levelA child or extra bed rule applied to the property broadly instead of to the specific rate plan or room type it should apply to.
2Age bands not mirrored in the PMSTrip.com's child age tiers have no equivalent structure configured on your PMS side.
3Extra bed treated as a room attribute instead of a chargeSome room types allow an extra bed but the fee for it was never separately configured.
How to check the current setup

Open the exact rate plan in the Trip.com extranet and look at how its child policy and extra bed charge are configured — the age bands used, whether the charge is per night or flat, and which room types it's attached to. Compare that against a recent affected reservation in your PMS: does the breakdown show the extra charge as its own line, or is it missing, or merged into the base rate with no label. If the extranet's policy looks correct but your PMS still shows it wrong, the mapping between the two is the thing to fix, not the policy itself.

A child or extra bed charge that's wrong rarely means the guest was overcharged or undercharged on Trip.com's side — it usually means the extra line never made it into your system as its own line at all.
Setting it up so it stays correct
Open the specific rate plan in the Trip.com extranet and record exactly how its child and extra bed policy is structured.
Confirm which room types the policy applies to, since not every room type should carry the same extra bed charge.
Check whether your PMS rate plan has a matching child or extra bed structure, and build one if it's missing rather than relying on a flat total.
Re-map at the rate plan level instead of adjusting individual reservations by hand.
Test with a sample booking that includes a child and an extra bed before trusting the setup for a real guest.
How Prime Host stops this from happening again

Trip.com is connected directly, and read-back verification applies to rate plan changes including child and extra bed structures — when a policy is pushed, the system reads back what Trip.com actually stored and compares it field by field against what was intended, rather than assuming the push succeeded because it didn't error. That catches a mismatched policy before it reaches a guest's reservation. If child or extra bed pricing keeps coming through wrong, that verification step is the structural fix — you can see it on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Why does a booking with a child show no extra charge in my PMS?
Most often the age band or extra charge configured in the Trip.com extranet has no equivalent structure set up on your PMS rate plan, so the extra detail doesn't carry across.
Should extra bed charges be set per room type or for the whole property?
Per room type, since not every room physically accommodates an extra bed. Setting the policy broadly at the property level is a common cause of it applying where it shouldn't.
Is this the same issue as a rate not syncing?
No. The base rate usually syncs correctly — it's specifically the child or extra bed layer on top of it that fails to map, so the booking itself still arrives, just with an incomplete price breakdown.
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