AP-204 Exam Dumps - Salesforce Accredited Agentforce Consumer Goods Professional

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 scalable Visit Recommendation strategy, Salesforce recommends implementing the selection logic through an Apex class. Visit Recommendations can use programmable logic to determine which stores should receive recommendations based on organization-specific criteria, and Apex is appropriate when the strategy must operate at business scale.

Salesforce allows an Apex class to select the stores for which Einstein should provide Visit Recommendations. The Apex method is exposed to automation by using @InvocableMethod, after which the class can be invoked from the Visit Recommendation strategy or from an autolaunched flow.

Salesforce also supports a Flow strategy for Visit Recommendations, but its documentation specifically notes that the flow-only method is not scalable for a business use case and recommends using Apex for scalable implementations. An Apex implementation gives developers greater control over bulk processing, complex filtering, reusable business logic, and Salesforce governor-limit considerations.

The strategy can return the recommended Store IDs and recommendation reasons so sales managers and field representatives understand both which stores should be visited and why those stores have been prioritized.

Workflow and Process Builder are not the architecture Salesforce defines for this Visit Recommendation capability.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Apex - > Invocable Methods - > Scalable Recommendation Strategies

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

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

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

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

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

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

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

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

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

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 Store Product represents the relationship between a Product2 record and a particular Retail Store or In-Store Location. This relationship supplies the store-specific product context required by several Retail Execution processes.

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

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

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

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

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

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

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

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

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