---
title: "Hotel Rebrand / Rename Reconciliation Playbook"
description: "Preserve canonical hotel identity across name and brand changes while managing aliases, source mappings and downstream invalidation."
slug: "hotel-rebrand-rename-reconciliation"
translationKey: "playbook-hotel-rebrand-reconciliation"
locale: "en"
type: "playbook"
category: "operations"
tags: ["hotel","rebrand","rename","mapping","reconciliation"]
publishedAt: "2026-09-26"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
---

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.