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

A Retail Store can be associated with many Visit records, creating the required one-to-many relationship. Each Visit represents a particular scheduled or completed engagement between a field representative and a physical retail location, while the same store can naturally be visited repeatedly over time.

Salesforce describes the Visit object as tracking information about a field representative ' s visit to a Retail Store where retail activities are performed. Visit records hold information such as planned and actual start and end times, status, visitor, priority, and the related location.

For Consumer Goods implementations, the Visit ' s Place relationship identifies the Retail Store being visited. Salesforce Maps uses the same model when scheduling Consumer Goods visits: Visit records can derive their map location from the related Retail Store through Place ID, allowing Maps to position each Visit at the correct physical outlet.

Because representatives return to stores according to visit frequencies, merchandising schedules, promotions, deliveries, and sales requirements, a single Retail Store can accumulate multiple Visit records over its lifecycle. Each Visit remains a distinct transaction with its own Action Plans, tasks, KPIs, timing, and execution results.

Study Guide Topics:Data Setup - > Retail Store - > Visit - > Place Relationship - > Store Visit History

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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 Consumer Goods data model uses several related objects to connect a Promotion to its products, retail destinations, and compliance measurements.

Promotion Product is the junction between a Promotion and a Product. It identifies the specific products included in a promotional activity. Promotion Channel associates the Promotion with the commercial destination where it applies, such as a Retail Store, Retail Store Group, or Account.

Promotions also participate in the Retail Store KPI framework. When a KPI is created for a Promotion Check, the applicable Promotion can be selected on the Retail Store KPI together with the Assessment Indicator Definition, product or product category, Retail Store Group, and other contextual information. The Retail Store KPI therefore defines the expected promotional-compliance target.

When an Action Plan is applied to a Visit, Retail Visit KPI records capture the actual field observations against the applicable Retail Store KPI targets. This provides the visit-level measurement layer for promotion compliance.

Delivery Task and In-Store Location have different primary roles and do not form the complete promotion-related object set represented by the question.

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

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

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

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

Salesforce Maps Click2Create is designed for field representatives who discover prospects, customers, or service locations while working in a territory. It allows a user to create Salesforce records directly from a map location or Point of Interest without leaving the mapping experience.

When a representative identifies a restaurant or grocery outlet while traveling the route, the representative can select the relevant Point of Interest and invoke Click2Create. Salesforce can use available business and location information to populate fields on the new Salesforce record. Administrators can configure field sets and field mappings so data captured through Click2Create is directed into the appropriate fields on Lead, Account, or other supported records.

This approach is significantly more efficient than manually creating an unrelated record and initiating an email-based handoff. It also allows the newly created prospect to enter an established Salesforce onboarding process immediately. Opportunity and CPQ functionality generally applies after sufficient prospect and account qualification has occurred, while directing the customer to an external commerce site does not provide the controlled field-sales onboarding process described in the scenario.

Click2Create therefore provides the most appropriate integration between Salesforce Maps, field prospecting, and customer onboarding.

Study Guide Topics:Integrations - > Salesforce Maps - > Click2Create - > Points of Interest - > Customer Onboarding

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

The 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

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