Consumer-Goods-Cloud-Accredited-Professional Consumer Goods Cloud Accredited Professional (AP-204) Question and Answers

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

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

Direct Store Delivery requires both the correct Action Plan configuration and the required user permissions. First, the administrator creates an Action Plan Template and adds a Delivery Task to it. When that template is assigned to a Visit, Salesforce creates the corresponding Delivery Task record for execution during the store visit.

Second, users who need to perform Direct Store Delivery functionality require the applicable Lightning Direct Store Delivery access. Salesforce identifies this permission set license for Direct Store Delivery capabilities in the Consumer Goods base data model. Delivery Tasks can then be associated with Shipments, which define the products to be delivered through related Product Transfer records.

Third, the Sales Manager requires access to Action Plans. Salesforce specifies the Action Plans permission set, or equivalent administrative privileges, for configuring and working with Action Plan Templates and Action Plans.

Assessment Indicator Definitions are used for KPI-based assessment activities and are not required to define the Delivery Task itself. The delivery process instead relies on the Delivery Task, Action Plan, Shipment, and Product Transfer architecture. Together, these three configuration steps provide the task definition, execution permission, and Action Plan access required for DSD operations.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Action Plan Template - > Permissions

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

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

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

The Sales Manager persona is responsible for managing the day-to-day Retail Execution processes performed by the field organization. Salesforce explicitly defines the Sales Manager as a standard Retail Execution user who can create visits, create tasks, and assign visits to field representatives.

This division of responsibilities is fundamental to the Agentforce Consumer Goods operating model. Sales managers coordinate retail coverage and determine what activities field representatives should perform at each store. They typically work with Retail Stores, Visits, Action Plans, Assessment Task Definitions, and Action Plan Templates to organize execution activities. By contrast, field representatives have a more execution-focused role: they review assigned visits, complete assessment tasks, capture observations, process orders, and record the results of store activities.

The permission model is designed around these personas. Salesforce recommends establishing separate permission configurations for Sales Managers and Field Reps so that each role receives the appropriate object-level and feature access. Delivery representatives can also be configured separately when the organization uses Direct Store Delivery.

Consequently, responsibility for creating and coordinating visits and assigning field work belongs to the Sales Manager persona.

Study Guide Topics:Platform - > User Personas - > Sales Manager - > Visit Management - > Task Assignment

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

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 Store Performance Dashboard is designed for sales managers who need to evaluate store-level Retail Execution performance and identify locations requiring intervention. It provides consolidated analysis of store KPIs, compliance trends, visits, and business performance rather than limiting the analysis to one representative, product, or individual visit.

Salesforce describes the Store Performance dashboard as answering two fundamental questions: how stores are performing based on Retail Execution KPIs and which stores need attention. It also provides correlation analysis showing how Retail Execution KPIs affect store performance and how store visits influence compliance and revenue.

The underlying metrics include Average Store Compliance and changes in compliance over the selected comparison period. Salesforce calculates these measurements from Retail Visit KPI records, allowing managers to identify stores whose compliance is deteriorating relative to an earlier period. Metrics such as facing compliance, price compliance, share-of-shelf compliance, inventory compliance, and out-of-stock compliance can contribute to the analysis.

Consequently, the Store Performance Dashboard provides the appropriate management-level view for locating stores with declining Retail Execution KPI performance.

Study Guide Topics:Analytics - > Store Performance - > Retail Execution KPIs - > Compliance Trends - > Stores Needing Attention

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

The Nearby Map component on the Promotion record page provides the required functionality through standard Salesforce Maps configuration with minimal custom development.

Salesforce specifically documents the use of a Nearby Map component for Consumer Goods scenarios. Administrators create a Nearby Map configuration using an appropriate Maps layer and then place the Maps Nearby Maps component on a Lightning Record Page through Lightning App Builder. The layer determines which business records are displayed and how they are filtered.

For promotions, Salesforce gives this precise use case: administrators can configure a Nearby Map with a layer containing Retail Stores and place that component on the Promotion record page. When a sales manager views the Promotion record, the component displays retail stores participating in the promotion in a map-based interface. This allows the manager to visualize nearby participating stores without leaving the promotion context.

Because the capability is supplied through Salesforce Maps and Lightning App Builder, it avoids developing a custom visual mashup or modifying an unmanaged AppExchange package. Adding a generic map to the Home page would also lack the Promotion record context needed to display stores associated with the specific promotion.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Nearby Map - > Promotion - > Retail Store Visualization

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

The frozen food aisle should be modeled as an In-Store Location. In-Store Location represents a specific physical area inside a retail store where products are displayed, stored, or evaluated. Salesforce identifies aisles, shelves, checkout counters, endcaps, and back rooms as typical examples.

Once the Frozen Food Aisle record is created, products can be associated with that location through Store Product. Store Product establishes the relationship among the Retail Store, Product2, and the applicable In-Store Location. This gives the Inventory Check sufficient context to tell the field representative exactly where the product should be inspected.

The In-Store Location can also be assigned an In-Store Location Category. Categories make it possible to group equivalent locations across multiple stores and configure Retail Store KPIs consistently for a store group. For example, all frozen-food aisles could share a category and common inventory-assessment rules.

Adding a custom picklist or task/store record type would duplicate functionality already provided by the standard Consumer Goods data model. Product2 identifies the commercial product; it does not by itself describe the product ' s physical placement within an individual store.

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

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

The Retail Store Group is a required field when configuring a Retail Store KPI. Retail Store KPIs establish target values for Assessment Indicator Definitions and provide the relationship between business metrics and the stores where those metrics must be evaluated. Salesforce defines these targets at the store-group level rather than directly at an individual retail store.

The Retail Store Group provides the organizational scope for the KPI. A single Retail Store Group can contain multiple Retail Stores with common operational characteristics, enabling administrators to apply consistent targets across those locations without creating separate KPI definitions for every store. Additional context can then be supplied through Product, Product Category, Promotion, Planogram, In-Store Location Category, and Assessment Indicator Definition fields.

Salesforce explicitly identifies Retail Store Group as required when creating a Retail Store KPI because KPIs cannot be defined directly at the individual-store level. Effective dates and KPI Type provide additional configuration context, but they do not replace the fundamental store-group association required to establish where the target applies.

Study Guide Topics:Data Setup - > Retail Store KPI - > Retail Store Group - > Assessment Indicator Definitions - > KPI Targets

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

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

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

In-Store Survey execution depends on both an available Salesforce Survey and a corresponding Survey Invitation. The survey supplies the questionnaire that the field representative must complete, while the invitation creates the specific survey instance that becomes available in the context of the visit, retail store, or contact.

Salesforce ' s Consumer Goods configuration process requires the administrator to set up and activate the survey before it can be distributed. An Assessment Task Definition of type In-Store Survey is then incorporated into the Action Plan Template used for the visit. To expose the actual survey instance, Salesforce requires a Survey Invitation to be generated, commonly through the Retail Store ' s primary contact. The invitation is associated with the relevant records so that it appears within the survey task during visit execution.

Field representatives do not require permission to create surveys merely to respond to them. Survey authoring is an administrative function. Likewise, the standard process does not depend on creating a custom task definition or on a separate Retail Execution Survey Lightning Flow.

Therefore, absence of either the activated Survey or the related Survey Invitation prevents the survey from being available to the field representative.

Study Guide Topics:Visit Execution - > In-Store Survey - > Salesforce Surveys - > Survey Invitations - > Visit

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

A Retail Store can be associated with many Visit records, creating the required one-to-many relationship. Each Visit represents a particular scheduled or completed engagement between a field representative and a physical retail location, while the same store can naturally be visited repeatedly over time.

Salesforce describes the Visit object as tracking information about a field representative ' s visit to a Retail Store where retail activities are performed. Visit records hold information such as planned and actual start and end times, status, visitor, priority, and the related location.

For Consumer Goods implementations, the Visit ' s Place relationship identifies the Retail Store being visited. Salesforce Maps uses the same model when scheduling Consumer Goods visits: Visit records can derive their map location from the related Retail Store through Place ID, allowing Maps to position each Visit at the correct physical outlet.

Because representatives return to stores according to visit frequencies, merchandising schedules, promotions, deliveries, and sales requirements, a single Retail Store can accumulate multiple Visit records over its lifecycle. Each Visit remains a distinct transaction with its own Action Plans, tasks, KPIs, timing, and execution results.

Study Guide Topics:Data Setup - > Retail Store - > Visit - > Place Relationship - > Store Visit History

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

For a particular retail outlet, frequently ordered products can be modeled through Store Product records and marked as Favorite. Store Product establishes the product-to-store relationship and provides outlet-specific ordering attributes that streamline repetitive order capture.

Salesforce ' s Consumer Goods data model includes both Is Favorite and Default Order Quantity on Store Product. This allows a frequently purchased SKU to be marked as a preferred product for the store and assigned the quantity that is normally ordered.

Salesforce Trailhead demonstrates this configuration directly. Administrators or sales managers associate products with a store or In-Store Location, select the Favorite checkbox, and optionally enter a Default Order Quantity. During order capture, field representatives can sort or filter for favorite products, helping them quickly locate the outlet ' s commonly purchased items and replenish them using the expected quantities.

This approach is outlet-specific because the favorite designation resides on the relationship between the product and the Retail Store rather than globally on Product2. It therefore accommodates situations where the same product may be frequently purchased by one store but not another.

Saved carts and Account-level assortment records do not provide this same store-specific favorite-product mechanism.

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

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

For a Visit Recommendation implementation that must scale to production business volumes, the recommendation-selection logic should be implemented using an Apex class.

Salesforce supports Flow-based strategies for Einstein Visit Recommendations, but its documentation explicitly states that the flow-only approach is not scalable for a business use case and recommends using Apex for scalable Visit Recommendation processing.

With Apex, a developer can implement the business logic needed to identify the Retail Stores for which Einstein should generate recommendations. The Apex method can be exposed through an invocable action and incorporated into the recommendation strategy or an associated flow. This architecture provides more control over bulk processing, complex filtering, governor-limit management, reusable logic, and enterprise-scale execution.

Salesforce ' s Visit Recommendation setup documentation supports both Flow and Apex approaches. It specifically provides an Apex-based option to select the list of stores for which recommendations should be generated and then use that Apex action within the recommendation framework.

Workflow Rules and Process Builder are not the supported architectural mechanisms for implementing scalable Einstein Visit Recommendation strategies.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Scalability - > Recommendation Strategy

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

The Inventory Check Lightning component is available for placement directly on an Assessment Task record page. Salesforce allows administrators to create or customize an Assessment Task Record Page through Lightning App Builder and add Consumer Goods-specific components that support field execution.

For the Assessment Task object, Salesforce documents the available components as Planogram List, In-Store Products, Promotion List, Inventory Check, and Consumer Goods Survey List. The Inventory Check component provides the dedicated interface for inventory-related assessment tasks and can expose information such as progress, summary information, location filtering, and assessment sections.

The wording of the other choices is important. Salesforce provides Planogram List, rather than a component named Planogram Check, and Promotion List, rather than a component named Promotion Check. Likewise, the supported product component is named In-Store Products, not In-Store Products Check.

After adding the Inventory Check component, the administrator can configure its component properties and activate the Lightning Record Page for the appropriate application, record type, and user profiles. This configuration provides field representatives with the required mobile or desktop execution interface when they open an inventory-related Assessment Task.

Study Guide Topics:Platform - > Lightning App Builder - > Assessment Task Record Page - > Inventory Check Component

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

For a product-level Inventory Check, the product must be associated with the Retail Store where the assessment will be executed. Retail Execution needs a store-specific product relationship so Salesforce can determine which products are available for assessment when the field representative opens the Inventory Check.

Salesforce ' s Inventory Check prerequisites explicitly require administrators to associate Products with the Retail Store and associate the applicable In-Store Locations with that same Retail Store. The Retail Store must also belong to the Retail Store Group selected on the Retail Store KPI.

The Retail Store KPI then defines the assessment target by combining the Retail Store Group, applicable In-Store Location Category, Assessment Indicator Definition, and Product or Product Category. Salesforce separately specifies that the Product field is required on a Retail Store KPI when inventory-check tasks are configured for the store group.

The Store Product relationship provides the standard data-model mechanism for associating an individual Product2 SKU with a Retail Store or particular In-Store Location. A Promotion or Product Category relationship serves a different business purpose, while an Assortment defines a collection of products eligible for sale rather than replacing the required store-product association for Inventory Check execution.

Study Guide Topics:Data Setup - > Inventory Check - > Product - > Retail Store - > Store Product - > Retail Store KPI

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

Users who need to access the CRM Analytics application for Consumer Goods require both the CRM Analytics Plus User entitlement and the CG Analytics User permission set. In the terminology used by this question, CRM Analytics Plus User corresponds to Tableau CRM Plus User.

Salesforce separates platform analytics access from Consumer Goods-specific analytics permissions. CRM Analytics Plus User provides access to CRM Analytics capabilities, while CG Analytics User grants the permissions required to consume the Consumer Goods analytics application and its associated dashboards and datasets.

Salesforce ' s documented setup process instructs administrators to open the user ' s Permission Set Assignments and assign CG Analytics User together with CRM Analytics Plus User when the organization uses CRM Analytics for Consumer Goods Cloud.

This dual-permission approach ensures that the user has both the underlying analytics platform entitlement and the Consumer Goods application-level access required to view dashboards such as product, store, field-representative, and territory performance analytics.

Administrative permissions such as CRM Analytics Plus Admin are intended for administrators who configure and maintain analytics applications. They are not necessary for ordinary application consumers who only need to view and interact with Consumer Goods analytics.

Study Guide Topics:Analytics - > CRM Analytics - > CG Analytics User - > CRM Analytics Plus User - > User Permissions

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

The supported Retail Store KPI types include Price, Facing, and Revenue, along with Share of Shelf, Out of Stock, and Inventory. KPI Type identifies the business interpretation of the Assessment Indicator Definition associated with a Retail Store KPI and is particularly important for Retail Execution measurements and analytics.

Facing is used when the organization measures the number of product facings visible on a shelf or display. It commonly supports planogram and merchandising compliance. Price supports assessments where the field representative records and evaluates the displayed or observed product price. Revenue provides the business classification for revenue-oriented performance measures.

Salesforce ' s Retail Store KPI configuration explicitly provides these values in the KPI Type picklist: Facing, Share of Shelf, Out of Stock, Inventory, Price, and Revenue. The KPI Type can also contribute to calculated performance indicators such as average facing compliance, average out-of-stock compliance, and average price compliance.

Promotion is business context rather than a KPI Type; a Promotion can instead be associated with the Retail Store KPI. Units can function as a unit of measure or assessment concept but is not one of the supported KPI Type values identified for the Retail Store KPI.

Study Guide Topics:Data Setup - > Retail Store KPI - > KPI Type - > Facing - > Price - > Revenue

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

A promotion is linked to a Retail Store through a Promotion Channel record. Salesforce uses Promotion Channel as the association object that determines where a promotional activity applies within the Consumer Goods Retail Execution data model.

The Promotion object defines the promotional activity itself, while related objects provide its product and distribution context. Promotion Product associates a promotion with an individual Product2 record, and Promotion Product Category associates the promotion with a product category. Promotion Channel, in contrast, associates the promotion with its intended retail destination.

Salesforce defines Promotion Channel as the association of a Promotion with a Retail Store, Retail Store Group, or Account. This design allows a promotion to be distributed at the most appropriate organizational level. For example, a promotion can target one individual outlet, all stores belonging to a particular retail group, or stores associated with an account.

This relationship also supports field execution. When a representative performs a Promotion Check, Salesforce can determine which promotions are applicable to the store being visited and present the appropriate promotion information and compliance assessments.

Therefore, Promotion Channel provides the standard data-model relationship between a Promotion and a Retail Store.

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

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

Users performing Delivery Tasks in the Consumer Goods base data model require access to the Lightning Direct Store Delivery functionality. Salesforce specifically identifies the Lightning Direct Store Delivery permission set license as the feature-specific entitlement required for Direct Store Delivery and van-sales functionality on the base data model.

Delivery Tasks involve objects and functionality beyond general Retail Execution. The delivery process can include Delivery Task, Shipment, Product Transfer, and Product Item records. Salesforce documentation also identifies Lightning Direct Store Delivery as the required user permission when creating Delivery Tasks in Action Plan Templates and when associating those tasks with Shipments.

If the tester does not have the required Direct Store Delivery access, delivery-related test cases can fail even when the underlying visits, action plans, shipments, and products have been configured correctly. General Retail Execution permissions alone do not provide the full set of Direct Store Delivery capabilities.

Geofencing is not the controlling authorization mechanism for Delivery Task access, and Retail Store KPI target values are unrelated to whether the tester can execute the Direct Store Delivery functionality.

Therefore, permission assignment should be verified early in delivery-task rollout testing.

Study Guide Topics:Platform - > Permissions - > Lightning Direct Store Delivery - > Delivery Tasks - > User Access

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

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

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

The Maximize Store Sales Einstein Discovery story is designed to identify factors that influence product sales and provide actionable insights that can help sales managers improve store performance.

Salesforce provides preconfigured Einstein Discovery stories within Analytics for Consumer Goods. The sales-focused story analyzes historical data to identify variables that have a positive or negative impact on product sales. Salesforce currently describes this capability as Maximize Store Product Sales, which provides insights into the factors affecting product sales and helps organizations devise strategies to increase sales at a store or store-group level.

Einstein Discovery uses the available analytics dataset to identify statistically relevant relationships and present explanations that business users can act upon. These insights can assist sales managers in understanding how factors such as product availability, assortment, store characteristics, and other operational conditions correlate with sales performance.

The Minimize Out-of-Stock story serves a different objective: it predicts products that are likely to run out of stock so representatives can mitigate availability problems. While out-of-stock conditions can affect revenue, the scenario specifically asks for broader insight into the factors affecting store sales, making the sales-maximization story the appropriate functionality.

Study Guide Topics:Analytics - > Einstein Discovery - > Maximize Store Sales - > Predictive Insights - > Sales Performance

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

A Delivery Task combined with SKU-level inventory tracking provides the appropriate operational model for tracking samples distributed through field representatives or distributors. Delivery Tasks represent delivery activities performed during store visits and are associated with Shipments that define which products must be delivered.

Within Salesforce inventory management, Product Item records represent quantities of specific products at inventory locations. A Product Item therefore provides the inventory relationship between the Product2 record and a location, with Quantity On Hand recording the current available quantity. For mobile inventory such as a distributor vehicle, Salesforce supports a Location configured as a mobile inventory location and allows Product Items to record the inventory carried in that vehicle.

Product Transfers associated with shipments identify the specific products and quantities being moved between locations. As delivery activities are performed, Salesforce can update inventory quantities accordingly. This provides operational traceability at the individual SKU level rather than merely reporting on shipping-document status.

Because the requirement is to monitor samples that remain available to distributors in the field, tracking the sample SKU ' s on-hand quantity together with the Delivery Task provides the most appropriate inventory-management approach.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Product Item - > Quantity On Hand - > SKU

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

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

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

In-Store Surveys are primarily designed to capture qualitative feedback from people associated with the retail location and to gather information about operational topics such as promotions, inventory requirements, and product quality.

Salesforce explicitly defines the In-Store Survey capability as a method for gathering feedback from store staff and customers about promotions, inventory needs, and product-quality conditions. The survey is executed as part of a Visit and can be incorporated into an Action Plan Template through an Assessment Task Definition of type In-Store Survey.

This model allows consumer goods organizations to collect information that is difficult to derive from purely transactional records. For example, store personnel can provide feedback about product availability, promotional effectiveness, packaging issues, shopper reactions, or changing inventory requirements. Surveys can also capture consumer or shopper opinions about products or promotional activities.

Inventory reconciliation is handled through inventory-management and Inventory Check processes rather than primarily through surveys. Point-of-sale information is normally imported or integrated as structured sales data for analytics rather than collected manually through an In-Store Survey.

Study Guide Topics:Visit Execution - > In-Store Survey - > Customer Feedback - > Promotions - > Inventory Requirements - > Product Quality

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