Salesforce Updated AP-204 Exam Questions and Answers by henri

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

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

Salesforce Maps Mobile Check In provides the field representative with the appropriate mechanism for recording arrival information at a customer or retail location. Salesforce Maps supports field activity tracking directly from map markers, routes, and schedules, enabling representatives to check in when they arrive and check out after the visit is complete.

Salesforce Maps Check In can capture the representative ' s location, check-in time, visit duration, and other activity information. Location information can be recorded as latitude and longitude, allowing the organization to verify where the representative was when the check-in occurred. Administrators can also configure a verification distance, requiring users to be within a defined distance of the record ' s geolocation before a check-in is accepted.

For a merchandiser performing an Inventory Check, this creates a reliable operational record of when the representative arrived at the store and the geographic coordinates associated with that event. The feature is integrated into the Salesforce Maps mobile experience and is designed specifically for field-based visit activity.

Einstein Vision performs image-analysis functions and does not provide visit check-in functionality. A generic location picker likewise does not provide the complete Maps activity-logging workflow.

Study Guide Topics:Visit Execution - > Salesforce Maps - > Mobile Check In - > Geolocation - > Visit Activity

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

Endcaps should be represented as In-Store Locations and In-Store Location Categories, with Retail Store KPIs specifically configured for that merchandising context. This allows NTO to measure endcap performance independently from primary shelves, checkout counters, backrooms, or other store areas.

Salesforce ' s Agentforce Consumer Goods data model supports In-Store Location categories precisely for this purpose. Similar physical locations across stores can be categorized-for example, Endcap Displays-and Retail Store KPIs can then use that category to define the measurements and targets applicable to those locations.

Salesforce ' s own Retail Execution configuration examples demonstrate creating Retail Store KPIs specifically for the Endcap Displays category. A promotion-compliance KPI can include the Retail Store Group, Endcap Displays as the In-Store Location Category, the relevant Assessment Indicator Definition, Promotion, Product Category, and a Boolean target value. This allows field representatives to capture endcap-specific performance during visits while managers analyze the resulting Retail Visit KPI data separately.

Creating Retail Store record types or unrelated custom objects would not provide the appropriate KPI granularity. Dedicated KPI configuration for the endcap context uses the standard Consumer Goods data model and provides targeted merchandising measurement.

Study Guide Topics:Data Setup - > In-Store Locations - > Endcap Displays - > Retail Store KPI - > Assessment Indicators

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

The Retail Store object should be used as the base object because Retail Stores represent the physical customer locations that field representatives need to visit. Salesforce Maps requires a mappable business object containing, or resolving to, geographic information so that records can be plotted, filtered, routed, and scheduled.

In Consumer Goods visit planning, Retail Store records supply this geographic and operational context. Store records contain the address and related location information required by Salesforce Maps. Salesforce states that the address entered when creating a Retail Store provides the location coordinates used by Salesforce Maps and also appears in the representative ' s visit list.

Salesforce ' s Consumer Goods optimized-routing process likewise uses Retail Store as the Maps base object. The planner selects relevant stores, applies business filters, identifies representatives and planning dates, and allows Maps to generate optimized visit schedules and routes.

The Visit subsequently represents the scheduled engagement with the selected Retail Store, but the physical destination being routed is the Retail Store itself. Account represents the broader customer organization and may encompass several stores, while Contact represents an individual person. Warehouse serves a different inventory and logistics purpose.

Using Retail Store therefore gives Salesforce Maps the correct geographic granularity for store-level visit planning and route optimization.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Base Object - > Retail Store - > Route Planning

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