Free Practice Questions for the Salesforce Consumer Goods Cloud Consumer-Goods-Cloud-Accredited-Professional Exam (2026 Updated)

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

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

The Promotion Channel object establishes the association between a Promotion and the retail destination where the promotion applies. Salesforce uses this intermediary object so that a single promotion can be distributed flexibly across different stores, store groups, or customer accounts.

In the Consumer Goods Retail Execution data model, Promotion represents the promotional activity itself. Promotion Channel is defined as the association of a Promotion with a Retail Store, Retail Store Group, or Account. This structure supports many-to-many promotional relationships without requiring the Promotion object to maintain a direct relationship with every individual retail location.

Product participation is modeled separately. Promotion Product associates a Promotion with an individual Product2 record, while Promotion Product Category connects a Promotion with a product category. This distinction allows Salesforce to separate two important questions: what merchandise is included in the promotion, and where the promotion is being executed.

During Promotion Check execution, these relationships enable Salesforce to identify the promotion applicable to the visited store and determine its associated product or category context.

Therefore, Promotion Channel is the standard object directly associated with Promotion for defining its retail distribution context.

Study Guide Topics:Data Setup - > Promotion - > Promotion Channel - > Promotion Product - > Retail Store

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

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

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

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 Store Performance Dashboard is designed for sales managers who need to evaluate store-level Retail Execution performance and identify locations requiring intervention. It provides consolidated analysis of store KPIs, compliance trends, visits, and business performance rather than limiting the analysis to one representative, product, or individual visit.

Salesforce describes the Store Performance dashboard as answering two fundamental questions: how stores are performing based on Retail Execution KPIs and which stores need attention. It also provides correlation analysis showing how Retail Execution KPIs affect store performance and how store visits influence compliance and revenue.

The underlying metrics include Average Store Compliance and changes in compliance over the selected comparison period. Salesforce calculates these measurements from Retail Visit KPI records, allowing managers to identify stores whose compliance is deteriorating relative to an earlier period. Metrics such as facing compliance, price compliance, share-of-shelf compliance, inventory compliance, and out-of-stock compliance can contribute to the analysis.

Consequently, the Store Performance Dashboard provides the appropriate management-level view for locating stores with declining Retail Execution KPI performance.

Study Guide Topics:Analytics - > Store Performance - > Retail Execution KPIs - > Compliance Trends - > Stores Needing Attention

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

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

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

Direct Store Delivery requires both the correct Action Plan configuration and the required user permissions. First, the administrator creates an Action Plan Template and adds a Delivery Task to it. When that template is assigned to a Visit, Salesforce creates the corresponding Delivery Task record for execution during the store visit.

Second, users who need to perform Direct Store Delivery functionality require the applicable Lightning Direct Store Delivery access. Salesforce identifies this permission set license for Direct Store Delivery capabilities in the Consumer Goods base data model. Delivery Tasks can then be associated with Shipments, which define the products to be delivered through related Product Transfer records.

Third, the Sales Manager requires access to Action Plans. Salesforce specifies the Action Plans permission set, or equivalent administrative privileges, for configuring and working with Action Plan Templates and Action Plans.

Assessment Indicator Definitions are used for KPI-based assessment activities and are not required to define the Delivery Task itself. The delivery process instead relies on the Delivery Task, Action Plan, Shipment, and Product Transfer architecture. Together, these three configuration steps provide the task definition, execution permission, and Action Plan access required for DSD operations.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Action Plan Template - > Permissions

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

Actual KPI values captured by a field representative during visit execution are stored in the Retail Visit KPI record. Salesforce separates KPI configuration from transactional execution data so that planned or target values remain distinct from values observed during individual visits.

The Retail Store KPI defines the target or expected value for a particular Assessment Indicator Definition. It provides the planning context, including the Retail Store Group, product or product category, In-Store Location Category, Custom Context, and target value. When an assessment task is generated for a visit, Salesforce creates the corresponding Retail Visit KPI records that represent the runtime measurements.

During execution, the field representative records the observed value. Salesforce stores fields such as the Actual Value, Target Value, Assessment Indicator Definition, Product, In-Store Location, and Custom Context on the Retail Visit KPI.

This architecture allows Salesforce to compare expected performance with actual field results across multiple visits. The custom object can supply the business context for a custom task, but it does not replace the Retail Visit KPI as the repository for actual assessment measurements.

Study Guide Topics:Data Setup - > Custom Tasks - > Retail Store KPI - > Retail Visit KPI - > Actual Values

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

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

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

The Retail Store Group is a required field when configuring a Retail Store KPI. Retail Store KPIs establish target values for Assessment Indicator Definitions and provide the relationship between business metrics and the stores where those metrics must be evaluated. Salesforce defines these targets at the store-group level rather than directly at an individual retail store.

The Retail Store Group provides the organizational scope for the KPI. A single Retail Store Group can contain multiple Retail Stores with common operational characteristics, enabling administrators to apply consistent targets across those locations without creating separate KPI definitions for every store. Additional context can then be supplied through Product, Product Category, Promotion, Planogram, In-Store Location Category, and Assessment Indicator Definition fields.

Salesforce explicitly identifies Retail Store Group as required when creating a Retail Store KPI because KPIs cannot be defined directly at the individual-store level. Effective dates and KPI Type provide additional configuration context, but they do not replace the fundamental store-group association required to establish where the target applies.

Study Guide Topics:Data Setup - > Retail Store KPI - > Retail Store Group - > Assessment Indicator Definitions - > KPI Targets

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

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

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

Einstein Vision product recognition is based on object detection, which identifies individual objects within an image and determines their position and classification. For shelf-analysis scenarios, the functionality depends on enabling the object-detection capability, providing suitable image data for recognition, and integrating that capability into the Planogram Check workflow used by field representatives.

Einstein Object Detection models rely on representative training images containing the objects that the system must recognize. Salesforce ' s object-detection architecture uses labeled images and object-location information to create a model capable of identifying multiple objects within a photograph. The quality and relevance of the image set are therefore important to reliable product recognition.

Within Consumer Goods Retail Execution, the operational component is the Planogram Check. Planogram assessment tasks provide the visit-level process through which representatives compare observed shelf conditions with the expected planogram and capture the resulting compliance information. Assessment Task Definitions define these repeatable field activities and allow them to be incorporated into Action Plan Templates used during visits.

The combination of object detection, appropriate image information, and a defined Planogram Check provides the technical and operational structure required for automated shelf-product detection in the implementation described.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Planogram Check - > Assessment Task Definition

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

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

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

A planogram is represented in Consumer Goods Retail Execution by an Image record. The Image object stores the reference representation of the expected product arrangement that a field representative uses during a Planogram Check.

Salesforce ' s Planogram Check prerequisites explicitly require administrators to create an Image record in the Image object representing the planogram at a store. The Image is then associated with the relevant In-Store Location, such as a primary shelf, aisle, checkout counter, or endcap. The Retail Store KPI subsequently references that Image through its Planogram field and combines it with the appropriate Assessment Indicator Definition, In-Store Location Category, Retail Store Group, and KPI Type.

When creating the Image record, the administrator can provide either the location URL of the image or upload an image file, specify the image category, activate the record, and make it available to field representatives.

During Planogram Check execution, representatives can open Product Details to review the expected reference image and compare the shelf arrangement against the merchandising standard.

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

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

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

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

The Promotion Channel object provides the association between a Promotion and the business entity or retail destination to which that promotion applies.

A Promotion record defines the commercial activity itself, including the offer or merchandising initiative. Salesforce then uses related records to establish the context of that promotion. Promotion Products identify individual products included in the promotion, while Promotion Product Categories establish category-level participation. Promotion Channel determines where the promotion is applicable.

Salesforce allows administrators to associate a Promotion Channel with a Retail Store, Retail Store Group, or Account. The administrator opens the relevant Promotion and adds the required retail destination through the Promotion Channel related list. An optional In-Store Location can also be specified when the promotional activity applies to a particular physical location inside the outlet-for example, a checkout counter or endcap.

This separation provides a flexible many-to-many structure: one promotion can apply to multiple retail destinations, and a store can participate in multiple promotions. During Visit Execution, Salesforce can then identify the promotions applicable to the store and expose them through Promotion Check activities.

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

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

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

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

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

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

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

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

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

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

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 Delivery Task is the Consumer Goods-specific object used to perform Direct Store Delivery activities during a retail-store visit. Salesforce describes DeliveryTask as a Retail Execution object representing delivery work performed at the store, whereas Shipment and ProductTransfer originate from inventory and Field Service capabilities.

Administrators add a Delivery Task to an Action Plan Template. When that template is applied to a Visit, Salesforce creates the Delivery Task record and associates it with the Visit. Users working with Delivery Tasks require the Direct Store Delivery permission capability.

The administrator then associates a Shipment with the Delivery Task to specify the inventory being delivered. Individual products and quantities are represented as Product Transfer records related to the Shipment. This architecture separates the Consumer Goods visit activity from the underlying inventory-transfer records.

During execution, the delivery representative selects the shipment, reviews its products, updates delivered quantities if required, and marks the products delivered. Completing the Delivery Task updates relevant inventory information.

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

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

The expected value for a planogram metric is defined on the Retail Store KPI. In the Consumer Goods Retail Execution data model, an Assessment Indicator Definition specifies what is measured, while the Retail Store KPI establishes the target or expected value against which the field representative ' s actual observation is evaluated.

When an administrator creates a Retail Store KPI, Salesforce requires selection of the relevant Assessment Indicator Definition and provides configuration fields for the Retail Store Group, In-Store Location Category, product or product category, planogram, KPI type, effective dates, and target value. Supported KPI types include Facing, Share of Shelf, Out of Stock, Inventory, Price, and Revenue. The administrator then defines the target value appropriate to the selected assessment indicator.

During visit execution, the representative captures an actual value. Salesforce stores visit-level actual information separately in the Retail Visit KPI and compares that value with the target defined in the Retail Store KPI. This separation enables consistent compliance measurement across multiple stores and visits while maintaining centrally managed targets.

Therefore, the Retail Store KPI is the configuration record responsible for holding the expected value used in planogram compliance measurement.

Study Guide Topics:Data Setup - > Retail Store KPI - > Assessment Indicator Definition - > Target Values - > Planogram Metrics

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

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

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

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

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

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

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

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

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

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

The 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

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

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

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

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

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