Expedia operates as a group of brands and a collect model that differs by booking, and understanding both is the starting point before listing a property.
Expedia is often talked about as a single OTA, but for a hotel manager it's really a group of consumer brands sharing inventory through one extranet, with a payment model that can differ by booking. Understanding the shape of it first makes everything else — rates, Partner Central, payouts — easier to follow.
A property listed with Expedia typically becomes visible across a family of consumer-facing brands that share the same underlying inventory and rates, rather than appearing on a single website. From a hotel's side, this mostly matters because the reservation and rate management happens in one place — Expedia Partner Central — even though guests may have found and booked the stay through different-looking brand sites.
That shared inventory model is also why a rate or availability change made once in Partner Central applies across the brand family, rather than needing to be repeated per site.
Expedia uses what's commonly called a merchant or collect model for at least some bookings, where Expedia collects payment from the guest and later pays the hotel, net of commission, rather than the hotel charging the guest directly. Other bookings may follow a pay-at-hotel model where the guest pays on arrival and Expedia invoices commission separately. Which model applies can depend on the specific rate plan and market, so it's worth checking the booking details rather than assuming one model covers every reservation.
If you're setting up a new listing, Expedia Partner Central is where rates, availability, content and policies are managed centrally, and it's worth reviewing the current extranet help pages for the exact current steps rather than relying on older guidance, since the interface and requirements change. If you already have a listing, periodically check that your rate plans, cancellation policy and room content in Partner Central match what you intend, since changes made through a channel manager should flow through but are worth spot-checking directly in the extranet.
Expedia is one of the channels the platform connects to, and read-back verification applies the same way here as on other channels — a rate or availability push to Expedia Partner Central is read back and compared against what was intended, rather than assumed correct from a 2xx response. For supported recovery, a reservation Expedia failed to deliver can also be pulled back in. The public demo at try.primehostpartners.com includes a sample property you can look at without signing up.