ServicesSalesforce consultingArchitectureImplementationOrg health checkDevelopmentIntegrations and APIsData migrationTesting and QAManaged supportSpecialist supportMarketing Cloud auditDeliverability
SolutionsMarketing Cloud EngagementMarketing Cloud NextSalesforce + BrazeAccount EngagementData Cloud (Data 360)Identity resolutionInsights and segmentsAgentforce and AIMCP integrationsSales and Service CloudReal-time personalisationIntegration solutionsEnterprise AI integrationBy industry
ArchitectureSalesforce CRMData 360Salesforce + BrazeAgentforceCustomer 360API-led integrationEvent-drivenMCP host, client and serverIdentity and consentMCP securityData governanceCI/CD and releasesOur public MCP server
ResourcesEngineering journalDecision guidesSolution blueprintsSalesforce productsProjects and achievementsSales ROI calculatorWhere we workChecklists and templatesPlanning toolsReadiness assessmentGlossaryAbout GeekMidstOur approachOur expertiseContact
CompanyAbout GeekMidstOur approachDelivery methodologyTrust and evidenceProjectsAchievementsBook a consultationContactWhere we workSecurity and data
Book a Consultation

Salesforce for Retail, Online and Loyalty

Retail customers shop in stores, online and on apps, but most retailers see them as separate people. Here is how Salesforce brings those views together.

Store associate handing a paper bag to a shopper holding up her phone at a click-and-collect counter

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.
A retail storefront linked through a customer hub to the checkout terminal, a shopping bag order and a loyalty offer on a phone

Retail use cases mapped to Salesforce

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.

  • 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.

How GeekMidst would start

  1. 01

    Inventory identifiers by channel

    Measure capture rates and quality for loyalty number, email and phone in stores and online.

  2. 02

    Agree a profile strategy

    Match rules, source priority for conflicting fields and how unified profiles will be used.

  3. 03

    Ingest two sources first

    Typically ecommerce and loyalty, then POS once the model is proven.

  4. 04

    Launch one cross-channel journey

    For example, loyalty tier messaging with suppression of recent store purchasers.

  5. 05

    Measure against a holdout

    Compare behaviour with a control group so the programme's contribution is clear.

Workflow diagram

Explore how the pieces fit together. Select a step to read what happens there.

Customer journey

Browse abandonment journey

Open full size
Browse abandonment journeyProduct views from known visitors are captured on the website, and a scheduled SQL query builds the browse audience. Journey Builder removes anyone who has since bought, sends a reminder with the viewed items, waits, and sends one lighter follow-up only to visitors who did not engage.Browse abandonment journeyVisitorJourney BuilderWebsiteAutomationStudioYesNoYesNoViews products: Known visitor, no cart. Browse journeys only work for identified visitors, for example people who arrived from an email click or are signed in, so views can be tied to a contact.Views productsKnown visitor, no cartViews captured: Web tracking with contact key. Tracking on the site records product, category and time against the contact key. Without the key, views stay anonymous and cannot trigger an email.Views capturedWeb tracking withcontact keyAudience query: Scheduled SQL activity. An Automation Studio SQL query picks recent views, removes anyone with a cart or order, applies a frequency cap and writes the journey entry data extension.Audience queryScheduled SQLactivityBought since viewing?. Orders can land between the query and the send, so the journey checks again at entry. Purchasers should never receive a browse reminder.Bought sinceviewing?Browse reminder: Viewed items plus similar. The email shows the viewed products with current price and stock, plus related items. Content falls back to bestsellers when product data is missing.Browse reminderViewed items plussimilarOrder already placed: Exits without email. Visitors who bought are removed from the journey. Order data synced from the commerce platform is what makes this check possible.Order alreadyplacedExits without emailWait 2 days: Send windows apply. Gives the visitor time to return on their own before any follow-up. Send-time windows keep messages within reasonable hours.Wait 2 daysSend windows applyClicked or ordered?. An engagement or decision split checks for a click or an order. Clicks and orders are better signals than opens, which mail privacy features inflate.Clicked orordered?Returned to the site: Engaged, exits. Engaged visitors leave this journey. Their next steps are handled by cart or post-purchase journeys instead, so messages do not overlap.Returned to thesiteEngaged, exitsFollow-up picks: Category or bestsellers. One last, lighter message with category picks or bestsellers. Sending more than this risks unsubscribes from people who were only browsing.Follow-up picksCategory orbestsellersExits journey: Re-entry rules. The visitor leaves the journey. Re-entry settings and the frequency cap in the query stop the same person being reminded too often.Exits journeyRe-entry rulesStartSystem or platformProcess stepDecisionChannel or touchpointEnd or outcomeWaitOriginal GeekMidst explanatory diagram, not an official Salesforce reference.

Select any step in the diagram, or use Step through, to see what happens at that point and why.

Text version: every step in order
  1. Views products VisitorKnown visitor, no cart

    Browse journeys only work for identified visitors, for example people who arrived from an email click or are signed in, so views can be tied to a contact.

    Next: Views captured

  2. Views captured WebsiteWeb tracking with contact key

    Tracking on the site records product, category and time against the contact key. Without the key, views stay anonymous and cannot trigger an email.

    Next: Audience query

  3. Audience query Automation StudioScheduled SQL activity

    An Automation Studio SQL query picks recent views, removes anyone with a cart or order, applies a frequency cap and writes the journey entry data extension.

    Next: Bought since viewing?

  4. Bought since viewing? Journey Builder

    Orders can land between the query and the send, so the journey checks again at entry. Purchasers should never receive a browse reminder.

    Next: Yes: Order already placed; No: Browse reminder

  5. Order already placed WebsiteExits without email

    Visitors who bought are removed from the journey. Order data synced from the commerce platform is what makes this check possible.

    End of the flow.

  6. Browse reminder VisitorViewed items plus similar

    The email shows the viewed products with current price and stock, plus related items. Content falls back to bestsellers when product data is missing.

    Next: Wait 2 days

  7. Wait 2 days Journey BuilderSend windows apply

    Gives the visitor time to return on their own before any follow-up. Send-time windows keep messages within reasonable hours.

    Next: Clicked or ordered?

  8. Clicked or ordered? Journey Builder

    An engagement or decision split checks for a click or an order. Clicks and orders are better signals than opens, which mail privacy features inflate.

    Next: Yes: Returned to the site; No: Follow-up picks

  9. Returned to the site WebsiteEngaged, exits

    Engaged visitors leave this journey. Their next steps are handled by cart or post-purchase journeys instead, so messages do not overlap.

    End of the flow.

  10. Follow-up picks VisitorCategory or bestsellers

    One last, lighter message with category picks or bestsellers. Sending more than this risks unsubscribes from people who were only browsing.

    Next: Exits journey

  11. Exits journey Journey BuilderRe-entry rules

    The visitor leaves the journey. Re-entry settings and the frequency cap in the query stop the same person being reminded too often.

    End of the flow.

Product views from known visitors are captured on the website, and a scheduled SQL query builds the browse audience. Journey Builder removes anyone who has since bought, sends a reminder with the viewed items, waits, and sends one lighter follow-up only to visitors who did not engage. Original GeekMidst explanatory diagram; not an official Salesforce reference architecture.

Questions we hear

How do we link in-store purchases to customers?
Through an identifier captured at the till, most often a loyalty number or phone. Capture rate is the main constraint, so store processes matter as much as technology.
Do we need Data Cloud, or is Marketing Cloud enough?
Marketing Cloud can segment on imported data. Data Cloud becomes worthwhile when you must resolve identities across several high-volume sources and reuse profiles across channels.
Can store staff see customer preferences?
Yes, through Salesforce apps or embedded components, with access limited to what staff need. Design this with your privacy team.

Connect your store, online and loyalty data

Tell us which channels and systems you run today. We will outline how to build a unified customer view in stages.

Talk to a Salesforce expert →

Tell us what you are trying to fix.

Share your Salesforce setup, goals and constraints. A practitioner reads every message and replies with questions, first thoughts or an honest view of whether you need outside help at all.

Talk to a Salesforce Expert
Book a Consultation