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