Delivery and collection in a mobile app

First-release scope

Collection needs a pickup location, readiness time and instructions. Delivery adds an address, service zone, fee, minimum order and recipient details. Do not offer slots when the kitchen is closed or already at capacity.

How to verify the result

Test boundary addresses, switching fulfilment after filling the basket and kitchen delays. Recalculate delivery on the server when the address changes. Paid and ready have different sources: payment confirmation does not mean the food is prepared.

What to prepare

Describe your current process, number of locations, required languages and main customer journey. Agree what belongs in the first release, what needs separate estimation and how you will accept the result.

First, define roles, the source of truth, payment and cancellation rules, and repeated actions. Test failures and network loss separately. A tap alone must never confirm a payment or appointment.

Plans and next steps

Start is €79/month and Business is €149/month. Launch is included in both plans. Complex features, migrations and third-party subscriptions are assessed separately after agreeing the brief.