Fleiko
Vertical Playbooks

Courier playbook

How Fleiko Dispatch is preset for courier / last-mile parcel delivery: terminology, defaults, proof, routing and the recommended way to add work.

What this preset sets up

Route, dispatch, track and prove every delivery. Work is called a delivery, done by a driver for a recipient; the account you bill is a client.

Default order: single stop. Service types offered: Standard, Same-day, Express, Scheduled, Multi-stop route, Return to sender, Redelivery.

The questions the setup wizard asks

Your answers shape recommendations and defaults only — never your plan or what you are entitled to — and you can change them any time in Dispatch → Settings → Operation profile.

Do you run from a depot?

Do drivers return to the depot after their route?

About how many deliveries per day?

Do you scan barcodes on packages?

How do you handle failed deliveries? (reattempt next day / return to sender / hold for pickup)

Routing and proof

Routing: route optimization is recommended; a depot / route start is recommended; routes return to the depot by default; time windows are prioritized.

Default proof: photo and signature. Proof is required to complete work. A failed stop needs a reason.

Failed stops can re-attempt automatically on the next business day (Dispatch → Settings → Re-attempts) and customers can reschedule from their tracking page.

Recommended way to add work

Import a spreadsheet. You can use any method your plan offers; the recommendation is a starting point.

Importing a spreadsheet? The Courier template expects: external_id, recipient_name, address_line1, city, postal_code (required); phone, email, delivery_window_start, delivery_window_end, barcode, package_count, client_reference, customer_notes (recommended).

Was this article helpful?

Have feedback? Share it with us →

Courier playbook | Fleiko Help