What this preset sets up
Ready times, delivery windows and contactless completion for local food operations. Work is called an order, done by a driver for a customer; the account you bill is a merchant.
Default order: single stop. Service types offered: Restaurant delivery, Catering delivery, Grocery delivery, Scheduled batch, Corporate meal delivery, Event drop-off, Contactless delivery.
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.
Merchant pickup or your own fleet? (merchant pickup / own fleet / both)
Do you track ready-by and deliver-by times?
Do you offer contactless deliveries?
Do you do catering with setup?
Which handling categories do you use? (hot / cold / frozen / mixed)
Routing and proof
Routing: route optimization is recommended; vehicle capacity matching is recommended; time windows are prioritized.
Default proof: contactless drop and photo. Proof is required to complete work. 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
Connect via API. You can use any method your plan offers; the recommendation is a starting point.
Importing a spreadsheet? The Food & catering template expects: order_number, merchant_name, delivery_address, ready_by, deliver_by (required); pickup_address, customer_phone, customer_email, order_count, handling_requirement, contactless, setup_required, merchant_account (recommended).
What Fleiko does and does not do here
Fleiko does not claim to be food safety compliant, temperature-controlled certified; it records what your team declares and captures.