Promotion Channel
Explanation:
The Promotion Channel object provides the association between a Promotion and the business entity or retail destination to which that promotion applies.
A Promotion record defines the commercial activity itself, including the offer or merchandising initiative.
Salesforce then uses related records to establish the context of that promotion. Promotion Products identify individual products included in the promotion, while Promotion Product Categories establish category-level participation. Promotion Channel determines where the promotion is applicable.
Salesforce allows administrators to associate a Promotion Channel with a Retail Store, Retail Store Group, or Account. The administrator opens the relevant Promotion and adds the required retail destination through the Promotion Channel related list. An optional In-Store Location can also be specified when the promotional activity applies to a particular physical location inside the outlet-for example, a checkout counter or endcap.
This separation provides a flexible many-to-many structure: one promotion can apply to multiple retail destinations, and a store can participate in multiple promotions. During Visit Execution, Salesforce can then identify the promotions applicable to the store and expose them through Promotion Check activities.
Study Guide Topics:Data Setup - > Promotion - > Promotion Channel - > Retail Store - > Retail Store Group -
> Account

For custom tasks of type Other, the related object ' s Lightning Record Page must contain the Consumer Goods Custom Task Measures component and that page must be activated for the appropriate users. If either configuration is missing, users can receive the standard record-page experience instead of the KPI-specific interface.
Salesforce instructs administrators to create or modify the applicable custom-object record page in Lightning App Builder, drag the Consumer Goods Custom Task Measures component onto the page, configure its properties, and save the configuration. The component can display measures such as overall compliance, product-category compliance, and product compliance.
Lightning Record Pages are also subject to activation and assignment rules. An administrator can assign a record page according to app, record type, and user profile. Consequently, creating a page containing the custom KPI component is insufficient if the intended field user ' s profile is not assigned to that page.
Salesforce Mobile supports Lightning Record Pages and does not inherently force custom tasks to display only standard pages. Similarly, Lightning App Builder does support inclusion of Consumer Goods custom- task components.
Therefore, both component configuration on the related object ' s record page and correct record-page assignment to the user profile are required for the custom KPI experience to appear.
Study Guide Topics:Platform - > Lightning App Builder - > Custom Task Measures - > Record Pages - > Profile Assignment

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

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

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