Pass the Salesforce Consumer Goods Cloud AP-204 Questions and answers with ExamsMirror

Users performing Consumer Goods Retail Execution activities require the appropriate combination of Retail Execution, Industries Visit, and Action Plans permissions.

Lightning Retail Execution Plus provides access to Consumer Goods Retail Execution capabilities for strategic-sales users. Salesforce lists Lightning Retail Execution Plus among the available Retail Execution permission set licenses used to enable Consumer Goods features.

The Industries Visit permission provides access to industry-specific Visit functionality. Visits are fundamental to Retail Execution because they represent scheduled interactions between field representatives and Retail Stores. The permission set supplies access to objects involved in visit execution, including Visit, Assessment Task, Assessment Task Definition, Action Plan, Action Plan Template, and related records.

The Action Plans permission enables users to access and manage Action Plans. Action Plan Templates define the repeatable activities that are subsequently associated with Visits and executed by field representatives.

Salesforce ' s setup instructions direct administrators to assign a Retail Execution permission set together with Action Plans and Industries Visit to users who require access to visits, tasks, and related Retail Execution capabilities. Sales Quotations addresses a different commercial process.

Study Guide Topics:Platform - > Permission Sets - > Lightning Retail Execution Plus - > Industries Visit - > Action Plans

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

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

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

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

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

For a Visit Recommendation implementation that must scale to production business volumes, the recommendation-selection logic should be implemented using an Apex class.

Salesforce supports Flow-based strategies for Einstein Visit Recommendations, but its documentation explicitly states that the flow-only approach is not scalable for a business use case and recommends using Apex for scalable Visit Recommendation processing.

With Apex, a developer can implement the business logic needed to identify the Retail Stores for which Einstein should generate recommendations. The Apex method can be exposed through an invocable action and incorporated into the recommendation strategy or an associated flow. This architecture provides more control over bulk processing, complex filtering, governor-limit management, reusable logic, and enterprise-scale execution.

Salesforce ' s Visit Recommendation setup documentation supports both Flow and Apex approaches. It specifically provides an Apex-based option to select the list of stores for which recommendations should be generated and then use that Apex action within the recommendation framework.

Workflow Rules and Process Builder are not the supported architectural mechanisms for implementing scalable Einstein Visit Recommendation strategies.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Scalability - > Recommendation Strategy

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

The consultant should create an In-Store Location named Frozen Food Aisle. In-Store Locations represent distinct physical areas within a Retail Store and provide the location context required by Retail Execution tasks such as Inventory Checks and Planogram Checks.

Salesforce uses In-Store Location records to model store areas including shelves, aisles, checkout counters, backrooms, and promotional displays. Each location can be associated with an In-Store Location Category so equivalent physical areas across stores can be grouped and managed consistently. Salesforce ' s Retail Execution guidance demonstrates creating specific In-Store Location records directly from the Retail Store record and assigning appropriate location types and categories.

Products can then be associated with the relevant store location through Store Product. During an Inventory Check, the representative can select the appropriate In-Store Location and capture product availability, facings, share of shelf, or out-of-stock information for products located there.

Product2 represents the commercial SKU and does not identify its physical placement inside an individual outlet. Creating custom picklists or record types would duplicate the standard store-location model.

Study Guide Topics:Data Setup - > In-Store Location - > Inventory Check - > Store Product - > Store Layout

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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