Fleiko
Vertical Playbooks

Retail playbook

How Fleiko Dispatch is preset for retail & local distribution: terminology, defaults, proof, routing and the recommended way to add work.

What this preset sets up

Store-to-door, branch transfer and repeat local distribution. Work is called a delivery, done by a driver for a recipient; the account you bill is a store.

Default order: single stop. Service types offered: Store-to-door, Branch transfer, Wholesale delivery, Scheduled replenishment, Local e-commerce order, Return pickup, Exchange, Multi-stop route.

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.

Store-to-door or branch transfer? (store to door / branch transfer / both)

Do you run recurring routes?

Do you handle returns / exchanges?

Do you bill clients / accounts?

Do you track barcodes / package counts?

Routing and proof

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

Default proof: photo and signature. Proof is required to complete work. The recipient's name is required. 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 Retail template expects: order_number, recipient, delivery_address (required); store, account, delivery_window, package_count, barcode, phone, email, return_required, purchase_order_number (recommended).

Was this article helpful?

Have feedback? Share it with us →

Retail playbook | Fleiko Help