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

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

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

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

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

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 Visit object should be used as the base object because the information that must be visualized-specifically the current status of today ' s visits-is stored on Visit records. Agentforce Consumer Goods uses the Visit object to track planned and completed retail-store engagements, including the responsible field representative, planned start and end times, retail location, and Visit Status.

Salesforce Maps supports Visit as a mappable object even though Visit itself does not contain a physical address. Salesforce Maps can inherit the location from the related Retail Store through the Visit ' s relationship to that store. A Marker Layer can then be constructed using Visit as its base object and filtered for the appropriate territory and date.

Salesforce Maps also supports dynamic marker formatting based on a field value. With the Varied Based On 1 Field configuration, the administrator can select Visit Status and assign different colors to different statuses. This allows an account manager to distinguish scheduled, in-progress, completed, or other visit states directly on the map without opening individual records.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Visit Object - > Marker Layers - > Visit Status

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

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

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

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

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

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

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

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

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

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

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

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

Store Action Plan Templates provide contextual task recommendations by connecting reusable Action Plan Templates with the retail hierarchy where those activities are applicable. The supported retail contexts are Retail Store Group, Retail Store, and In-Store Location.

A Retail Store Group provides broad reusable scope. Stores with similar layouts, product ranges, commercial agreements, or operational characteristics can be grouped so that common activities can be recommended consistently across those stores. Salesforce specifically uses Retail Store Groups to organize locations with common characteristics and to reduce repetitive configuration.

The Retail Store level provides a more specific context when a task is applicable to one physical outlet rather than every store in a group. The In-Store Location level offers the finest execution granularity for activities associated with specific areas such as an aisle, primary shelf, endcap, checkout counter, or back room.

These entities form part of the Salesforce Retail Execution data model together with Store Action Plan Template, Action Plan Template, Visit, and other activity-planning objects. This layered architecture allows recommended visit activities to be associated with the level of the retail hierarchy most appropriate to the business requirement.

Study Guide Topics:Visit Planning - > Store Action Plan Template - > Retail Store Group - > Retail Store - > In-Store Location

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

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

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

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

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

The appropriate action is to edit the product tags so that the incorrectly detected object is associated with its correct product classification. Product identification depends on the relationship between the detected item and the product label assigned to it. When two packages have highly similar visual characteristics, a detected object can require correction to ensure subsequent shelf-analysis results reflect the correct SKU or competitor product.

Share-of-shelf measurements depend on accurate identification of the products occupying the shelf. If an item belonging to a competitor is classified as the company ' s own product, the calculated shelf presence becomes overstated and the resulting compliance data is unreliable. Correcting the product tag addresses the classification problem at its source rather than manipulating the physical shelf or abandoning the assessment.

This approach also aligns with the underlying object-detection model. Detection systems generate identified objects and associate those detections with product classifications. Accurate labels and representative examples are fundamental to reliable image-based object recognition. Where product appearance changes substantially, maintaining accurate classification information is essential to preserving measurement quality.

Creating a different planogram would change the expected merchandising arrangement but would not correct an incorrectly classified detected product.

Study Guide Topics:Platform - > Einstein Object Detection - > Product Recognition - > Product Tags - > Share-of-Shelf Accuracy

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

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

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

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

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

A Planogram Check requires the planogram Image to be associated with the appropriate In-Store Location. The In-Store Location identifies the physical area inside the retail outlet-such as an aisle, primary shelf, checkout counter, or endcap-where the expected product arrangement applies.

Salesforce ' s Planogram Check prerequisites require administrators to create an Image record representing the planogram and associate the Image with an In-Store Location. The Product must also be associated with both the Retail Store and the relevant In-Store Location.

The Retail Store KPI then supplies the assessment configuration. Administrators select the appropriate Retail Store Group, In-Store Location Category, Assessment Indicator Definition, planogram Image, and KPI Type. Supported planogram-related KPI Types include Facing, Share of Shelf, and Out of Stock, depending on the indicator being measured.

This relationship ensures that Salesforce can determine which reference layout applies when a representative performs the assessment at a particular location within the store. Associating the Image only with a Promotion, Assessment Task, or Retail Store does not establish the precise physical merchandising context required for Planogram Check execution.

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

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

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

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

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 custom tasks of type Other, the related object ' s Lightning Record Page must contain the Consumer Goods Custom Task Measures component and that page must be activated for the appropriate users. If either configuration is missing, users can receive the standard record-page experience instead of the KPI-specific interface.

Salesforce instructs administrators to create or modify the applicable custom-object record page in Lightning App Builder, drag the Consumer Goods Custom Task Measures component onto the page, configure its properties, and save the configuration. The component can display measures such as overall compliance, product-category compliance, and product compliance.

Lightning Record Pages are also subject to activation and assignment rules. An administrator can assign a record page according to app, record type, and user profile. Consequently, creating a page containing the custom KPI component is insufficient if the intended field user ' s profile is not assigned to that page.

Salesforce Mobile supports Lightning Record Pages and does not inherently force custom tasks to display only standard pages. Similarly, Lightning App Builder does support inclusion of Consumer Goods custom-task components.

Therefore, both component configuration on the related object ' s record page and correct record-page assignment to the user profile are required for the custom KPI experience to appear.

Study Guide Topics:Platform - > Lightning App Builder - > Custom Task Measures - > Record Pages - > Profile Assignment

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

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

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

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

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

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

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

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

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

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

In Consumer Goods Retail Execution, an Action Plan is associated with a Visit so that the required activities can be presented to the field representative during store execution. The Visit represents the scheduled interaction with the retail location, while the Action Plan provides the operational work that must be completed during that interaction.

Salesforce uses Action Plan Templates as reusable frameworks. When creating an Action Plan Template for Retail Execution, the administrator selects Visit as the Target Object. Tasks and flows are then added to the template, and the template is published. The same template can subsequently be associated with multiple visits, allowing standardized activities to be consistently deployed across stores and representatives.

Assessment Tasks are individual execution activities contained within the Action Plan rather than the primary object to which the overall plan is connected. Retail Store provides the physical store context, but execution is organized around the Visit. Action Plan Template defines the reusable structure, whereas the instantiated Action Plan operates within the specific Visit.

This design gives Salesforce a consistent mechanism for translating reusable task configurations into executable activities for individual scheduled store visits.

Study Guide Topics:Visit Planning - > Visit - > Action Plans - > Action Plan Templates - > Assessment Tasks

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

The consultant must identify the hierarchy level that represents the stock keeping unit (SKU). In the Consumer Goods Retail Execution data model, individual products are represented through Product2 records, and Salesforce describes each Product2 record as a SKU or sellable unit. Consequently, the ERP hierarchy level that contains SKU-level information provides the appropriate product granularity for product-specific retail execution processes.

Share-of-shelf measurement requires Salesforce to identify precisely which products occupy shelf space so that actual shelf presence can be evaluated against configured targets. Retail Store KPIs can associate Assessment Indicator Definitions such as Share of Shelf with products, product categories, planograms, store groups, and in-store location categories. The underlying product master therefore needs a level that reliably represents the individual sellable products being measured.

Salesforce product master data can contain multiple hierarchy levels such as categories, subcategories, brands, and SKUs. The numerical position of a tier is not itself significant; what matters is the business meaning of that tier. For this requirement, the tier representing SKUs provides the required product-level data for shelf measurement and Retail Execution processing.

Study Guide Topics:Data Setup - > Product2 - > Product Hierarchy - > SKU - > Share-of-Shelf KPI

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

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

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

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

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

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

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

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

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