Configurations for Delivery Documents
Typically, delivery documents are integrated from the external systems as orders and have the document type as delivery in the Consumer Goods Cloud desktop app. You can use the out-of-the-box templates (such as Order Template, Order Item Template, and Inventory Transaction Template) with relevant configurations for delivery, sellable return delivery, and damaged return delivery after you do the demo data upload in Static Resources. The templates are prepopulated with key fields to execute deliveries, and you don’t need to manually make these configurations. To customize these templates or create new delivery templates, configure these key fields on the Consumer Goods Cloud desktop app along with the relevant fields required for that template.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise and Unlimited Editions where Consumer Goods Cloud is enabled |
Delivery Document Configurations
Delivery documents have precalculated values and the tour drivers can't adjust the quantities without the required settings enabled.
Tour drivers can view a maximum of 10 delivery documents on the delivery documents card on the offline mobile app. Customize and implement an overview page for delivery documents in case your project has more than 10 delivery documents as part of a tour.
Here're the configuration needed for key fields along with relevant fields for delivery documents.
- In Order Template
- Document Type as Delivery
- Record Type as Order Entry
- Status as Active
- Current date, which falls within Valid From and Valid Thru dates
- The Document Transaction Type as Delivery Cash Invoice or Delivery Credit Invoice. The document transaction type controls whether the driver must collect cash as part of the release process.
- In Order Item Template
- Modify Quantity as No
- In Unit of Measure (UoM), units of measure with Order Ability as Yes. Only the units that are marked with Order Ability as Yes are shown for the products on All Items page for the tour driver.
- In Unit of Measure (UoM), configuration of the Sort field for various product units. Based on the Sort field in Unit of Measure, for a tour driver, UoMs for products shown in the product details section in delivery documents are sorted.
Prepopulation of Products in Delivery Documents
The configurations for prepopulation of order items in a delivery document are similar to prepopulation configurations for a retail order. To learn more about prepopulation conditions, see Order Management. The prepopulation conditions even apply for products shown on the Add Product page. The prepopulation conditions are applied when the driver opens a delivery document post sync on the Offline mobile app.
If an order item becomes invalid because of the settings in Order Template and Order Item Template, the driver is notified and the target quantity is set to zero. The driver can no longer change the quantity for the order item. To see all products from the ERP system, uncheck all filters options in Order Template. These include Closed Listing, and Sales Document Assortment Inventory Filter.
Adjust Product Quantities
Here're the configurations needed in Order Item Template to define the behavior of adjusting product quantities in delivery documents.
- To increase or decrease the quantity of the order item, set Modify Quantity as Yes.
- To not increase or not decrease the quantity of the order item, set Modify Quantity as No. The driver sees a warning message if they try to decrease or increase the quantity and the quantity is reset to the target quantity.
- To only increase the quantity of the order item, set Modify Quantity as Only Increase. The driver sees a warning message if they try to decrease the quantity below the target quantity and the quantity is reset to the target quantity.
- To only decrease the quantity of the order item, set Modify Quantity as Only Decrease. The driver sees a warning message if they try to increase the quantity above the target quantity and the quantity is reset to the target quantity.
- Consider Modification Reason field on Order Template for the display of the Reason Type field on the Items tab.
- Modification Reason field as Mandatory, Optional, or Not Required in the Order Item Template for the behavior of the Reason Type field on the Items tab.
Add and Scan Products in a Delivery Document
Here're the configuration needed for adding and scanning products in a delivery document:
- In Order Template, Barcode Scan Behavior
- In Order Item Template
- Scanning Increment that determines the increment in quantity post each scan
- Add Allowed as Yes
- UoM Scan Behavior
- If UoM Scan Behavior is set to Standard, the product scan applies to the UoM whose Is Order Unit is Yes.
- If UoM Scan Behavior is set to Current, the product scan applies to the unit of measure chosen in the UoM Scan Default Unit field.
- If UoM Scan Behavior is set to Barcode, the product scan applies to the exact unit of measure of a product.
- UoM Scan Default Unit
- For products to be added or scanned, along with required configuration, make sure the product
- Is part of a warehouse and is in the Active status
- Has at least one UoM with Is Order Unit as Yes
- Has State as Active Has Current Date between Delivery Valid From and Delivery Valid Thru Has Order Ability as Yes for the UoM
For delivery documents, the Add Products button is shown on the mobile app when the current item type (order item template) selected by the driver in settings has Add Allowed set as True in the desktop app.
Partial Payment, Discounts, and Header Changes
- To enable partial payment collection by the driver, set Partial Payment Allowed as Yes in Order Template
- To enable adding of delivery discounts by the driver, set, Allow Header Discount as Yes in Order Template. Do the required changes in the calculation schema for the application of header discount while price computation.
- To enable changing the customer's purchase number by the driver, set Purchase Number Update Allowed as Yes in Order Template.
Calculation and Release of Delivery Document
Recalculation Required setting in Order Template determines the calculation and release behavior of a delivery document. When this setting is set as
- Yes (With Notification): The app informs the driver that order calculation is outdated (yesterday or any prior date) and to calculate the price immediately. The driver can’t release the order without calculation if this option is selected.
- Yes: The app calculates the price each time before document release without informing the driver.
- No: The app skips calculation before document release.
- Always Calculate: The app calculates the price before document release without informing
the driver.
- If Edit Mode is selected for Compute Price in Order Template, the price is calculated automatically when the document is opened.
- If Button Mode is selected for Compute Price in Order Template, the Release button is disabled until the price is calculated.
Difference Between Always Calculate and Yes Options for Recalculation Required
The Yes option considers an order outdated when the calculation occurred yesterday or earlier. The Always Calculate option considers a calculation outdated when the driver moves out of the order without releasing it. The price is recalculated when the order is reopened, even on the same day.
Inventory Adjustments for Delivery Documents
After the release of the delivery document and sync, based on the confirmed delivery quantities, the truck inventory for each product is adjusted using withdrawal inventory transactions in the Salesforce org (Consumer Goods Cloud desktop app). The withdrawal inventory transactions are created corresponding to the inventory transactions that are created during the product checkout. For returns, the inventory transactions are positive addition entries and not withdrawal entries.
Inventory configurations needed for tracking inventory of delivery documents:
- In Order Template of the delivery document, use the same inventory reference (tour, user, or vehicle) as the product checkout document for the withdrawal transaction creation.
- In Order Item Template, for Order Item Inventory Transaction, use:
- Inventory Control Template with similar anchor combination (product with user, tour, or vehicle) as the Inventory Control Template for the product checkout document.
- Inventory Transaction Template having inventory references similar to the inventory reference of the order template.
- Active as Yes
- Used for Display as Yes
- Check Inventory Overdraft as Yes if you want validation to take place when the total delivery quantity of a product is more than the available quantity in the inventory during document release.
Inventory Overdraft for Delivery Documents
The app checks if the delivery quantities are more than the truck's available inventory. It does this by using the Check Inventory Overdraft setting in the Order Item template. If the setting is
- No: Drivers can exceed recorded inventory
- Yes: The app prevents exceeding inventory
- Warning: The app issues a warning, but drivers can still exceed recorded inventory. Inventory checks take place after quantity adjustments and during the release process to detect any shortages
Invoice ID Generation for Delivery Document
These configurations are needed to generate invoice ID for delivery cash or credit invoices.
- In Order Template
- Document Transaction Type set as Delivery Cash Invoice or Delivery Credit Invoice
- Id Generation as None
- Invoice Id generation set to Number generation at release time. The invoice ID generated is stored in the Invoice ID field on the Consumer Goods Cloud desktop app for the order.
You can set the structure of the invoice number by configuring the Invoice Number Definition field. Define the parts of the System Number Generator such as Init Counter (initial characters), Logical Unit (Device ID), and Counter (number generator). If the Invoice Number Definition isn’t present, the app uses the Mobile Number Definition for generating invoice number.

