Data CloudIntermediatesurvivorshipaddressconflict
Resolve conflicting survivorship for address across CRM and ecommerce
Real World Scenario
Unified profile shows CRM billing address while customer receives shipments to ecommerce shipping address; service agents give wrong guidance.
Expected Answer
• Separate address types: billing, shipping, service visit — not single address field
• Survivorship rules per address type: most recent ecommerce ship for shipping
• Display all source addresses in service UI with primary flag
• Calculated insight for best contact address per use case
• Do not overwrite shipping with billing in harmonization
• Validate address standardization API applied consistently
• Agent training on multi-address profiles
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Separate address types: billing, shipping, service visit — not single address field Also consider: Survivorship rules per address type: most recent ecommerce ship for shipping In practice: Display all source addresses in service UI with primary flag Balance speed of delivery with maintainability.
Architect Perspective
Survivorship without semantic address roles creates wrong-primary-address incidents daily.