Now accepting projects — Q3 2026

Home/Industries/Salesforce platform path

Retail & Consumer Goods: Salesforce Solution

The real retail pain is fragmented customer data — POS, service, web, social, and loyalty platforms each own a slice. Salesforce pulls those channels back into a customer 360 and uses Service Cloud, Loyalty Management, and Consumer Goods Cloud to connect service, loyalty, and channel execution. EKel delivered Taiwan’s first Consumer Goods Cloud Enhanced rollout.

// Typical modules

Customer 360 and membership

Integrate in-store purchases, online behaviour, service history, loyalty tier, and marketing interactions into a single customer view shared by marketing and service.

Service Cloud consolidation

Bring complaints, returns, member issues, and store escalations into case routing, SLAs, and knowledge — agents stop opening five systems.

Loyalty Management and channel execution

Marketing owns tier, points, and cross-channel redemption rules. Consumer Goods Cloud owns the store-visit workflow (visit plan, check-list, visit records, task dispatch); field reps execute the full standardised flow.

// How EKel would deliver it

01Map existing POS, e-commerce, loyalty, service, and marketing systems and identify where customer data is scattered.
02Define data boundaries for customer, order, member, and channel events without copying POS wholesale into Salesforce.
03Start with one module — Service Cloud consolidation or Loyalty rule design — that can show value in 6–8 weeks.
04Hand daily rule operations back to marketing and service so IT is no longer the bottleneck for every rule change.

// Best fit

→Retail chains, retailers, and consumer-goods brands with customer data fragmented across channels and systems.
→Teams with POS / e-commerce in place but loyalty and service stuck in Excel or stitched-together tools.
→Programs evaluating Service Cloud, Loyalty Management, or Consumer Goods Cloud (including Enhanced) or considering an org refactor.

// Sources

Salesforce Retail Salesforce Consumer Goods Cloud

Back to industries See retail custom AI →

// Architecture stack

Retail Salesforce is a three-layer choreography: channel + member + service.

// LAYER 1

Channel ingestion

POS, e-commerce, LINE, web, social, store app — every touchpoint writes “what the customer did” onto one customer record. Event-driven sync, not nightly batch.

POSE-commerceLINEStore App

// LAYER 2

Member & service

Customer 360 + Loyalty Management + Service Cloud. Tier, points, cross-channel redemption — marketing changes the rules without queueing IT. Complaints and returns enter case routing — one agent surface for the full history.

Customer 360LoyaltyService CloudCase Routing

// LAYER 3

Channel execution

Consumer Goods Cloud Enhanced owns the store-visit workflow — visit plans, check-lists, visit records, report photos, follow-up task dispatch. Field reps execute a standardised flow on a mobile app; HQ receives structured data, not Excel patchwork. Shelf execution and promotion tracking are extensions on top.

CGC EnhancedVisit PlanChecklistsField Mobile

// Typical timeline

24 weeks, four phases

Median scenario. Service Cloud + Loyalty consolidation alone shows value in 6–8 weeks; full scope with CGC Enhanced + channel integration runs 24–28 weeks.

W12

W22

W24

// 00 · Week 1–3

Channel discovery

Interviews with marketing, service, store ops, loyalty, and e-commerce leads. Map where customer data lives, decide which system is the source of truth for each entity.

// 01 · Week 4–12

Service + Loyalty MVP

Service Cloud case routing + Loyalty Management rule design. First end-to-end cross-channel member journey (e.g., in-store purchase → app push → email follow-up).

// 02 · Week 13–22

CGC Enhanced + integration

Consumer Goods Cloud Enhanced store-visit workflow (visit plan, check-list, visit records, photo reports, task dispatch) + POS / e-commerce integration. Two-way sync between in-store and online.

// 03 · Week 23–24

Operations handover

Hypercare across marketing, service, and store ops. Hand loyalty rule changes back to marketing — IT is no longer the bottleneck for every promo update.

// FAQ

Five questions that come up most in retail architecture discussions.

01We already have POS and e-commerce — why add Salesforce?

POS handles checkout. E-commerce handles online purchase. Neither owns the cross-channel timeline of "bought in store + asked on LINE + browsed online + complained at service centre." Salesforce sits as the customer 360 + service workflow + loyalty engine — pulling scattered signals onto one customer so marketing, service, and store ops see the same truth. If your member data still lives in Excel, that is the gap.

02Loyalty Management vs an in-house loyalty system?

Two checks. (1) Rule-change frequency — if marketing wants to change promo rules 20× a year, Loyalty Management lets them do it themselves; in-house systems queue every change behind IT. (2) Cross-partner / cross-brand redemption — Loyalty Management has this built in; in-house has to build it. For <1M members with moderate complexity, Loyalty Management usually pays off. For 10M+ members with mature in-house systems, refactor risk may exceed ROI.

03Who is Consumer Goods Cloud Enhanced for?

Brands with field reps running channels who need a structured store-visit workflow — typical for FMCG, consumer goods, and chain F&B. Taiwan’s first CGC Enhanced implementation centred on **the store-visit workflow itself: a series of activities, tasks, and check-lists** (visit plans, checklists, visit records, report photos, follow-up task dispatch). Field reps execute a standardised flow on a mobile app; HQ receives structured data instead of stitched-together Excel from every store. If you have no field reps at all (pure online or owned-stores with no visits), standard Service Cloud usually suffices.

04Should POS / e-commerce sync be batch or real-time?

Members, orders, and returns should sync event-driven (Platform Events / Kafka) in seconds — customers see points right after they pay in store. Inventory and product master can run nightly batch (low change rate, tolerable lag). Do not nightly-batch transactions — “bought 5 minutes ago, service cannot find it” damages the brand directly.

05Does Service Cloud have to unify every service channel?

No — phase it. A common sequence: integrate the contact centre + email first (highest case volume), add LINE / WhatsApp / Messenger second, store escalations third. The constraint is one measurable KPI per phase (first-response time, resolution time, SLA attainment) — not “unify everything in one go.” Trying to do it all at once is the #1 reason these projects stall.

Retail Salesforce work starts with channel data discovery.

In 30 minutes we can align on your channel, loyalty, and service systems, then decide whether to start with Service Cloud, Loyalty Management, or Consumer Goods Cloud.

Book Free Consult→

We use cookies

We use strictly necessary cookies to run this site, plus optional analytics cookies (Google Analytics) to understand how visitors use it. See our Cookie Policy and Privacy Policy.