# Supersede

Source: https://lemon.cy/glossary/supersede/  
Publisher: Lemon.cy (Red Tribe Media Ltd, Limassol, Cyprus)  
Updated: 2026-09-10 · Verified against production: 2026-09-10

**Short answer:** When a genuinely new reservation replaces one or more now-cancelled stays inside a single Booking.com block, as opposed to a merge of stays that are all still live. Lemon decides between the two by parsimony and, when unsure, asks the host.

The same widened block can mean two opposite things. Either the stays Lemon already tracks are still real and the OTA merged them (protect them), or those stays were cancelled and a new reservation now occupies the range (track the new one, release the old). The feed cannot say which.

Lemon's classifier prefers the explanation that requires fewer coincidences: explaining a block as a merge would require several brand-new, perfectly chained reservations to appear within one five-minute sync. When the block is classified as a supersede, it is consolidated into one `pending_review` booking under the real UID and the stale stays are allowed to cancel normally. When the classifier cannot decide, nothing automatic happens — the host is asked.

## Related

- [Merged block](https://lemon.cy/glossary/merged-block/)
- [Reshape](https://lemon.cy/glossary/reshape/)
- [Uncovered nights](https://lemon.cy/glossary/uncovered-nights/)