The Retail Store is a central object in Agentforce Consumer Goods and provides the operational context for Visits and store-level Orders. Salesforce requires the Visit object ' s Place field to reference a Retail Store in Consumer Goods implementations. Orders captured during field visits can also be tracked at the Retail Store level, allowing representatives to review orders from previous visits and efficiently reorder products.

Retail Store record access can also inherit sharing from the parent Account. Salesforce establishes a master-detail relationship between Retail Store and Account for this purpose. The default Retail Store sharing model can be configured as Controlled by Parent, allowing Account sharing rules to govern access to the associated Retail Store records. This eliminates the need to maintain an independent set of sharing rules for every store when the organization wants store access to follow Account access.

Promotions are not linked directly to Retail Stores; Salesforce uses Promotion Channel to create that relationship. Similarly, Direct Store Delivery uses Delivery Task, Shipment, and Product Transfer relationships rather than establishing the Retail Store-to-Shipment relationship described in the alternative.

Study Guide Topics:Data Setup - > Retail Store - > Visit - > Order - > Account Relationship - > Sharing Model

===============

The Product Performance dashboard is designed to help sales managers analyze how products, product categories, brands, and assortments are performing across the Consumer Goods organization. It provides detailed performance views that allow users to identify both strong and weak performers and then drill into the underlying metrics.

Salesforce states that the Product Performance dashboard analyzes product category, brand, product, assortment, and the impact of promotions on performance. Its Product page shows overall product trends and enables managers to identify high-performing products and analyze recently launched products. Its Category and Assortment pages provide equivalent analysis at those organizational levels.

Typical measures include revenue, quantity, average order value, store coverage, average compliance, and related sales-performance indicators. Salesforce specifically describes the dashboard as answering questions such as which products, categories, brands, and assortments are high-performing or least-performing. Managers can drill into individual entities to investigate performance trends and identify where intervention or additional investment is appropriate.

Therefore, the dashboard gives the Sales Manager the ability to identify top- and low-performing products, categories, and assortments and investigate their performance in greater detail.

Study Guide Topics:Analytics - > Product Performance - > Product Categories - > Assortments - > Performance Analysis

===============

A planogram is represented in Consumer Goods Retail Execution by an Image record. The Image object stores the reference representation of the expected product arrangement that a field representative uses during a Planogram Check.

Salesforce ' s Planogram Check prerequisites explicitly require administrators to create an Image record in the Image object representing the planogram at a store. The Image is then associated with the relevant In-Store Location, such as a primary shelf, aisle, checkout counter, or endcap. The Retail Store KPI subsequently references that Image through its Planogram field and combines it with the appropriate Assessment Indicator Definition, In-Store Location Category, Retail Store Group, and KPI Type.

When creating the Image record, the administrator can provide either the location URL of the image or upload an image file, specify the image category, activate the record, and make it available to field representatives.

During Planogram Check execution, representatives can open Product Details to review the expected reference image and compare the shelf arrangement against the merchandising standard.

Study Guide Topics:Data Setup - > Planogram - > Image Object - > In-Store Location - > Retail Store KPI

===============

Flow-based activities execute within the context of the Visit and Assessment Task, while the Retail Execution KPI architecture maintains the relationship between Retail Store KPIs and Retail Visit KPIs.

Salesforce supports adding flows directly to an Action Plan Template. A flow can receive visitId, assessmentTaskId, or both as input parameters. These identifiers allow the flow to operate against the specific Visit and Assessment Task instance from which it was launched, ensuring that business automation remains tied to the correct retail execution transaction.

Retail Visit KPIs provide the transactional measurement layer for a visit. Salesforce documents that when an Action Plan Template is assigned to a Visit, Assessment Tasks are generated from Assessment Task Definitions and Retail Visit KPI records are created based on the applicable Retail Store KPIs. The Retail Store KPI defines the expected target and assessment context, while the Retail Visit KPI captures the visit-specific actual measurement against that target.

Salesforce ' s data model also records the Assessment Task ID, Visit ID, Assessment Indicator Definition, Target Value, and Actual Value on Retail Visit KPI records.

Study Guide Topics:Visit Execution - > Flow Tasks - > visitId - > assessmentTaskId - > Retail Store KPI - > Retail Visit KPI

===============

A Store Product represents the relationship between a Product2 record and a particular Retail Store or In-Store Location. This relationship supplies the store-specific product context required by several Retail Execution processes.

For Inventory Checks, Salesforce must determine which products are relevant to the store being visited. Store Product records provide that relationship, allowing the Inventory Check experience to present applicable products rather than the entire enterprise product catalog. The same store-level product context supports the Search and Scan experience, where field representatives locate a product directly or scan its barcode while performing an inventory assessment.

Store Products also contribute to order capture. Salesforce stores operational attributes on the Store Product relationship, including the associated Product, Retail Store, In-Store Location, default order quantity, and favorite-product indicator. These fields allow the order experience to identify products that are relevant to a specific outlet and facilitate efficient repeat ordering.

Salesforce distinguishes Store Product from Store Assortment: Store Product represents products directly associated with a store or in-store location, while assortments define broader groups of products eligible for sale.

Study Guide Topics:Data Setup - > Store Product - > Inventory Check - > Search and Scan - > Order Capture

===============

An Action Plan Template intended for retail visit execution must be configured with Visit as its Target Object and then published before it can be associated with an individual Visit. The Target Object determines the Salesforce record type against which Action Plans created from the template can operate.

Salesforce ' s Consumer Goods configuration procedure specifies that administrators create an Action Plan Template, select Visit in the Target Object field, configure the appropriate Action Plan Type, add the required tasks and flows, and publish the template. A published template can subsequently be reused across multiple Visit records, which enables standardized store-execution processes.

To apply the template, a user opens the applicable Visit, selects New Plan from the Action Plan related section, and chooses the published Action Plan Template. Salesforce then presents the tasks contained in the template and creates the Action Plan for that specific visit. Only one Action Plan can be assigned to a Visit through this standard process.

This architecture separates reusable process design from visit-specific execution and ensures consistent field activities across stores.

Study Guide Topics:Visit Planning - > Action Plan Template - > Target Object - > Visit - > Publish Template

===============

Planogram analysis focuses on measurable shelf-compliance indicators such as Out of Stock, Share of Shelf, and product facings. These metrics allow a consumer goods organization to determine whether products are available, whether they occupy the expected proportion of shelf space, and whether the required number of product faces are visible to shoppers.

Salesforce defines Planogram Check as an assessment task used to track product displays and evaluate shelf execution. For planogram-related Retail Store KPIs, Salesforce explicitly maps Assessment Indicator Definitions to KPI types. Product-facing measurements use Facings, share-of-shelf measurements use Share of Shelf, and stock-availability measurements use Out of Stock. The facing measure is associated with individual products or SKUs when the organization needs to determine the number of visible product facings.

The underlying planogram model associates the reference Image with an In-Store Location and connects products to that location. During execution, those relationships provide the product-specific context required to assess whether the shelf configuration conforms to the intended merchandising arrangement. Shelf size itself is not one of the supported KPI types for this planogram-compliance configuration.

Study Guide Topics:Visit Execution - > Planogram Check - > Share of Shelf - > Facings - > Out-of-Stock Compliance

===============

The In-Store Survey experience uses contextually associated Survey Invitations rather than displaying every open survey invitation in the organization. The relevant contexts are the Visit, Retail Store, and Store Primary Contact.

Salesforce allows a Survey Invitation to be generated for a contact and associated with a Visit as the related record. When the Action Plan Template assigned to the visit contains an In-Store Survey task, this association makes the invitation available within the visit ' s survey execution context. Salesforce also supports generating the invitation from the Retail Store ' s primary contact and associating the survey with the applicable account or store context.

This design ensures that field representatives see surveys relevant to the specific retail engagement they are executing. Showing all open invitations or every invitation targeted to any contact or user would introduce unrelated survey records and would not preserve the visit-level execution context.

The relationship between the Survey, Survey Invitation, Primary Contact, Retail Store, and Visit therefore provides controlled survey distribution while ensuring that the correct questionnaire is available during the appropriate store visit.

Study Guide Topics:Visit Execution - > In-Store Survey - > Survey Invitation - > Visit - > Retail Store - > Primary Contact

===============

Einstein Visit Recommendations support Next Best Action strategies for determining which retail stores should be recommended for visits. Salesforce allows administrators to configure a recommendation strategy that evaluates relevant records and business criteria and produces prioritized visit recommendations for sales managers and field representatives.

A Next Best Action strategy can load relevant data, apply business rules, generate scores and reasons, and return recommendations that support store-visit planning. When a user creates a Visit Recommendation Request, the selected recommendation strategy is executed for the specified store and date context. Salesforce can also incorporate prediction information from Einstein Discovery when organizations require model-based recommendations.

The architecture separates recommendation logic from visit execution. Administrators can therefore create multiple strategies for different business priorities-for example, prioritizing stores with declining inventory, important upcoming promotions, or revenue opportunities. Salesforce documentation specifically supports both flow-based strategies and Next Best Action strategies for Einstein Visit Recommendations, enabling organizations to select the implementation approach that aligns with their planning logic and scalability requirements.

Accordingly, the ability to create Visit Recommendations through a Next Best Action Strategy is a standard supported configuration.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Next Best Action - > Recommendation Strategies - > Visit Prioritization

===============

The expected value for a planogram metric is defined on the Retail Store KPI. In the Consumer Goods Retail Execution data model, an Assessment Indicator Definition specifies what is measured, while the Retail Store KPI establishes the target or expected value against which the field representative ' s actual observation is evaluated.

When an administrator creates a Retail Store KPI, Salesforce requires selection of the relevant Assessment Indicator Definition and provides configuration fields for the Retail Store Group, In-Store Location Category, product or product category, planogram, KPI type, effective dates, and target value. Supported KPI types include Facing, Share of Shelf, Out of Stock, Inventory, Price, and Revenue. The administrator then defines the target value appropriate to the selected assessment indicator.

During visit execution, the representative captures an actual value. Salesforce stores visit-level actual information separately in the Retail Visit KPI and compares that value with the target defined in the Retail Store KPI. This separation enables consistent compliance measurement across multiple stores and visits while maintaining centrally managed targets.

Therefore, the Retail Store KPI is the configuration record responsible for holding the expected value used in planogram compliance measurement.

Study Guide Topics:Data Setup - > Retail Store KPI - > Assessment Indicator Definition - > Target Values - > Planogram Metrics

===============