An Action Plan Template can contain multiple Inventory Check, Planogram Check, and Promotion Check assessment tasks. These are KPI-based Retail Execution activities that may need to be repeated within a single store visit for different products, categories, promotions, or in-store locations.

Salesforce explicitly states that administrators can add multiple Inventory Check, Planogram Check, and Promotion Check tasks to one Action Plan Template. By contrast, Salesforce restricts the template to only one Order Creation task or one In-Store Survey task.

This flexibility is important because a typical consumer-goods visit can involve several independent merchandising objectives. A representative might perform separate inventory checks for different store areas, validate several planograms, and verify multiple promotions during the same visit. The Action Plan Template provides a reusable framework that groups these activities and controls their required status and display sequence.

Templates must also progress through the appropriate lifecycle before operational use; simply defining the structure does not substitute for making the template available for visit execution. Salesforce further supports extensibility through flows, component tasks, and other Action Plan mechanisms.

Therefore, the ability to include multiple planogram, inventory, and promotion checks is the accurate statement.

Study Guide Topics:Visit Planning - > Action Plan Templates - > Inventory Check - > Planogram Check - > Promotion Check

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

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

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

Einstein Vision product recognition is based on object detection, which identifies individual objects within an image and determines their position and classification. For shelf-analysis scenarios, the functionality depends on enabling the object-detection capability, providing suitable image data for recognition, and integrating that capability into the Planogram Check workflow used by field representatives.

Einstein Object Detection models rely on representative training images containing the objects that the system must recognize. Salesforce ' s object-detection architecture uses labeled images and object-location information to create a model capable of identifying multiple objects within a photograph. The quality and relevance of the image set are therefore important to reliable product recognition.

Within Consumer Goods Retail Execution, the operational component is the Planogram Check. Planogram assessment tasks provide the visit-level process through which representatives compare observed shelf conditions with the expected planogram and capture the resulting compliance information. Assessment Task Definitions define these repeatable field activities and allow them to be incorporated into Action Plan Templates used during visits.

The combination of object detection, appropriate image information, and a defined Planogram Check provides the technical and operational structure required for automated shelf-product detection in the implementation described.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Planogram Check - > Assessment Task Definition

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

Salesforce Maps Mobile Check In provides the field representative with the appropriate mechanism for recording arrival information at a customer or retail location. Salesforce Maps supports field activity tracking directly from map markers, routes, and schedules, enabling representatives to check in when they arrive and check out after the visit is complete.

Salesforce Maps Check In can capture the representative ' s location, check-in time, visit duration, and other activity information. Location information can be recorded as latitude and longitude, allowing the organization to verify where the representative was when the check-in occurred. Administrators can also configure a verification distance, requiring users to be within a defined distance of the record ' s geolocation before a check-in is accepted.

For a merchandiser performing an Inventory Check, this creates a reliable operational record of when the representative arrived at the store and the geographic coordinates associated with that event. The feature is integrated into the Salesforce Maps mobile experience and is designed specifically for field-based visit activity.

Einstein Vision performs image-analysis functions and does not provide visit check-in functionality. A generic location picker likewise does not provide the complete Maps activity-logging workflow.

Study Guide Topics:Visit Execution - > Salesforce Maps - > Mobile Check In - > Geolocation - > Visit Activity

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

Assortment Product, Promotion Product, and Store Product are Consumer Goods data-model objects that establish important relationships between Product2 and retail business contexts.

Assortment Product is a junction object connecting individual products with an Assortment. An Assortment represents a collection of products that are eligible or targeted for sale at specific stores, store groups, or accounts. Salesforce uses the junction relationship to support different product portfolios across retail locations.

Promotion Product connects a Promotion with a Product2 record when a promotion is defined at the product level. This relationship allows Salesforce to determine which specific products participate in promotional activities and enables product-level Promotion Checks during store visits.

Store Product directly associates Product2 with a Retail Store or specific In-Store Location. This relationship supports store-specific product execution, including inventory checks, order capture, product placement, and merchandising activities.

These junction objects provide three distinct dimensions around Product2: assortment eligibility, promotional participation, and store-level availability or placement. Delivery Product and Assessment Task Product are not the corresponding standard junction objects used for these Product2 relationships.

Study Guide Topics:Data Setup - > Product2 - > Assortment Product - > Promotion Product - > Store Product

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

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 frozen food aisle should be modeled as an In-Store Location. In-Store Location represents a specific physical area inside a retail store where products are displayed, stored, or evaluated. Salesforce identifies aisles, shelves, checkout counters, endcaps, and back rooms as typical examples.

Once the Frozen Food Aisle record is created, products can be associated with that location through Store Product. Store Product establishes the relationship among the Retail Store, Product2, and the applicable In-Store Location. This gives the Inventory Check sufficient context to tell the field representative exactly where the product should be inspected.

The In-Store Location can also be assigned an In-Store Location Category. Categories make it possible to group equivalent locations across multiple stores and configure Retail Store KPIs consistently for a store group. For example, all frozen-food aisles could share a category and common inventory-assessment rules.

Adding a custom picklist or task/store record type would duplicate functionality already provided by the standard Consumer Goods data model. Product2 identifies the commercial product; it does not by itself describe the product ' s physical placement within an individual store.

Study Guide Topics:Data Setup - > In-Store Location - > Store Product - > Inventory Check - > Store Layout

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

Inventory Check execution is scoped to the products associated with the specific Retail Store being visited. Salesforce Retail Execution uses this relationship to ensure that the field representative works only with products relevant to that outlet rather than searching the organization ' s entire Product2 catalog.

The Store Product object establishes the association between a product and a Retail Store or a specific In-Store Location. This relationship provides the product context used during store-level execution. Inventory Checks allow representatives to capture real-time information such as stock quantities, facings, share of shelf, product placement, and other assessment indicators for products sold in the store.

Product ownership or the identity of the user who created a Product record does not determine whether it should appear during an Inventory Check. Those attributes are unrelated to the commercial assortment or stocking relationship between a product and the retail location. Searching every product in the organization would also introduce irrelevant records and reduce mobile execution efficiency.

Therefore, product search during an Inventory Check is based on products associated with the Retail Store, ensuring the representative receives an operationally relevant product list for that visit.

Study Guide Topics:Visit Execution - > Inventory Check - > Store Product - > Retail Store - > Product Association

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

Frequently purchased products can be prioritized for a specific outlet by associating them through Store Product and marking the appropriate products as Favorite. Store Product represents the relationship between Product2 and a Retail Store or specific In-Store Location, which allows Salesforce to maintain outlet-specific merchandising and ordering attributes.

The Store Product data model includes both Is Favorite and Default Order Quantity. These attributes are designed to streamline recurring order capture. Salesforce explains that field representatives can prioritize favorite products when creating orders so commonly purchased items are replenished efficiently and remain in stock. Default Order Quantity can further reduce data entry by predefining the quantity normally ordered for the product.

Salesforce ' s Retail Execution configuration also allows products associated with a store to be marked as favorites. The Inventory and ordering user interfaces can expose favorite products as a focused subset, reducing the time required to create routine orders.

This makes Store Product the correct outlet-specific mechanism for modeling frequently ordered products rather than creating artificial Order records with a template status.

Study Guide Topics:Visit Execution - > Order Capture - > Store Product - > Favorite Products - > Default Order Quantity

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

Salesforce provides several standard Lightning components specifically scoped to the Assessment Task object. Among the listed options, In-Store Products, Promotion List, and Inventory Check are standard Assessment Task components.

The In-Store Products component presents products relevant to the store and can expose information such as product images, pricing, favorite products, and ordering actions. The Promotion List component gives field representatives access to promotions associated with the assessment context and can display progress and in-store location information. The Inventory Check component provides the user interface for inventory-related assessment execution, including product and location-oriented information used during a store visit.

Salesforce ' s Assessment Task record-page configuration also supports additional components such as Planogram List and Consumer Goods Survey List. Administrators can place the required components on an Assessment Task record page through Lightning App Builder and configure their properties according to the mobile field-execution requirement.

Promotion Details is scoped to the Promotion object rather than Assessment Task, while Cart Review is scoped to the Order object. Their object scope makes them unsuitable as the three Assessment Task components requested.

Study Guide Topics:Platform - > Lightning App Builder - > Assessment Task Record Page - > Standard Consumer Goods Components

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