Base Model · Enhanced Model · Use Case · Feature Comparison

Consumer Goods Cloud — Standard Retail Execution

The Base Model uses the standard CG Cloud data model built on native Salesforce objects. No managed package required beyond the CGCloud license. Field reps use the standard Salesforce mobile app or browser — an active internet connection is required at all times.

What the Admin configures

• RetailStore — one record per physical store. Stores billing info, timezone, operating hours, preferred visit windows.
• In-Store Locations — aisles, endcaps, checkout counters. Each location must be tied to an In-Store Location Category to link it to RSKPIs.
• RetailLocationGroup — group stores by size, region, or product type. KPIs are defined at the store group level (not individual store).
• Operating Hours + Time Slots — define business hours and preferred visit windows per store.

• Product2 — standard Salesforce Product object. Each product is a SKU.
• StoreProduct — associates a product to a specific retail store or in-store location.
• Assortment + AssortmentProduct — define product lists eligible for sale at a store, store group, or account.
• Price Book — standard Salesforce Price Book stores list prices. Associated to Product2 via Price Book Entry.

• Promotion — a campaign or targeted promotion to run at retail stores. Has category (advertising, sales promotion, publicity), level (product, product category, none), and method (discounts, displays, sampling).
• PromotionChannel — associates a promotion to a specific store, store group, or account, with a date range and optional in-store location.
• PromotionProduct / PromotionProductCategory — ties the promotion to specific SKUs or product categories.

• Assessment Indicator Definition (AID) — defines a KPI metric. Types: Number, Boolean, DateTime, Text, Decimal. KPI types include: Facing, Share of Shelf, Out of Stock, Inventory, Price, Revenue.
• Retail Store KPI (RSKPI) — links an AID to a store group (not individual store), product/promotion/planogram, and defines the target value. KPIs can't be set at the store level — only at store group level.
• Retail Visit KPI — auto-created when a field rep captures an actual value during a visit. Stores actual vs target.

Each task type enables a different in-store activity. An assessment task definition holds name, description, category, and task type.

• Reusable visit checklists — define the ordered list of tasks a rep performs at every visit of a given type.
• Set Target Object = Visit, Action Plan Type = Assessment Execution.
• Add tasks (Inventory Check, Planogram Check, etc.) with Is Required flag and Display Order.
• Must be Published before use — published templates cannot be edited.
• One Action Plan Template can be associated to multiple visits. You can add multiple Inventory Check, Planogram Check, and Promotion Check tasks, but only one Order Creation or In-Store Survey per template.

How visits are planned in the Base Model

• Create visits manually in Salesforce Lightning — one by one, or in bulk using the Retail Execution app.
• Assign the field rep and the Action Plan Template to each visit.
• Associate the visit to a specific RetailStore.
• Set the scheduled date and time window.
• Optional: use Einstein Visit Recommendations (basic) — requires setup and configuration to suggest which stores to prioritize.

How field reps execute visits in the Base Model

• Opens the Salesforce mobile app (Lightning) — requires active internet connection.
• Navigates to their visit list — sees today's scheduled stores.
• Opens a visit → sees the ordered task list from the Action Plan Template.
• Executes tasks in order: Inventory Check (captures facings, OOS, Share of Shelf) → Planogram Check (photo comparison) → Promotion Check → Place Order.
• Captures actual KPI values — system generates Retail Visit KPI records against the store group targets.
• Captures digital signature from store manager to release the order.
• Closes the visit — data is immediately available in Salesforce.

What the Base Model cannot do

• No offline mobile app — field reps must have internet access at all times in store.
• No territory management — no Org Units, no Sales Org segmentation, no automatic rep-to-store assignments.
• No advanced orders — no Penny Perfect Pricing, no listing modules, no authorization lists. All customers see the same price book.
• No Advanced Promotions (TPM) — promotions have no lifecycle (no Planning → ForApproval → Committed phases), no lock status, no tactic management.
• No master data management from mobile — reps can view customer master data but cannot edit it. No customer templates or product templates.
• No CRM Analytics — no pre-built compliance dashboards, no store-level performance analytics out of the box.
• No Agentforce integration — no AI-generated visit insights, no automated visit creation, no product/promotion suggestions.
• No VS Code Modeler customization — mobile app UI customization via Design Contracts not available in base model workflow.
• No GPS tracking on visits — GPS tracking is only available for advanced (template-based) visits in the Enhanced Model.

Core objects in the Base Model

Key objects and relationships

Core objects grouped by process: store master data, product catalog, visit execution, and KPI framework.

Consumer Goods Cloud — Advanced Retail Execution

The Enhanced Model adds the Consumer Goods Cloud managed package on top of the base configuration. It introduces a new data model layer (harmonized objects + side-by-side objects), unlocking offline mobile, territory management, advanced orders, advanced promotions, and AI capabilities.

Org Units, Sales Orgs, and Multi-Market

• Org Units and Org Unit Hierarchies — model your sales organization structure (Country → Region → District → Team). Each org unit maps to a set of customers and reps.
• Multi-Market with Sales Orgs — use separate Sales Orgs to segregate data and configure different business processes for different markets (e.g., different countries or brands).
• Automatic rep-to-customer assignment — instead of manual visit creation per store, the system assigns reps to their territory's customers (accounts) automatically.
• Substitute assignment — when a rep is absent, assign a substitute who inherits the same customer (account) assignments and visits temporarily.
• Team Supervisors — supervisors have role-based visibility into their team's daily activities, visits, and KPI performance.

Customer and Product Data — editable from mobile

• Customer Templates — standardize the data model for customer records. Ensures consistency across all customer (account) records.
• Customer Records with Roles — customers (accounts) can have roles like Orderer, defining who is authorized to place orders at that account.
• Customer Sets and Grouping — group customers for targeted business processes, promotions, or reporting.
• Time-dependent account and product hierarchies — account and product structures can change over time with effective dates, keeping historical accuracy.
• Product Templates — standardize product data. Field reps can view and edit customer master data from the offline mobile app (not just view-only as in Base).
• Editable from mobile — the new UI flow in the offline app lets reps update customer master data in the field, syncing back to Salesforce at end of day.

Penny Perfect Pricing, Listing Modules, Barcode Scanning

• Penny Perfect Pricing — calculates exact prices and discounts per customer at order time. Accounts for customer-specific price lists, volume discounts, and promotional pricing — no rounding errors.
• Authorization Lists + Listing Modules — controls which SKUs are authorized for each customer. A rep can only order products that are listed for that specific account. Eliminates unauthorized orders.
• Flexible product unit of measures — products can have multiple units of measure (case, pallet, individual unit) with automatic conversion at order time.
• Barcode scanning (offline app) — reps scan product barcodes to quickly add items to an order. No manual product lookup needed.
• Advanced order templates — reusable order templates with quantity rounding rules and pre-configured product selections.
• Sales Folder — enhances the sales pitch with promotional materials shown during the order-taking process in the mobile app.

Trade Promotion Management — Lifecycle and Approvals

• Promotion lifecycle phases — promotions move through phases: Planning → ForApproval → Committed. Each phase can trigger lock rules preventing edits or deletion.
• Promotion Lock Status — configure which phases lock the promotion from modification (RE_Promotion_Lock_Status Custom Setting). Prevents accidental changes to committed promotions.
• Tactics and Tactic Products — break a promotion into individual tactics (display, sampling, price reduction) each with their own products and targets.
• Copy Promotion — copy a successful promotion's slogan, products, and tactics to a new promotion for another customer or period, with a new anchor customer and in-store date.
• Promotion Planning for KAM — Key Account Managers plan and commit promotions per account, with visibility into spend, ROI, and execution compliance.

Consumer Goods Cloud Offline Mobile App — work without internet

The CG Cloud Offline Mobile App is the cornerstone capability of the Enhanced Model. Field reps download their data at the start of day (sync), work completely offline in store, then sync again at end of day.

• Start-of-Day sync — app downloads visits, customer data, products, promotions, and task lists for the day.
• End-of-Day sync — app uploads all captured data (KPIs, orders, survey responses, photos) to Salesforce.
• New UI flow — offline app has a new experience supporting: offline visit planning, advanced orders, sales folder, mobile links, CRM Analytics integration, editable master data, and personal settings.
• Advanced Visits (template-based) — created using job templates. Supports different visit types (audit, sales, delivery). GPS tracking enabled on advanced visits.
• Map-based visit creation — supervisors and reps can create visits by selecting accounts (customers) on a map. Salesforce Maps integration.
• Trip Lists — optimized daily routes. Supervisor creates a trip list (ordered account sequence), rep follows the route on the mobile app.
• Create Visits from Job Lists — auto-create visits from predefined job lists, reducing manual planning effort.
• Barcode scan to create visits — scan a store barcode to instantly create a visit for that store.

• Sync Management app (Admin) — configures what data is included in each sync: business data, workflow-specific data, Runtime Artifacts, and metadata.
• Checks for updates to the mobile app itself and transfers them automatically.
• Controls sync frequency and conflict resolution strategy.

Job Templates, Trip Lists, and Activity Templates

CRM Analytics for Consumer Goods

Agentforce for Retail Execution + Einstein AI

• Assists sales managers and field reps in identifying which accounts to prioritize for field visits
• Analyzes visit history, KPI trends, and sales data to surface high-priority accounts
• Enhances efficiency by focusing field time on accounts with the most business impact
• Requires setup and scheduling via the Visit Recommendations configuration

Assets, Audits, and AI Summaries

• Asset Templates — define standard asset types (refrigerators, display units, vending machines) with expected service intervals and audit criteria.
• Assets — individual asset records placed at specific stores or in-store locations. Tracked via serial number, condition, and maintenance history.
• Asset Audits — field reps audit assets during visits: verify condition, temperature, stocking levels, branding compliance.
• AI-generated summaries — Einstein Generative AI produces natural language summaries of asset condition and service history for field reps and supervisors.
• Telematics data — integrate asset telemetry (e.g., refrigerator temperature sensors) for proactive service alerts.

Additional objects in the Enhanced Model

All Base Model objects plus the following (green = Enhanced-only):

New objects and how they connect to the base layer

Shows Enhanced-only objects (territory, advanced orders, advanced promotions, offline visits) and how they extend the base model relationships.

Data Architecture: Base vs Enhanced

Side-by-side overview of both data models organized by functional domain. Green = Enhanced-only objects (requires managed package).

Base Model vs Enhanced Model — applied to the SnackCo scenario

Same use case, different capabilities. The "When it matters" column explains the real-world implication for SnackCo's field force.

How the two models coexist

Starting Spring '22, CG Cloud introduced a side-by-side architecture. The Base Model uses the existing UI flow. The Enhanced Model introduces the new UI flow. Both share the same Visit object and core data model, but have different business logic and UI layers.

Which model for SnackCo?

All objects used by Retail Execution — by model layer

Three tiers: standard Salesforce objects (no CG license needed), objects that come with the CG Cloud license (Base), and objects only available with the Enhanced managed package.