Customer Registration · Unified Customer Onboarding¶
A new customer creates a unified identity that can be recognised consistently across digital and physical channels. The registration flow captures identity, profile, and consent data while optionally enrolling the customer into loyalty at the same time.
| Domains | customer |
| Actors | customer · store-associate · system |
| Process | Customer Registration |
| Capabilities | 4 |
| Steps | 7 |
| Events | 9 |
| Lifecycles | 3 |
| Min UCMI | 2.5 |
⚙️ Step-by-Step Flow¶
| # | Step | Actor | Lifecycle | State Change | Event |
|---|---|---|---|---|---|
| 1 | Start registration | customer | customer-lifecycle |
→ prospect | customer-created |
| 2 | Verify identity and create account | system | customer-lifecycle |
prospect → active | customer-identified · customer-registered |
| 3 | Capture profile attributes | customer | customer-lifecycle |
active → active | customer-profile-updated |
| 4 | Record consent selections | customer | consent-lifecycle |
draft → recorded | consent-recorded |
| 5 | Activate consent status | system | consent-lifecycle |
recorded → active | customer-consent-updated |
| 6 | Enrol loyalty membership | system | loyalty-member-lifecycle |
→ enrolled | loyalty-member-enrolled |
| 7 | Activate welcome benefits and send confirmation | system | loyalty-member-lifecycle |
enrolled → active | loyalty-benefits-calculated · customer-communication-sent |
⚡ Event Sequence¶
customer-created → customer-identified → customer-registered → customer-profile-updated → consent-recorded → customer-consent-updated → loyalty-member-enrolled → loyalty-benefits-calculated → customer-communication-sent
🔄 Lifecycles Involved¶
🧩 Capabilities Required¶
| Capability | |
|---|---|
customer-identity |
Customer Identity |
customer-profile |
Customer Profile |
customer-consent |
Customer Consent |
loyalty |
Loyalty |
🖥️ Application Coverage¶
Applications that implement the capabilities required by this scenario.
| Capability | Implementing Applications |
|---|---|
customer-identity |
POS · eCommerce Platform |
customer-profile |
Clienteling App · CRM |
customer-consent |
CRM |
loyalty |
Loyalty Platform |
📊 Readiness by Profile¶
Capability readiness across assessment profiles.
| Profile | Capabilities Met | Avg Score | Ready? |
|---|---|---|---|
| Acme Electronics | 2/4 | 1.5 | ❌ |
| BuildPro Trade | 4/4 | 1.8 | ❌ |
| Flash Delivery | 1/4 | 1.0 | ❌ |
| Luxe Maison | 4/4 | 3.0 | ✅ |
| Metro Fresh Group | 2/4 | 1.5 | ❌ |
| Stella Fashion Group | 4/4 | 2.5 | ✅ |
| Reference Tier 2 Non-food Retailer | 4/4 | 2.8 | ✅ |
✅ Preconditions¶
- Identity and profile services support omnichannel customer creation
- Duplicate checking is enabled across existing customer records
- Consent policies are configured for the relevant jurisdiction and channel
- Loyalty enrollment rules are available if membership is offered during signup
🎯 Success Criteria¶
- One unified customer identity is created without duplicate records
- Consent preferences are stored with an auditable timestamp and source channel
- New customer can be recognised consistently across commerce and store systems
- Loyalty enrollment is completed in the same journey when the customer opts in
⚠️ Failure Modes¶
- Duplicate identity detected and registration must merge or prompt login
- Consent cannot be recorded, blocking activation of downstream communications
- Federated login token fails verification and registration falls back to manual flow
- Loyalty enrollment succeeds late, leaving temporary mismatch between account and benefits
UCMI Requirements¶
Minimum UCMI Score: 2.5
| Capability | Minimum Level |
|---|---|
customer-identity |
🟠 2 |
customer-profile |
🟠 2 |
customer-consent |
🟠 2 |
loyalty |
🔴 1 |
UC-BoK Scenario Catalog · All Scenarios · Scenario Catalog