AP-204 Sample Questions Answers

For a product-level Inventory Check, the product must be associated with the Retail Store where the assessment will be executed. Retail Execution needs a store-specific product relationship so Salesforce can determine which products are available for assessment when the field representative opens the Inventory Check.

Salesforce ' s Inventory Check prerequisites explicitly require administrators to associate Products with the Retail Store and associate the applicable In-Store Locations with that same Retail Store. The Retail Store must also belong to the Retail Store Group selected on the Retail Store KPI.

The Retail Store KPI then defines the assessment target by combining the Retail Store Group, applicable In-Store Location Category, Assessment Indicator Definition, and Product or Product Category. Salesforce separately specifies that the Product field is required on a Retail Store KPI when inventory-check tasks are configured for the store group.

The Store Product relationship provides the standard data-model mechanism for associating an individual Product2 SKU with a Retail Store or particular In-Store Location. A Promotion or Product Category relationship serves a different business purpose, while an Assortment defines a collection of products eligible for sale rather than replacing the required store-product association for Inventory Check execution.

Study Guide Topics:Data Setup - > Inventory Check - > Product - > Retail Store - > Store Product - > Retail Store KPI

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

Endcaps should be represented as In-Store Locations and In-Store Location Categories, with Retail Store KPIs specifically configured for that merchandising context. This allows NTO to measure endcap performance independently from primary shelves, checkout counters, backrooms, or other store areas.

Salesforce ' s Agentforce Consumer Goods data model supports In-Store Location categories precisely for this purpose. Similar physical locations across stores can be categorized-for example, Endcap Displays-and Retail Store KPIs can then use that category to define the measurements and targets applicable to those locations.

Salesforce ' s own Retail Execution configuration examples demonstrate creating Retail Store KPIs specifically for the Endcap Displays category. A promotion-compliance KPI can include the Retail Store Group, Endcap Displays as the In-Store Location Category, the relevant Assessment Indicator Definition, Promotion, Product Category, and a Boolean target value. This allows field representatives to capture endcap-specific performance during visits while managers analyze the resulting Retail Visit KPI data separately.

Creating Retail Store record types or unrelated custom objects would not provide the appropriate KPI granularity. Dedicated KPI configuration for the endcap context uses the standard Consumer Goods data model and provides targeted merchandising measurement.

Study Guide Topics:Data Setup - > In-Store Locations - > Endcap Displays - > Retail Store KPI - > Assessment Indicators

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

The In-Store Survey experience uses contextually associated Survey Invitations rather than displaying every open survey invitation in the organization. The relevant contexts are the Visit, Retail Store, and Store Primary Contact.

Salesforce allows a Survey Invitation to be generated for a contact and associated with a Visit as the related record. When the Action Plan Template assigned to the visit contains an In-Store Survey task, this association makes the invitation available within the visit ' s survey execution context. Salesforce also supports generating the invitation from the Retail Store ' s primary contact and associating the survey with the applicable account or store context.

This design ensures that field representatives see surveys relevant to the specific retail engagement they are executing. Showing all open invitations or every invitation targeted to any contact or user would introduce unrelated survey records and would not preserve the visit-level execution context.

The relationship between the Survey, Survey Invitation, Primary Contact, Retail Store, and Visit therefore provides controlled survey distribution while ensuring that the correct questionnaire is available during the appropriate store visit.

Study Guide Topics:Visit Execution - > In-Store Survey - > Survey Invitation - > Visit - > Retail Store - > Primary Contact

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

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

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

The Delivery Task is the Consumer Goods Retail Execution object specifically designed to support Direct Store Delivery activities during a visit. It represents the delivery activity assigned to the field or delivery representative and provides the execution context through which shipments and individual product transfers are processed.

Salesforce separates the delivery process into several related records. The Delivery Task defines the activity that must be performed as part of the Action Plan associated with the Visit. A Shipment is then associated with that Delivery Task to identify the inventory that must be delivered. Products and quantities within the Shipment are represented through Product Transfer records.

This architecture allows the same delivery task framework to control execution while shipment records manage the physical movement of inventory. Salesforce specifies the Lightning Direct Store Delivery permission for users who perform Delivery Task functionality. When an Action Plan Template containing a delivery task is assigned to a visit, Delivery Task records are created and can subsequently be associated with shipments.

Therefore, Delivery Task is the purpose-built Consumer Goods object for initiating and managing Direct Store Delivery execution.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

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

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

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

Promotion Check functionality is intended to allow field representatives to validate whether a planned promotion has been executed correctly at a retail location. Two important execution capabilities are reviewing the products included in the promotion and capturing photographic evidence of the promotional display.

Salesforce supports promotions at Product Category, individual Product, and General Promotion levels. When performing the check, the representative needs visibility into the promotion context so the correct products or categories can be inspected. Product information establishes exactly what must be evaluated and prevents the representative from auditing unrelated merchandise.

Photo capture provides supporting visual evidence of the in-store execution. This is particularly useful for validating display placement, promotional materials, shelf presentation, or other compliance requirements. The recorded observation can then be evaluated together with applicable assessment indicators and Retail Store KPI targets.

Planning dates and discounts are part of promotion configuration and commercial planning rather than field compliance execution. The field representative ' s responsibility during the visit is to observe, validate, and record execution rather than modify the underlying promotional terms.

Therefore, viewing promoted products and taking photographs are the applicable standard field-execution capabilities.

Study Guide Topics:Visit Execution - > Promotion Check - > Products - > Compliance - > Photo Capture

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

Salesforce Maps Advanced supports sophisticated store-visit planning through traffic-aware routing, routing constraints, and Visit Windows.

Traffic information helps field representatives and planners account for expected travel conditions. Agentforce Consumer Goods optimized-route functionality uses travel time between visits and provides real-time traffic information and route suggestions so representatives can react to congestion, roadworks, and other delays.

Maps Advanced also performs constraint-based optimization. Route generation considers operational constraints such as the planning period, required visit frequency, working schedules, travel time, maximum segment length, and other optimization criteria. These constraints allow the routing engine to generate routes that balance customer-coverage requirements with the practical capacity of field representatives.

Visit Windows define when a customer or retail location can accept a visit. Administrators can establish specific days and times, such as weekdays between 9:00 AM and 11:00 AM. Maps Advanced then attempts to schedule future visits inside those windows while generating optimized routes.

Together, these capabilities allow sales managers to create realistic multi-stop schedules that account for travel conditions, operational restrictions, and customer availability.

Study Guide Topics:Visit Planning - > Salesforce Maps Advanced - > Route Optimization - > Constraints - > Visit Windows - > Traffic

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

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

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

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

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

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

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

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

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

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

The planogram Image record is associated with an In-Store Location. This relationship identifies the specific physical area of the retail store where the reference shelf arrangement applies.

Salesforce ' s Planogram Check prerequisites require administrators to create an Image record representing the planogram and then associate that Image with the appropriate In-Store Location. Typical In-Store Locations include primary shelves, aisles, checkout counters, endcaps, and other areas where products are displayed.

The association is important because a single Retail Store can contain many merchandising locations, each with a different expected layout. Linking the planogram directly to its In-Store Location enables Salesforce to present the correct reference image when a field representative performs a Planogram Check at that particular location.

The Retail Store KPI then references the corresponding In-Store Location Category, Assessment Indicator Definition, Image or planogram, product context, and KPI Type. During execution, the field representative can open Product Details within the Planogram Check and view both the products to be inspected and the associated reference image.

Therefore, the Image object containing the planogram is related to the In-Store Location where that planogram must be evaluated.

Study Guide Topics:Data Setup - > Planogram - > Image - > In-Store Location - > Planogram Check

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

Flow-based tasks operate within the Visit and Assessment Task execution context and require the business context necessary to determine the applicable KPI configuration. The Retail Store KPI represents the target definition for an Assessment Indicator Definition and provides information such as store group, product, location category, target value, and other assessment context.

The flow also operates with the relevant Assessment Task and Visit identifiers so that automation can execute against the correct task instance and scheduled retail visit. This maintains the relationship between the reusable configuration and the transaction generated for an individual field visit.

Salesforce ' s broader assessment architecture reflects the same hierarchy: assigning an Action Plan Template to a Visit creates Assessment Tasks based on Assessment Task Definitions, while Retail Visit KPIs are generated using the applicable Retail Store KPI configuration.

This separation is essential. Retail Store KPI supplies expected business targets, Assessment Task provides the executable activity, and Visit supplies the store-engagement context in which the Flow runs.

Study Guide Topics:Visit Execution - > Flow-Based Tasks - > Retail Store KPI - > Assessment Task - > Visit Context

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

The Retail Store object should be used as the base object because Retail Stores represent the physical customer locations that field representatives need to visit. Salesforce Maps requires a mappable business object containing, or resolving to, geographic information so that records can be plotted, filtered, routed, and scheduled.

In Consumer Goods visit planning, Retail Store records supply this geographic and operational context. Store records contain the address and related location information required by Salesforce Maps. Salesforce states that the address entered when creating a Retail Store provides the location coordinates used by Salesforce Maps and also appears in the representative ' s visit list.

Salesforce ' s Consumer Goods optimized-routing process likewise uses Retail Store as the Maps base object. The planner selects relevant stores, applies business filters, identifies representatives and planning dates, and allows Maps to generate optimized visit schedules and routes.

The Visit subsequently represents the scheduled engagement with the selected Retail Store, but the physical destination being routed is the Retail Store itself. Account represents the broader customer organization and may encompass several stores, while Contact represents an individual person. Warehouse serves a different inventory and logistics purpose.

Using Retail Store therefore gives Salesforce Maps the correct geographic granularity for store-level visit planning and route optimization.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Base Object - > Retail Store - > Route Planning

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

Administrators review object-detection results through Detected Objects. Each object identified by the vision model is represented as a Detected Object record, providing administrators with the information required to examine how the model is performing against actual images.

A Detected Object record contains operational details about a particular detection, including the source image, the model responsible for identifying the object, the object ' s coordinates within the image, and the probability or confidence associated with the detection. Reviewing these records allows administrators to determine whether products are being identified correctly and to recognize patterns of incorrect classification or missed detections.

This review process is also important for continuous model improvement. When model output is inaccurate, additional representative examples can be incorporated into the training dataset and the model can be trained again. Salesforce ' s Einstein Vision architecture supports iterative model development because a dataset can generate multiple models, enabling implementers to compare model performance and refine training data over time.

Creating an unrelated custom object, enabling a feature, or using Einstein Bots does not provide the detection-result records required to assess object-recognition performance.

Study Guide Topics:Platform - > Einstein Vision - > Detected Objects - > Model Performance - > Model Refinement

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

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

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

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

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

Consumer Goods supports product-focused promotions at the Product Category and individual Product levels. These levels determine the merchandise scope against which promotional activities and Promotion Checks are configured.

A Product Category-level promotion is used when a promotional activity applies to a group of related products. Salesforce gives the example of applying a discount across an entire beverage category and then using a category-level Promotion Check to measure the resulting promotional execution and sales impact.

A Product-level promotion applies to individual products. For example, a consumer goods organization can promote a newly launched product through free samples and then use a product-level Promotion Check to capture consumption or customer feedback.

Salesforce also supports a General Promotion, which has no Product or Product Category context. Retail Store and Retail Store Group are not promotion product levels; instead, they define where the promotion applies. That geographic or organizational reach is established through Promotion Channel, which can associate a Promotion with a store, store group, or account.

This separation lets administrators independently configure the merchandise scope and retail distribution scope of each promotion.

Study Guide Topics:Data Setup - > Promotion - > Product Category - > Product - > General Promotion - > Promotion Channel

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

Einstein Visit Recommendations provide decision support for sales managers and field representatives by helping them determine which stores should receive attention and when those visits should be scheduled. The capability supplements the expertise of the field organization by presenting prioritized information derived from business rules and prediction insights.

Salesforce describes the feature as a mechanism for scheduling the right stores at the right time in order to maximize profit and deliver brand value. Visit Recommendations can identify stores that have not been serviced recently and present recommended visits that users can review and schedule. Managers remain responsible for deciding which recommendations to accept and for coordinating execution.

The recommendation architecture can use configurable flow strategies or Next Best Action strategies. Organizations can tailor the logic to their own business requirements rather than relying on a mandatory external market-research dataset. This enables field professionals to focus their expertise on selling, merchandising, customer relationships, and execution while Salesforce surfaces relevant visit-planning intelligence.

The intended value is therefore workforce augmentation and improved prioritization-not replacement of experienced personnel.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Recommendation Strategies - > Store Prioritization - > Field Productivity

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

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

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

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

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

The Nearby Map component on the Promotion record page provides the required functionality through standard Salesforce Maps configuration with minimal custom development.

Salesforce specifically documents the use of a Nearby Map component for Consumer Goods scenarios. Administrators create a Nearby Map configuration using an appropriate Maps layer and then place the Maps Nearby Maps component on a Lightning Record Page through Lightning App Builder. The layer determines which business records are displayed and how they are filtered.

For promotions, Salesforce gives this precise use case: administrators can configure a Nearby Map with a layer containing Retail Stores and place that component on the Promotion record page. When a sales manager views the Promotion record, the component displays retail stores participating in the promotion in a map-based interface. This allows the manager to visualize nearby participating stores without leaving the promotion context.

Because the capability is supplied through Salesforce Maps and Lightning App Builder, it avoids developing a custom visual mashup or modifying an unmanaged AppExchange package. Adding a generic map to the Home page would also lack the Promotion record context needed to display stores associated with the specific promotion.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Nearby Map - > Promotion - > Retail Store Visualization

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

A Planogram Check requires the planogram Image to be associated with the appropriate In-Store Location. The In-Store Location identifies the physical area inside the retail outlet-such as an aisle, primary shelf, checkout counter, or endcap-where the expected product arrangement applies.

Salesforce ' s Planogram Check prerequisites require administrators to create an Image record representing the planogram and associate the Image with an In-Store Location. The Product must also be associated with both the Retail Store and the relevant In-Store Location.

The Retail Store KPI then supplies the assessment configuration. Administrators select the appropriate Retail Store Group, In-Store Location Category, Assessment Indicator Definition, planogram Image, and KPI Type. Supported planogram-related KPI Types include Facing, Share of Shelf, and Out of Stock, depending on the indicator being measured.

This relationship ensures that Salesforce can determine which reference layout applies when a representative performs the assessment at a particular location within the store. Associating the Image only with a Promotion, Assessment Task, or Retail Store does not establish the precise physical merchandising context required for Planogram Check execution.

Study Guide Topics:Data Setup - > Planogram - > Image - > In-Store Location - > Retail Store KPI

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

The Inventory Check Lightning component is available for placement directly on an Assessment Task record page. Salesforce allows administrators to create or customize an Assessment Task Record Page through Lightning App Builder and add Consumer Goods-specific components that support field execution.

For the Assessment Task object, Salesforce documents the available components as Planogram List, In-Store Products, Promotion List, Inventory Check, and Consumer Goods Survey List. The Inventory Check component provides the dedicated interface for inventory-related assessment tasks and can expose information such as progress, summary information, location filtering, and assessment sections.

The wording of the other choices is important. Salesforce provides Planogram List, rather than a component named Planogram Check, and Promotion List, rather than a component named Promotion Check. Likewise, the supported product component is named In-Store Products, not In-Store Products Check.

After adding the Inventory Check component, the administrator can configure its component properties and activate the Lightning Record Page for the appropriate application, record type, and user profiles. This configuration provides field representatives with the required mobile or desktop execution interface when they open an inventory-related Assessment Task.

Study Guide Topics:Platform - > Lightning App Builder - > Assessment Task Record Page - > Inventory Check Component

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

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

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

For the Agentforce Consumer Goods visit-execution model, the appropriate Action Plan Type is Visit Execution. Action Plan Templates provide reusable collections of activities that field representatives repeatedly perform during visits to retail stores.

Salesforce ' s Consumer Goods data-model training identifies Visit Execution as the Action Plan Type used for Retail Execution templates and Visit as the Target Object. The template can then contain tasks such as inventory checks, planogram checks, promotion checks, asset checks, surveys, order-related activities, and other recurring work.

The Action Plan Template separates reusable task configuration from individual Visit records. Administrators define the common activities once, establish their order and mandatory status, and then associate the template with multiple visits. When the template is applied, Salesforce creates the necessary visit-level tasks so the field representative receives a consistent execution workflow.

This approach is particularly important in consumer goods organizations where representatives may perform essentially the same merchandising, inventory, promotion, order, and compliance activities across hundreds or thousands of stores. Visit Execution provides the action-plan classification aligned with that Retail Execution business process.

Study Guide Topics:Visit Planning - > Action Plan Template - > Visit Execution - > Visit Target Object - > Assessment Tasks

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

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

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