Salesforce for Retail, Online and Loyalty

Retailers know a great deal about transactions and surprisingly little about customers. The point-of-sale (POS) system records a basket, the ecommerce platform records an order, and the loyalty programme records points, but the same person often appears as three records with different identifiers. Without a reliable link between them, personalisation stays shallow and store teams cannot recognise their best customers.

Retail engagement challenges

• Anonymous store transactions. Many in-store sales are not tied to a customer at all. Capturing an identifier at the till (loyalty number, phone, e-receipt email) is the foundation for everything else.
• Duplicate and conflicting profiles. A customer who shops online with one email and in store with a phone number looks like two people until you resolve them.
• Promotions without context. Sending discounts to people who would have bought anyway erodes margin.
• Inventory-blind messaging. Recommending products that are out of stock locally frustrates customers.
• Store and head office misalignment. Clienteling tools, service desks and marketing often work from different customer lists.

Getting identity right

Identity resolution only works as well as the identifiers you capture. Before configuring match rules, look at what each channel collects and how clean it is: loyalty numbers are usually reliable, phone numbers need normalising, and email addresses captured at a till are often mistyped. Decide which identifiers can be used for exact matching and which only support fuzzy matching, and test rules against a sample before applying them to the full base. Over-matching (merging two different people) is usually more harmful than under-matching.

Using store and inventory context

Messages become more useful when they reflect the customer's preferred store and what is actually available there. That means bringing store attributes and, where practical, stock signals into the data that drives segments and content. Real-time stock is not always necessary; a daily availability flag by store and category often covers promotional needs.

Data, consent and compliance considerations

• PCI DSS. Payment card data should stay with your payment provider and POS. Marketing and CRM systems should never receive full card numbers.
• Consent at the till. Capturing an email for an e-receipt is not the same as consent to marketing. Ask separately and record the answer with a timestamp and source.
• Privacy law. India's DPDP Act and, for UK or EU customers, GDPR apply to customer data. Offer clear ways to withdraw consent and access preferences.
• Loyalty terms. Make sure how you use purchase data for personalisation matches what your loyalty terms say.

Your legal team should confirm specific obligations; this is general guidance.

Integration landscape

POS and store systems, ecommerce platform, loyalty engine (Salesforce offers Loyalty Management, or you may run another), order management, product catalogue and pricing, customer service tools, and data warehouse. POS data is often loaded in daily batches; online events and loyalty tier changes benefit from streaming or API-based ingestion.