Salesforce Consumer-Goods-Cloud-Accredited-Professional Consumer Goods Cloud Accredited Professional (AP-204) Exam Practice Test

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

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

Object Metrics and Model Metrics provide complementary mechanisms for evaluating the accuracy and performance of an Einstein object-detection implementation. Object-level metrics focus on how accurately individual object classes are being recognized, while model-level metrics provide an overall view of the trained model ' s predictive quality.

Salesforce ' s Einstein Vision model APIs expose model-performance information so administrators and developers can evaluate whether a trained model is sufficiently accurate for production use. Model metrics include measurements that quantify detection quality and allow implementers to identify weaknesses before relying on predictions operationally. Salesforce ' s Einstein Vision API specifically provides a Get Model Metrics operation for vision models, allowing performance information to be retrieved for an object-detection model.

Object-level analysis is equally important because overall accuracy can hide differences between individual classes. For example, a model may reliably identify one product but repeatedly confuse another product with visually similar packaging. Reviewing object-specific performance identifies those classification weaknesses and indicates where additional or improved training examples are required.

Together, Object Metrics and Model Metrics provide both granular and aggregate perspectives on detection accuracy, supporting systematic evaluation and refinement of product-recognition models.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Object Metrics - > Model Metrics - > Detection Accuracy

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 Whitespace Analysis dashboard is specifically designed to identify opportunities to introduce additional products or product categories into stores. It analyzes sales information across products, categories, and retail locations to expose areas where a store has unused sales potential.

Salesforce describes whitespace as an opportunity where a product or category that performs successfully elsewhere is not currently generating sales in a particular store. The dashboard allows sales managers to evaluate revenue and quantity patterns, identify top-performing products, compare performance across stores, and determine where introducing a product could increase revenue. This makes it directly applicable to GreenTech ' s requirement to determine which new products may be suitable for a particular retail location.

The dashboard can answer questions such as which stores have the potential to sell top-selling products and whether a product or category can be introduced into additional stores. It also provides product-performance trends so the sales manager can evaluate whether a candidate product has demonstrated sufficiently strong performance elsewhere before expanding distribution.

Therefore, Whitespace Analysis provides the cross-selling and assortment-expansion insight needed for this scenario.

Study Guide Topics:Analytics - > CRM Analytics - > Whitespace Analysis - > Product Opportunities - > Store Sales Potential

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

The consultant must identify the hierarchy level that represents the stock keeping unit (SKU). In the Consumer Goods Retail Execution data model, individual products are represented through Product2 records, and Salesforce describes each Product2 record as a SKU or sellable unit. Consequently, the ERP hierarchy level that contains SKU-level information provides the appropriate product granularity for product-specific retail execution processes.

Share-of-shelf measurement requires Salesforce to identify precisely which products occupy shelf space so that actual shelf presence can be evaluated against configured targets. Retail Store KPIs can associate Assessment Indicator Definitions such as Share of Shelf with products, product categories, planograms, store groups, and in-store location categories. The underlying product master therefore needs a level that reliably represents the individual sellable products being measured.

Salesforce product master data can contain multiple hierarchy levels such as categories, subcategories, brands, and SKUs. The numerical position of a tier is not itself significant; what matters is the business meaning of that tier. For this requirement, the tier representing SKUs provides the required product-level data for shelf measurement and Retail Execution processing.

Study Guide Topics:Data Setup - > Product2 - > Product Hierarchy - > SKU - > Share-of-Shelf KPI

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

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 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 computer display unit should be represented as the business object being inspected, while its operational condition should be captured through an Assessment Task and associated KPI. This aligns with Salesforce ' s custom-task model for Retail Execution.

Salesforce supports custom tasks specifically for business scenarios that do not fit the standard Inventory Check, Promotion Check, Planogram Check, Order Creation, or Survey task types. Salesforce gives the example of capturing maintenance information for a refrigerator placed in a store, which is directly analogous to assessing the condition or functionality of a computer display unit.

For a custom assessment, administrators define Assessment Indicator Definitions representing the values that field representatives need to capture. The associated Retail Store KPI provides the target and business context, while the Retail Visit KPI stores the actual observation entered during execution. Custom Context can connect the KPI configuration to the relevant standard or custom business object.

An In-Store Survey is intended for collecting feedback from customers or store personnel and is not the appropriate mechanism for recording equipment-performance KPIs. Creating a dedicated task record type also does not replace the assessment/KPI architecture.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assets - > Assessment Indicators - > Retail Visit KPI

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

The Visit object should be used as the base object because the information that must be visualized-specifically the current status of today ' s visits-is stored on Visit records. Agentforce Consumer Goods uses the Visit object to track planned and completed retail-store engagements, including the responsible field representative, planned start and end times, retail location, and Visit Status.

Salesforce Maps supports Visit as a mappable object even though Visit itself does not contain a physical address. Salesforce Maps can inherit the location from the related Retail Store through the Visit ' s relationship to that store. A Marker Layer can then be constructed using Visit as its base object and filtered for the appropriate territory and date.

Salesforce Maps also supports dynamic marker formatting based on a field value. With the Varied Based On 1 Field configuration, the administrator can select Visit Status and assign different colors to different statuses. This allows an account manager to distinguish scheduled, in-progress, completed, or other visit states directly on the map without opening individual records.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Visit Object - > Marker Layers - > Visit Status

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

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

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

Setting up an In-Store Survey requires configuration of the Salesforce Survey, the corresponding In-Store Survey Assessment Task Definition, and an appropriate Survey Invitation.

The administrator first creates and prepares the Survey using Salesforce Surveys. This record contains the questions and response structure that the participant will complete. Next, the administrator creates an Assessment Task Definition and selects In-Store Survey as its task type. Assessment Task Definitions store reusable activities that can be incorporated into an Action Plan Template and subsequently instantiated as Assessment Tasks when that template is applied to a Visit.

The Survey must also be distributed through a Survey Invitation. Salesforce ' s Consumer Goods setup procedure supports generating the invitation from the primary contact of the Retail Store, associating the survey with the applicable related record, and then making it available from the task section of the Visit.

Assessment Indicator Definitions and Retail Store KPIs are primarily used for target-based compliance and KPI assessment processes. The In-Store Survey workflow instead relies on Salesforce Surveys, Survey Invitations, and the In-Store Survey Assessment Task Definition to deliver and execute the questionnaire during a retail visit.

Study Guide Topics:Data Setup - > Salesforce Surveys - > In-Store Survey - > Assessment Task Definition - > Survey Invitation

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

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

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

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

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

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

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

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

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

For a particular retail outlet, frequently ordered products can be modeled through Store Product records and marked as Favorite. Store Product establishes the product-to-store relationship and provides outlet-specific ordering attributes that streamline repetitive order capture.

Salesforce ' s Consumer Goods data model includes both Is Favorite and Default Order Quantity on Store Product. This allows a frequently purchased SKU to be marked as a preferred product for the store and assigned the quantity that is normally ordered.

Salesforce Trailhead demonstrates this configuration directly. Administrators or sales managers associate products with a store or In-Store Location, select the Favorite checkbox, and optionally enter a Default Order Quantity. During order capture, field representatives can sort or filter for favorite products, helping them quickly locate the outlet ' s commonly purchased items and replenish them using the expected quantities.

This approach is outlet-specific because the favorite designation resides on the relationship between the product and the Retail Store rather than globally on Product2. It therefore accommodates situations where the same product may be frequently purchased by one store but not another.

Saved carts and Account-level assortment records do not provide this same store-specific favorite-product mechanism.

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

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

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

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

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

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

A Delivery Task combined with SKU-level inventory tracking provides the appropriate operational model for tracking samples distributed through field representatives or distributors. Delivery Tasks represent delivery activities performed during store visits and are associated with Shipments that define which products must be delivered.

Within Salesforce inventory management, Product Item records represent quantities of specific products at inventory locations. A Product Item therefore provides the inventory relationship between the Product2 record and a location, with Quantity On Hand recording the current available quantity. For mobile inventory such as a distributor vehicle, Salesforce supports a Location configured as a mobile inventory location and allows Product Items to record the inventory carried in that vehicle.

Product Transfers associated with shipments identify the specific products and quantities being moved between locations. As delivery activities are performed, Salesforce can update inventory quantities accordingly. This provides operational traceability at the individual SKU level rather than merely reporting on shipping-document status.

Because the requirement is to monitor samples that remain available to distributors in the field, tracking the sample SKU ' s on-hand quantity together with the Delivery Task provides the most appropriate inventory-management approach.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Product Item - > Quantity On Hand - > SKU

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

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

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

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

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