Orders, returns, store transactions, loyalty activity and retail partner sell-through move between Salesforce and the commerce and supply systems of a brand.
Retailers and consumer goods brands integrate Salesforce with the systems that record what customers buy and where. For direct-to-consumer and retail operations, that means linking e-commerce, order management, point of sale and loyalty so service agents see orders and returns, and marketing segments on actual purchases. For brands selling through retail partners, it means bringing in retailer sell-through, trade promotion and distributor data so account teams manage each retail relationship with facts. We decide which system owns customers, orders and products, and how often each flow must refresh to serve its use.
Retail volume and velocity set this industry apart. Transaction counts are large, promotions change demand overnight and holiday peaks can multiply order volume, so integrations must scale and degrade gracefully. Customer identity is fragmented across web accounts, store receipts, loyalty programs and marketplace orders, many of them anonymous or partial. Product data changes constantly with new SKUs, seasonal assortments and variants. Consumer goods brands also depend on retail partners whose data arrives in retailer-specific formats and schedules. Payment data and consumer privacy rules add constraints on what may be stored and how it can be used for marketing. Marketplace channels often withhold shopper contact details entirely, which limits what can be linked.
Orders, shipments, returns and refunds from commerce and order management systems attach to the customer in Salesforce. Service agents answer where-is-my-order, exchange and refund questions without switching screens, and can trigger returns or reshipments that post back to order management. Holiday surges are handled through event-based updates rather than bulk polling, so the service console stays responsive when volume peaks.
Web accounts, loyalty members, store receipts and marketplace orders are resolved into shopper profiles through Data Cloud or a customer data platform. Marketing segments by actual behavior across channels, and service agents recognize loyal customers regardless of where they bought. Anonymous store transactions link to a profile only when an identifier such as a loyalty number or e-receipt email is available.
For brands selling through retailers, point-of-sale and inventory data shared by retail partners and distributors is normalized and loaded against accounts, stores and products. Account teams review sell-through, out-of-stocks and promotion lift by retailer before business reviews, and supply planning sees demand signals from the shelf rather than only shipments to retailer warehouses. Gaps in a partner's reporting are flagged rather than silently treated as zero sales.
Points, tier status, rewards and preferences from the loyalty platform enrich shopper profiles in Salesforce. Store associates using clienteling tools see purchase history and preferences for their customers, and service agents can issue goodwill points that post back to the loyalty ledger. Campaigns reference loyalty status directly, keeping offers consistent between email, app and store. Tier changes reach associates the next morning, so recognition in the store matches what the app shows.
Merchandising, e-commerce, stores, customer service, marketing and IT all participate, because each owns part of the customer or product picture. We connect order and return data first where service is the pain point, or shopper identity first where marketing drives the program. Product and loyalty data follow. Load tests replay peak season volume, including promotional spikes, before any change reaches production. The holiday code freeze and major promotional events set the release calendar, and new retailer feeds are onboarded one partner at a time with validation against their reports.
Orders, fulfillment status, returns and refunds flow to Salesforce, and service-initiated returns, reshipments and appeasements post back for processing and financial reconciliation.
Store transactions tied to known shoppers, loyalty points, tiers and rewards enrich profiles, and goodwill points issued in Salesforce post to the loyalty ledger.
Sell-through, store inventory and promotion data from partners are normalized to brand products and accounts for account team reporting and demand planning.
Integration throughput, Salesforce API usage and middleware capacity must handle the busiest promotional days, not typical weeks. Use event-driven patterns and queueing, test with realistic peak volumes, and have a plan to pause non-essential syncs during extreme peaks. Queued records should catch up automatically once traffic subsides.
Commerce and store systems process card data covered by PCI DSS. Integrations should pass order and payment references only, never full card numbers, and service workflows should avoid capturing card details in cases, chats or notes. Scan chat transcripts and email intake for card patterns and mask them automatically.
A growing number of state statutes let consumers request their data, demand erasure and refuse targeted advertising. Carry consent flags and deletion requests across integrations, so a shopper who opts out in one channel is honored in Salesforce, marketing tools and connected systems.
Usually not. Most store transactions are anonymous, and loading all of them adds cost without improving service or marketing. We load transactions tied to known shoppers, or summarized behavior, and leave full transaction detail in the data warehouse or Data Cloud, where it can be referenced for segmentation and analytics without cluttering service records or consuming storage the service team needs.
Build an intake layer that accepts each retailer's format, whether EDI documents, portal downloads or files, and maps partner item numbers, store identifiers and dates to your own. Validation checks catch missing weeks or unexpected totals. Once normalized, the data loads to Salesforce the same way for every retailer, making cross-partner comparison possible. New retailers are onboarded by adding a mapping, not rebuilding the pipeline.
Yes, when the order management system supports return and refund APIs. Agents start the return in the Salesforce console, the integration creates it in order management with the right reason codes, and status updates flow back. Financial processing stays in order management and payments, keeping refunds auditable and consistent with store and online policies. Agents see the refund status update in the case once payment processing completes.
The integration has to support two customer types: consumers who buy direct and retail accounts that buy wholesale. We keep them in separate but connected models, so consumer data powers service and marketing while retail account data powers trade and sales planning. Product data is shared between both, keeping SKUs, variants and launches consistent. Reporting can then compare direct sales with sell-through for the same product line.
One onshore team with 150 Salesforce certifications, a Salesforce Consulting Partner since 2017.
A monthly brief for the people who own Salesforce, AI and revenue technology
What changed in Salesforce and AI this month, and what to do about it.
One email a month. Written by the consultants who deliver the work, not by a marketing team, for the leaders who make the technology decisions.
Consultant analysis, not vendor recaps. One click to leave.