Pass the Salesforce Consumer Goods Cloud AP-204 Questions and answers with CertsForce

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

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

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

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

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

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

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

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

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

The 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

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

An Einstein Vision object-detection model must be developed from a training dataset containing representative images of the objects that the model is expected to recognize. Model creation is therefore an implementation activity rather than something that occurs automatically from a single image or during ordinary field execution.

Salesforce ' s Einstein Vision development process begins by collecting representative training images. For object detection, each training example must also identify the relevant objects using bounding-box coordinates. The resulting examples are assembled into a dataset and submitted to the Einstein Vision training service. Training that dataset produces a model that can subsequently identify, classify, count, and locate corresponding objects in new images.

The quality and diversity of the base image set directly influence model performance. A sufficiently representative dataset must account for differences such as product orientation, lighting, shelf arrangement, packaging appearance, and surrounding objects. Salesforce also allows multiple models to be trained from evolving datasets so their performance can be evaluated and refined.

Consequently, the model is deliberately built during implementation from a prepared base dataset before it is incorporated into the field-execution process.

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

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

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

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

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

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

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

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

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

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

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

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