Setting up Einstein Vision for product detection in Consumer Goods Cloud involves three primary stages. First, the feature must be technically enabled in Salesforce Setup (B). Second, the AI model must be trained to recognize the products; this is accomplished by creating a dataset with product images and training the Einstein Vision model (E). Finally, to make this functionality available to field reps, a specific "Planogram Check" task must be defined within the retail execution process (D). This task type is specifically designed to trigger the image capture and analysis workflow using the trained model.

A. Setup in store location and associate planogram: This is a foundational step for general retail execution, not a specific configuration step for the Einstein Vision feature itself.

C. Upload the training pictures as attachments to the planogram for Einstein Object Detection to work: Training images are uploaded to a dataset and associated with product records to train the model, not attached to individual planogram records.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Set Up Einstein Object Detection for Consumer Goods Cloud": This guide explicitly outlines the required setup process. It lists the main steps as: "Enable Einstein Object Detection," "Create a Planogram Check Task," and "Train Your Einstein Vision Model." This directly supports options B, D, and E.

2. Salesforce Help, Consumer Goods Cloud Documentation, "Einstein Object Detection": This overview states, "To get started, enable Einstein Object Detection. Then, create a planogram check task. Finally, train your Einstein Vision model." This confirms the sequence and validity of options B, D, and E.

3. Salesforce Help, Consumer Goods Cloud Documentation, "Guidelines for Creating a Training Dataset": This document details the process of preparing images for training the model. It specifies associating images with products to create a dataset, which contradicts the idea of attaching images to a planogram (Option C). It also implicitly supports the necessity of training the model (Option E).

Salesforce Maps Advanced provides powerful route and schedule optimization for field representatives. Its capabilities are designed to create the most efficient plans while adhering to business rules. The system incorporates real-time and predictive traffic data (A) to calculate accurate travel times and avoid delays. The core of the tool is its constraint-based routing engine (B), which allows planners to define rules such as working hours, break times, and skills. A critical constraint for store visits is respecting Visit Windows (C), which ensures that representatives arrive at a location only during its specified hours of operation or appointment times. These three capabilities work together to generate realistic and productive daily schedules.

D. Visit Prioritization: While Salesforce Maps Advanced can prioritize visits, this is a specific rule handled by the broader Constraint based Routing (B) engine and is less foundational than the core engine itself or hard constraints like visit windows.

E. Gantt-chart Routing: This is not a standard Salesforce feature or industry term for a routing capability. A Gantt chart is a method for visualizing a schedule, not a mechanism for creating one.

1. Salesforce Help, Optimize Routes with Salesforce Maps Advanced: This document explicitly states that the optimization engine "considers various factors, such as work hours, travel time, stop duration, traffic conditions, and visit priorities." This confirms the use of traffic data (A) and the general principle of constraint-based logic (B).

2. Salesforce Help, Salesforce Maps Route and Schedule Optimization: This guide details the scheduling policies and work rules that form the basis of constraint-based routing. Under "Field Service Settings," it describes the use of an "Arrival Window Start Field" and "Arrival Window End Field" for Service Appointments, which directly corresponds to the Visit Windows capability (C).

3. Salesforce Help, Routing and Optimization Services: This documentation for the underlying engine explains the different types of constraints (called "work rules") that can be applied, such as "Match Skills," "Time-Bound," and "Service Territory." This confirms the fundamental nature of constraint-based routing (B) as the core capability.

When a flow is initiated as part of a visit task, the Salesforce platform automatically passes crucial contextual information into the flow as input variables. This includes the VisitId and the AssessmentTaskId, enabling the flow to perform actions on the correct records. Furthermore, if the task involves creating a RetailVisitKpi record, a corresponding RetailStoreKpi must exist for that store. The ID of this RetailStoreKpi is passed to the flow in the RetailStoreKPI variable, providing the necessary context for the flow to calculate and record the visit-specific KPI value against the store-level target.

B. This describes the general data model, not a specific mechanism of flow-based tasks. Options A and C are more precise about the flow's execution context.

D. This is incorrect. A Retail Store KPI is a mandatory prerequisite for a flow to create a corresponding Retail Visit KPI record.

E. This is incorrect. A primary use case for flow-based tasks is to implement custom logic for calculating and creating Retail Visit KPIs.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Create a Flow for a Task": This document explicitly states the input variables for a flow-based task.

Reference for C: Under the section "Create a Flow for a Task," the documentation notes, "When you create a flow for a task, the Assessment Task ID and the Visit ID are passed to the flow."

Reference for A & D: In the "Considerations for Creating a Flow for a Task" section, it specifies, "To create a Retail Visit KPI record, you must have a Retail Store KPI record. The Retail Store KPI ID is passed to the flow in the RetailStoreKPI variable." This confirms A is correct and D is incorrect.

Reference for E: The entire purpose of the documentation page is to describe how to use flows for tasks, including those that create KPIs, which directly refutes option E.

2. Salesforce Help, Consumer Goods Cloud Documentation, "Consumer Goods Cloud Data Model": This resource details the object relationships.

Reference for B: The data model shows that the RetailVisitKpi object has a master-detail relationship to both Visit and RetailStoreKpi, confirming a Retail Store KPI is required for a Retail Visit KPI to exist. This supports why option B is a generally true statement but less specific to the process of a flow task than A and C.

The standard process for a field representative, such as a merchandiser, is to use the Salesforce Mobile App to manage their daily tasks. When arriving at a customer location for a scheduled visit (appointment), the user navigates to the specific Visit record within the app and uses the "Check-In" quick action. This action is specifically designed to capture and record the exact time of arrival and the device's current geo-coordinates, fulfilling the requirements of the inventory-check appointment.

A. Check-in through Einstein Vision: Einstein Vision is used for image recognition tasks like planogram compliance or shelf analysis, not for the primary action of checking into a visit to log time and location.

B. Check-in through standard location picker Lightning Web Component in Salesforce Mobile App: This is overly specific and incorrect. The check-in is a dedicated, pre-built action on the Visit object, not a generic Lightning Web Component that a user would select independently.

D. Check-in through Salesforce Maps on mobile: While Salesforce Maps is used for routing and location intelligence, the core check-in functionality is a standard feature of the Consumer Goods Cloud application on the Salesforce Mobile App and does not require Salesforce Maps.

1. Salesforce Help Documentation, "Execute Visits on the Mobile App": This document explicitly outlines the procedure for field reps. It states, "When a field rep reaches a store, the rep can check in to the store to record the time and location of the visit... From the navigation bar, tap Today's Visits. Tap a visit. Tap Check-In." This confirms the action is performed within the Salesforce Mobile App on the Visit record.

2. Salesforce Help Documentation, "Visit Execution": This section details the lifecycle of a visit, which begins with the check-in process. It describes how the check-in action captures the ActualVisitStartTime and location data, which is fundamental to tracking field rep activity and performance.

3. Trailhead, "Consumer Goods Cloud: Offline Mobile App" Module, "Manage Your Visits" Unit: This educational module describes the capabilities of the mobile app for field reps. It details how reps can "start their day, check in to a store, perform their tasks, and check out," reinforcing that the check-in/check-out process is a core feature of the mobile application experience for visit management.

The KPI Type field is a mandatory field when creating a Retail Store KPI record in Salesforce Consumer Goods Cloud. This field is a picklist that defines the specific metric being measured, such as 'Share of Shelf', 'Out of Stock', or 'Count of Facings'. Without defining the KPI Type, the record would lack its fundamental purpose, as the system would not know what performance indicator to track or how to evaluate it during a store visit.

A. Effective to: This field specifies the end date for the KPI's validity. It is not a required field, as a KPI can be set up to be ongoing without a defined end date.

B. Retail Store Group: A Retail Store KPI must be associated with either a Retail Store Group or an individual Retail Store, but not necessarily the group. Therefore, this specific field is not universally required.

D. Promotions: While KPIs can be linked to promotions to measure their effectiveness, they are also used for standard, non-promotional compliance checks. This makes the link to a promotion optional, not required.

1. Salesforce Help, Consumer Goods Cloud Implementation Guide, "Set Up Retail Store KPIs": This document outlines the process for creating Retail Store KPIs. It implicitly requires a type to define what is being measured. The core function of a KPI record is to define a metric, which is handled by the KPI Type field.

2. Salesforce Object Reference for Consumer Goods Cloud, RetailStoreKpi Object: The official object documentation lists KpiType as a required picklist field. It states, "The type of KPI. For example, Share of Shelf, Count of Facings, or Out of Stock." This confirms its mandatory nature for record creation.

3. Salesforce Help, Consumer Goods Cloud Data Model, "Retail Execution Objects": The data model diagram and descriptions show that the RetailStoreKpi object's definition is centered around the type of KPI it represents, distinguishing it from other optional associations like RetailStoreGroupId or time-bounding fields like EffectiveToDate.