Practice Free AP-204 Salesforce Accredited Agentforce Consumer Goods Professional Exam Questions Answers With Explanation

A custom task implemented with Flow is the appropriate architecture when the information to be captured does not fit the standard Inventory Check, Planogram Check, Promotion Check, Order Creation, or In-Store Survey task types. Salesforce specifically provides the Other assessment task type for custom business activities that require organization-specific data capture.

For asset compliance, an administrator can create an Assessment Indicator Definition with a Boolean data type to capture whether the asset meets the required compliance condition. Assessment Indicator Definitions support Number, Boolean, Date Time, Text, Decimal, and Picklist data types, making Boolean appropriate for a compliant/non-compliant assessment.

The custom task can be connected to the relevant business record through the Custom Context field of the Retail Store KPI. Salesforce supports standard or custom objects as custom-task context when the object supports activities. Flow can then evaluate the captured Boolean value and invoke the required follow-up automation, such as generating corrective actions or other downstream processes.

Using Flow instead of Apex follows Salesforce ' s declarative automation model and minimizes custom code while keeping the logic maintainable by administrators.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assessment Indicator Definition - > Boolean KPI - > Flow Automation

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

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

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

For a Visit Recommendation implementation that must scale to production business volumes, the recommendation-selection logic should be implemented using an Apex class.

Salesforce supports Flow-based strategies for Einstein Visit Recommendations, but its documentation explicitly states that the flow-only approach is not scalable for a business use case and recommends using Apex for scalable Visit Recommendation processing.

With Apex, a developer can implement the business logic needed to identify the Retail Stores for which Einstein should generate recommendations. The Apex method can be exposed through an invocable action and incorporated into the recommendation strategy or an associated flow. This architecture provides more control over bulk processing, complex filtering, governor-limit management, reusable logic, and enterprise-scale execution.

Salesforce ' s Visit Recommendation setup documentation supports both Flow and Apex approaches. It specifically provides an Apex-based option to select the list of stores for which recommendations should be generated and then use that Apex action within the recommendation framework.

Workflow Rules and Process Builder are not the supported architectural mechanisms for implementing scalable Einstein Visit Recommendation strategies.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Scalability - > Recommendation Strategy

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

The Retail Execution assessment architecture uses Retail Store KPIs as the configuration basis for Retail Visit KPIs. Salesforce states that when an Action Plan Template is assigned to a Visit, Assessment Tasks are generated from the Assessment Task Definitions and Retail Visit KPI records are created based on the applicable Retail Store KPIs. This preserves the connection between the expected target configured centrally and the actual value captured during a specific visit.

Flows can also be associated with an Action Plan Template to support business-specific store activities. Salesforce supports flow input parameters named visitId and assessmentTaskId. A flow can accept only visitId, only assessmentTaskId, both parameters, or no parameters depending on the activity being implemented. When the identifiers are used, Salesforce passes the current Visit and Assessment Task context into the flow so that the automation operates on the appropriate execution records.

This model keeps responsibilities clearly separated: Retail Store KPI contains the target context; Retail Visit KPI records the visit-specific assessment result; Assessment Task identifies the executable activity; and Visit establishes the retail engagement within which the task occurs.

Study Guide Topics:Visit Execution - > Flow Tasks - > Retail Store KPI - > Retail Visit KPI - > visitId - > assessmentTaskId

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

Einstein Visit Recommendations support Next Best Action strategies for determining which retail stores should be recommended for visits. Salesforce allows administrators to configure a recommendation strategy that evaluates relevant records and business criteria and produces prioritized visit recommendations for sales managers and field representatives.

A Next Best Action strategy can load relevant data, apply business rules, generate scores and reasons, and return recommendations that support store-visit planning. When a user creates a Visit Recommendation Request, the selected recommendation strategy is executed for the specified store and date context. Salesforce can also incorporate prediction information from Einstein Discovery when organizations require model-based recommendations.

The architecture separates recommendation logic from visit execution. Administrators can therefore create multiple strategies for different business priorities-for example, prioritizing stores with declining inventory, important upcoming promotions, or revenue opportunities. Salesforce documentation specifically supports both flow-based strategies and Next Best Action strategies for Einstein Visit Recommendations, enabling organizations to select the implementation approach that aligns with their planning logic and scalability requirements.

Accordingly, the ability to create Visit Recommendations through a Next Best Action Strategy is a standard supported configuration.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Next Best Action - > Recommendation Strategies - > Visit Prioritization

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

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

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

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

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

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

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

Retail Execution Lightning Plus provides the Retail Execution entitlement associated with strategic sales functionality in Consumer Goods Cloud. Einstein Visit Recommendations operate within the Retail Execution environment and help sales managers and field representatives determine which stores should be visited based on configurable recommendation strategies.

Salesforce documents the Lightning Retail Execution Plus permission set license as the Retail Execution license for Consumer Goods strategic sales users. The Retail Execution license framework provides access to Consumer Goods capabilities that are not included in the underlying Salesforce user license.

Einstein Visit Recommendations must also be enabled in Setup. Once configured, authorized sales managers and field representatives can create recommendation requests and schedule store visits based on the recommendations returned by Salesforce. Recommendation logic can be implemented using either a Flow strategy or a Next Best Action strategy, enabling organizations to align the feature with specific business-planning requirements.

CRM Analytics permission sets govern access to analytics applications and dashboards, while Lightning Direct Store Delivery provides access to DSD-specific functionality. Action Plans provide access to the Action Plan framework. For Visit Recommendation execution within Retail Execution, Retail Execution Lightning Plus is the applicable choice.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Retail Execution Permissions - > Recommendation Strategies

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

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

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

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 Consumer Goods notification framework provides the most appropriate user experience for communicating team information to field representatives while they continue performing their operational activities. Salesforce supports User Notifications specifically so supervisors and field personnel can communicate important information such as selling messages, business strategies, team updates, customer information, and other operational guidance.

Notifications are created as Task records with the User Notification record type and assigned to the relevant field representative. Users can review notifications and manage their read or unread status without requiring a separate Chatter navigation pattern.

The mobile user experience is optimized for this communication model. Salesforce ' s Advanced User Cockpit includes a dedicated Notifications card. On tablets, the card displays the five most recent unread notifications, enabling representatives to monitor messages while remaining within their normal field-work environment.

This approach avoids modifying every Consumer Goods page, consuming tablet space with a persistent messaging column, or misusing notes as person-to-person notifications. Using the native notification mechanism keeps communication integrated with the field representative ' s workflow while minimizing navigation disruption.

Study Guide Topics:Platform - > Notifications and Tasks - > User Notifications - > Mobile User Cockpit - > Field Collaboration

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

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

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

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

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

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

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

Users performing Delivery Tasks in the Consumer Goods base data model require access to the Lightning Direct Store Delivery functionality. Salesforce specifically identifies the Lightning Direct Store Delivery permission set license as the feature-specific entitlement required for Direct Store Delivery and van-sales functionality on the base data model.

Delivery Tasks involve objects and functionality beyond general Retail Execution. The delivery process can include Delivery Task, Shipment, Product Transfer, and Product Item records. Salesforce documentation also identifies Lightning Direct Store Delivery as the required user permission when creating Delivery Tasks in Action Plan Templates and when associating those tasks with Shipments.

If the tester does not have the required Direct Store Delivery access, delivery-related test cases can fail even when the underlying visits, action plans, shipments, and products have been configured correctly. General Retail Execution permissions alone do not provide the full set of Direct Store Delivery capabilities.

Geofencing is not the controlling authorization mechanism for Delivery Task access, and Retail Store KPI target values are unrelated to whether the tester can execute the Direct Store Delivery functionality.

Therefore, permission assignment should be verified early in delivery-task rollout testing.

Study Guide Topics:Platform - > Permissions - > Lightning Direct Store Delivery - > Delivery Tasks - > User Access

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

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

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

Flow-based activities execute within the context of the Visit and Assessment Task, while the Retail Execution KPI architecture maintains the relationship between Retail Store KPIs and Retail Visit KPIs.

Salesforce supports adding flows directly to an Action Plan Template. A flow can receive visitId, assessmentTaskId, or both as input parameters. These identifiers allow the flow to operate against the specific Visit and Assessment Task instance from which it was launched, ensuring that business automation remains tied to the correct retail execution transaction.

Retail Visit KPIs provide the transactional measurement layer for a visit. Salesforce documents that when an Action Plan Template is assigned to a Visit, Assessment Tasks are generated from Assessment Task Definitions and Retail Visit KPI records are created based on the applicable Retail Store KPIs. The Retail Store KPI defines the expected target and assessment context, while the Retail Visit KPI captures the visit-specific actual measurement against that target.

Salesforce ' s data model also records the Assessment Task ID, Visit ID, Assessment Indicator Definition, Target Value, and Actual Value on Retail Visit KPI records.

Study Guide Topics:Visit Execution - > Flow Tasks - > visitId - > assessmentTaskId - > Retail Store KPI - > Retail Visit KPI

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

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

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

Salesforce Maps provides bulk geocoding capabilities so administrators can populate latitude and longitude values for groups of records rather than manually maintaining coordinates one retail location at a time.

Salesforce Maps geocodes records by matching address information against its geocoding provider and writing the corresponding latitude and longitude values back to the configured coordinate fields. A record can then be accurately plotted on a Maps layer and used for visit planning, route optimization, territory visualization, and proximity analysis.

One supported approach is to plot the records in a Maps layer and geocode the records represented by that layer. This enables administrators to work with a selected collection of Retail Store locations and perform the geocoding operation in bulk rather than copying coordinates from individual map markers.

Salesforce also supports scheduled or batch geocoding through Maps configuration for larger datasets, but within the workflow represented by the question, the Maps layer and mass geocoding action provide the direct administrative method for adding coordinates to the selected retail store records.

Accurate geocoding is foundational to Maps-based Retail Execution because route calculations and map visualization depend on verified geographic coordinates.

Study Guide Topics:Integrations - > Salesforce Maps - > Geocoding - > Retail Store - > Map Layers - > Mass Actions

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

In-Store Surveys are primarily designed to capture qualitative feedback from people associated with the retail location and to gather information about operational topics such as promotions, inventory requirements, and product quality.

Salesforce explicitly defines the In-Store Survey capability as a method for gathering feedback from store staff and customers about promotions, inventory needs, and product-quality conditions. The survey is executed as part of a Visit and can be incorporated into an Action Plan Template through an Assessment Task Definition of type In-Store Survey.

This model allows consumer goods organizations to collect information that is difficult to derive from purely transactional records. For example, store personnel can provide feedback about product availability, promotional effectiveness, packaging issues, shopper reactions, or changing inventory requirements. Surveys can also capture consumer or shopper opinions about products or promotional activities.

Inventory reconciliation is handled through inventory-management and Inventory Check processes rather than primarily through surveys. Point-of-sale information is normally imported or integrated as structured sales data for analytics rather than collected manually through an In-Store Survey.

Study Guide Topics:Visit Execution - > In-Store Survey - > Customer Feedback - > Promotions - > Inventory Requirements - > Product Quality

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

The Sales Manager persona is responsible for managing the day-to-day Retail Execution processes performed by the field organization. Salesforce explicitly defines the Sales Manager as a standard Retail Execution user who can create visits, create tasks, and assign visits to field representatives.

This division of responsibilities is fundamental to the Agentforce Consumer Goods operating model. Sales managers coordinate retail coverage and determine what activities field representatives should perform at each store. They typically work with Retail Stores, Visits, Action Plans, Assessment Task Definitions, and Action Plan Templates to organize execution activities. By contrast, field representatives have a more execution-focused role: they review assigned visits, complete assessment tasks, capture observations, process orders, and record the results of store activities.

The permission model is designed around these personas. Salesforce recommends establishing separate permission configurations for Sales Managers and Field Reps so that each role receives the appropriate object-level and feature access. Delivery representatives can also be configured separately when the organization uses Direct Store Delivery.

Consequently, responsibility for creating and coordinating visits and assigning field work belongs to the Sales Manager persona.

Study Guide Topics:Platform - > User Personas - > Sales Manager - > Visit Management - > Task Assignment

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

The representative should edit the product tags so that the detected object is associated with the correct product classification. Accurate tagging is fundamental to maintaining reliable object-recognition results, particularly when two products have visually similar packaging.

Object detection identifies objects within an image and maps those detections to labels or product classes. If a competitor changes packaging so that its product resembles another SKU, the resulting classification can incorrectly increase the measured facings or share-of-shelf for the wrong product. Correcting the tag provides accurate classification information and helps maintain the integrity of the shelf measurement.

Salesforce ' s Einstein Vision architecture supports a feedback process for incorrectly classified objects. When an object-detection model misclassifies an image, corrected examples and labels can be added back to the dataset and used in subsequent training or retraining. Salesforce describes this feedback mechanism specifically as a way to improve models after misclassification.

Creating a new planogram would only alter the expected shelf arrangement and would not correct product identity. Turning competitor products around manipulates the physical merchandising environment rather than correcting the data. Canceling the task similarly fails to improve future recognition.

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

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