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

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

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

Salesforce Maps Advanced supports sophisticated store-visit planning through traffic-aware routing, routing constraints, and Visit Windows.

Traffic information helps field representatives and planners account for expected travel conditions. Agentforce Consumer Goods optimized-route functionality uses travel time between visits and provides real-time traffic information and route suggestions so representatives can react to congestion, roadworks, and other delays.

Maps Advanced also performs constraint-based optimization. Route generation considers operational constraints such as the planning period, required visit frequency, working schedules, travel time, maximum segment length, and other optimization criteria. These constraints allow the routing engine to generate routes that balance customer-coverage requirements with the practical capacity of field representatives.

Visit Windows define when a customer or retail location can accept a visit. Administrators can establish specific days and times, such as weekdays between 9:00 AM and 11:00 AM. Maps Advanced then attempts to schedule future visits inside those windows while generating optimized routes.

Together, these capabilities allow sales managers to create realistic multi-stop schedules that account for travel conditions, operational restrictions, and customer availability.

Study Guide Topics:Visit Planning - > Salesforce Maps Advanced - > Route Optimization - > Constraints - > Visit Windows - > Traffic

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

Administrators review object-detection results through Detected Objects. Each object identified by the vision model is represented as a Detected Object record, providing administrators with the information required to examine how the model is performing against actual images.

A Detected Object record contains operational details about a particular detection, including the source image, the model responsible for identifying the object, the object ' s coordinates within the image, and the probability or confidence associated with the detection. Reviewing these records allows administrators to determine whether products are being identified correctly and to recognize patterns of incorrect classification or missed detections.

This review process is also important for continuous model improvement. When model output is inaccurate, additional representative examples can be incorporated into the training dataset and the model can be trained again. Salesforce ' s Einstein Vision architecture supports iterative model development because a dataset can generate multiple models, enabling implementers to compare model performance and refine training data over time.

Creating an unrelated custom object, enabling a feature, or using Einstein Bots does not provide the detection-result records required to assess object-recognition performance.

Study Guide Topics:Platform - > Einstein Vision - > Detected Objects - > Model Performance - > Model Refinement

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

A custom task implemented with Flow is the appropriate architecture when the information to be captured does not fit the standard Inventory Check, Planogram Check, Promotion Check, Order Creation, or In-Store Survey task types. Salesforce specifically provides the Other assessment task type for custom business activities that require organization-specific data capture.

For asset compliance, an administrator can create an Assessment Indicator Definition with a Boolean data type to capture whether the asset meets the required compliance condition. Assessment Indicator Definitions support Number, Boolean, Date Time, Text, Decimal, and Picklist data types, making Boolean appropriate for a compliant/non-compliant assessment.

The custom task can be connected to the relevant business record through the Custom Context field of the Retail Store KPI. Salesforce supports standard or custom objects as custom-task context when the object supports activities. Flow can then evaluate the captured Boolean value and invoke the required follow-up automation, such as generating corrective actions or other downstream processes.

Using Flow instead of Apex follows Salesforce ' s declarative automation model and minimizes custom code while keeping the logic maintainable by administrators.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assessment Indicator Definition - > Boolean KPI - > Flow Automation

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

The Retail Store object should be used as the base object because Retail Stores represent the physical customer locations that field representatives need to visit. Salesforce Maps requires a mappable business object containing, or resolving to, geographic information so that records can be plotted, filtered, routed, and scheduled.

In Consumer Goods visit planning, Retail Store records supply this geographic and operational context. Store records contain the address and related location information required by Salesforce Maps. Salesforce states that the address entered when creating a Retail Store provides the location coordinates used by Salesforce Maps and also appears in the representative ' s visit list.

Salesforce ' s Consumer Goods optimized-routing process likewise uses Retail Store as the Maps base object. The planner selects relevant stores, applies business filters, identifies representatives and planning dates, and allows Maps to generate optimized visit schedules and routes.

The Visit subsequently represents the scheduled engagement with the selected Retail Store, but the physical destination being routed is the Retail Store itself. Account represents the broader customer organization and may encompass several stores, while Contact represents an individual person. Warehouse serves a different inventory and logistics purpose.

Using Retail Store therefore gives Salesforce Maps the correct geographic granularity for store-level visit planning and route optimization.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Base Object - > Retail Store - > Route Planning

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

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

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

The Action Plan Template must use Visit as the Target Object and must be published before it can be used to generate an Action Plan for a retail visit.

Salesforce defines the Action Plan Template as a reusable framework for activities that remain consistent across multiple visits. During template creation, the administrator specifies Visit as the Target Object and configures the required Action Plan Type. Assessment tasks, flows, delivery-related activities, or other supported work items are then added before the template is published.

Publishing is an essential lifecycle step because Salesforce permits only published templates to be used when associating an Action Plan with a Visit. To create the association, the user opens the Visit, navigates to the Action Plan related section, selects New Plan, and chooses the required published template. Salesforce displays the tasks defined by the template and creates the Visit-specific Action Plan after the configuration is saved.

The process therefore does not depend on activating the Visit or separately activating an Action Plan. The key configuration is ensuring that the reusable template is explicitly designed for Visit records and has been published for use.

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

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

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

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

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

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

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

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

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 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

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

Promotions can be defined at the Product Category level or the individual Product level when the promotion has a product-specific commercial context. Salesforce also supports a general promotion with no product or product-category context, but among the listed options, Product Category and Product are the applicable promotion-definition levels.

A Product Category promotion applies the promotional activity to a collection of related products. This design is appropriate when the same commercial offer applies across an entire category, such as discounted beverages or energy bars. A Product-level promotion applies to one or more specific products, such as a new-product launch, sampling campaign, or SKU-specific discount.

Salesforce stores the relationship between a promotion and its individual products through Promotion Product. For category-based promotions, the relationship is represented through Promotion Product Category. Account, Retail Store Group, and Retail Store describe the reach or channel through which a promotion is distributed rather than the product level at which the promotion itself is defined. These destinations are associated through the Promotion Channel model.

This separation allows administrators to independently define what products a promotion concerns and where the promotion applies.

Study Guide Topics:Data Setup - > Promotions - > Product Level - > Product Category Level - > Promotion Product

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

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

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

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

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

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

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

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 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

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

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

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

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

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

Consumer Goods can be customized declaratively through Lightning App Builder and Flow, while Lightning Web Components provide the component-level extensibility required for specialized user experiences.

Lightning App Builder allows administrators to configure Salesforce record pages by placing and configuring standard components without rebuilding the underlying application. This supports customer-specific page composition while remaining within the Salesforce Platform configuration model.

Where more specialized behavior is required, Lightning Web Components provide an extensibility layer. Salesforce supports custom LWCs that interact with standard components and extend or modify business functionality. For example, Salesforce ' s Consumer Goods extensibility documentation describes using custom LWCs alongside standard components so custom interactions and data changes can be reflected in the standard experience.

For process-oriented customization, administrators can create Flows and associate them directly with an Action Plan Template. Salesforce states that flows can implement activities specific to a business that are not covered by standard Consumer Goods task types. Once associated with the template, those flows become available to field representatives during store visits.

The Consumer Goods mobile platform also supports LWC-based mobile extensions through its integration framework, keeping customization aligned with Salesforce Platform technologies rather than requiring Apache Cordova development.

Study Guide Topics:Platform - > Mobile Customization - > Lightning App Builder - > Lightning Web Components - > Flow - > Action Plan Templates

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

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 Shipment must be associated with the Delivery Task so that the products scheduled for delivery can be presented during execution. In Salesforce Direct Store Delivery, the Delivery Task provides the activity context, while the Shipment defines the inventory movement that the field representative is expected to complete.

Salesforce specifies that after a Delivery Task is generated from an Action Plan Template assigned to a visit, the task must be associated with a Shipment. Products are then added to that Shipment through related Product Transfer records. Each Product Transfer identifies the product and quantity involved in the shipment.

This hierarchy is important because the Delivery Task does not independently maintain its own product list. Instead, it obtains the delivery-item context from its related shipment. A standalone Product record does not establish that the product is scheduled for a particular delivery, and a Retail Store KPI belongs to the Retail Execution assessment framework rather than inventory delivery processing.

Accordingly, if delivery items do not appear within the Delivery Task, the administrator should verify that the appropriate Shipment has been associated with the task and that the shipment contains the necessary Product Transfer records.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

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

The Delivery Task is the Consumer Goods-specific object used to perform Direct Store Delivery activities during a retail-store visit. Salesforce describes DeliveryTask as a Retail Execution object representing delivery work performed at the store, whereas Shipment and ProductTransfer originate from inventory and Field Service capabilities.

Administrators add a Delivery Task to an Action Plan Template. When that template is applied to a Visit, Salesforce creates the Delivery Task record and associates it with the Visit. Users working with Delivery Tasks require the Direct Store Delivery permission capability.

The administrator then associates a Shipment with the Delivery Task to specify the inventory being delivered. Individual products and quantities are represented as Product Transfer records related to the Shipment. This architecture separates the Consumer Goods visit activity from the underlying inventory-transfer records.

During execution, the delivery representative selects the shipment, reviews its products, updates delivered quantities if required, and marks the products delivered. Completing the Delivery Task updates relevant inventory information.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

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

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

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

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

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