Blog›Connectivity

Expedia Booking Not Received by Your PMS: Where It Went

A guest has an Expedia confirmation but the reservation never shows up in your PMS, and this covers the usual reasons and the steps to recover the booking before the guest arrives.

The Prime Host Partners team13 Nov 2026 · 7 min read

A guest contacts you with a confirmed Expedia itinerary number, but a search of your PMS for that date and name turns up nothing. The booking is real on Expedia's side, which makes this unsettling rather than a simple data-entry question, and the priority is getting the reservation into your system correctly before it turns into a walk-in surprise.

Full guide on this topic
What this looks like when it happens

A guest arrives or calls quoting an Expedia itinerary number and a rate, you search your PMS by name, date and reference, and nothing matches. The room may still show as available in your calendar, or in a worse version of this problem, it's already been sold to someone else because your system had no reason to think it was taken.

This differs from a reservation that's simply slow to sync — those eventually catch up once a scheduled update processes. A booking that was never received tends to stay missing indefinitely, because the message that should have created it never reached your system in a form it could act on.

Why a confirmed Expedia reservation can fail to reach your PMS

Mapping is the most common cause: Expedia sends the reservation tagged to a specific room type and rate plan ID, and if that ID has no matching item configured in your PMS or channel manager, the message has nowhere valid to land and is dropped or logged as an error that often isn't surfaced clearly. The connection between Expedia and your channel manager can also drop — an expired authorization, a token needing renewal, or a temporary outage — which stops new reservations from arriving at all, not just this one. Less often, the specific delivery of this one reservation's notification fails even though the booking is genuinely confirmed and paid for on Expedia's side, which is exactly why the guest's confirmation is completely real while your system shows nothing.

The usual causes, in the order to check them
1Mapping breakA room type or rate plan on Expedia has no matching ID configured in your PMS, so the reservation has nowhere valid to go.
2Dropped connectionThe link between your channel manager and Expedia has expired or disconnected, stopping all new reservations, not just this one.
3Single delivery failureThe connection and mapping are both fine, but this specific reservation's message failed to deliver and was never retried.
How to check which one happened

Open Expedia Partner Central first and pull up the reservation directly, confirming the room type, rate plan, dates and status — that's the version of the truth you're trying to match in your own system. Check your channel manager's activity or error log for that date range, since most will log a mapping failure or connection issue even if it isn't displayed prominently on the main dashboard. If other recent Expedia bookings have arrived normally, the issue is most likely mapping specific to this room type or rate plan. If nothing recent has come through from Expedia at all, suspect the connection itself and check whether it needs reauthorizing.

A missing booking almost always has a specific, findable cause — the risk is only in not checking before the guest is already standing at the front desk.
Recovering the booking and preventing a repeat
Pull the reservation details directly from Expedia Partner Central so you have the exact dates, room type and rate to enter manually.
Create the booking in your PMS by hand and block the room immediately, before doing anything else.
Check your channel manager's mapping for that room type and rate plan and correct any ID that doesn't match Expedia's side.
If no recent Expedia bookings have arrived at all, check whether the connection needs reauthorizing.
Keep the itinerary number on file in case Expedia support needs it to confirm the original booking existed.
How Prime Host stops this from happening again

Automatic recovery of a reservation a channel failed to deliver is available for supported channels, including Expedia, so a booking like this one can be pulled in rather than left for someone to find manually at the front desk. Read-back verification covers the connection itself — mapping changes and new connections are checked against what the channel actually confirms, so a mapping break is more likely to be caught before it causes a missing reservation. If a missing booking has caused a guest surprise before, that combination is the structural fix — you can see it on the public demo at try.primehostpartners.com without signing up.

Frequently asked
Why does Expedia show the booking as confirmed if my PMS never received it?
Expedia's confirmation to the guest — their payment and itinerary — is independent of whether the reservation message was successfully delivered to and accepted by your PMS. The two only agree once that message arrives and maps correctly.
Is the room still available if this happens?
Not necessarily. If your calendar shows it open because the booking never registered, another reservation or a walk-in could already occupy it. Check and block the room as soon as you find the mismatch.
Can a missing Expedia reservation be recovered automatically?
For supported channels, including Expedia, yes — a connectivity layer can pull in a booking the channel failed to deliver rather than requiring a fully manual recovery every time.
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