/// kitchen operating system · 0% commission
Your menu. Your orders. Your delivery. No commission.
Marketplaces take a cut of every plate — at commission rates as publicly reported (see our sourced comparison below) — and keep the customer relationship. Phone orders get half-heard in a loud kitchen. Dloter is your own ordering channel: your menu site, your orders dashboard, your riders, your customers — on your own subdomain.
no credit card · yourkitchen.dloter.com today · we charge for the platform, never a percentage of your food sales
new
preparing
ready
out for delivery
/// follow ORD-0092 · five real states
Scroll. The kitchen carries it.
Placed
your menu site
Kitchen notified
in-app · honest
Preparing
modifiers honored
Rider assigned
out for delivery
Delivered ✓
pod recorded
● state 1 · Placed
Placed on your menu site — exactly as chosen
2× Paneer Tikka (less spicy) · 1× Dal Tadka, ordered on yourkitchen.dloter.com. Veg badges shown at choice, modifiers captured at checkout, minimum order met, zone fee applied. Not a phone call someone half-heard over the exhaust fan.
✓ recorded with modifiers✓ veg ● preserved✓ min ₹200 met · T. Nagar ₹30
● state 2 · Kitchen notified
The kitchen knows — honestly
An in-app alert routes to the kitchen role. Dloter never fakes a “sent”: WhatsApp order alerts aren’t live yet, so the system doesn’t pretend they are. What it shows delivered, it delivered.
✓ alert routed in-app✓ no fake “sent”
● state 3 · Preparing
Preparing — the ticket is the order
What the customer chose is what the kitchen sees: “less spicy” travels on the ticket, veg badges stay visible on the rail. And an 86’d dish could never have been ordered in the first place — the toggle removes it from the live menu, not just from your memory.
✓ modifiers on ticket✓ 86 respected at order time
● state 4 · Rider assigned
Rider assigned — out for delivery
You assign Arun and advance the status. Zone T. Nagar, fee ₹30 — set by you in delivery zones, applied at checkout. Status moves because your team moved it, not because a timer guessed.
✓ rider assigned✓ status advanced by your team
● state 5 · Delivered ✓
Delivered — POD recorded
The customer followed the whole journey by their tracking link — real status at every step, never an invented “arriving in 8 minutes”. Delivery closes with proof-of-delivery recorded. The order’s story is complete.
✓ pod recorded✓ tracking = status truth✓ record complete
// every state above is a shipped product state · customer tracking shows real status only — no eta theater
/// screenshots, not promises
The actual software.
Three chambers — captures from an approved demo tenant with dummy dishes. Until each capture lands, its slot says exactly what will be shown.
/// chamber 01 · your menu, your brand
A menu site that belongs to you — not a card in someone else’s feed.
Your dishes, your photos, your subdomain. Modifiers and veg/non-veg badges are first-class — customers choose precisely, and an 86’d dish simply isn’t there to order.
proof: restaurant vertical rv-1/rv-2 · modifiers + menu builder live-verified
/// chamber 02 · the kitchen’s desk
An orders dashboard that keeps up with a dinner rush.
Every order with its modifiers, badges and delivery/takeaway mode. Ran out of paneer at 8pm? The 86-toggle takes it off the live menu in one tap — no more apologising to customers who already ordered it.
proof: restaurant vertical rv-1/rv-2 · orders dashboard + 86-toggle live-verified
/// chamber 03 · your riders, your last mile
Dispatch your own riders. Close every order with proof.
Assign a rider, advance the status, and the customer’s tracking link tells the truth the whole way. Delivery ends with POD recorded — not with a shrug.
proof: restaurant vertical rv-3 · rider dispatch + pod live-verified · tracking ref: platform tracking
/// the honest capability matrix
What’s live in your kitchen today.
What’s coming — labelled.
Every ● maps to a live-verified proof reference. Everything unshipped says so, here, on the sales page.
Menu with modifiers
Less spicy, extra raita, no onion — captured at checkout, printed on the ticket.
ref: restaurant vertical rv-1 · live-verified
Veg / non-veg badges
India-convention ● and ▲ marks on every dish, at the point of choice.
ref: restaurant vertical rv-1 · live-verified
86-toggle
Ran out? One tap removes the dish from the live menu — it can’t be ordered.
ref: restaurant vertical rv-2 · live-verified
Delivery / takeaway toggle
Run both, or takeaway-only. The customer chooses per order; you control what’s offered.
ref: restaurant vertical rv-3 · live-verified
Zones, fees & minimum order
Your delivery zones, your fees, your minimum — applied honestly at checkout.
ref: restaurant vertical rv-3 · live-verified
Rider dispatch
Assign your rider, advance the status. The system reflects your ops — it doesn’t invent them.
ref: restaurant vertical rv-3 · live-verified
Proof of delivery (POD) recorded
Every delivery closes with proof of delivery on the order record.
ref: restaurant vertical rv-3 · live-verified
Customer tracking links
Real status at every step. No invented ETA, no GPS pretense — status truth.
ref: platform tracking · live
Own-brand menu site
Your restaurant on your subdomain — yourkitchen.dloter.com — not a listing.
ref: restaurant vertical rv-1 · live-verified
Orders dashboard
The whole rush on one screen: new, preparing, ready, out for delivery.
ref: restaurant vertical rv-2 · live-verified
In-app alerts — honest
New-order alerts routed to the acting role. Never marked “sent” unless delivered.
ref: business event spine · live
Team roles
Kitchen, counter, riders — each sees what their role permits. Backend denies, UI hides, both proven.
ref: enterprise operations · live
WhatsApp order alerts
Unclaimed until delivery is proven end-to-end. Today, alerts are in-app — and honest about it.
status: held until proven
POS / dine-in / KOT
Not built yet, so not claimed. When a POS exists, it will appear here as live — not before.
status: not built · labelled
Aggregator listing
We’re the anti-aggregator — if we ever list you anywhere, it’ll be your choice, not our default.
status: no integration · by design + honesty
what we don’t do: marketplace or aggregator listing · pos, dine-in or kot · whatsapp order alerts · payment-settlement guarantees
/// the truth firewall
Claims food-tech loves to ship.
Dloter’s firewall rejects them.
These rejections are product behavior, not marketing copy. The same firewall that protects your customers protects your kitchen.
- fake_etano “arriving in 8 minutes” theater. Tracking links render real status only — an ETA renders only from a real source, and none exists today.✕ REJECTED
- commission_creepplatform pricing, never a percentage of your food sales. Not at signup, not at scale, not in a footnote.✕ REJECTED
- fake_sentan order alert is never marked sent unless a live channel actually delivered it. WhatsApp isn’t live yet — so it isn’t claimed.✕ REJECTED
- ghost_posno POS, dine-in or KOT claims until a POS exists. “Coming” means coming — it never renders as a button that does nothing.✕ REJECTED
- modifier_truthwhat the customer chose is what the kitchen sees — modifiers travel on the ticket, veg badges stay attached.✓ LIVE
- pod_evidencedelivery closes with POD recorded — every order’s story ends with proof, not a guess.✓ LIVE
full register: /proof — what’s live, what’s not, and how we decide
/// install sequence
Your kitchen’s operating system installs in a day.
Service tonight.
Register with an OTP and watch it assemble — your subdomain, a truthfully-seeded menu, delivery zones through an honest readiness checklist, roles for the counter and the riders. This sequence is real, not aspirational.
/// the commission math
A marketplace takes a percentage of every plate.
A platform charges for the platform.
Both models exist for a reason. Here’s the honest difference — with the assumptions on the table.
Listing on a marketplace / aggregator
their storefront · their customer · their rules
- Commission on every order — at rates the platforms and press have publicly reported; verify current rates for your city and category before you decide
- The customer relationship belongs to the marketplace — their app, their data, their re-marketing
- Your brand is one card among hundreds on the same screen
- Real discovery — new customers do find you there; that reach is genuinely what the commission buys
commission figures: as publicly reported · verify current rates — we don’t invent competitors’ numbers
Your own ordering channel on Dloter
your storefront · your customer · your rules
- Platform pricing — ₹0 free tier, ₹999/month metered — never a percentage of a single plate
- Your customers stay yours: their orders, their history, their repeat business
- Your brand on your own subdomain — menu, badges, modifiers, tracking, all yours
- You bring the demand — regulars, word of mouth, the board outside your door; we make ordering from you effortless
pricing shown is the real platform pricing · no restaurant-tier pricing exists yet — when it does, it will be published, not implied
illustrative arithmetic — not a quote, not a guarantee
Assume a kitchen doing 300 own-channel orders a month at an average of ₹350 — ₹1,05,000 in orders. At a 20% commission (a figure within the range publicly reported for major Indian food aggregators as of mid-2026 — verify current rates), that channel would cost:
₹1,05,000 × 20% = ₹21,000/month to the marketplace · vs · flat platform pricing on Dloter (₹0 or ₹999/month metered)
Assumptions stated above; your volumes, average order value and applicable commission will differ. Aggregators also bring discovery this arithmetic doesn’t price in — which is exactly why many restaurants run both, and keep their regulars on their own channel.
Full metering table and honest pricing FAQs: see pricing → · Also run a retail or D2C store? explore the ecommerce OS →
Questions, answered straight.
How is this different from Swiggy or Zomato?
Honestly: aggregators bring discovery — new customers who’ve never heard of you find you in their feed, and that reach is real. Dloter doesn’t do that. Dloter is your own ordering channel: your menu site on your subdomain, commission-free, where your regulars and walk-ins order directly and stay your customers. Many restaurants run both — and move their repeat business to the channel that doesn’t take a cut.
Do you take a commission on my orders?
No. We charge for the platform — a ₹0 free tier and a ₹999/month metered plan — never a percentage of your food sales. There is no per-order cut anywhere in the model.
How do online payments work?
You connect your own Razorpay account, so payments flow through your own money path — Dloter never sits between you and your settlement. We make no payment-settlement guarantees on anyone’s behalf; your gateway’s terms are your gateway’s terms.
Do I need my own riders?
For delivery, yes — Dloter dispatches your riders: you assign, advance status, and record POD. If you don’t have riders, run takeaway-only: the delivery/takeaway toggle is live, and your menu site simply offers pickup.
Do you support veg badges and dish modifiers?
Yes, both are live and first-class: India-convention veg ● / non-veg ▲ badges on every dish, and modifiers (“less spicy”, “extra raita”, “no onion”) captured at checkout and shown to the kitchen exactly as chosen. Ran out of something mid-service? The 86-toggle removes it from the live menu in one tap.
What do I actually get on day 1?
Register with an OTP and the same day you have: your subdomain (yourkitchen.dloter.com), a truthfully-seeded menu site to fill with your real dishes, delivery zones + fees + minimum order via an honest readiness checklist, and an orders dashboard with in-app alerts. Invite staff and riders when you’re ready — each role-scoped from first login.
/// begin
Put your kitchen on its own operating system.
Start self-serve in minutes — or tell us how you run today and a human walks you through the real product, on real screens.
Start your kitchen’s OS →