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 Consumer Goods notification framework provides the most appropriate user experience for communicating team information to field representatives while they continue performing their operational activities. Salesforce supports User Notifications specifically so supervisors and field personnel can communicate important information such as selling messages, business strategies, team updates, customer information, and other operational guidance.
Notifications are created as Task records with the User Notification record type and assigned to the relevant field representative. Users can review notifications and manage their read or unread status without requiring a separate Chatter navigation pattern.
The mobile user experience is optimized for this communication model. Salesforce ' s Advanced User Cockpit includes a dedicated Notifications card. On tablets, the card displays the five most recent unread notifications, enabling representatives to monitor messages while remaining within their normal field-work environment.
This approach avoids modifying every Consumer Goods page, consuming tablet space with a persistent messaging column, or misusing notes as person-to-person notifications. Using the native notification mechanism keeps communication integrated with the field representative ' s workflow while minimizing navigation disruption.
Study Guide Topics:Platform - > Notifications and Tasks - > User Notifications - > Mobile User Cockpit - > Field Collaboration

The Retail Store object includes retail-execution-specific attributes such as Delivery Method, Preferred Visit Hours, and Payment Method, which provide operational details required for managing field sales and distribution activities.
Delivery Method describes how orders are delivered to the store and supports logistics and Direct Store Delivery planning. Preferred Visit Hours identifies the periods during which field representatives should ideally visit the outlet and contributes to effective visit and route planning. Payment Method records the payment arrangement applicable to the retail location and supports store-specific commercial execution.
Salesforce ' s Retail Store data model explicitly includes fields corresponding to DeliveryMethod, PreferredVisitHoursText, and PaymentMethodId. It also contains attributes for delivery frequency, opening and closing times, recommended visit frequency, pricing strategy, primary contact, priority, and related retail- location information.
Shipping Address is a standard concept already available in the Account data model and therefore does not serve as a distinguishing Retail Store attribute. Operating Hours are handled through the broader operating- hours model and relationship rather than being one of the three specific Retail Store fields represented by the choices.
These store-specific attributes allow Agentforce Consumer Goods to distinguish the operational requirements of an individual physical outlet from its parent customer Account.
Study Guide Topics:Data Setup - > Retail Store - > Delivery Method - > Preferred Visit Hours - > Payment Method

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

An Action Plan Template intended for retail visit execution must be configured with Visit as its Target Object and then published before it can be associated with an individual Visit. The Target Object determines the Salesforce record type against which Action Plans created from the template can operate.
Salesforce ' s Consumer Goods configuration procedure specifies that administrators create an Action Plan Template, select Visit in the Target Object field, configure the appropriate Action Plan Type, add the required tasks and flows, and publish the template. A published template can subsequently be reused across multiple Visit records, which enables standardized store-execution processes.
To apply the template, a user opens the applicable Visit, selects New Plan from the Action Plan related section, and chooses the published Action Plan Template. Salesforce then presents the tasks contained in the template and creates the Action Plan for that specific visit. Only one Action Plan can be assigned to a Visit through this standard process.
This architecture separates reusable process design from visit-specific execution and ensures consistent field activities across stores.
Study Guide Topics:Visit Planning - > Action Plan Template - > Target Object - > Visit - > Publish Template