Hotel Rebrand / Rename Reconciliation Playbook
Preserve canonical hotel identity across name and brand changes while managing aliases, source mappings and downstream invalidation.
During a rebrand, do not create a new canonical hotel merely because the display name changed. First prove whether physical property identity continued.
Trigger and evidence
Supplier name/brand changes or old/new names coexist. Compare canonical/source IDs, address, geo, phone, website, brand history, effective dates and provider observations.
Decision
If physical property continuity remains, treat the change as rename/rebrand. If the property split, moved or became a distinct operation, consider a new/split entity.
Implementation
Add aliases, update display attributes using source confidence/freshness, preserve source mappings and invalidate search indexes/caches.
Failure modes
Avoid duplicate canonical creation, fragmented historical analytics, lost source IDs and treating brand identity as property identity.
Metrics and prevention
Track rebrand duplicates, alias hits, mapping continuity and reversals. Model names as attributes/events rather than permanent identity.
Planning a similar integration?
We can review requirements, feed/API design and the production approach with you.