Salesforce Consumer-Goods-Cloud-Accredited-Professional - Consumer Goods Cloud Accredited Professional (AP-204)

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

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

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

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

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

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

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

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

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

Action Plan Templates can contain both Assessment Task Definitions and Component Tasks, allowing organizations to combine standard Retail Execution activities with customized Lightning Web Component-based tasks in a reusable visit framework.

An Assessment Task Definition represents a recurring field activity such as an Inventory Check, Planogram Check, Promotion Check, In-Store Survey, Order Creation activity, or custom assessment. Salesforce allows administrators to add these Assessment Task Definitions to an Action Plan Template. When that template is used for a Visit, the corresponding tasks become associated with the visit and are presented to the assigned field representative.

Salesforce also supports Component Tasks. Administrators can select Add Component Task on an Action Plan Template, provide a name and description, select the required Lightning Web Component through its fully qualified name, and determine whether the task is mandatory. This allows organizations to extend store execution with specialized interactive experiences while continuing to use the standard Action Plan framework.

Action Plan Templates are configured administratively and function as reusable frameworks for repeatable business processes. Their ability to combine multiple task types is fundamental to creating consistent and scalable store-visit execution plans.

Study Guide Topics:Visit Planning - > Action Plan Templates - > Assessment Task Definitions - > Component Tasks - > Visit Execution

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

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

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

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

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

Retail Execution Lightning Plus provides access to Consumer Goods Retail Execution functionality for strategic-sales users and is the applicable entitlement for users working with Visit Recommendation capabilities in the Retail Execution environment.

Salesforce identifies Lightning Retail Execution Plus PSL as the Consumer Goods Retail Execution permission set license for strategic-sales users. Retail Execution permission set licenses enable Consumer Goods functionality that is not included automatically in the user ' s standard Salesforce license.

Einstein Visit Recommendations allow sales managers and field representatives to request recommended stores for future visits. Administrators can configure either a Flow strategy or a Next Best Action strategy. When users request recommendations, they can select the strategy that best corresponds to their business requirement, and Salesforce returns the stores that should be considered together with the associated recommendation reasons.

Tableau CRM Plus User and Tableau CRM Plus Admin permissions apply to CRM Analytics capabilities and are not the Retail Execution entitlement represented by this question.

The Retail Execution access model can also include Action Plans and Industries Visit permissions where users need the associated visit and task functionality.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Lightning Retail Execution Plus - > Recommendation Strategies - > User Access

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

The Consumer Goods data model uses several related objects to connect a Promotion to its products, retail destinations, and compliance measurements.

Promotion Product is the junction between a Promotion and a Product. It identifies the specific products included in a promotional activity. Promotion Channel associates the Promotion with the commercial destination where it applies, such as a Retail Store, Retail Store Group, or Account.

Promotions also participate in the Retail Store KPI framework. When a KPI is created for a Promotion Check, the applicable Promotion can be selected on the Retail Store KPI together with the Assessment Indicator Definition, product or product category, Retail Store Group, and other contextual information. The Retail Store KPI therefore defines the expected promotional-compliance target.

When an Action Plan is applied to a Visit, Retail Visit KPI records capture the actual field observations against the applicable Retail Store KPI targets. This provides the visit-level measurement layer for promotion compliance.

Delivery Task and In-Store Location have different primary roles and do not form the complete promotion-related object set represented by the question.

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

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

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

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

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

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