Deliveries

This content is for Spring ’26. Switch to the latest version for up-to-date documentation.

Deliveries link orders to what is physically shipped or returned. Records are usually created from telesales or back-office processes, or generated when an order is confirmed from the field.

Generate in telesales

Create and submit an Order.
Create a Delivery record (your org may use automation to build delivery lines from the order).
Plan the delivery on the relevant visit so the Delivery task appears for the driver.

Generate in Field

Create an Order.
On the order confirmation screen, choose Create delivery if offered so delivery lines are generated for your delivery object.
The visit task for delivery appears according to your visit template.

By default, new delivery lines often start in To be loaded (wording may vary). Typical statuses include loaded, delivered, not delivered, returned, to be collected, and similar labels your org configures.

The status controls which step of the flow a line appears in.

Delivery in the field

Sign in to Field.
Use Van Load (or equivalent console control) to pull scheduled deliveries into the day’s load and build the manifest.
After loading, open the Manifest control to review vehicle stock.

Arriving on site

Travel to the first stop and Check in.
Open the Delivery task.

The overview lists steps such as Unloading, Delivery, Collection, and Cancel Delivery, plus any Notes linked to the delivery.

Cancelling a delivery

You can cancel from multiple points in the flow using the delete/trash control in the header; confirm when prompted.

Delivery process steps

On Start delivery, the first required step opens.

Unloading typically shows:

Stocked - quantity currently on the van.
Unloaded - quantity you remove for this stop.

Unload line by line or use Check All where available. If quantities do not match expectations, the app may ask you to confirm on Continue.

After unload, the Delivery step shows unloaded versus expected delivered quantities and an Issues path to record short or damaged goods. Issue reasons are picklist values defined in Salesforce.

When returns or collections are due, follow the parallel Collection flow, then finish on the Review screen with an overview of delivered, rejected, and collected lines, plus recipient name and signature where required.

Document sharing at review may be disabled by default in mobile configuration; administrators sometimes pair review with a smart action so pricing on paperwork matches what was actually delivered.