Free Practice Questions for the Salesforce Consumer Goods Cloud AP-204 Exam (2026 Updated)

The Retail Store is a central object in Agentforce Consumer Goods and provides the operational context for Visits and store-level Orders. Salesforce requires the Visit object ' s Place field to reference a Retail Store in Consumer Goods implementations. Orders captured during field visits can also be tracked at the Retail Store level, allowing representatives to review orders from previous visits and efficiently reorder products.

Retail Store record access can also inherit sharing from the parent Account. Salesforce establishes a master-detail relationship between Retail Store and Account for this purpose. The default Retail Store sharing model can be configured as Controlled by Parent, allowing Account sharing rules to govern access to the associated Retail Store records. This eliminates the need to maintain an independent set of sharing rules for every store when the organization wants store access to follow Account access.

Promotions are not linked directly to Retail Stores; Salesforce uses Promotion Channel to create that relationship. Similarly, Direct Store Delivery uses Delivery Task, Shipment, and Product Transfer relationships rather than establishing the Retail Store-to-Shipment relationship described in the alternative.

Study Guide Topics:Data Setup - > Retail Store - > Visit - > Order - > Account Relationship - > Sharing Model

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

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 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

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

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

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

Einstein Visit Recommendations support Next Best Action strategies for determining which retail stores should be recommended for visits. Salesforce allows administrators to configure a recommendation strategy that evaluates relevant records and business criteria and produces prioritized visit recommendations for sales managers and field representatives.

A Next Best Action strategy can load relevant data, apply business rules, generate scores and reasons, and return recommendations that support store-visit planning. When a user creates a Visit Recommendation Request, the selected recommendation strategy is executed for the specified store and date context. Salesforce can also incorporate prediction information from Einstein Discovery when organizations require model-based recommendations.

The architecture separates recommendation logic from visit execution. Administrators can therefore create multiple strategies for different business priorities-for example, prioritizing stores with declining inventory, important upcoming promotions, or revenue opportunities. Salesforce documentation specifically supports both flow-based strategies and Next Best Action strategies for Einstein Visit Recommendations, enabling organizations to select the implementation approach that aligns with their planning logic and scalability requirements.

Accordingly, the ability to create Visit Recommendations through a Next Best Action Strategy is a standard supported configuration.

Study Guide Topics:Visit Planning - > Einstein Visit Recommendations - > Next Best Action - > Recommendation Strategies - > Visit Prioritization

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

In-Store Surveys are primarily designed to capture qualitative feedback from people associated with the retail location and to gather information about operational topics such as promotions, inventory requirements, and product quality.

Salesforce explicitly defines the In-Store Survey capability as a method for gathering feedback from store staff and customers about promotions, inventory needs, and product-quality conditions. The survey is executed as part of a Visit and can be incorporated into an Action Plan Template through an Assessment Task Definition of type In-Store Survey.

This model allows consumer goods organizations to collect information that is difficult to derive from purely transactional records. For example, store personnel can provide feedback about product availability, promotional effectiveness, packaging issues, shopper reactions, or changing inventory requirements. Surveys can also capture consumer or shopper opinions about products or promotional activities.

Inventory reconciliation is handled through inventory-management and Inventory Check processes rather than primarily through surveys. Point-of-sale information is normally imported or integrated as structured sales data for analytics rather than collected manually through an In-Store Survey.

Study Guide Topics:Visit Execution - > In-Store Survey - > Customer Feedback - > Promotions - > Inventory Requirements - > Product Quality

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

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

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

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

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

Flow-based tasks operate within the Visit and Assessment Task execution context and require the business context necessary to determine the applicable KPI configuration. The Retail Store KPI represents the target definition for an Assessment Indicator Definition and provides information such as store group, product, location category, target value, and other assessment context.

The flow also operates with the relevant Assessment Task and Visit identifiers so that automation can execute against the correct task instance and scheduled retail visit. This maintains the relationship between the reusable configuration and the transaction generated for an individual field visit.

Salesforce ' s broader assessment architecture reflects the same hierarchy: assigning an Action Plan Template to a Visit creates Assessment Tasks based on Assessment Task Definitions, while Retail Visit KPIs are generated using the applicable Retail Store KPI configuration.

This separation is essential. Retail Store KPI supplies expected business targets, Assessment Task provides the executable activity, and Visit supplies the store-engagement context in which the Flow runs.

Study Guide Topics:Visit Execution - > Flow-Based Tasks - > Retail Store KPI - > Assessment Task - > Visit Context

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

A Shipment must be associated with the Delivery Task so that the products scheduled for delivery can be presented during execution. In Salesforce Direct Store Delivery, the Delivery Task provides the activity context, while the Shipment defines the inventory movement that the field representative is expected to complete.

Salesforce specifies that after a Delivery Task is generated from an Action Plan Template assigned to a visit, the task must be associated with a Shipment. Products are then added to that Shipment through related Product Transfer records. Each Product Transfer identifies the product and quantity involved in the shipment.

This hierarchy is important because the Delivery Task does not independently maintain its own product list. Instead, it obtains the delivery-item context from its related shipment. A standalone Product record does not establish that the product is scheduled for a particular delivery, and a Retail Store KPI belongs to the Retail Execution assessment framework rather than inventory delivery processing.

Accordingly, if delivery items do not appear within the Delivery Task, the administrator should verify that the appropriate Shipment has been associated with the task and that the shipment contains the necessary Product Transfer records.

Study Guide Topics:Visit Execution - > Direct Store Delivery - > Delivery Task - > Shipment - > Product Transfer

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

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

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

The planogram Image record is associated with an In-Store Location. This relationship identifies the specific physical area of the retail store where the reference shelf arrangement applies.

Salesforce ' s Planogram Check prerequisites require administrators to create an Image record representing the planogram and then associate that Image with the appropriate In-Store Location. Typical In-Store Locations include primary shelves, aisles, checkout counters, endcaps, and other areas where products are displayed.

The association is important because a single Retail Store can contain many merchandising locations, each with a different expected layout. Linking the planogram directly to its In-Store Location enables Salesforce to present the correct reference image when a field representative performs a Planogram Check at that particular location.

The Retail Store KPI then references the corresponding In-Store Location Category, Assessment Indicator Definition, Image or planogram, product context, and KPI Type. During execution, the field representative can open Product Details within the Planogram Check and view both the products to be inspected and the associated reference image.

Therefore, the Image object containing the planogram is related to the In-Store Location where that planogram must be evaluated.

Study Guide Topics:Data Setup - > Planogram - > Image - > In-Store Location - > Planogram Check

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

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

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

In Consumer Goods Retail Execution, an Action Plan is associated with a Visit so that the required activities can be presented to the field representative during store execution. The Visit represents the scheduled interaction with the retail location, while the Action Plan provides the operational work that must be completed during that interaction.

Salesforce uses Action Plan Templates as reusable frameworks. When creating an Action Plan Template for Retail Execution, the administrator selects Visit as the Target Object. Tasks and flows are then added to the template, and the template is published. The same template can subsequently be associated with multiple visits, allowing standardized activities to be consistently deployed across stores and representatives.

Assessment Tasks are individual execution activities contained within the Action Plan rather than the primary object to which the overall plan is connected. Retail Store provides the physical store context, but execution is organized around the Visit. Action Plan Template defines the reusable structure, whereas the instantiated Action Plan operates within the specific Visit.

This design gives Salesforce a consistent mechanism for translating reusable task configurations into executable activities for individual scheduled store visits.

Study Guide Topics:Visit Planning - > Visit - > Action Plans - > Action Plan Templates - > Assessment Tasks

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

Users performing Delivery Tasks in the Consumer Goods base data model require access to the Lightning Direct Store Delivery functionality. Salesforce specifically identifies the Lightning Direct Store Delivery permission set license as the feature-specific entitlement required for Direct Store Delivery and van-sales functionality on the base data model.

Delivery Tasks involve objects and functionality beyond general Retail Execution. The delivery process can include Delivery Task, Shipment, Product Transfer, and Product Item records. Salesforce documentation also identifies Lightning Direct Store Delivery as the required user permission when creating Delivery Tasks in Action Plan Templates and when associating those tasks with Shipments.

If the tester does not have the required Direct Store Delivery access, delivery-related test cases can fail even when the underlying visits, action plans, shipments, and products have been configured correctly. General Retail Execution permissions alone do not provide the full set of Direct Store Delivery capabilities.

Geofencing is not the controlling authorization mechanism for Delivery Task access, and Retail Store KPI target values are unrelated to whether the tester can execute the Direct Store Delivery functionality.

Therefore, permission assignment should be verified early in delivery-task rollout testing.

Study Guide Topics:Platform - > Permissions - > Lightning Direct Store Delivery - > Delivery Tasks - > User Access

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

The Whitespace Analysis dashboard is specifically designed to identify opportunities to introduce additional products or product categories into stores. It analyzes sales information across products, categories, and retail locations to expose areas where a store has unused sales potential.

Salesforce describes whitespace as an opportunity where a product or category that performs successfully elsewhere is not currently generating sales in a particular store. The dashboard allows sales managers to evaluate revenue and quantity patterns, identify top-performing products, compare performance across stores, and determine where introducing a product could increase revenue. This makes it directly applicable to GreenTech ' s requirement to determine which new products may be suitable for a particular retail location.

The dashboard can answer questions such as which stores have the potential to sell top-selling products and whether a product or category can be introduced into additional stores. It also provides product-performance trends so the sales manager can evaluate whether a candidate product has demonstrated sufficiently strong performance elsewhere before expanding distribution.

Therefore, Whitespace Analysis provides the cross-selling and assortment-expansion insight needed for this scenario.

Study Guide Topics:Analytics - > CRM Analytics - > Whitespace Analysis - > Product Opportunities - > Store Sales Potential

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

The representative should edit the product tags so that the detected object is associated with the correct product classification. Accurate tagging is fundamental to maintaining reliable object-recognition results, particularly when two products have visually similar packaging.

Object detection identifies objects within an image and maps those detections to labels or product classes. If a competitor changes packaging so that its product resembles another SKU, the resulting classification can incorrectly increase the measured facings or share-of-shelf for the wrong product. Correcting the tag provides accurate classification information and helps maintain the integrity of the shelf measurement.

Salesforce ' s Einstein Vision architecture supports a feedback process for incorrectly classified objects. When an object-detection model misclassifies an image, corrected examples and labels can be added back to the dataset and used in subsequent training or retraining. Salesforce describes this feedback mechanism specifically as a way to improve models after misclassification.

Creating a new planogram would only alter the expected shelf arrangement and would not correct product identity. Turning competitor products around manipulates the physical merchandising environment rather than correcting the data. Canceling the task similarly fails to improve future recognition.

Study Guide Topics:Platform - > Einstein Object Detection - > Product Tags - > Classification - > Share-of-Shelf Accuracy

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

Custom assessment tasks use the Consumer Goods Custom Task Measures component to expose KPI information on the related object ' s record page. For this experience to appear, the administrator must both place the component on the relevant Lightning Record Page and ensure that the intended users receive that page through the correct page assignment.

Salesforce instructs administrators to open the custom or standard object ' s Lightning Record Page in Lightning App Builder, drag the Consumer Goods Custom Task Measures component onto the page, configure its properties, and save the page. If the component has not been added, users naturally see the object ' s standard record-page experience instead of the custom KPI interface.

Lightning Record Pages must also be activated for the appropriate application, record type, and user profile. Salesforce ' s page activation framework supports assignments by app, record type, and profile, allowing different users to receive different record-page experiences. If the custom task page is not assigned to the field representative ' s profile, Salesforce can display another assigned or standard record page instead.

These two configuration layers-component placement and profile/page assignment-are therefore required for the KPI component to appear.

Study Guide Topics:Platform - > Lightning App Builder - > Custom Tasks - > Consumer Goods Custom Task Measures - > Record Page Assignment

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

Salesforce Maps supports optimized visit sequencing and route guidance for field representatives. Agentforce Consumer Goods integrates mapping and routing capabilities so representatives can reduce travel time, determine an efficient order for store visits, and respond to changing road and traffic conditions throughout their working day.

Salesforce documents that Optimized Routes calculate the best visit sequence and display the day ' s stores and route on a map. The experience provides the sequence of visits, store addresses, real-time traffic information, route suggestions based on traffic, and the next customer location. Field representatives can use the Optimized Route sorting option in Scheduled Visits to organize their visits according to the calculated route.

Salesforce Maps Mobile also supports standard routes where Salesforce automatically optimizes the stop order. Representatives can add store locations to a route, optimize the sequence, and use mobile route controls while in the field.

This capability directly supports Consumer Goods visit planning because the objective is not simply to visualize locations but to determine an efficient sequence that minimizes travel and helps representatives reach the appropriate stores at the appropriate times.

Study Guide Topics:Visit Planning - > Salesforce Maps - > Optimized Routes - > Visit Sequence - > Real-Time Traffic

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

The Retail Store Group is a required field when configuring a Retail Store KPI. Retail Store KPIs establish target values for Assessment Indicator Definitions and provide the relationship between business metrics and the stores where those metrics must be evaluated. Salesforce defines these targets at the store-group level rather than directly at an individual retail store.

The Retail Store Group provides the organizational scope for the KPI. A single Retail Store Group can contain multiple Retail Stores with common operational characteristics, enabling administrators to apply consistent targets across those locations without creating separate KPI definitions for every store. Additional context can then be supplied through Product, Product Category, Promotion, Planogram, In-Store Location Category, and Assessment Indicator Definition fields.

Salesforce explicitly identifies Retail Store Group as required when creating a Retail Store KPI because KPIs cannot be defined directly at the individual-store level. Effective dates and KPI Type provide additional configuration context, but they do not replace the fundamental store-group association required to establish where the target applies.

Study Guide Topics:Data Setup - > Retail Store KPI - > Retail Store Group - > Assessment Indicator Definitions - > KPI Targets

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

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

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

Actual KPI values captured by a field representative during visit execution are stored in the Retail Visit KPI record. Salesforce separates KPI configuration from transactional execution data so that planned or target values remain distinct from values observed during individual visits.

The Retail Store KPI defines the target or expected value for a particular Assessment Indicator Definition. It provides the planning context, including the Retail Store Group, product or product category, In-Store Location Category, Custom Context, and target value. When an assessment task is generated for a visit, Salesforce creates the corresponding Retail Visit KPI records that represent the runtime measurements.

During execution, the field representative records the observed value. Salesforce stores fields such as the Actual Value, Target Value, Assessment Indicator Definition, Product, In-Store Location, and Custom Context on the Retail Visit KPI.

This architecture allows Salesforce to compare expected performance with actual field results across multiple visits. The custom object can supply the business context for a custom task, but it does not replace the Retail Visit KPI as the repository for actual assessment measurements.

Study Guide Topics:Data Setup - > Custom Tasks - > Retail Store KPI - > Retail Visit KPI - > Actual Values

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

Administrators review object-detection results through Detected Objects. Each object identified by the vision model is represented as a Detected Object record, providing administrators with the information required to examine how the model is performing against actual images.

A Detected Object record contains operational details about a particular detection, including the source image, the model responsible for identifying the object, the object ' s coordinates within the image, and the probability or confidence associated with the detection. Reviewing these records allows administrators to determine whether products are being identified correctly and to recognize patterns of incorrect classification or missed detections.

This review process is also important for continuous model improvement. When model output is inaccurate, additional representative examples can be incorporated into the training dataset and the model can be trained again. Salesforce ' s Einstein Vision architecture supports iterative model development because a dataset can generate multiple models, enabling implementers to compare model performance and refine training data over time.

Creating an unrelated custom object, enabling a feature, or using Einstein Bots does not provide the detection-result records required to assess object-recognition performance.

Study Guide Topics:Platform - > Einstein Vision - > Detected Objects - > Model Performance - > Model Refinement

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

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

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