Agoda is showing a reservation as failed or pending while your inventory already looks sold, and this explains what each status actually means and what to check before you release the room.
Agoda's extranet uses several different in-between statuses for a reservation that hasn't cleanly confirmed — failed, pending payment, or sold with no guest details yet. Each one means something different for whether you should hold the room or release it, and mixing them up is how rooms get double-sold or sit blocked for a guest who was never actually coming.
A reservation marked “failed” on Agoda generally means the reservation attempt did not complete — most often a payment authorization issue on the guest's card — and no valid reservation exists for you to honor. A booking still marked “pending” is different: Agoda has accepted the request but the payment or guest confirmation hasn't finished processing, which can take anywhere from a few minutes to longer depending on the payment method used. The dangerous middle case is when your PMS or channel manager already reduced your available inventory for a booking that Agoda itself has not finished confirming.
This matters because inventory and reservation status are not the same system. Inventory — how many rooms you have left to sell — can move the instant a request comes in, while the reservation's actual status can lag behind or resolve differently than expected.
Most connectivity setups decrement your available room count as soon as a booking request is created, not once it is fully confirmed, because the alternative — waiting to react until confirmation — risks overselling in the gap. That is a sensible default, but it means a failed-payment booking can still have held a room in your calendar for the minutes or hours before it resolves. If your channel manager doesn't automatically restore that inventory when Agoda marks the booking failed, you are left holding a room closed for nobody.
Open the specific reservation in the Agoda extranet and read its current status directly — do not rely on what your PMS calendar shows, since that is a downstream copy that may not have updated. If the extranet says failed, check your channel manager's inventory for that date and room type and confirm the room count went back up; if it didn't, that is the actual bug to fix, not the booking itself. If the extranet still says pending, give it a reasonable window before assuming it failed, since some payment methods take time to clear.
This is exactly what read-back verification is built for: every availability change the system makes is read back from the channel and compared against what was intended, instead of trusting that a request was accepted just because it didn't error. When a failed or reversed booking should free up a room, the system checks that the room actually shows open again rather than assuming it. If this kind of stuck-inventory problem keeps costing you rooms, that structural check is the fix — you can open the public demo at try.primehostpartners.com and see it without signing up.