| name | consumer-goods-cloud-setup |
| description | Consumer Goods Cloud setup: visit execution, retail execution, route planning, in-store task management, compliance checks, off-shelf detection, and image recognition. NOT for Field Service dispatch (use field-service-core-setup). NOT for B2B Commerce storefronts (use b2b-commerce-store-setup). |
| category | admin |
| salesforce-version | Spring '25+ |
| well-architected-pillars | ["Reliability","Operational Excellence","Scalability"] |
| tags | ["consumer-goods","retail-execution","visit-execution","route-planning","compliance","industries","cg-cloud"] |
| triggers | ["how do i set up consumer goods cloud in salesforce","retail execution visit planning route configuration","field rep store visit task compliance checks","cg cloud perfect store and in store task configuration","image recognition off shelf detection setup","visit execution survey and order capture"] |
| inputs | ["CG Cloud edition and license assignment","Retail segmentation (store types, banners, territories)","Visit cadence and task list mix (merchandising, compliance, sales order)","Mobile offline and image-recognition requirements"] |
| outputs | ["CG Cloud feature activation checklist","Visit templates with task mix configured","Route plan + territory assignment rules","Mobile offline and image-recognition setup notes"] |
| dependencies | [] |
| version | 1.0.0 |
| author | Pranav Nagrecha |
| updated | 2026-04-21T00:00:00.000Z |
Consumer Goods Cloud Setup
Activate when configuring Salesforce Consumer Goods (CG) Cloud for a consumer-packaged-goods company: retail execution, visit planning, in-store task capture, order-taking on the field, promotion compliance, and image-recognition-driven off-shelf detection. CG Cloud is distinct from Field Service — it is merchandising-first, not dispatch-first.
Before Starting
- Confirm the CG Cloud license and mobile offline package. The CG mobile app is its own download; reps cannot use the standard Salesforce mobile app for visit execution.
- Map the retail hierarchy. Retailer → Banner → Store → Shelf is the typical hierarchy. Modeling this as Account hierarchies drives visit targeting, route planning, and reporting.
- Know the visit cadence. Weekly, biweekly, monthly, or exception-triggered visits each imply a different Route Plan and Visit auto-generation strategy.
Core Concepts
Retail Store + Visit + Task model
RetailStore (typically Account with record type Retail Store) is the location. Visit is a planned interaction with a store, usually generated by Route Plan automation. Each Visit has a Task list — merchandising checks, compliance surveys, order capture, competitive data collection.
Route Plan
RoutePlan governs how reps visit stores: frequency, priority, territory rules. RoutePlanEntry lists target stores and their visit cadence. Route Plan feeds Visit auto-generation and backs the mobile offline agenda.
Visit Templates
Shared visit definitions with task lists, forms (surveys), and prerequisite steps. Templates are assigned to stores/segments so a beverage company's Tier-1 hypermarket gets a different visit template than a Tier-3 convenience store.
Image Recognition / Computer Vision
CG Cloud integrates with Salesforce Image Recognition for on-shelf photo analysis. It scores SKU facing counts, out-of-stock flags, and planogram compliance. Requires IR license and the shipped ML models.
Common Patterns
Pattern: Weekly route with in-store survey
RoutePlan runs weekly for a Tier-1 territory; each Visit auto-creates from a VisitTemplate with a merchandising survey, an order-capture step, and a compliance photo step. Rep's offline app caches the agenda at start-of-day.
Pattern: Off-shelf alert routing
Image Recognition flags a SKU out-of-stock; CG Cloud creates a Case routed to the retailer's category manager Account contact. Resolution SLA tracked via Entitlement.
