Fleiko
Vertical Playbooks

Auto parts playbook

How Fleiko Dispatch is preset for auto parts delivery: terminology, defaults, proof, routing and the recommended way to add work.

What this preset sets up

Urgent parts runs, shop handoffs and core returns in one dispatch board. Work is called a parts run, done by a driver for a counter; the account you bill is a branch.

Default order: single stop. Service types offered: Shop delivery, Branch transfer, Warehouse pickup, Urgent / VOR part, Core return, Customer return, Scheduled replenishment.

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 dispatch from a branch or warehouse? (branch / warehouse / both)

Do you run urgent / VOR parts?

Do you handle core returns?

Do you run recurring shop routes?

Do you use order or RO numbers?

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; vehicle capacity matching is recommended; time windows are prioritized.

Default proof: signature and barcode scan. Proof is required to complete work. The recipient's name is required. A failed stop needs a reason.

Failed runs are marked for manual handling — this preset never re-attempts automatically, and customers cannot reschedule from the tracking page.

Recommended way to add work

Add jobs manually. You can use any method your plan offers; the recommendation is a starting point.

Importing a spreadsheet? The Auto parts template expects: order_number, destination_shop, address, priority (required); source_branch, repair_order_number, part_count, counter_contact, phone, ready_time, required_by_time, core_return_required, client_reference (recommended).

Was this article helpful?

Have feedback? Share it with us →

Auto parts playbook | Fleiko Help