
π Food Delivery & QSR Β· Flowchart
How a delivery platform onboards a new restaurant partner: documents, FSSAI licence, menu setup, photos and go-live.
Drawing diagramβ¦
Restaurant onboarding workflow: the restaurant signs up online. The platform verifies documents (FSSAI food licence, GST, PAN, bank account). Missing or invalid documents go back to the restaurant. The partner team digitises the menu, sets prices and commission, and schedules a food photoshoot. The restaurant gets tablet or app training, a test order is placed end to end, and the listing goes live.
flowchart TD
A[Restaurant signs up online] --> B[Upload FSSAI, GST, PAN, bank details]
B --> C{Documents valid?}
C -->|No| D[Ask for corrections] --> B
C -->|Yes| E[Sign partner agreement and commission]
E --> F[Digitise menu and prices]
F --> G[Food photoshoot]
G --> H[Partner app training]
H --> I[Place test order]
I --> J{Test order OK?}
J -->|No| K[Fix menu or settings] --> I
J -->|Yes| L[Go live on platform]A Swiggy/Zomato-style food delivery platform: customer, restaurant and rider apps, and the services that match orders, riders and payments.
Everything that happens between a customer tapping Place Order and the food arriving: payment, restaurant acceptance, rider assignment, pickup and delivery.
Every status of a food delivery order, from placed to delivered, including restaurant rejection, no rider and customer cancellation.
How orders from dine-in, takeaway and delivery apps flow through a restaurant kitchen display system to the pass and out.
A schema for a food delivery platform: restaurants, menus, items with add-ons, customers, orders, order items and riders.
How a food delivery platform scales for lunch and dinner peaks: pre-scaling, autoscaling services, sharded databases and a surge-protected dispatch.