Solutions · Cloud kitchens
A direct ordering channel for cloud kitchens that live on delivery apps
A cloud kitchen has no shopfront, no walk-ins and no dining room. Marketplaces are how people find you, and that will not change on day one. What can change is where the second order goes. Tuckly gives you an online ordering system of your own to point repeat customers at, with delivery through Porter where it operates or through your own riders.
- Delivery-only ordering, with pickup if you want it
- Porter rider requests where Porter operates
- A packaging insert QR that opens your own menu
- No platform commission on direct reorders
Order #1047 · Delivery
3 items · $24 · Paid online
Fulfil with
- Order placed 12:31
- Accepted by kitchen 12:32
- Rider assigned 12:44
- Picked up 12:58
- Delivered —
Illustrative view.
First order, second order
The second order is where the margin is
The first order from a new customer comes through a marketplace. That is fine. You paid the commission to be found, the same way you would pay for an advert.
Say the order was ₹450. At a marketplace commission of 25% (rates vary by platform and contract; this is for the arithmetic), ₹112.50 went to the marketplace. The customer liked the food.
Now suppose the second order comes through your own site because there was a card in the bag. The same ₹450 order carries no Tuckly commission. Your payment gateway charges its fee, around 2% in India at published rates, so ₹9. Delivery costs whatever the rider costs you: a Porter trip fee for that distance, or your own rider's time. If you charge the customer a delivery fee, that offsets it. Assume ₹70 for the trip and no delivery fee charged: the direct order costs ₹79 to fulfil against ₹112.50 in commission, and the customer's details are on your order, not the app's.
The gap is not dramatic on one order. On every repeat order from every customer who liked the food, it is the difference between a kitchen that is working for the apps and one that is working for itself.
Figures are illustrative and chosen to show the arithmetic, not to predict your results.
-
Built for a kitchen with no front door
Delivery is the default order type. Pickup can be switched on for customers nearby who would rather collect; dine-in stays off.
-
The insert card
A QR code in every marketplace bag opens your own menu. It is the cheapest marketing a cloud kitchen will ever do, and the generator makes one in a minute.
-
Riders without a fleet
Request a Porter rider for a direct order in the cities Porter serves, assign one of your own, or mix per order. See delivery management.
-
The customer stays yours
Name, number, address and order history sit on your orders. A marketplace never shares those.
Moving repeat customers across, one bag at a time
This is a slow process by design. Each step is small, and the insert card does most of the work.
- 1
Rebuild the menu on your own page
The same dishes, your own photos and names, with variants and add-ons priced the way you want rather than the way the app's template allows. Marketplace menus do not sync into Tuckly, so this is a manual job; a cloud kitchen menu usually takes an afternoon. The menu builder page covers the structure.
- 2
Set the delivery area and charge
Draw the area you will deliver to and set what the customer pays. Keep the area close to begin with: a direct order that arrives cold undoes the point of the card in the bag.
- 3
Print the insert
A card with the QR code, the web address in plain text for people who do not scan, and one honest reason to use it: a dish that is only on the direct menu, a lower delivery charge, or simply 'order direct and we keep more of what you pay'.
- 4
Keep the order screen in the kitchen
Direct orders alert on the same tablet that shows the marketplace tablets, or a phone on the pass. Accept with a time, cook, request a rider. The order management page explains the flow.
- 5
Watch for the first repeat
The first customer who orders a second time through your site is the proof the loop works. Note how they found the link and do more of that.
Delivery without a fleet of your own
Most cloud kitchens have no riders, because the marketplaces supply them. For a direct order you need another answer.
Where Porter operates, you request a rider for the order. The Porter page is specific about which parts of that workflow are live today and which are still being validated, including automated booking and live tracking. If you have a rider or two on shift, assign them instead. Fulfilment is chosen per order, so a far order can go to Porter while a nearby one goes to your own rider.
- Porter rider requests in the cities Porter serves
- Own riders assigned per order
- Pickup as an option for customers who are close
- Delivery charge set by you, per area
Order #1047 · Delivery
3 items · $24 · Paid online
Fulfil with
- Order placed 12:31
- Accepted by kitchen 12:32
- Rider assigned 12:44
- Picked up 12:58
- Delivered —
Where a direct order differs for a cloud kitchen
Not a case for leaving the marketplaces. A case for knowing which channel does what.
| Question | Marketplace order | Order from your own site |
|---|---|---|
| Who finds you | The marketplace's users, browsing | People who already ordered once, or saw your link |
| Commission | A percentage set by the marketplace | None from Tuckly; payment gateway fee only |
| Who delivers | The marketplace's riders | Porter where available, your own riders, or pickup |
| Who holds the customer | The marketplace | You, on the order |
| Menu control | The app's template: names, photos, option structure | Your names, your photos, variants and add-ons as you want them |
| Packaging and branding | Whatever the rider carries | Yours, with the card for the next order |
Marketplace terms vary by platform, city and agreement. The comparison page goes through the trade-offs in more detail.
What a cloud kitchen uses most
-
Delivery management
Porter, own riders, pickup. Chosen per order, with the status visible to the kitchen.
-
Order management
Direct orders on one screen with prep times, notes and the customer's contact details.
-
Menu builder
Your photos, your names, variants and add-ons priced your way.
-
POS integrations
If you run Petpooja or UrbanPiper, check the status before assuming orders will flow.
Making a direct channel work when nobody walks past your door
A restaurant with a shopfront can put a QR code in the window. A cloud kitchen has an industrial unit with a roller door. Everything about the direct channel has to be done deliberately, because nothing about the premises will do it for you.
The card in the bag is the whole strategy
Every marketplace order you send out is a bag going to someone who has just chosen your food. That bag is the only moment you have their attention without paying for it. A card with a QR code, the web address written out, and a single sentence is enough. The sentence should be true and specific: “Order direct and the delivery charge is ₹X less”, or “The lamb biryani is only on our own menu”, or simply “Ordering direct means we keep more of what you pay”. Discount codes are not something Tuckly offers, so the reason has to be something you can set up: a lower delivery charge, or an item on the direct menu that is not listed on the apps.
Print more cards than you think you need and make putting one in every bag part of packing, not an afterthought.
Make the direct menu worth opening
If the page is a worse version of the app listing, nobody will use it twice. Use your own photos. Name the dishes the way you would say them. Price add-ons sensibly rather than inflating them to cover a commission that no longer applies. A direct-only item, even one, gives the page a reason to exist beyond price.
Keep the delivery radius tight
A direct order delivered cold is worse than no direct order, because the customer will go back to the app and blame you. Start with the area your own rider or a Porter trip can cover in twenty minutes. Widen it later, when you can see from the order screen how long trips are actually taking.
Google Business Profile for a kitchen without a storefront
Google allows service-area businesses that do not serve customers at their address. Set the profile up that way, with the delivery area as the service area and your ordering link as the website. People searching for your brand name after seeing it on an app will find the direct link rather than only the app listing.
WhatsApp is the other front door
Cloud kitchens get messages: “Do you deliver to Koramangala?”, “Is the paneer gluten-free?”. Every reply should end with the link. A saved reply with the ordering address takes ten seconds to set up and gets used fifty times a week.
Measure the loop with the order screen
There is no dashboard for this today; the signal is simpler. Watch for customers whose name appears a second time on a direct order. When it happens, you know the card worked, the food travelled well enough, and the page was easy enough to use. When it does not happen for a fortnight, something in that chain is broken, and the card is the first place to look.
Keep the apps, and know what they are for
The marketplaces are a paid acquisition channel. They are good at it. The direct site is a retention channel. It is cheaper, and it is yours. A cloud kitchen that treats the two as a single “online orders” bucket will never see what each one is doing. One that keeps them separate can decide, every month, how much of its volume it wants to pay a commission on.
Questions cloud kitchens ask
Should we leave Swiggy, Zomato or the other apps?
No. A cloud kitchen depends on marketplace discovery and a direct site does not replace that. The direct channel is for the second, third and tenth orders from people who already liked the food. Keep both and be clear with yourself about which does which.
Do marketplace orders show up in Tuckly?
Not today. Marketplace orders stay on the marketplace tablets. The integrations directory explains what is and is not connected for Swiggy, Zomato and the POS systems cloud kitchens commonly use.
How does delivery work for a direct order if we have no riders?
Where Porter operates, you request a rider through the supported workflow; the Porter page says which steps are live. Outside Porter's cities, you would need your own rider or offer pickup only.
We run four brands. Can we have four ordering pages?
Talk to us before setting up. There is no confirmed multi-brand feature today, and the answer depends on how the brands share menus, payments and delivery.
What is the cheapest way to tell customers the direct link exists?
A printed card in every marketplace bag, with a QR code and the address written out. Then the WhatsApp reply you send to anyone who messages, and a Google Business Profile for the kitchen as a service-area business. The cloud kitchen setup guide walks through all three.
Give the second order somewhere better to go
Set up your menu, decide how direct orders get delivered, and put a card in every bag.
Gateway fees, delivery and taxes are separate. Pricing
More business types
Last reviewed 29 October 2026.