Salesforce AP-204 Salesforce Accredited Agentforce Consumer Goods Professional Exam Practice Test

A Shipment must be associated with the Delivery Task so that the products scheduled for delivery can be presented during execution. In Salesforce Direct Store Delivery, the Delivery Task provides the activity context, while the Shipment defines the inventory movement that the field representative is expected to complete.

Salesforce specifies that after a Delivery Task is generated from an Action Plan Template assigned to a visit, the task must be associated with a Shipment. Products are then added to that Shipment through related Product Transfer records. Each Product Transfer identifies the product and quantity involved in the shipment.

This hierarchy is important because the Delivery Task does not independently maintain its own product list. Instead, it obtains the delivery-item context from its related shipment. A standalone Product record does not establish that the product is scheduled for a particular delivery, and a Retail Store KPI belongs to the Retail Execution assessment framework rather than inventory delivery processing.

Accordingly, if delivery items do not appear within the Delivery Task, the administrator should verify that the appropriate Shipment has been associated with the task and that the shipment contains the necessary Product Transfer records.

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

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

The Assessment Indicator Definition defines the KPI or measurable parameter that field representatives capture during Retail Execution. It provides the reusable definition of what must be measured, such as the number of products on a shelf, product facings, stock availability, promotional compliance, or another store-performance indicator.

Salesforce supports several data types for Assessment Indicator Definitions, including Number, Boolean, Date Time, Text, Decimal, and Picklist. The definition can then be associated with one or more Assessment Task Definitions covering products, product categories, promotions, planograms, or custom assessment scenarios.

The Assessment Indicator Definition works together with two additional KPI objects. A Retail Store KPI associates the indicator with its business context and defines the expected or target value. A Retail Visit KPI stores the actual result captured by the field representative during a specific visit. Salesforce therefore separates the reusable KPI definition, target configuration, and transactional result into distinct layers.

This design enables the same Assessment Indicator Definition to be reused across multiple store groups, products, locations, and visits while maintaining separate targets and actual values for each applicable context.

Study Guide Topics:Data Setup - > Assessment Indicator Definition - > Retail Store KPI - > Retail Visit KPI - > KPI Measurement

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

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

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

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

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

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

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

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

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

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

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

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 provides several standard Lightning components specifically scoped to the Assessment Task object. Among the listed options, In-Store Products, Promotion List, and Inventory Check are standard Assessment Task components.

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

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

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

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

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

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

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

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

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

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

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

Sales Rep Performance, Store Insights, and Product Performance are standard analytics dashboards provided for Consumer Goods Retail Execution.

The Sales Rep Performance dashboard enables sales managers to compare representatives, identify high- and low-performing team members, and analyze performance trends over time. Metrics can include revenue, product sales, visits, compliance, and other Retail Execution measurements.

The Store Insights dashboard provides store-focused analysis. It enables users to examine store sales, compliance metrics, product performance, visits, and related trends to identify outlets that require attention. Salesforce documents Store Insights as one of the embedded dashboards available within the Consumer Goods analytics experience.

The Product Performance dashboard provides product- and category-level insights. Sales managers can identify high- and low-performing products, review revenue and quantity trends, analyze compliance, and determine which products require intervention.

The native analytics portfolio contains additional dashboards such as Store Performance, Territory Performance, Whitespace Analysis, and Sales Manager Home. Category Insights and Inventory Performance are not the corresponding standard dashboard names represented by these options.

Study Guide Topics:Analytics - > CRM Analytics - > Sales Rep Performance - > Store Insights - > Product Performance

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

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

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

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

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

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

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

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

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

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

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

Photos captured during an asset-compliance activity are maintained within the assessment-task content framework, allowing the evidence to remain associated with the task that generated it. For an asset check implemented as a custom Assessment Task, this provides the most direct relationship between the compliance observation and its supporting photographic evidence.

Salesforce provides the Assessment Task Content Document object specifically for associating Content Documents with assessment activities. Its data model includes a reference to the parent Assessment Task and a Content Document reference, allowing files generated during execution to remain connected to the task. Salesforce also supports a content-context reference that can identify contextual business records such as an Asset or Visit.

Within Retail Execution, Salesforce uses Assessment Task Content Document records for notes and pictures captured by field representatives while performing assessment activities. This preserves the evidentiary relationship between the field observation and the work performed, enabling managers to review photographs alongside the associated compliance task.

The photo therefore remains accessible through the asset check Assessment Task, where the manager can review the evidence in the same operational context as the captured asset-compliance measurements.

Study Guide Topics:Visit Execution - > Asset Checks - > Assessment Task - > Content Documents - > Photo Evidence

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

The Store Product object establishes the relationship between a Product2 record and a specific Retail Store or In-Store Location. Salesforce defines Product2 as the product master representation of a SKU, while Store Product provides the store-specific relationship required for Retail Execution.

Salesforce ' s Retail Execution object model explicitly defines Store Product as the association of a product to a retail store or to a specific in-store location. This association enables Salesforce to determine which products are relevant to a particular outlet rather than exposing the organization ' s entire Product2 catalog during field execution.

Store Product supports several operational scenarios. Inventory Checks use the relationship to identify products available for searching and scanning at the store. Order capture can use Store Product information to prioritize products relevant to that outlet, including frequently ordered or favorite products. Store Product can also associate an SKU with a specific shelf, aisle, or other In-Store Location for merchandising activities.

A Store Assortment serves a different purpose: it associates an assortment-a collection of products-with a store, store group, or account. Price Books and Price Book Entries support pricing and selling relationships but do not represent the standard Consumer Goods relationship between a retail outlet and its individual SKU.

Study Guide Topics:Data Setup - > Product2 - > Store Product - > Retail Store - > In-Store Location

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

The Retail Visit KPI provides the visit-level relationship between the configured KPI framework and the Assessment Task that is executed in the field. Retail Store KPI defines expected values, while Retail Visit KPI captures the actual measurement generated during a specific Visit and Assessment Task.

Salesforce ' s Consumer Goods data model shows that Retail Visit KPI includes references to Assessment Task, Visit, Assessment Indicator Definition, Product, Product Category, In-Store Location, Promotion, Planogram, and other assessment context. It also contains the Target Value and Actual Value used to evaluate store performance.

The records are created as part of the assessment-task generation process. When an Action Plan Template is assigned to a Visit, Salesforce creates Assessment Tasks based on the included Assessment Task Definitions and creates Retail Visit KPIs based on the applicable Retail Store KPIs.

This design enables one centrally configured Retail Store KPI to drive repeated measurements across many store visits. Each individual visit receives its own Retail Visit KPI record, allowing the actual execution result to remain associated with the Assessment Task that produced it.

Study Guide Topics:Data Setup - > Retail Visit KPI - > Retail Store KPI - > Assessment Task - > Actual and Target Values

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

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

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

Consumer Goods can be customized declaratively through Lightning App Builder and Flow, while Lightning Web Components provide the component-level extensibility required for specialized user experiences.

Lightning App Builder allows administrators to configure Salesforce record pages by placing and configuring standard components without rebuilding the underlying application. This supports customer-specific page composition while remaining within the Salesforce Platform configuration model.

Where more specialized behavior is required, Lightning Web Components provide an extensibility layer. Salesforce supports custom LWCs that interact with standard components and extend or modify business functionality. For example, Salesforce ' s Consumer Goods extensibility documentation describes using custom LWCs alongside standard components so custom interactions and data changes can be reflected in the standard experience.

For process-oriented customization, administrators can create Flows and associate them directly with an Action Plan Template. Salesforce states that flows can implement activities specific to a business that are not covered by standard Consumer Goods task types. Once associated with the template, those flows become available to field representatives during store visits.

The Consumer Goods mobile platform also supports LWC-based mobile extensions through its integration framework, keeping customization aligned with Salesforce Platform technologies rather than requiring Apache Cordova development.

Study Guide Topics:Platform - > Mobile Customization - > Lightning App Builder - > Lightning Web Components - > Flow - > Action Plan Templates

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

Salesforce Maps supports optimized visit sequencing and route guidance for field representatives. Agentforce Consumer Goods integrates mapping and routing capabilities so representatives can reduce travel time, determine an efficient order for store visits, and respond to changing road and traffic conditions throughout their working day.

Salesforce documents that Optimized Routes calculate the best visit sequence and display the day ' s stores and route on a map. The experience provides the sequence of visits, store addresses, real-time traffic information, route suggestions based on traffic, and the next customer location. Field representatives can use the Optimized Route sorting option in Scheduled Visits to organize their visits according to the calculated route.

Salesforce Maps Mobile also supports standard routes where Salesforce automatically optimizes the stop order. Representatives can add store locations to a route, optimize the sequence, and use mobile route controls while in the field.

This capability directly supports Consumer Goods visit planning because the objective is not simply to visualize locations but to determine an efficient sequence that minimizes travel and helps representatives reach the appropriate stores at the appropriate times.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Optimized Routes - > Visit Sequence - > Real-Time Traffic

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

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

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

A Store Product represents the relationship between a Product2 record and a particular Retail Store or In-Store Location. This relationship supplies the store-specific product context required by several Retail Execution processes.

For Inventory Checks, Salesforce must determine which products are relevant to the store being visited. Store Product records provide that relationship, allowing the Inventory Check experience to present applicable products rather than the entire enterprise product catalog. The same store-level product context supports the Search and Scan experience, where field representatives locate a product directly or scan its barcode while performing an inventory assessment.

Store Products also contribute to order capture. Salesforce stores operational attributes on the Store Product relationship, including the associated Product, Retail Store, In-Store Location, default order quantity, and favorite-product indicator. These fields allow the order experience to identify products that are relevant to a specific outlet and facilitate efficient repeat ordering.

Salesforce distinguishes Store Product from Store Assortment: Store Product represents products directly associated with a store or in-store location, while assortments define broader groups of products eligible for sale.

Study Guide Topics:Data Setup - > Store Product - > Inventory Check - > Search and Scan - > Order Capture

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

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

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