Delivery execution with delivery documents
Key Takeaway
A tour driver delivers the quantities a store preordered. The "Modify Quantity" setting on the Order Item Template (Yes, No, Only Increase, or Only Decrease) decides whether the driver can change those quantities.
Delivery documents let a tour driver deliver preordered products to a store from the inventory on the truck, during a visit in the Consumer Goods offline mobile app. During the visit, the driver hands over products, collects signatures and payment, releases a cash or credit invoice, and can pick up returns. When the visit is complete, the documents and inventory data sync back to Salesforce.
What delivery documents are
Delivery documents are typically integrated from external systems as orders. In the Agentforce Consumer Goods desktop app, they have the document type Delivery.
Each document carries precalculated values, so the driver delivers what was already ordered instead of building a new order.
A driver works with three kinds of documents: delivery, sellable return, and damaged return. Delivery documents drop off preordered products. Drivers use return documents to pick up sellable returns, damaged products, or empty containers.
Settings on the Order Template and the Order Item Template control many of the driver's options. After the demo data upload in Static Resources, out-of-the-box Order Template, Order Item Template, and Inventory Transaction Template records become available for delivery, sellable return delivery, and damaged return delivery. These templates come prepopulated with the key fields for deliveries.
Order items are prepopulated much like a retail order. Prepopulation happens when the driver opens the document after sync. If template settings make an item invalid, the app flags the item to the driver. The item's target quantity is set to zero and can't be changed. Prepopulation based on promotions or listing modules is not supported.