A refused booking can come back
A push refused at the door — a key that did not match, a hotel not yet mapped — is kept whole and applied from the log once the cause is fixed.
On one morning a channel sent four bookings and the hotel refused all four, because a key had been changed on one side and not the other. Every product refuses things; the question is what it keeps.
What is kept
Every knock at the door — not only the ones we opened. The whole payload, the time, the reason for the refusal. A body that fails to parse is still stored, so it can be read afterwards rather than lost with its error.
What can be done
Once the cause is fixed, the refused push is applied from the log — the same code path as a live push, with the same guest matching, the same room allocation, the same price handling. The guest is on the chart with the channel's original reference, and the log says it was applied late and by whom.
Where else this applies
An order pushed by a food aggregator with an item the outlet had not mapped is refused naming the item, kept whole, and applied once the item is mapped.