When a Supplier’s Confirmation Looks Wrong, a Person Decides
A “confirmed” does not mean everything is fine; a confirmation whose numbers do not add up deserves a pause.
When a supplier confirms a booking but the status is unclear, the amount is missing, or the confirmed cost is higher than the price the guest saw, the order is no longer confirmed automatically. It waits as awaiting supplier confirmation until a person confirms or cancels and refunds, and the API reports it as pending.
The last step of a booking is the supplier saying “confirmed”. Usually that is the end of the story. Sometimes it is not: the status is unclear, the confirmation carries no amount, or the cost the supplier confirms is higher than the price the guest saw when booking. The last case is the dangerous one. The guest has paid the earlier price, while the platform now owes the supplier more.
Recording these warnings is not enough on its own; the problem simply waits for month-end reconciliation. Stopping it needs care too. Cancelling automatically sounds decisive, but the supplier booking is real and cancelling may cost a fee; that is not a call software should make on behalf of the guest and the seller.
Unclear status, a missing amount, and a confirmed cost above the price recorded at booking now each block automatic confirmation. The order stays in the existing awaiting supplier confirmation state, the reason goes to the audit trail, and a person decides whether to confirm or to cancel and refund. A confirmed cost counts as higher only when it exceeds the booking price by more than the smallest currency unit; equal or cheaper confirmations pass.
For anyone booking through the API, the booking result now says pending supplier confirmation instead of announcing “confirmed” first, and order queries show the booking as confirming until a person has decided. When a supplier legitimately raises the price after quoting, the order stops and waits as well. That is deliberate, not a side effect.