AP-204 Salesforce Accredited Agentforce Consumer Goods Professional Questions and Answers

An Inventory Check requires the Retail Store KPI to identify the applicable Retail Store Group and Assessment Indicator Definition. These fields establish where the measurement applies and exactly what the field representative must measure.

The Retail Store Group is fundamental because Salesforce defines Retail Store KPIs at the store-group level rather than directly at an individual store level. The group connects the KPI configuration to the Retail Stores that inherit and use the target during field execution.

The Assessment Indicator Definition identifies the metric to be captured-for example, stock quantity, availability, damaged-product count, or another inventory-related measurement. Salesforce ' s Inventory Check prerequisites explicitly require the Retail Store Group and an Assessment Indicator Definition for the applicable product or product category and In-Store Location Category.

Custom Context is associated with custom-task configurations and should remain empty for a standard Inventory Check. Inventory Count is not the configuration field that establishes the Retail Store KPI relationship. KPI Type can categorize the business meaning of an indicator, but the core Inventory Check configuration depends on the Retail Store Group and Assessment Indicator Definition.

Together, these records enable Salesforce to generate the corresponding Retail Visit KPIs when the Inventory Check is instantiated for a Visit.

Study Guide Topics:Data Setup - > Retail Store KPI - > Inventory Check - > Retail Store Group - > Assessment Indicator Definition

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

The Retail Execution assessment architecture uses Retail Store KPIs as the configuration basis for Retail Visit KPIs. Salesforce states that when an Action Plan Template is assigned to a Visit, Assessment Tasks are generated from the Assessment Task Definitions and Retail Visit KPI records are created based on the applicable Retail Store KPIs. This preserves the connection between the expected target configured centrally and the actual value captured during a specific visit.

Flows can also be associated with an Action Plan Template to support business-specific store activities. Salesforce supports flow input parameters named visitId and assessmentTaskId. A flow can accept only visitId, only assessmentTaskId, both parameters, or no parameters depending on the activity being implemented. When the identifiers are used, Salesforce passes the current Visit and Assessment Task context into the flow so that the automation operates on the appropriate execution records.

This model keeps responsibilities clearly separated: Retail Store KPI contains the target context; Retail Visit KPI records the visit-specific assessment result; Assessment Task identifies the executable activity; and Visit establishes the retail engagement within which the task occurs.

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

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

The Retail Store object includes retail-execution-specific attributes such as Delivery Method, Preferred Visit Hours, and Payment Method, which provide operational details required for managing field sales and distribution activities.

Delivery Method describes how orders are delivered to the store and supports logistics and Direct Store Delivery planning. Preferred Visit Hours identifies the periods during which field representatives should ideally visit the outlet and contributes to effective visit and route planning. Payment Method records the payment arrangement applicable to the retail location and supports store-specific commercial execution.

Salesforce ' s Retail Store data model explicitly includes fields corresponding to DeliveryMethod, PreferredVisitHoursText, and PaymentMethodId. It also contains attributes for delivery frequency, opening and closing times, recommended visit frequency, pricing strategy, primary contact, priority, and related retail-location information.

Shipping Address is a standard concept already available in the Account data model and therefore does not serve as a distinguishing Retail Store attribute. Operating Hours are handled through the broader operating-hours model and relationship rather than being one of the three specific Retail Store fields represented by the choices.

These store-specific attributes allow Agentforce Consumer Goods to distinguish the operational requirements of an individual physical outlet from its parent customer Account.

Study Guide Topics:Data Setup - > Retail Store - > Delivery Method - > Preferred Visit Hours - > Payment Method

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

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

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

Retail Execution Lightning Plus provides the Retail Execution entitlement associated with strategic sales functionality in Consumer Goods Cloud. Einstein Visit Recommendations operate within the Retail Execution environment and help sales managers and field representatives determine which stores should be visited based on configurable recommendation strategies.

Salesforce documents the Lightning Retail Execution Plus permission set license as the Retail Execution license for Consumer Goods strategic sales users. The Retail Execution license framework provides access to Consumer Goods capabilities that are not included in the underlying Salesforce user license.

Einstein Visit Recommendations must also be enabled in Setup. Once configured, authorized sales managers and field representatives can create recommendation requests and schedule store visits based on the recommendations returned by Salesforce. Recommendation logic can be implemented using either a Flow strategy or a Next Best Action strategy, enabling organizations to align the feature with specific business-planning requirements.

CRM Analytics permission sets govern access to analytics applications and dashboards, while Lightning Direct Store Delivery provides access to DSD-specific functionality. Action Plans provide access to the Action Plan framework. For Visit Recommendation execution within Retail Execution, Retail Execution Lightning Plus is the applicable choice.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Retail Execution Permissions - > Recommendation Strategies

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

Endcaps should be represented as In-Store Locations and In-Store Location Categories, with Retail Store KPIs specifically configured for that merchandising context. This allows NTO to measure endcap performance independently from primary shelves, checkout counters, backrooms, or other store areas.

Salesforce ' s Agentforce Consumer Goods data model supports In-Store Location categories precisely for this purpose. Similar physical locations across stores can be categorized-for example, Endcap Displays-and Retail Store KPIs can then use that category to define the measurements and targets applicable to those locations.

Salesforce ' s own Retail Execution configuration examples demonstrate creating Retail Store KPIs specifically for the Endcap Displays category. A promotion-compliance KPI can include the Retail Store Group, Endcap Displays as the In-Store Location Category, the relevant Assessment Indicator Definition, Promotion, Product Category, and a Boolean target value. This allows field representatives to capture endcap-specific performance during visits while managers analyze the resulting Retail Visit KPI data separately.

Creating Retail Store record types or unrelated custom objects would not provide the appropriate KPI granularity. Dedicated KPI configuration for the endcap context uses the standard Consumer Goods data model and provides targeted merchandising measurement.

Study Guide Topics:Data Setup - > In-Store Locations - > Endcap Displays - > Retail Store KPI - > Assessment Indicators

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

Sales Rep Performance, Store Insights, and Product Performance are standard analytics dashboards provided for Consumer Goods Retail Execution.

The Sales Rep Performance dashboard enables sales managers to compare representatives, identify high- and low-performing team members, and analyze performance trends over time. Metrics can include revenue, product sales, visits, compliance, and other Retail Execution measurements.

The Store Insights dashboard provides store-focused analysis. It enables users to examine store sales, compliance metrics, product performance, visits, and related trends to identify outlets that require attention. Salesforce documents Store Insights as one of the embedded dashboards available within the Consumer Goods analytics experience.

The Product Performance dashboard provides product- and category-level insights. Sales managers can identify high- and low-performing products, review revenue and quantity trends, analyze compliance, and determine which products require intervention.

The native analytics portfolio contains additional dashboards such as Store Performance, Territory Performance, Whitespace Analysis, and Sales Manager Home. Category Insights and Inventory Performance are not the corresponding standard dashboard names represented by these options.

Study Guide Topics:Analytics - > CRM Analytics - > Sales Rep Performance - > Store Insights - > Product Performance

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

The Whitespace Analysis dashboard is specifically designed to identify opportunities to introduce additional products or product categories into stores. It analyzes sales information across products, categories, and retail locations to expose areas where a store has unused sales potential.

Salesforce describes whitespace as an opportunity where a product or category that performs successfully elsewhere is not currently generating sales in a particular store. The dashboard allows sales managers to evaluate revenue and quantity patterns, identify top-performing products, compare performance across stores, and determine where introducing a product could increase revenue. This makes it directly applicable to GreenTech ' s requirement to determine which new products may be suitable for a particular retail location.

The dashboard can answer questions such as which stores have the potential to sell top-selling products and whether a product or category can be introduced into additional stores. It also provides product-performance trends so the sales manager can evaluate whether a candidate product has demonstrated sufficiently strong performance elsewhere before expanding distribution.

Therefore, Whitespace Analysis provides the cross-selling and assortment-expansion insight needed for this scenario.

Study Guide Topics:Analytics - > CRM Analytics - > Whitespace Analysis - > Product Opportunities - > Store Sales Potential

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

Consumer Goods supports product-focused promotions at the Product Category and individual Product levels. These levels determine the merchandise scope against which promotional activities and Promotion Checks are configured.

A Product Category-level promotion is used when a promotional activity applies to a group of related products. Salesforce gives the example of applying a discount across an entire beverage category and then using a category-level Promotion Check to measure the resulting promotional execution and sales impact.

A Product-level promotion applies to individual products. For example, a consumer goods organization can promote a newly launched product through free samples and then use a product-level Promotion Check to capture consumption or customer feedback.

Salesforce also supports a General Promotion, which has no Product or Product Category context. Retail Store and Retail Store Group are not promotion product levels; instead, they define where the promotion applies. That geographic or organizational reach is established through Promotion Channel, which can associate a Promotion with a store, store group, or account.

This separation lets administrators independently configure the merchandise scope and retail distribution scope of each promotion.

Study Guide Topics:Data Setup - > Promotion - > Product Category - > Product - > General Promotion - > Promotion Channel

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

The consultant should create an In-Store Location named Frozen Food Aisle. In-Store Locations represent distinct physical areas within a Retail Store and provide the location context required by Retail Execution tasks such as Inventory Checks and Planogram Checks.

Salesforce uses In-Store Location records to model store areas including shelves, aisles, checkout counters, backrooms, and promotional displays. Each location can be associated with an In-Store Location Category so equivalent physical areas across stores can be grouped and managed consistently. Salesforce ' s Retail Execution guidance demonstrates creating specific In-Store Location records directly from the Retail Store record and assigning appropriate location types and categories.

Products can then be associated with the relevant store location through Store Product. During an Inventory Check, the representative can select the appropriate In-Store Location and capture product availability, facings, share of shelf, or out-of-stock information for products located there.

Product2 represents the commercial SKU and does not identify its physical placement inside an individual outlet. Creating custom picklists or record types would duplicate the standard store-location model.

Study Guide Topics:Data Setup - > In-Store Location - > Inventory Check - > Store Product - > Store Layout

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

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

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

Frequently purchased products can be prioritized for a specific outlet by associating them through Store Product and marking the appropriate products as Favorite. Store Product represents the relationship between Product2 and a Retail Store or specific In-Store Location, which allows Salesforce to maintain outlet-specific merchandising and ordering attributes.

The Store Product data model includes both Is Favorite and Default Order Quantity. These attributes are designed to streamline recurring order capture. Salesforce explains that field representatives can prioritize favorite products when creating orders so commonly purchased items are replenished efficiently and remain in stock. Default Order Quantity can further reduce data entry by predefining the quantity normally ordered for the product.

Salesforce ' s Retail Execution configuration also allows products associated with a store to be marked as favorites. The Inventory and ordering user interfaces can expose favorite products as a focused subset, reducing the time required to create routine orders.

This makes Store Product the correct outlet-specific mechanism for modeling frequently ordered products rather than creating artificial Order records with a template status.

Study Guide Topics:Visit Execution - > Order Capture - > Store Product - > Favorite Products - > Default Order Quantity

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

The Retail Visit KPI provides the visit-level relationship between the configured KPI framework and the Assessment Task that is executed in the field. Retail Store KPI defines expected values, while Retail Visit KPI captures the actual measurement generated during a specific Visit and Assessment Task.

Salesforce ' s Consumer Goods data model shows that Retail Visit KPI includes references to Assessment Task, Visit, Assessment Indicator Definition, Product, Product Category, In-Store Location, Promotion, Planogram, and other assessment context. It also contains the Target Value and Actual Value used to evaluate store performance.

The records are created as part of the assessment-task generation process. When an Action Plan Template is assigned to a Visit, Salesforce creates Assessment Tasks based on the included Assessment Task Definitions and creates Retail Visit KPIs based on the applicable Retail Store KPIs.

This design enables one centrally configured Retail Store KPI to drive repeated measurements across many store visits. Each individual visit receives its own Retail Visit KPI record, allowing the actual execution result to remain associated with the Assessment Task that produced it.

Study Guide Topics:Data Setup - > Retail Visit KPI - > Retail Store KPI - > Assessment Task - > Actual and Target Values

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

Because the promotion applies to all energy bars, the Retail Store KPI should be configured at the Product Category level. Salesforce supports promotion checks at the Product Category, individual Product, and General Promotion levels. Product Category is the appropriate level when a promotional activity applies uniformly to a group of related products.

A category-level configuration minimizes administrative overhead because a single KPI configuration can represent the target for the complete energy-bar category rather than requiring individual KPI records for every SKU. Salesforce allows the administrator to associate a Product Category with a Retail Store KPI together with the Assessment Indicator Definition, Retail Store Group, In-Store Location Category, promotion, KPI type, and target value.

An SKU-level configuration would be appropriate when each individual product requires separate measurement or targets. In this scenario, however, the same BOGO promotion applies across the full energy-bar category, so SKU-specific records would unnecessarily increase data volume and maintenance.

Custom Context applies primarily to custom assessment tasks rather than standard promotion-check configuration. Consequently, Product Category provides the correct granularity while supporting scalable and maintainable Retail Store KPI administration.

Study Guide Topics:Data Setup - > Promotions - > Product Categories - > Retail Store KPI - > Promotion Checks

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

Setting up an In-Store Survey requires configuration of the Salesforce Survey, the corresponding In-Store Survey Assessment Task Definition, and an appropriate Survey Invitation.

The administrator first creates and prepares the Survey using Salesforce Surveys. This record contains the questions and response structure that the participant will complete. Next, the administrator creates an Assessment Task Definition and selects In-Store Survey as its task type. Assessment Task Definitions store reusable activities that can be incorporated into an Action Plan Template and subsequently instantiated as Assessment Tasks when that template is applied to a Visit.

The Survey must also be distributed through a Survey Invitation. Salesforce ' s Consumer Goods setup procedure supports generating the invitation from the primary contact of the Retail Store, associating the survey with the applicable related record, and then making it available from the task section of the Visit.

Assessment Indicator Definitions and Retail Store KPIs are primarily used for target-based compliance and KPI assessment processes. The In-Store Survey workflow instead relies on Salesforce Surveys, Survey Invitations, and the In-Store Survey Assessment Task Definition to deliver and execute the questionnaire during a retail visit.

Study Guide Topics:Data Setup - > Salesforce Surveys - > In-Store Survey - > Assessment Task Definition - > Survey Invitation

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

Salesforce Lightning pages can combine standard platform components with components specifically provided for Consumer Goods Retail Execution. The applicable combination is Quip Documents, Einstein Predictions, and Custom Object Task List.

The Quip Document component allows administrators to embed collaborative Quip documents directly on Salesforce record pages. Users can create, view, and edit supporting documents without leaving Salesforce. The component is configured through Lightning App Builder and can use either individual documents or reusable templates.

The Einstein Predictions component displays deployed Einstein Discovery predictions and recommendations on standard or custom-object record pages. Administrators add the component using Lightning App Builder and select the applicable deployed prediction model.

For Retail Execution, Salesforce provides Custom Object Task List as one of the standard Consumer Goods mobile components. It is scoped to Assessment Task and can be incorporated into customized mobile pages together with other Consumer Goods components such as Inventory Check, Promotion List, Planogram List, and In-Store Products.

The other option sets contain capabilities that are not identified as corresponding Lightning page components for this configuration.

Study Guide Topics:Platform - > Consumer Goods Mobile App - > Lightning App Builder - > Quip - > Einstein Predictions - > Custom Object Task List

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

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

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

Actual KPI values captured by a field representative during visit execution are stored in the Retail Visit KPI record. Salesforce separates KPI configuration from transactional execution data so that planned or target values remain distinct from values observed during individual visits.

The Retail Store KPI defines the target or expected value for a particular Assessment Indicator Definition. It provides the planning context, including the Retail Store Group, product or product category, In-Store Location Category, Custom Context, and target value. When an assessment task is generated for a visit, Salesforce creates the corresponding Retail Visit KPI records that represent the runtime measurements.

During execution, the field representative records the observed value. Salesforce stores fields such as the Actual Value, Target Value, Assessment Indicator Definition, Product, In-Store Location, and Custom Context on the Retail Visit KPI.

This architecture allows Salesforce to compare expected performance with actual field results across multiple visits. The custom object can supply the business context for a custom task, but it does not replace the Retail Visit KPI as the repository for actual assessment measurements.

Study Guide Topics:Data Setup - > Custom Tasks - > Retail Store KPI - > Retail Visit KPI - > Actual Values

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

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

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

CRM Analytics for Agentforce Consumer Goods requires a minimum set of records before the Analytics for Consumer Goods app can be successfully created. Salesforce identifies the required data objects as Account, RetailStore, Visit, RetailVisitKpi, and Product2. An Order record is additionally required when the organization wants to include both Retail Execution and sales data.

The Retail Visit KPI requirement is particularly important because Retail Visit KPI records contain actual information captured during visits against the Assessment Indicator Definitions and targets configured for Retail Execution. These records provide the analytics layer with visit-level compliance and performance measurements that can be used in dashboards for store performance, product performance, territory analysis, and other Retail Execution insights.

Retail Visit KPI records are generated as part of the assessment-task process based on the underlying Retail Store KPI configuration. Salesforce therefore requires at least one RetailVisitKpi record in the organization when validating the data prerequisites for the CRM Analytics application.

The analytics setup process validates these minimum data requirements and displays a message when required records are missing.

Study Guide Topics:Analytics - > CRM Analytics for Agentforce Consumer Goods - > Data Requirements - > Retail Visit KPI - > Retail Execution Analytics

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

An Einstein object-detection implementation depends on three essential elements: a suitable training dataset, a properly trained and evaluated model, and appropriate user access to the functionality.

The implementation begins by collecting representative images of the products or objects that must be detected. For object detection, the training images require labeled bounding boxes identifying the position and dimensions of each object. These examples are uploaded as a dataset and used by the training process to create an object-detection model.

The trained model should then be evaluated before deployment. Salesforce ' s model-training architecture reserves data for testing and provides model information that allows implementers to evaluate the model ' s detection performance. Reviewing model quality before exposing the capability to field representatives is essential because representative training data and adequate model performance directly affect detection results.

Finally, the field users who execute the functionality require the relevant access and permissions. Permissions are part of the Salesforce security model and determine whether users can access the required Consumer Goods and Einstein functionality.

OCR configuration and competitor-suppression datasets are not baseline requirements for this object-detection setup.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Dataset - > Model Training - > User Permissions

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

For a scalable Visit Recommendation strategy, Salesforce recommends implementing the selection logic through an Apex class. Visit Recommendations can use programmable logic to determine which stores should receive recommendations based on organization-specific criteria, and Apex is appropriate when the strategy must operate at business scale.

Salesforce allows an Apex class to select the stores for which Einstein should provide Visit Recommendations. The Apex method is exposed to automation by using @InvocableMethod, after which the class can be invoked from the Visit Recommendation strategy or from an autolaunched flow.

Salesforce also supports a Flow strategy for Visit Recommendations, but its documentation specifically notes that the flow-only method is not scalable for a business use case and recommends using Apex for scalable implementations. An Apex implementation gives developers greater control over bulk processing, complex filtering, reusable business logic, and Salesforce governor-limit considerations.

The strategy can return the recommended Store IDs and recommendation reasons so sales managers and field representatives understand both which stores should be visited and why those stores have been prioritized.

Workflow and Process Builder are not the architecture Salesforce defines for this Visit Recommendation capability.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Invocable Methods - > Scalable Recommendation Strategies

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

The Assessment Indicator Definition defines the KPI or measurable parameter that field representatives capture during Retail Execution. It provides the reusable definition of what must be measured, such as the number of products on a shelf, product facings, stock availability, promotional compliance, or another store-performance indicator.

Salesforce supports several data types for Assessment Indicator Definitions, including Number, Boolean, Date Time, Text, Decimal, and Picklist. The definition can then be associated with one or more Assessment Task Definitions covering products, product categories, promotions, planograms, or custom assessment scenarios.

The Assessment Indicator Definition works together with two additional KPI objects. A Retail Store KPI associates the indicator with its business context and defines the expected or target value. A Retail Visit KPI stores the actual result captured by the field representative during a specific visit. Salesforce therefore separates the reusable KPI definition, target configuration, and transactional result into distinct layers.

This design enables the same Assessment Indicator Definition to be reused across multiple store groups, products, locations, and visits while maintaining separate targets and actual values for each applicable context.

Study Guide Topics:Data Setup - > Assessment Indicator Definition - > Retail Store KPI - > Retail Visit KPI - > KPI Measurement

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

The planogram Image record is associated with an In-Store Location. This relationship identifies the specific physical area of the retail store where the reference shelf arrangement applies.

Salesforce ' s Planogram Check prerequisites require administrators to create an Image record representing the planogram and then associate that Image with the appropriate In-Store Location. Typical In-Store Locations include primary shelves, aisles, checkout counters, endcaps, and other areas where products are displayed.

The association is important because a single Retail Store can contain many merchandising locations, each with a different expected layout. Linking the planogram directly to its In-Store Location enables Salesforce to present the correct reference image when a field representative performs a Planogram Check at that particular location.

The Retail Store KPI then references the corresponding In-Store Location Category, Assessment Indicator Definition, Image or planogram, product context, and KPI Type. During execution, the field representative can open Product Details within the Planogram Check and view both the products to be inspected and the associated reference image.

Therefore, the Image object containing the planogram is related to the In-Store Location where that planogram must be evaluated.

Study Guide Topics:Data Setup - > Planogram - > Image - > In-Store Location - > Planogram Check

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

The Promotion Channel object establishes the association between a Promotion and the retail destination where the promotion applies. Salesforce uses this intermediary object so that a single promotion can be distributed flexibly across different stores, store groups, or customer accounts.

In the Consumer Goods Retail Execution data model, Promotion represents the promotional activity itself. Promotion Channel is defined as the association of a Promotion with a Retail Store, Retail Store Group, or Account. This structure supports many-to-many promotional relationships without requiring the Promotion object to maintain a direct relationship with every individual retail location.

Product participation is modeled separately. Promotion Product associates a Promotion with an individual Product2 record, while Promotion Product Category connects a Promotion with a product category. This distinction allows Salesforce to separate two important questions: what merchandise is included in the promotion, and where the promotion is being executed.

During Promotion Check execution, these relationships enable Salesforce to identify the promotion applicable to the visited store and determine its associated product or category context.

Therefore, Promotion Channel is the standard object directly associated with Promotion for defining its retail distribution context.

Study Guide Topics:Data Setup - > Promotion - > Promotion Channel - > Promotion Product - > Retail Store

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

Salesforce supports Promotion Checks at three defined levels: General Promotion, Individual Product, and Product Category. These levels determine the commercial context against which a field representative performs the promotional compliance assessment.

A Product Category-level Promotion Check is appropriate when the promotion applies across a category of products. For example, an organization may discount all beverages or energy bars and assess compliance collectively rather than creating an independent promotion check for each SKU.

An Individual Product-level Promotion Check is used when a promotion applies to a specific product, such as the launch of a new flavor or an in-store sampling activity. The field representative evaluates execution specifically for that product.

A General Promotion does not require association with a particular product or product category. It is suitable for store-wide activities such as coupons, signage, or general promotional conditions that apply across the outlet.

These three levels allow promotion configuration to match the intended scope while avoiding unnecessary duplication of promotional records and assessment tasks. Salesforce uses the same levels when defining the promotion and when executing the corresponding Promotion Check in the field.

Study Guide Topics:Visit Execution - > Promotion Check - > General Promotion - > Product - > Product Category

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