Salesforce AP-204 Dumps

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

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

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

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

An Inventory Check requires the Retail Store KPI to identify the applicable Retail Store Group and Assessment Indicator Definition. These fields establish where the measurement applies and exactly what the field representative must measure.

The Retail Store Group is fundamental because Salesforce defines Retail Store KPIs at the store-group level rather than directly at an individual store level. The group connects the KPI configuration to the Retail Stores that inherit and use the target during field execution.

The Assessment Indicator Definition identifies the metric to be captured-for example, stock quantity, availability, damaged-product count, or another inventory-related measurement. Salesforce ' s Inventory Check prerequisites explicitly require the Retail Store Group and an Assessment Indicator Definition for the applicable product or product category and In-Store Location Category.

Custom Context is associated with custom-task configurations and should remain empty for a standard Inventory Check. Inventory Count is not the configuration field that establishes the Retail Store KPI relationship. KPI Type can categorize the business meaning of an indicator, but the core Inventory Check configuration depends on the Retail Store Group and Assessment Indicator Definition.

Together, these records enable Salesforce to generate the corresponding Retail Visit KPIs when the Inventory Check is instantiated for a Visit.

Study Guide Topics:Data Setup - > Retail Store KPI - > Inventory Check - > Retail Store Group - > Assessment Indicator Definition

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

Salesforce supports Promotion Checks at three defined levels: General Promotion, Individual Product, and Product Category. These levels determine the commercial context against which a field representative performs the promotional compliance assessment.

A Product Category-level Promotion Check is appropriate when the promotion applies across a category of products. For example, an organization may discount all beverages or energy bars and assess compliance collectively rather than creating an independent promotion check for each SKU.

An Individual Product-level Promotion Check is used when a promotion applies to a specific product, such as the launch of a new flavor or an in-store sampling activity. The field representative evaluates execution specifically for that product.

A General Promotion does not require association with a particular product or product category. It is suitable for store-wide activities such as coupons, signage, or general promotional conditions that apply across the outlet.

These three levels allow promotion configuration to match the intended scope while avoiding unnecessary duplication of promotional records and assessment tasks. Salesforce uses the same levels when defining the promotion and when executing the corresponding Promotion Check in the field.

Study Guide Topics:Visit Execution - > Promotion Check - > General Promotion - > Product - > Product Category

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

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

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

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

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

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

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

The Retail Store object represents an individual physical outlet within a retailer ' s organizational structure. Salesforce deliberately separates the customer organization represented by Account from the physical selling locations where field representatives execute retail activities.

The Account object stores information about the retailer, distributor, wholesaler, or other customer organization, while Retail Store stores information about each physical store. Salesforce identifies Retail Store as the location where products are stored and sold.

A retailer can therefore have one Account associated with multiple Retail Store records. Each store can maintain its own operational characteristics, including location, delivery method, recommended visit frequency, store type, products, in-store locations, visits, orders, and other Retail Execution data. Retail Stores can also be organized into Retail Store Groups when multiple outlets share characteristics such as format, geographic area, size, or membership in a retail chain.

Assortments serve a different function: they define collections of products eligible or targeted for sale. They do not represent physical retail outlets. Therefore, Retail Store is the standard Consumer Goods object used to model each specific store operated within a retailer.

Study Guide Topics:Data Setup - > Account - > Retail Store - > Retail Store Group - > Retail Hierarchy

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

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

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

CRM Analytics for Agentforce Consumer Goods requires a minimum set of records before the Analytics for Consumer Goods app can be successfully created. Salesforce identifies the required data objects as Account, RetailStore, Visit, RetailVisitKpi, and Product2. An Order record is additionally required when the organization wants to include both Retail Execution and sales data.

The Retail Visit KPI requirement is particularly important because Retail Visit KPI records contain actual information captured during visits against the Assessment Indicator Definitions and targets configured for Retail Execution. These records provide the analytics layer with visit-level compliance and performance measurements that can be used in dashboards for store performance, product performance, territory analysis, and other Retail Execution insights.

Retail Visit KPI records are generated as part of the assessment-task process based on the underlying Retail Store KPI configuration. Salesforce therefore requires at least one RetailVisitKpi record in the organization when validating the data prerequisites for the CRM Analytics application.

The analytics setup process validates these minimum data requirements and displays a message when required records are missing.

Study Guide Topics:Analytics - > CRM Analytics for Agentforce Consumer Goods - > Data Requirements - > Retail Visit KPI - > Retail Execution Analytics

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

Planogram execution in Consumer Goods Cloud depends on connecting the planogram to the physical location within the retail store where the shelf configuration must be evaluated. Salesforce uses an In-Store Location to represent areas such as shelves, aisles, displays, or endcaps. During planogram configuration, an Image record representing the planogram is associated with the appropriate In-Store Location. The Retail Store KPI then provides the assessment context by connecting the relevant Retail Store Group, In-Store Location Category, Assessment Indicator Definition, product or product category, and planogram.

This relationship ensures that when the field representative opens a Planogram Check during a visit, Salesforce can determine which reference planogram applies to the specific area being inspected. Simply attaching an image to an Assessment Task does not establish the required retail-location relationship. Custom Context is intended for custom assessment use cases rather than the standard Planogram Check configuration.

The critical design principle is therefore the association between the planogram and its In-Store Location, which provides the physical execution context required by Retail Execution.

Study Guide Topics:Data Setup - > Planograms - > In-Store Locations - > Retail Store KPIs - > Planogram Checks

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

Users who need to access the CRM Analytics application for Consumer Goods require both the CRM Analytics Plus User entitlement and the CG Analytics User permission set. In the terminology used by this question, CRM Analytics Plus User corresponds to Tableau CRM Plus User.

Salesforce separates platform analytics access from Consumer Goods-specific analytics permissions. CRM Analytics Plus User provides access to CRM Analytics capabilities, while CG Analytics User grants the permissions required to consume the Consumer Goods analytics application and its associated dashboards and datasets.

Salesforce ' s documented setup process instructs administrators to open the user ' s Permission Set Assignments and assign CG Analytics User together with CRM Analytics Plus User when the organization uses CRM Analytics for Consumer Goods Cloud.

This dual-permission approach ensures that the user has both the underlying analytics platform entitlement and the Consumer Goods application-level access required to view dashboards such as product, store, field-representative, and territory performance analytics.

Administrative permissions such as CRM Analytics Plus Admin are intended for administrators who configure and maintain analytics applications. They are not necessary for ordinary application consumers who only need to view and interact with Consumer Goods analytics.

Study Guide Topics:Analytics - > CRM Analytics - > CG Analytics User - > CRM Analytics Plus User - > User Permissions

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

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

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

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 Product Performance dashboard is designed to help sales managers analyze how products, product categories, brands, and assortments are performing across the Consumer Goods organization. It provides detailed performance views that allow users to identify both strong and weak performers and then drill into the underlying metrics.

Salesforce states that the Product Performance dashboard analyzes product category, brand, product, assortment, and the impact of promotions on performance. Its Product page shows overall product trends and enables managers to identify high-performing products and analyze recently launched products. Its Category and Assortment pages provide equivalent analysis at those organizational levels.

Typical measures include revenue, quantity, average order value, store coverage, average compliance, and related sales-performance indicators. Salesforce specifically describes the dashboard as answering questions such as which products, categories, brands, and assortments are high-performing or least-performing. Managers can drill into individual entities to investigate performance trends and identify where intervention or additional investment is appropriate.

Therefore, the dashboard gives the Sales Manager the ability to identify top- and low-performing products, categories, and assortments and investigate their performance in greater detail.

Study Guide Topics:Analytics - > Product Performance - > Product Categories - > Assortments - > Performance Analysis

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

The Maximize Store Sales Einstein Discovery story is designed to identify factors that influence product sales and provide actionable insights that can help sales managers improve store performance.

Salesforce provides preconfigured Einstein Discovery stories within Analytics for Consumer Goods. The sales-focused story analyzes historical data to identify variables that have a positive or negative impact on product sales. Salesforce currently describes this capability as Maximize Store Product Sales, which provides insights into the factors affecting product sales and helps organizations devise strategies to increase sales at a store or store-group level.

Einstein Discovery uses the available analytics dataset to identify statistically relevant relationships and present explanations that business users can act upon. These insights can assist sales managers in understanding how factors such as product availability, assortment, store characteristics, and other operational conditions correlate with sales performance.

The Minimize Out-of-Stock story serves a different objective: it predicts products that are likely to run out of stock so representatives can mitigate availability problems. While out-of-stock conditions can affect revenue, the scenario specifically asks for broader insight into the factors affecting store sales, making the sales-maximization story the appropriate functionality.

Study Guide Topics:Analytics - > Einstein Discovery - > Maximize Store Sales - > Predictive Insights - > Sales Performance

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

Custom assessment tasks use the Consumer Goods Custom Task Measures component to expose KPI information on the related object ' s record page. For this experience to appear, the administrator must both place the component on the relevant Lightning Record Page and ensure that the intended users receive that page through the correct page assignment.

Salesforce instructs administrators to open the custom or standard object ' s Lightning Record Page in Lightning App Builder, drag the Consumer Goods Custom Task Measures component onto the page, configure its properties, and save the page. If the component has not been added, users naturally see the object ' s standard record-page experience instead of the custom KPI interface.

Lightning Record Pages must also be activated for the appropriate application, record type, and user profile. Salesforce ' s page activation framework supports assignments by app, record type, and profile, allowing different users to receive different record-page experiences. If the custom task page is not assigned to the field representative ' s profile, Salesforce can display another assigned or standard record page instead.

These two configuration layers-component placement and profile/page assignment-are therefore required for the KPI component to appear.

Study Guide Topics:Platform - > Lightning App Builder - > Custom Tasks - > Consumer Goods Custom Task Measures - > Record Page Assignment

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

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

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

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

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

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

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

Salesforce Maps Click2Create is designed for field representatives who discover prospects, customers, or service locations while working in a territory. It allows a user to create Salesforce records directly from a map location or Point of Interest without leaving the mapping experience.

When a representative identifies a restaurant or grocery outlet while traveling the route, the representative can select the relevant Point of Interest and invoke Click2Create. Salesforce can use available business and location information to populate fields on the new Salesforce record. Administrators can configure field sets and field mappings so data captured through Click2Create is directed into the appropriate fields on Lead, Account, or other supported records.

This approach is significantly more efficient than manually creating an unrelated record and initiating an email-based handoff. It also allows the newly created prospect to enter an established Salesforce onboarding process immediately. Opportunity and CPQ functionality generally applies after sufficient prospect and account qualification has occurred, while directing the customer to an external commerce site does not provide the controlled field-sales onboarding process described in the scenario.

Click2Create therefore provides the most appropriate integration between Salesforce Maps, field prospecting, and customer onboarding.

Study Guide Topics:Integrations - > Salesforce Maps - > Click2Create - > Points of Interest - > Customer Onboarding

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

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

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

A Retail Store can be associated with many Visit records, creating the required one-to-many relationship. Each Visit represents a particular scheduled or completed engagement between a field representative and a physical retail location, while the same store can naturally be visited repeatedly over time.

Salesforce describes the Visit object as tracking information about a field representative ' s visit to a Retail Store where retail activities are performed. Visit records hold information such as planned and actual start and end times, status, visitor, priority, and the related location.

For Consumer Goods implementations, the Visit ' s Place relationship identifies the Retail Store being visited. Salesforce Maps uses the same model when scheduling Consumer Goods visits: Visit records can derive their map location from the related Retail Store through Place ID, allowing Maps to position each Visit at the correct physical outlet.

Because representatives return to stores according to visit frequencies, merchandising schedules, promotions, deliveries, and sales requirements, a single Retail Store can accumulate multiple Visit records over its lifecycle. Each Visit remains a distinct transaction with its own Action Plans, tasks, KPIs, timing, and execution results.

Study Guide Topics:Data Setup - > Retail Store - > Visit - > Place Relationship - > Store Visit History

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

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

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

Because the promotion applies to all energy bars, the Retail Store KPI should be configured at the Product Category level. Salesforce supports promotion checks at the Product Category, individual Product, and General Promotion levels. Product Category is the appropriate level when a promotional activity applies uniformly to a group of related products.

A category-level configuration minimizes administrative overhead because a single KPI configuration can represent the target for the complete energy-bar category rather than requiring individual KPI records for every SKU. Salesforce allows the administrator to associate a Product Category with a Retail Store KPI together with the Assessment Indicator Definition, Retail Store Group, In-Store Location Category, promotion, KPI type, and target value.

An SKU-level configuration would be appropriate when each individual product requires separate measurement or targets. In this scenario, however, the same BOGO promotion applies across the full energy-bar category, so SKU-specific records would unnecessarily increase data volume and maintenance.

Custom Context applies primarily to custom assessment tasks rather than standard promotion-check configuration. Consequently, Product Category provides the correct granularity while supporting scalable and maintainable Retail Store KPI administration.

Study Guide Topics:Data Setup - > Promotions - > Product Categories - > Retail Store KPI - > Promotion Checks

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

For a business-specific activity such as auditing coolers installed in retail stores, the Assessment Task Definition should use the Other task type. Consumer Goods provides standard task types for common Retail Execution activities, including Inventory Check, Planogram Check, Promotion Check, In-Store Survey, and Order Creation. Activities that do not fit those predefined processes are implemented through a custom assessment using the Other task type.

A cooler audit can require measurements such as operational condition, cleanliness, temperature compliance, branding condition, or whether required products are stocked. Administrators can represent these measurements through Assessment Indicator Definitions using appropriate data types such as Boolean, Number, Decimal, Text, or Picklist.

For custom tasks, the Retail Store KPI can also use Custom Context to associate the KPI with an appropriate standard or custom object. Salesforce permits eligible objects with activities enabled to provide this business context.

The resulting custom task can then be added to an Action Plan Template so that field representatives receive the cooler-audit activity during applicable store visits. This uses the standard Consumer Goods assessment framework while supporting specialized business processes without incorrectly modeling the audit as inventory, promotion, or planogram activity.

Study Guide Topics:Visit Execution - > Assessment Task Definition - > Other Task Type - > Custom Tasks - > Assessment Indicators

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

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

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

The supported Retail Store KPI types include Price, Facing, and Revenue, along with Share of Shelf, Out of Stock, and Inventory. KPI Type identifies the business interpretation of the Assessment Indicator Definition associated with a Retail Store KPI and is particularly important for Retail Execution measurements and analytics.

Facing is used when the organization measures the number of product facings visible on a shelf or display. It commonly supports planogram and merchandising compliance. Price supports assessments where the field representative records and evaluates the displayed or observed product price. Revenue provides the business classification for revenue-oriented performance measures.

Salesforce ' s Retail Store KPI configuration explicitly provides these values in the KPI Type picklist: Facing, Share of Shelf, Out of Stock, Inventory, Price, and Revenue. The KPI Type can also contribute to calculated performance indicators such as average facing compliance, average out-of-stock compliance, and average price compliance.

Promotion is business context rather than a KPI Type; a Promotion can instead be associated with the Retail Store KPI. Units can function as a unit of measure or assessment concept but is not one of the supported KPI Type values identified for the Retail Store KPI.

Study Guide Topics:Data Setup - > Retail Store KPI - > KPI Type - > Facing - > Price - > Revenue

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