AP-204 Questions and Answers

In-Store Survey execution depends on both an available Salesforce Survey and a corresponding Survey Invitation. The survey supplies the questionnaire that the field representative must complete, while the invitation creates the specific survey instance that becomes available in the context of the visit, retail store, or contact.

Salesforce ' s Consumer Goods configuration process requires the administrator to set up and activate the survey before it can be distributed. An Assessment Task Definition of type In-Store Survey is then incorporated into the Action Plan Template used for the visit. To expose the actual survey instance, Salesforce requires a Survey Invitation to be generated, commonly through the Retail Store ' s primary contact. The invitation is associated with the relevant records so that it appears within the survey task during visit execution.

Field representatives do not require permission to create surveys merely to respond to them. Survey authoring is an administrative function. Likewise, the standard process does not depend on creating a custom task definition or on a separate Retail Execution Survey Lightning Flow.

Therefore, absence of either the activated Survey or the related Survey Invitation prevents the survey from being available to the field representative.

Study Guide Topics:Visit Execution - > In-Store Survey - > Salesforce Surveys - > Survey Invitations - > Visit

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

The computer display unit should be represented as the business object being inspected, while its operational condition should be captured through an Assessment Task and associated KPI. This aligns with Salesforce ' s custom-task model for Retail Execution.

Salesforce supports custom tasks specifically for business scenarios that do not fit the standard Inventory Check, Promotion Check, Planogram Check, Order Creation, or Survey task types. Salesforce gives the example of capturing maintenance information for a refrigerator placed in a store, which is directly analogous to assessing the condition or functionality of a computer display unit.

For a custom assessment, administrators define Assessment Indicator Definitions representing the values that field representatives need to capture. The associated Retail Store KPI provides the target and business context, while the Retail Visit KPI stores the actual observation entered during execution. Custom Context can connect the KPI configuration to the relevant standard or custom business object.

An In-Store Survey is intended for collecting feedback from customers or store personnel and is not the appropriate mechanism for recording equipment-performance KPIs. Creating a dedicated task record type also does not replace the assessment/KPI architecture.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assets - > Assessment Indicators - > Retail Visit KPI

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

Inventory Check execution is scoped to the products associated with the specific Retail Store being visited. Salesforce Retail Execution uses this relationship to ensure that the field representative works only with products relevant to that outlet rather than searching the organization ' s entire Product2 catalog.

The Store Product object establishes the association between a product and a Retail Store or a specific In-Store Location. This relationship provides the product context used during store-level execution. Inventory Checks allow representatives to capture real-time information such as stock quantities, facings, share of shelf, product placement, and other assessment indicators for products sold in the store.

Product ownership or the identity of the user who created a Product record does not determine whether it should appear during an Inventory Check. Those attributes are unrelated to the commercial assortment or stocking relationship between a product and the retail location. Searching every product in the organization would also introduce irrelevant records and reduce mobile execution efficiency.

Therefore, product search during an Inventory Check is based on products associated with the Retail Store, ensuring the representative receives an operationally relevant product list for that visit.

Study Guide Topics:Visit Execution - > Inventory Check - > Store Product - > Retail Store - > Product Association

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

A custom task implemented with Flow is the appropriate architecture when the information to be captured does not fit the standard Inventory Check, Planogram Check, Promotion Check, Order Creation, or In-Store Survey task types. Salesforce specifically provides the Other assessment task type for custom business activities that require organization-specific data capture.

For asset compliance, an administrator can create an Assessment Indicator Definition with a Boolean data type to capture whether the asset meets the required compliance condition. Assessment Indicator Definitions support Number, Boolean, Date Time, Text, Decimal, and Picklist data types, making Boolean appropriate for a compliant/non-compliant assessment.

The custom task can be connected to the relevant business record through the Custom Context field of the Retail Store KPI. Salesforce supports standard or custom objects as custom-task context when the object supports activities. Flow can then evaluate the captured Boolean value and invoke the required follow-up automation, such as generating corrective actions or other downstream processes.

Using Flow instead of Apex follows Salesforce ' s declarative automation model and minimizes custom code while keeping the logic maintainable by administrators.

Study Guide Topics:Visit Execution - > Custom Tasks - > Assessment Indicator Definition - > Boolean KPI - > Flow Automation

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

An Einstein object-detection implementation depends on three essential elements: a suitable training dataset, a properly trained and evaluated model, and appropriate user access to the functionality.

The implementation begins by collecting representative images of the products or objects that must be detected. For object detection, the training images require labeled bounding boxes identifying the position and dimensions of each object. These examples are uploaded as a dataset and used by the training process to create an object-detection model.

The trained model should then be evaluated before deployment. Salesforce ' s model-training architecture reserves data for testing and provides model information that allows implementers to evaluate the model ' s detection performance. Reviewing model quality before exposing the capability to field representatives is essential because representative training data and adequate model performance directly affect detection results.

Finally, the field users who execute the functionality require the relevant access and permissions. Permissions are part of the Salesforce security model and determine whether users can access the required Consumer Goods and Einstein functionality.

OCR configuration and competitor-suppression datasets are not baseline requirements for this object-detection setup.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Dataset - > Model Training - > User Permissions

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

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

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

The Retail Visit KPI provides the visit-level relationship between the configured KPI framework and the Assessment Task that is executed in the field. Retail Store KPI defines expected values, while Retail Visit KPI captures the actual measurement generated during a specific Visit and Assessment Task.

Salesforce ' s Consumer Goods data model shows that Retail Visit KPI includes references to Assessment Task, Visit, Assessment Indicator Definition, Product, Product Category, In-Store Location, Promotion, Planogram, and other assessment context. It also contains the Target Value and Actual Value used to evaluate store performance.

The records are created as part of the assessment-task generation process. When an Action Plan Template is assigned to a Visit, Salesforce creates Assessment Tasks based on the included Assessment Task Definitions and creates Retail Visit KPIs based on the applicable Retail Store KPIs.

This design enables one centrally configured Retail Store KPI to drive repeated measurements across many store visits. Each individual visit receives its own Retail Visit KPI record, allowing the actual execution result to remain associated with the Assessment Task that produced it.

Study Guide Topics:Data Setup - > Retail Visit KPI - > Retail Store KPI - > Assessment Task - > Actual and Target Values

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

The Visit object should be used as the base object because the information that must be visualized-specifically the current status of today ' s visits-is stored on Visit records. Agentforce Consumer Goods uses the Visit object to track planned and completed retail-store engagements, including the responsible field representative, planned start and end times, retail location, and Visit Status.

Salesforce Maps supports Visit as a mappable object even though Visit itself does not contain a physical address. Salesforce Maps can inherit the location from the related Retail Store through the Visit ' s relationship to that store. A Marker Layer can then be constructed using Visit as its base object and filtered for the appropriate territory and date.

Salesforce Maps also supports dynamic marker formatting based on a field value. With the Varied Based On 1 Field configuration, the administrator can select Visit Status and assign different colors to different statuses. This allows an account manager to distinguish scheduled, in-progress, completed, or other visit states directly on the map without opening individual records.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Visit Object - > Marker Layers - > Visit Status

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

For a product-level Inventory Check, the product must be associated with the Retail Store where the assessment will be executed. Retail Execution needs a store-specific product relationship so Salesforce can determine which products are available for assessment when the field representative opens the Inventory Check.

Salesforce ' s Inventory Check prerequisites explicitly require administrators to associate Products with the Retail Store and associate the applicable In-Store Locations with that same Retail Store. The Retail Store must also belong to the Retail Store Group selected on the Retail Store KPI.

The Retail Store KPI then defines the assessment target by combining the Retail Store Group, applicable In-Store Location Category, Assessment Indicator Definition, and Product or Product Category. Salesforce separately specifies that the Product field is required on a Retail Store KPI when inventory-check tasks are configured for the store group.

The Store Product relationship provides the standard data-model mechanism for associating an individual Product2 SKU with a Retail Store or particular In-Store Location. A Promotion or Product Category relationship serves a different business purpose, while an Assortment defines a collection of products eligible for sale rather than replacing the required store-product association for Inventory Check execution.

Study Guide Topics:Data Setup - > Inventory Check - > Product - > Retail Store - > Store Product - > Retail Store KPI

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

The In-Store Survey experience uses contextually associated Survey Invitations rather than displaying every open survey invitation in the organization. The relevant contexts are the Visit, Retail Store, and Store Primary Contact.

Salesforce allows a Survey Invitation to be generated for a contact and associated with a Visit as the related record. When the Action Plan Template assigned to the visit contains an In-Store Survey task, this association makes the invitation available within the visit ' s survey execution context. Salesforce also supports generating the invitation from the Retail Store ' s primary contact and associating the survey with the applicable account or store context.

This design ensures that field representatives see surveys relevant to the specific retail engagement they are executing. Showing all open invitations or every invitation targeted to any contact or user would introduce unrelated survey records and would not preserve the visit-level execution context.

The relationship between the Survey, Survey Invitation, Primary Contact, Retail Store, and Visit therefore provides controlled survey distribution while ensuring that the correct questionnaire is available during the appropriate store visit.

Study Guide Topics:Visit Execution - > In-Store Survey - > Survey Invitation - > Visit - > Retail Store - > Primary Contact

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

An Inventory Check requires the Retail Store KPI to identify the applicable Retail Store Group and Assessment Indicator Definition. These fields establish where the measurement applies and exactly what the field representative must measure.

The Retail Store Group is fundamental because Salesforce defines Retail Store KPIs at the store-group level rather than directly at an individual store level. The group connects the KPI configuration to the Retail Stores that inherit and use the target during field execution.

The Assessment Indicator Definition identifies the metric to be captured-for example, stock quantity, availability, damaged-product count, or another inventory-related measurement. Salesforce ' s Inventory Check prerequisites explicitly require the Retail Store Group and an Assessment Indicator Definition for the applicable product or product category and In-Store Location Category.

Custom Context is associated with custom-task configurations and should remain empty for a standard Inventory Check. Inventory Count is not the configuration field that establishes the Retail Store KPI relationship. KPI Type can categorize the business meaning of an indicator, but the core Inventory Check configuration depends on the Retail Store Group and Assessment Indicator Definition.

Together, these records enable Salesforce to generate the corresponding Retail Visit KPIs when the Inventory Check is instantiated for a Visit.

Study Guide Topics:Data Setup - > Retail Store KPI - > Inventory Check - > Retail Store Group - > Assessment Indicator Definition

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

A planogram is represented in Consumer Goods Retail Execution by an Image record. The Image object stores the reference representation of the expected product arrangement that a field representative uses during a Planogram Check.

Salesforce ' s Planogram Check prerequisites explicitly require administrators to create an Image record in the Image object representing the planogram at a store. The Image is then associated with the relevant In-Store Location, such as a primary shelf, aisle, checkout counter, or endcap. The Retail Store KPI subsequently references that Image through its Planogram field and combines it with the appropriate Assessment Indicator Definition, In-Store Location Category, Retail Store Group, and KPI Type.

When creating the Image record, the administrator can provide either the location URL of the image or upload an image file, specify the image category, activate the record, and make it available to field representatives.

During Planogram Check execution, representatives can open Product Details to review the expected reference image and compare the shelf arrangement against the merchandising standard.

Study Guide Topics:Data Setup - > Planogram - > Image Object - > In-Store Location - > Retail Store KPI

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

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

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

The Inventory Check Lightning component is available for placement directly on an Assessment Task record page. Salesforce allows administrators to create or customize an Assessment Task Record Page through Lightning App Builder and add Consumer Goods-specific components that support field execution.

For the Assessment Task object, Salesforce documents the available components as Planogram List, In-Store Products, Promotion List, Inventory Check, and Consumer Goods Survey List. The Inventory Check component provides the dedicated interface for inventory-related assessment tasks and can expose information such as progress, summary information, location filtering, and assessment sections.

The wording of the other choices is important. Salesforce provides Planogram List, rather than a component named Planogram Check, and Promotion List, rather than a component named Promotion Check. Likewise, the supported product component is named In-Store Products, not In-Store Products Check.

After adding the Inventory Check component, the administrator can configure its component properties and activate the Lightning Record Page for the appropriate application, record type, and user profiles. This configuration provides field representatives with the required mobile or desktop execution interface when they open an inventory-related Assessment Task.

Study Guide Topics:Platform - > Lightning App Builder - > Assessment Task Record Page - > Inventory Check Component

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

Object Metrics and Model Metrics provide complementary mechanisms for evaluating the accuracy and performance of an Einstein object-detection implementation. Object-level metrics focus on how accurately individual object classes are being recognized, while model-level metrics provide an overall view of the trained model ' s predictive quality.

Salesforce ' s Einstein Vision model APIs expose model-performance information so administrators and developers can evaluate whether a trained model is sufficiently accurate for production use. Model metrics include measurements that quantify detection quality and allow implementers to identify weaknesses before relying on predictions operationally. Salesforce ' s Einstein Vision API specifically provides a Get Model Metrics operation for vision models, allowing performance information to be retrieved for an object-detection model.

Object-level analysis is equally important because overall accuracy can hide differences between individual classes. For example, a model may reliably identify one product but repeatedly confuse another product with visually similar packaging. Reviewing object-specific performance identifies those classification weaknesses and indicates where additional or improved training examples are required.

Together, Object Metrics and Model Metrics provide both granular and aggregate perspectives on detection accuracy, supporting systematic evaluation and refinement of product-recognition models.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Object Metrics - > Model Metrics - > Detection Accuracy

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

The frozen food aisle should be modeled as an In-Store Location. In-Store Location represents a specific physical area inside a retail store where products are displayed, stored, or evaluated. Salesforce identifies aisles, shelves, checkout counters, endcaps, and back rooms as typical examples.

Once the Frozen Food Aisle record is created, products can be associated with that location through Store Product. Store Product establishes the relationship among the Retail Store, Product2, and the applicable In-Store Location. This gives the Inventory Check sufficient context to tell the field representative exactly where the product should be inspected.

The In-Store Location can also be assigned an In-Store Location Category. Categories make it possible to group equivalent locations across multiple stores and configure Retail Store KPIs consistently for a store group. For example, all frozen-food aisles could share a category and common inventory-assessment rules.

Adding a custom picklist or task/store record type would duplicate functionality already provided by the standard Consumer Goods data model. Product2 identifies the commercial product; it does not by itself describe the product ' s physical placement within an individual store.

Study Guide Topics:Data Setup - > In-Store Location - > Store Product - > Inventory Check - > Store Layout

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

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

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

CRM Analytics for Agentforce Consumer Goods requires a minimum set of records before the Analytics for Consumer Goods app can be successfully created. Salesforce identifies the required data objects as Account, RetailStore, Visit, RetailVisitKpi, and Product2. An Order record is additionally required when the organization wants to include both Retail Execution and sales data.

The Retail Visit KPI requirement is particularly important because Retail Visit KPI records contain actual information captured during visits against the Assessment Indicator Definitions and targets configured for Retail Execution. These records provide the analytics layer with visit-level compliance and performance measurements that can be used in dashboards for store performance, product performance, territory analysis, and other Retail Execution insights.

Retail Visit KPI records are generated as part of the assessment-task process based on the underlying Retail Store KPI configuration. Salesforce therefore requires at least one RetailVisitKpi record in the organization when validating the data prerequisites for the CRM Analytics application.

The analytics setup process validates these minimum data requirements and displays a message when required records are missing.

Study Guide Topics:Analytics - > CRM Analytics for Agentforce Consumer Goods - > Data Requirements - > Retail Visit KPI - > Retail Execution Analytics

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

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

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

The Maximize Store Sales Einstein Discovery story is designed to identify factors that influence product sales and provide actionable insights that can help sales managers improve store performance.

Salesforce provides preconfigured Einstein Discovery stories within Analytics for Consumer Goods. The sales-focused story analyzes historical data to identify variables that have a positive or negative impact on product sales. Salesforce currently describes this capability as Maximize Store Product Sales, which provides insights into the factors affecting product sales and helps organizations devise strategies to increase sales at a store or store-group level.

Einstein Discovery uses the available analytics dataset to identify statistically relevant relationships and present explanations that business users can act upon. These insights can assist sales managers in understanding how factors such as product availability, assortment, store characteristics, and other operational conditions correlate with sales performance.

The Minimize Out-of-Stock story serves a different objective: it predicts products that are likely to run out of stock so representatives can mitigate availability problems. While out-of-stock conditions can affect revenue, the scenario specifically asks for broader insight into the factors affecting store sales, making the sales-maximization story the appropriate functionality.

Study Guide Topics:Analytics - > Einstein Discovery - > Maximize Store Sales - > Predictive Insights - > Sales Performance

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

An Einstein Vision object-detection model must be developed from a training dataset containing representative images of the objects that the model is expected to recognize. Model creation is therefore an implementation activity rather than something that occurs automatically from a single image or during ordinary field execution.

Salesforce ' s Einstein Vision development process begins by collecting representative training images. For object detection, each training example must also identify the relevant objects using bounding-box coordinates. The resulting examples are assembled into a dataset and submitted to the Einstein Vision training service. Training that dataset produces a model that can subsequently identify, classify, count, and locate corresponding objects in new images.

The quality and diversity of the base image set directly influence model performance. A sufficiently representative dataset must account for differences such as product orientation, lighting, shelf arrangement, packaging appearance, and surrounding objects. Salesforce also allows multiple models to be trained from evolving datasets so their performance can be evaluated and refined.

Consequently, the model is deliberately built during implementation from a prepared base dataset before it is incorporated into the field-execution process.

Study Guide Topics:Platform - > Einstein Vision - > Object Detection - > Training Dataset - > Model Creation

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

Retail Execution Lightning Plus provides access to Consumer Goods Retail Execution functionality for strategic-sales users and is the applicable entitlement for users working with Visit Recommendation capabilities in the Retail Execution environment.

Salesforce identifies Lightning Retail Execution Plus PSL as the Consumer Goods Retail Execution permission set license for strategic-sales users. Retail Execution permission set licenses enable Consumer Goods functionality that is not included automatically in the user ' s standard Salesforce license.

Einstein Visit Recommendations allow sales managers and field representatives to request recommended stores for future visits. Administrators can configure either a Flow strategy or a Next Best Action strategy. When users request recommendations, they can select the strategy that best corresponds to their business requirement, and Salesforce returns the stores that should be considered together with the associated recommendation reasons.

Tableau CRM Plus User and Tableau CRM Plus Admin permissions apply to CRM Analytics capabilities and are not the Retail Execution entitlement represented by this question.

The Retail Execution access model can also include Action Plans and Industries Visit permissions where users need the associated visit and task functionality.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Lightning Retail Execution Plus - > Recommendation Strategies - > User Access

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

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

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

A Delivery Task combined with SKU-level inventory tracking provides the appropriate operational model for tracking samples distributed through field representatives or distributors. Delivery Tasks represent delivery activities performed during store visits and are associated with Shipments that define which products must be delivered.

Within Salesforce inventory management, Product Item records represent quantities of specific products at inventory locations. A Product Item therefore provides the inventory relationship between the Product2 record and a location, with Quantity On Hand recording the current available quantity. For mobile inventory such as a distributor vehicle, Salesforce supports a Location configured as a mobile inventory location and allows Product Items to record the inventory carried in that vehicle.

Product Transfers associated with shipments identify the specific products and quantities being moved between locations. As delivery activities are performed, Salesforce can update inventory quantities accordingly. This provides operational traceability at the individual SKU level rather than merely reporting on shipping-document status.

Because the requirement is to monitor samples that remain available to distributors in the field, tracking the sample SKU ' s on-hand quantity together with the Delivery Task provides the most appropriate inventory-management approach.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Product Item - > Quantity On Hand - > SKU

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