Trip.com eBooking: Content Requirements Before Rates Even Matter

A rate is worthless on a listing that has not cleared content review. These are the blocks Trip.com asks for, and the order that gets you live fastest.

Last updated: September 25, 2026

Content review is a gate, and it sits upstream of pricing. A listing that hasn't cleared it doesn't appear in search, so whatever rate you've built for it is a number in a form nobody can buy. Hosts lose weeks here, not because any single block is hard, but because they fill blocks in an order that makes one rejection undo the rest.

This guide sets out the three blocks a listing is reviewed against, what goes in each, and the submission order that keeps a rejection local instead of global. Which fields exist, how many photographs are asked for and how long review takes differ by market and change over time — check the platform's current terms and your local authority rather than treating anything below as a fixed rule.

Key Takeaways

• Content is checked before rates. A rate attaches to a room type, and a room type has to be approved first.
• Three blocks, reviewed apart. Property, media and policy can each pass while another fails.
• Room types carry everything. Capacity, bedding and photographs hang off them, and so does the rate.
• A claimed amenity is a promise. If the photograph doesn't show it, you've created a dispute, not a feature.
• Submit upstream first. Address before room types, room types before photos, photos before rates.

What 'content complete' means on Trip.com, and why it is checked before pricing

"Content complete" is a lower bar than most hosts assume. It doesn't mean the listing reads well or photographs beautifully. It means every block that the page needs to function has something in it that passes review. A sparse listing can be complete. A gorgeous one can be incomplete, and it'll sit just as invisible.

The three blocks are the property block — what this thing is, where it is, and what's inside it; the media block — the photographs that carry the page; and the policy block — the terms a guest actually buys under. They're reviewed separately, which is why a host can hear "approved" on one part and be blocked on another without any indication of which.

The reason pricing comes last is structural rather than bureaucratic. A rate attaches to a room type. A room type has to have a capacity, a bed configuration and a set of photographs before it can be approved. So the sequence isn't a preference the platform has about workflow; it's the order the objects depend on each other in.

Worth separating two ideas that get conflated. Passing content review makes a listing sellable. It doesn't make it competitive. Hosts who treat the gate as the finish line end up live and invisible, which feels worse than being rejected — at least a rejection tells you what to fix.

The property blocks: address, room types, amenities and the photographs that carry the page

The address. It has to resolve to the place a guest will actually arrive at. A pin that lands three streets away is the most common reason a listing gets pulled after going live, and it's also the one guests complain about first. Where a city requires a registration number in the advertisement, that field belongs in this block, and the requirement comes from the local authority rather than from the platform. Which cities require what changes constantly, so treat that as inferred and confirm it locally.

Room types. Each room type is its own sellable unit with its own capacity, bed configuration and size. Rates attach here, not to the listing as a whole. Get the capacity wrong and you've built a rate for a unit that can't legally hold the number of people it's sold to — a problem that surfaces at check-in, when it's expensive.

Amenities. This list is what the filters run on, and it's the block most hosts over-claim. Ticking a box is a promise about the unit, not a marketing choice. An amenity that's claimed and then not shown in any photograph is the classic setup for a guest arriving with an expectation you didn't mean to create.

Photographs. They carry the page, and they're checked for the boring things first: enough of them, in focus, obviously of the unit being sold. What review looks for and what sells are different questions. Review checks that the photographs are of this property. Guests check whether there's a shot of the thing they care about — the bed, the bathroom, the window, the way in.

The policy blocks: cancellation, children, pets and the payment terms guests actually read

Cancellation. Write it as a schedule, not as a sentence. Free until a stated point, then a stated charge, then a stated charge for a no-show. Vague wording is what turns a cancellation into an argument, because both sides read it generously. And it has to match the rate plan it's attached to — a mismatch here is the same failure described in rate type mapping, arriving from the other direction.

Children. The questions are narrower than hosts expect: what age counts as a child, whether infants count toward the occupancy cap, whether an extra bed is available and what it costs. A listing that's silent on the first two will get bookings it can't honour, and a listing that's silent on the third gets an argument at check-in.

Pets. Allowed or not, and if allowed, what size, how many, and whether there's a fee. This block generates a disproportionate number of disputes, almost always because "pets allowed" appears on one screen while a fee or a size limit sits somewhere the guest never opened.

Payment terms. When the guest is charged, whether a deposit is held, what currency the figure is in, and what's included in the number they see. Guests read this block far more carefully than hosts believe. A nightly rate that excludes a mandatory charge reads as a lower rate on the search page and a worse one at checkout, and that gap is what produces the complaint.

The thread through all four is that these are the terms the guest buys under. Whatever's written here is what you sold, regardless of what your own calendar says. Airbnb, Booking.com, Agoda and Trip.com sit on one calendar at localsbnb.com, each showing the rate and status it's holding — which is how you notice that one channel is quoting a cancellation line you didn't write.

The order to submit them so one rejection does not reset the whole listing

Submit upstream blocks before downstream ones. That's the whole rule, and it's worth being explicit about what it means here.

First, the address and whatever registration your locality requires. Nothing downstream can be approved against an address that's being changed. Lock it.

Second, room types, with capacity and bed configuration. Photographs and rates both hang off these. Define them once, correctly, and leave them alone.

Third, photographs, attached to the room types you just defined. Attach them to a room type that later gets renamed or re-sized and you'll re-trigger review on that type — the reset hosts mistake for a random rejection.

Fourth, amenities. Fill this last among the property blocks, because it should describe what the photographs already show. Claim what you can evidence.

Fifth, policies. They reference the room types and the payment terms, and they're the block most likely to be read by a guest rather than a reviewer.

Last, rates. By this point every object they attach to has been approved, so a rate change doesn't send anything back into review.

Two habits make this cheaper. Submit in batches and wait for each to clear rather than editing five blocks at once — an edit to a block under review restarts that block's clock. And keep your own copy of what you submitted, because when something comes back you'll want to compare against the version that was accepted, not the one you remember.

FAQ

My rates were already set and the listing still got rejected. Why?

Because rates aren't what was reviewed. Content review checks the blocks a rate attaches to, and a rejected room type or address carries the rate down with it. Look upstream of the rate.

Do the photographs have to be of the exact unit?

Yes. Photographs of a similar unit, or of a show unit, are the fastest route to a listing being pulled after it goes live — which is worse than a rejection, because by then guests may already have booked.

How long does content review take?

It varies by market and by how complete the submission is, so I won't give a number. What makes it long is nearly always an incomplete submission being edited while it's under review. Submit complete, in order, and wait.

A rate you can't sell is a number in a form. Clear the property blocks, then the photographs, then the policies, and only then set the rate — and do it in that order, because the objects depend on each other in that order. Four channels on one calendar at localsbnb.com, each showing the rate and status it's holding, is the quickest way to see whether the listing you just finished is actually live everywhere you think it is.

---

Which content fields exist, how many are required and how review is sequenced differ by market, property and platform, and change over time; this is general guidance rather than platform policy advice. Confirm against that platform's current terms and, where a registration or advertising requirement applies, your local authority.