ADR-007 — Tenant-Wide Customer Identity and Cross-Business-Unit Orders¶
Status: ACCEPTED / FROZEN — Foundation v1.0
Context¶
A single Tenant may operate Hotel, Spa, Restaurant, Vehicle Rental, Yacht Charter and other Business Units. Modeling customers or orders as permanently bound to one Business Unit would duplicate customer identities and make bundled experiences difficult to support.
Decision¶
Customer identity¶
Customer identity is Tenant-wide.
A person interacting with multiple Business Units of the same Tenant is represented by one tenant Customer identity/profile, subject to identity resolution/deduplication rules defined later.
Staff authorization may restrict which Business Unit interactions or sensitive customer data a staff member may access.
This does not create a cross-Tenant customer record.
Orders¶
An Order is Tenant-scoped and may contain Order Lines belonging to multiple Business Units of that same Tenant.
Orders never span Tenants.
The first product release may expose narrower single-Business-Unit checkout experiences while retaining this domain capability.
Consequences¶
- CRM can build one tenant customer timeline across Business Units.
- permissions must separate identity scope from staff visibility scope;
- Commerce must not encode a permanent one-Order-to-one-Business-Unit invariant;
- bundles such as Hotel + Transfer + Spa + Yacht can be supported later without redesigning the Order boundary;
- cross-Business-Unit settlement/tax/fulfillment rules remain future design work, not reasons to change the aggregate scope.