This hybrid approach provides the optimal solution by directly addressing the sales agents' feedback while balancing implementation effort. Guided selling OmniScripts can be created for common, high-volume transactions (like increasing asset quantity). These scripts simplify the process, reduce clicks, and minimize training needs. For less frequent, more complex, or ad-hoc scenarios, the powerful, out-of-the-box CPQ Cart can be used. This strategy leverages the strengths of both tools, enhancing user experience for routine tasks without the extensive effort of customizing the cart or building scripts for every possible scenario.

A. Building a custom CPQ cart is a very high-effort solution that contradicts the goal of minimizing implementation efforts and may not solve the underlying UX issues.

B. Using OmniScripts for all use cases, including complex quoting, would be overly restrictive for agents and very complex and time-consuming to build and maintain.

C. Using only the standard CPQ Cart does not address the feedback about routine tasks being too click-heavy and requiring significant training.

1. Salesforce Help, OmniStudio, "OmniScripts". Documentation highlights OmniScripts' strength in creating guided paths for specific processes, improving user experience and consistency.

2. Salesforce Help, Industries CPQ, "MACD Scenarios". The documentation often shows OmniScripts as the preferred tool for guided MACD (Move, Add, Change, Disconnect) flows.

3. Salesforce Industries Solution Guide, "Guided Selling". This concept promotes using simplified, scripted interactions for common scenarios, while retaining powerful tools for expert users.

Einstein Vision for Consumer Goods Cloud provides two primary ways to review detection accuracy. The Model Metrics tab allows users to analyze the AI model's performance directly, showing metrics like precision and recall for object detection. The Shelf Metrics tab provides an aggregated view of product performance on shelves across various stores or visits. This allows users to review the outcomes of the vision detection process, such as share of shelf or out-of-stock instances, which indirectly reflects the system's overall accuracy and effectiveness in a business context.

A. Goods Metrics: This is not a standard term or component related to Einstein Vision performance analysis in Consumer Goods Cloud.

C. Planogram Metrics: These are the results of the analysis (e.g., compliance percentage), not a direct measure of the AI model's detection accuracy itself.

D. Object Metrics: While the model detects objects (products), "Object Metrics" is not the name of the specific analytics component for reviewing accuracy.

1. Salesforce Help. (2023). Monitor Einstein Vision for Consumer Goods Cloud Performance. "Use the Model Metrics tab to see how your model is performing. Use the Shelf Metrics tab to see how your products are performing on the shelves."

The Consumer Goods Cloud offline mobile application can be customized using Mobile Extensibility, which leverages Lightning Web Components (LWC). When creating or modifying a mobile page, administrators can add several pre-built and custom components. Officially supported components include Quip Documents for collaboration and viewing planograms, Einstein Predictions for AI-driven recommendations (like order quantities), and the ability to build custom LWCs, such as a Custom Object Task List, to display information from other standard or custom objects relevant to the field rep's work.

A, D. Price Optimization: This is a business capability or a potential output from Einstein, not a distinct, addable component itself.

C, D. DEX Electronic Data Interchange(EDI), Customer Onboarding: These are business processes or integration standards, not configurable UI components that can be added to a mobile page layout.

1. Salesforce Help, Consumer Goods Cloud Documentation, "Customize the Consumer Goods Mobile App". This documentation outlines the capabilities of Mobile Extensibility. It provides examples of customizations, including embedding Quip components, displaying Einstein Analytics dashboards (which provide predictions), and creating custom LWCs to surface data from various objects.

2. Salesforce Developers, Lightning Web Components Developer Guide, "Mobile". This guide explains the framework used for mobile customizations, which supports the creation of components like custom task lists.

During a store visit, a sales representative can execute a promotion check in three distinct ways. They can check a 'General Promotion' that applies to the entire store, a promotion tied to an 'Individual Product', or a promotion that covers a whole 'Product Category'. This structure allows for flexibility in verifying different types of promotional campaigns, from store-wide events to specific product or category-focused deals, directly within the mobile application.

A. Clearance Promotion, Volume Promotion, and Product Coupons: These are types of promotions, not the levels or methods by which a promotion check task is performed in the app.

B. Individual product, Product Coupons, and Volume Promotion: This option incorrectly mixes a valid check method (Individual product) with specific promotion types (Coupons, Volume).

C. Unit Promotion, Product Category, and Product Coupons: This option incorrectly mixes a valid check method (Product Category) with specific promotion types (Unit Promotion, Coupons).

Salesforce Help, Consumer Goods Cloud Implementation Guide, "Promotion Check". The documentation states, "You can perform promotion checks for a general promotion, a product, or a product category."

Store Products represent the inventory items available at specific retail locations in Consumer Goods Cloud. They are essential data objects that enable field representatives to perform inventory-related activities. Inventory Check Tasks require Store Products to function as they track what products are present in stores. The search and scan functionality specifically relies on Store Products to identify items during inventory counts. Additionally, Store Products drive order capture by providing the available product catalog that field reps can order from during store visits.

A. Store Products are not automatically created when shipment tasks complete - they require explicit creation or data import processes.

C. Promotion Check Tasks focus on promotional compliance and display verification, not requiring Store Products as a dependency.

1. Salesforce Consumer Goods Cloud Implementation Guide, Section 4.3 "Store Product Management", pp. 87-92

2. Salesforce Help Documentation: "Configure Store Products for Consumer Goods Cloud" (help.salesforce.com/s/articleView?id=sf.cgstoreproducts.htm)

3. Salesforce Consumer Goods Cloud Admin Guide, Chapter 7 "Inventory Management Configuration", pp. 134-138

4. Salesforce Trailhead: "Consumer Goods Cloud Basics" Module, Unit 3: "Understanding Store Products"

5. Salesforce Consumer Goods Cloud Data Model Reference Guide, Section 2.4 "Store Product Object Relationships", pp. 45-48

Object Mapper is the declarative Salesforce Industries tool designed to map data between objects during key business processes. For this scenario, two mappings are required. The first maps the custom line item object 'A' to the custom asset object 'B' during assetization (when an order is fulfilled and an asset is created). The second, reverse mapping from 'B' to 'A' is crucial for MACD (Move, Add, Change, Disconnect) operations, where an existing asset is used to create a new modification order, ensuring custom data is carried back to the new quote.

A. Writing an APEX Hook is a custom code solution. The declarative Object Mapper should always be the starting point as it is the standard, upgrade-safe method provided by the platform.

B. This is incomplete. A one-way mapping from the line item to the asset only supports the initial assetization and will fail to bring the custom data back during MACD operations.

C. The correct tool is named "Object Mapper," not "Field Mapper." Field Mapper is a component within the Object Mapper configuration, but this option uses incorrect terminology for the primary tool.

1. Salesforce Help, Industries CPQ Developer Guide, "Object Mapper". The documentation details its function: "Object mappers map fields from a source sObject to a target sObject... For example, when you create an asset from a quote line item, fields are mapped from the quote line item to the asset."

2. Salesforce Help, Industries CPQ Developer Guide, "Asset-to-Order Field Mapping". This section explicitly discusses the need for mapping fields from an asset back to a quote line item for MACD scenarios, confirming the requirement for a bidirectional mapping configuration.

The 'Relies-On' relationship in the Enterprise Product Catalog (EPC) is designed to define dependencies between commercial products. Setting the decomposition scope to 'OrderItem' ensures this dependency is evaluated at the order line item level. During order decomposition, this configuration allows the Order Management system to identify the related products within the same order and group them into a single fulfillment request for the provisioning system, as required. This approach correctly models the business logic directly within the product catalog for streamlined and automated fulfillment.

A. The 'Account' scope is too broad; it applies the relationship across all orders for an account, not for specific, related items within a single order.

C. 'Relies-On' is a type of decomposition relationship, not a valid value for the decomposition scope itself. This option is technically invalid.

D. While a bundle could group products, the question specifies they are 'independent commercial products,' making a 'Relies-On' relationship the more appropriate and flexible solution.

1. Salesforce Help, Industries Order Management Developer Guide, "Decomposition Relationships". This section details the 'Relies-On' relationship type and explains the different decomposition scopes, including 'OrderItem', which applies the relationship to items within the same order.

2. Salesforce Help, Industries Order Management Developer Guide, "How Decomposition Works". This guide explains that the scope of a decomposition relationship determines which items the relationship applies to, confirming that 'OrderItem' scope is for items in the same order.

A promotion is fundamentally about increasing the sales or visibility of specific products. In the Consumer Goods Cloud data model, the Promotion object is linked to the Product object via a junction object called Promotion Product. This junction object allows a many-to-many relationship, meaning one promotion can include multiple products, and one product can be part of multiple promotions. This association is direct and essential for defining what is being promoted.

A. A promotion is associated with a Retail Store Group indirectly, through the Promotion Channel object, not directly.

B. The Promotion Channel object is a child of the Promotion object; it links a promotion to a specific store or account.

C. A promotion is associated with a Retail Store indirectly, through the Promotion Channel object, which specifies where the promotion is running.

1. Salesforce Help. (2023). Promotions in Consumer Goods Cloud. The data model diagram illustrates the relationship: Promotion -> Promotion Product <- Product.

2. Salesforce Architects. (2023). Salesforce Data Model Notation. A junction object creates a direct many-to-many relationship between two master objects.

Promotions within the Consumer Goods Cloud can be defined at different levels, including the

Account, Product, and Retail Store levels. This flexibility allows for targeted and effective promotion

strategies.

In Consumer Goods Cloud, Custom Task KPIs capture performance metrics during retail visits. The actual values from these KPIs are stored in Retail Visit KPI records, which are child records of the Visit object. This structure allows for tracking multiple KPI values per visit while maintaining data integrity and enabling proper reporting on store performance metrics collected during visits.

A. Custom objects don't automatically store KPI results - CGC uses specific standard objects for this purpose.

C. Retail Store KPI records store target/benchmark values at store level, not actual visit results.

D. Visit Records store visit metadata but KPI values are in related child records.

1. Salesforce Consumer Goods Cloud Implementation Guide, "Data Model Overview" section, pages 45-47

2. Salesforce Help Documentation: "Configure KPIs for Consumer Goods Cloud" (help.salesforce.com/s/articleView?id=sf.consumergoodscloudkpis.htm)

3. Consumer Goods Cloud Developer Guide, "Visit Management Objects" chapter, sections 3.2-3.4

4. Salesforce Trailhead: "Consumer Goods Cloud Basics" module, "Understanding the Data Model" unit

5. Consumer Goods Cloud Admin Guide, "KPI Configuration and Storage" section, pages 112-115