consumer-goods-cloud-setup
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).
Best use case
consumer-goods-cloud-setup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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).
Teams using consumer-goods-cloud-setup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/consumer-goods-cloud-setup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How consumer-goods-cloud-setup Compares
| Feature / Agent | consumer-goods-cloud-setup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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. ### Pattern: Promotion compliance audit Seasonal promotion runs Aug 1–14. Visit Template set for that window includes a compliance check: "Is the endcap display up?" Photos are captured; IR scores planogram match. Results aggregate to a promotion compliance dashboard. ## Decision Guidance | Situation | Recommended Approach | Reason | |---|---|---| | Scheduled weekly rep visits | RoutePlan + VisitTemplate | Shipped flow; offline-capable | | Exception-driven visit | Event-triggered Visit via Flow | No route disruption | | Planogram compliance | Image Recognition + IR models | Deterministic, auditable scoring | | Field order capture | CG Order + OrderItem | Native to CG Cloud | | Dispatch-based field work | Use Field Service, not CG | Different shipped features | ## Recommended Workflow 1. Confirm CG Cloud license, IR license (if using), and mobile offline package are provisioned. 2. Enable CG Cloud features in Setup and create the RetailStore account record type. 3. Import the retail hierarchy (Retailer → Banner → Store) before any visit/route data. 4. Define Visit Templates per store tier; attach surveys, tasks, and prerequisite steps. 5. Build Route Plans per territory; assign reps; smoke-test auto-Visit generation. 6. Configure Image Recognition models (shipped or custom-trained) and attach to photo task steps. 7. Run a full round-trip in a sandbox: sync offline → execute a Visit → upload → verify KPIs populate. ## Review Checklist - [ ] CG mobile offline app installed on a rep test device - [ ] Retail hierarchy loaded before visit/route records - [ ] Visit Templates assigned to every active store segment - [ ] Route Plan auto-generation validated for next week's window - [ ] IR models trained / validated on agency SKU set - [ ] Offline conflict resolution policy documented - [ ] KPI dashboards render expected rollups per rep/territory ## Salesforce-Specific Gotchas 1. **CG Cloud uses shipped platform events for visit sync.** Disabling the events breaks offline reconciliation silently; always check the Platform Events usage monitor after enabling. 2. **Image Recognition requires pre-trained models per product line.** Out-of-the-box models do not know your SKUs; budget model-training time before go-live. 3. **Route Plan regeneration is expensive.** Rebuilding routes on large territories can take hours — schedule off-hours. ## Output Artifacts | Artifact | Description | |---|---| | CG activation runbook | License checks, feature toggles, data load order | | Visit template catalog | Templates by store tier and program | | Route plan matrix | Territory × rep × cadence view | | IR model inventory | Models in use, accuracy metrics, retrain cadence | ## Related Skills - `admin/sales-cloud-core-setup` — account hierarchy foundation - `integration/platform-events-basics` — CG visit-sync backbone - `security/field-level-access-for-mobile-users` — offline security
Related Skills
shield-kms-byok-setup
Configure Shield Platform Encryption with customer-supplied (BYOK) or customer-held (Cache-Only Key Service) tenant secrets, rotate them, and recover. NOT for Classic Encryption or field masking.
experience-cloud-security
Use when configuring access controls, sharing, or site security for authenticated or guest Experience Cloud (community) users: external OWD, Sharing Sets, Share Groups, CSP, clickjack protection, guest user record access. NOT for internal sharing model configuration (use sharing-and-visibility).
headless-experience-cloud
Use when building custom frontends (React, Vue, mobile, static sites) that consume Salesforce CMS content via the Connect REST API headless delivery endpoint. Triggers: 'headless Salesforce CMS', 'deliver CMS content to external frontend', 'React app Salesforce content API', 'custom frontend Experience Cloud data', 'CMS delivery channel API'. NOT for standard Experience Builder site development. NOT for CMS Connect (3rd-party CMS federation into Experience Builder). NOT for Experience Cloud LWC components rendered inside a site.
experience-cloud-search-customization
Use this skill when configuring or extending search on an Experience Cloud site — covering Search Manager scope configuration, LWR vs Aura search component selection, federated search setup, guest user search access, and custom search result components. NOT for SOSL/SOQL query development. NOT for internal Salesforce global search or Einstein Search for agents.
experience-cloud-multi-idp-sso
Use this skill when configuring multiple identity providers (OIDC and/or SAML) on a single Experience Cloud site or across tenant-specific portals in the same org — covering auth provider registration, Start SSO URL routing, Federation ID mapping, RegistrationHandler implementation, and simultaneous SP+IdP topology. Trigger keywords: multiple identity providers Experience Cloud, multi-tenant SSO community portal, vendor and citizen portal same site, OIDC SAML both on login page, tenant-specific login routing community. NOT for internal Salesforce employee SSO configuration. NOT for single auth provider setups — see experience-cloud-authentication for basic SSO.
experience-cloud-lwc-components
Use when building custom LWC components for Experience Cloud (Experience Builder sites, LWR portals, Aura-based communities). Covers community context imports, guest user Apex access patterns, navigation API differences between LWR and Aura, and JS-meta.xml target configuration for Experience Builder exposure. NOT for internal LWC components deployed to Lightning App Builder or standard record pages (see lwc/lwc-development). NOT for Aura community components. Trigger keywords: build LWC for Experience Cloud, custom component community portal LWC, guest user LWC component, community context import salesforce, lightningCommunity target, @salesforce/community, guest Apex.
experience-cloud-authentication
Use when building custom login pages, social SSO flows, self-registration flows, or passwordless OTP login for Experience Cloud (community) sites. Trigger keywords: custom login page Experience Cloud, social SSO community portal, passwordless login Experience Cloud, self-registration custom flow, headless authentication community, auth provider OIDC SAML site. NOT for internal SSO configuration (use identity/sso skills). NOT for standard username/password authentication with no customization.
experience-cloud-api-access
Use this skill when configuring or troubleshooting API access for Experience Cloud external users and guest users: guest user Apex data access, Customer Community Plus or Partner Community REST/SOAP API access, external user OAuth scopes, and sharing enforcement on API responses. Trigger keywords: Experience Cloud API access external user, community user REST API, guest user API limits, Customer Community API permissions, external user OAuth. NOT for internal Salesforce API authentication, non-community OAuth flows, or internal user API security.
slack-salesforce-integration-setup
Use this skill when setting up or troubleshooting the Salesforce for Slack managed app — including connecting a Salesforce org to a Slack workspace, configuring the three-party admin handshake, linking Slack channels to Salesforce records, enabling record preview sharing, and managing org-level limits. Triggers on: Salesforce for Slack app not connecting, Slack org connection setup, Salesforce record sharing in Slack, Slack workspace admin approval, connecting Salesforce to Slack. NOT for building custom Slack apps or Slack bots (separate development platform), not for Slack Workflow Builder Salesforce connector (use slack-workflow-builder skill), not for Flow-based Slack messaging (use flow-for-slack skill).
salesforce-maps-setup
Use when configuring Salesforce Maps (formerly MapAnything) — territory planning, route optimization, live tracking, geo-grid visualizations, and check-in/check-out workflows for Sales or Service field reps not on Field Service. Covers package installation order (Maps + Maps Advanced + Maps Routing/Live Tracking add-ons), the MapsTerritoryPlan / MapsAdvancedRoute / MapsLayer object family, base-data syncs (Geocoding and Routing services), and integration with Sales and Service Cloud records. Triggers: 'Salesforce Maps setup', 'MapAnything migration', 'territory planning by polygon', 'route optimization for sales reps', 'live tracking field reps', 'plot accounts on a map', 'check-in to the closest account'. NOT for Field Service Lightning territory and scheduling (use admin/fsl-scheduling-optimization-design and data/fsl-territory-data-setup) — Maps and FSL are different products. NOT for Consumer Goods Cloud retail visit planning (use admin/consumer-goods-cloud-setup) — RoutePlan/Visit objects are CG-specific. NOT for Tableau / CRM Analytics geo charts.
private-connect-setup
Configure Private Connect between Salesforce and AWS/Azure for traffic to stay on private networks. NOT for standard internet callouts.
net-zero-cloud-setup
Use this skill when configuring Salesforce Net Zero Cloud — including Scope 1/2/3 emission source modeling via the StnryAssetCrbnFtprnt / VehicleAssetCrbnFtprnt / Scope3CrbnFtprnt object families, emission factor library setup (EmssnFctr / EmssnFctrSet), DPE-driven carbon calculation jobs, supplier engagement scoring, and CSRD / ESRS / TCFD disclosure pack mapping. Triggers on: Net Zero Cloud setup, Sustainability Cloud carbon accounting, Scope 1 2 3 emissions Salesforce, emission factor library, supplier engagement Net Zero, ESG disclosure pack mapping. NOT for ESG content scoring (use Marketing Cloud), NOT for general financial reporting (use Accounting Subledger), NOT for energy-only utility billing (use Energy & Utilities Cloud).