Salesforce Decode
Salesforcedecode
Back to questions
Data CloudArchitect (Hardest)unified-profileretailomnichannelpos

Build retail unified profiles spanning POS, e-commerce, and marketplace sellers

Real World Scenario

A department store chain sells on owned e-commerce, in-store POS, and third-party marketplace with different customer IDs. Loyalty tier benefits fail when online purchases do not appear in store associate apps.

Expected Answer

• Ingest all channels into separate DLOs with channel-specific keys mapped to Individual DMO • Prioritize loyalty ID and verified phone matches over marketplace pseudonymous buyer IDs • Near-real-time streaming for POS and web behavioral events; batch reconciliation for marketplace settlement files • Expose unified profile API to store clienteling apps with latency SLA under 2 seconds • Handle marketplace orders where buyer PII is partially masked by platform policies • Activation of loyalty tier segments must refresh before weekend promotional windows • Reconcile revenue attribution without double-counting cross-channel returns

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Direct answer: Ingest all channels into separate DLOs with channel-specific keys mapped to Individual DMO Also consider: Prioritize loyalty ID and verified phone matches over marketplace pseudonymous buyer IDs In practice: Near-real-time streaming for POS and web behavioral events; batch reconciliation for marketplace settlement files Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Retail unified profiles are operational, not just marketing—store apps need fresh data. Design ingestion latency per activation use case, not one pipeline speed.