---
title: "Follow the Transport Workflow"
description: "The normal planned flow starts with a submitted business request and finishes with recorded execution and any required stock or commercial follow-up."
space: "Vuna Transport"
url: "https://docs.navari.co.ke/vuna-transport/introduction/the-end-to-end-transport-flow"
updated: "2026-11-09"
---

The normal planned flow starts with a submitted business request and finishes with recorded execution and any required stock or commercial follow-up.

```text
Submitted source document
        ↓
Transport Demand → selected quantities → Transport Load
        ↓
Vehicle Allocation + required pre-trip stock documents
        ↓
Delivery Trip → stop/task → Proof of Delivery or Collection
        ↓
Completed work, or variance requiring receiving/returns follow-up
```

The exact stock-document sequence depends on the movement. Use the appropriate path below rather than applying one customer-delivery sequence to every job.

## Deliver to a customer

Sales Order → Transport Demand → Transport Load → submitted Delivery Notes and Vehicle Allocation → Delivery Trip → customer Proof of Delivery.

**Vehicle Allocation Timing** controls whether initial allocation happens before or after Delivery Notes. Its default is **After Delivery Notes**. In both sequences, customer Delivery Notes must be submitted before the trip is prepared. Pick Lists support warehouse picking when used; they do not replace submitted Delivery Notes.

## Transfer company stock to a depot

Material Request of type **Material Transfer** → Transport Demand → Transport Load → Vehicle Allocation → submitted **Stock Entry (Add to Transit)** → Delivery Trip → receipt at the depot → **End Transit** stock posting.

Loading is dealt with before the trip. The driver normally records the receiving task at the destination, not another pickup proof at the loading warehouse. A correctly linked warehouse-posted End Transit can confirm the task without a driver POD.

## Collect purchases from a supplier

Company-arranged Purchase Order → Transport Demand → Transport Load and Vehicle Allocation when planning is required → Delivery Trip → supplier collection proof → Purchase Receipt into the vehicle warehouse when driver receiving is enabled, or receiving by authorised purchasing staff.

Do not create an Add-to-Transit transfer from your own warehouse before collecting a purchase that is not yet in your inventory. After a vehicle Purchase Receipt, movement to the final warehouse uses a normal Material Transfer, not End Transit.

## Pick up an approved return

Return Request → matching trip pickup assignment, or planned demand/load for supported depot returns → collection proof → the correct receiving stock document → Return Inspection → stock transfer and commercial follow-up as applicable.

Supplier demands with planning switched off can be assigned directly to an active trip. This is an explicit assignment path, not an automatic bypass of required planning. See [supplier collections](/vuna-transport/operations/supplier-collections).

> [Diagram: Side-by-side customer delivery, depot transfer, supplier collection and return pickup paths, highlighting which stock document posts at each handover]

Partial quantities leave work to review. A terminal task with variance is not a claim that all original demand was fulfilled. Use [Monitor Daily Transport Work](/vuna-transport/review/monitoring) and [Recover from Blocked Work](/vuna-transport/help/recovery) before closing the day.