Blog›Connectivity

Expedia Connection Guide: Connecting Partner Central to a Channel Manager

Connecting Expedia Partner Central to a channel manager has a specific setup order, and following it correctly the first time avoids mapping problems once reservations start arriving.

The Prime Host Partners team14 Nov 2026 · 8 min read

Linking Expedia Partner Central to a channel manager is what lets rates, availability and reservations flow automatically instead of being managed by hand in the extranet. The connection itself is usually a short authorization step, but the setup around it — room and rate plan mapping especially — is where most of the actual work and most of the risk of a mistake sit.

Full guide on this topic
What the connection process actually involves

Connecting Expedia to a channel manager generally means authorizing the channel manager to act on your Partner Central account, then mapping each of your Expedia room types and rate plans to the matching items in your PMS or channel manager, one by one. The authorization step itself is usually quick. Mapping is the part that takes care, because every room type and rate plan on Expedia's side needs a correct, specific match on your side — there's no reliable way to connect a channel generically and have it figure out the mapping on its own.

Properties with multiple rate plans per room type — different cancellation policies, for instance, sold as separate plans — have proportionally more mapping to get right, since each one needs its own correct link.

Why mapping is where connections usually go wrong

A room type or rate plan ID on Expedia's side is just an identifier — it has no meaning to your PMS until it's explicitly linked to the matching room type and rate plan on your side. If a room type is mapped to the wrong equivalent, or a rate plan is left unmapped entirely, reservations for that specific type can arrive with the wrong room assigned, or fail to arrive at all because there's nowhere valid for the message to land. This is more likely to happen on properties with similarly named room types, since it's an easy mistake to map two different categories to each other by name alone rather than by checking occupancy and amenities too.

What to check carefully during mapping
1Every rate plan, not just every room typeA room type can be mapped correctly while one of its rate plans is still missing or mapped to the wrong item.
2Occupancy and amenities, not just the nameSimilarly named room types on either side can still be different categories — check the actual attributes, not the label.
3New room types added after the initial connectionA room type created on Expedia after the first mapping pass needs to be mapped separately — it won't inherit a connection automatically.
How to verify the connection and mapping are correct

After authorizing the connection, go through each room type in Expedia Partner Central and confirm it's mapped to the matching room type in your channel manager, checking occupancy and bed configuration against the name rather than trusting the label alone. Do the same for every rate plan under each room type. Once mapping looks complete, push a test rate or availability change from your channel manager and confirm it's reflected correctly in Partner Central, then check that a real reservation for each mapped room type arrives in your PMS as expected.

The authorization is the easy part of this connection — the mapping underneath it is where a connection that looks successful can still send every reservation to the wrong place.
Setting the connection up without early mistakes
Authorize the channel manager's access to Partner Central first, before attempting any mapping.
Map every room type individually, checking occupancy and amenities rather than relying on matching names.
Map every rate plan under each room type separately — a room type being mapped doesn't guarantee its rate plans are.
Push a test rate and availability change after mapping and confirm it reflects correctly in Partner Central.
Map any room type added to Expedia after the initial connection — new additions don't inherit mapping automatically.
How Prime Host stops this from happening again

Read-back verification checks every rate and availability update against what Expedia Partner Central actually stores after it's sent, which surfaces a mapping mistake as a mismatch rather than letting it look successful because the request didn't error. For supported channels, including Expedia, a reservation the connection failed to deliver during setup or afterward can also be recovered rather than lost. You can walk through the mapping screens yourself on the public demo at try.primehostpartners.com, including a 44-room and a 500-room sample property, without signing up.

Frequently asked
Does connecting Expedia to a channel manager automatically map my room types?
No — authorization and mapping are separate steps. Each room type and rate plan needs to be matched individually to the corresponding item in your PMS or channel manager.
What happens if a rate plan is left unmapped?
Reservations for that specific rate plan may not arrive correctly, or may not arrive at all, since there's no valid destination for the message once it reaches your system.
Do new room types added later need to be mapped separately?
Yes — a room type created on Expedia after your initial connection and mapping pass needs its own mapping step. It won't connect automatically just because the channel link already exists.
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