Indian Restaurant Online Ordering: Spice Levels, Sides & Set Meals

The phone version of an Indian order carries a lot of unspoken detail. "A chicken madras, lamb rogan josh, two pilau and a garlic naan" hides three decisions your kitchen has to guess at over a noisy line: how hot, which protein, what rice. Online ordering removes the guesswork — but only if you build the menu as a set of structured choices rather than a flat list of dishes. Each curry becomes one item with the options attached, so the ticket that reaches the pass is complete.

Make spice level a required choice. Add a modifier group to every curry with mild, medium, hot, madras and vindaloo, and mark it as required so the order cannot be placed without one selected. The customer picks before the dish goes in the basket, and the heat prints clearly on the kitchen ticket. No more "was that mild or medium?" shouted across the kitchen mid-service.

Let customers swap the base and protein. Most houses cook one sauce across several proteins. Model that as a single choice with a price difference for each option — chicken as standard, lamb at +£1.50, paneer at +£1.00, king prawn at +£3.00. The customer builds their own rogan josh or bhuna, and the price adjusts automatically. You list the dish once instead of maintaining five near-identical entries.

• Add rice, naan and sundries as add-ons — pilau at £3.50, plain rice at £2.95, garlic naan at £3.50, peshwari naan at £3.95, a poppadom and chutney tray at £4.50. Attach them to the curry as optional extras, or keep a dedicated "Sundries" category so a customer can top up the order before checkout.
• Use categories the way customers order — starters, tandoori, house specials, traditional curries, biryani, breads, rice and sundries. Sticky category tabs let someone jump straight to the breads without scrolling past forty curries, which matters on a long menu viewed on a phone.
• Keep a free-text box for special requests — "no dairy, extra sauce, mild for the kids". A short notes field handles the edge cases your modifiers do not, without a phone call. Pair it with a clear allergen note on dishes containing nuts, dairy or gluten — it is a legal requirement and a trust signal.

Set meals are where Indian takeaways make their margin. A banquet bundles a starter, two curries, rice and a naan into one attractive price, and the customer spends more than they would ordering à la carte. The trick online is to make these bundles as easy to add as a single dish — one tap, fixed price, no maths for the customer and no manual adjustment for you.

Build banquets as fixed-price bundles. A banquet for two at £27.95 might include two poppadoms, two starters, two curries, two pilau rice and a naan. A family feast for four at £52.95 scales it up. The customer chooses the components from the allowed options — their pick of starter, their curries at their spice levels — and the price stays fixed regardless. It reaches the kitchen as a complete, priced order with every choice attached.

Run offers as automatic rules, not codes. A first-order discount of 15%, a midweek deal of 10% off Monday to Thursday, or free delivery over £30 — set the rule once and it applies itself at checkout. Customers do not hunt for a code to type, and you do not field calls about a promo that did not work. A collection discount, say £3 off any collection order, nudges customers to save you the delivery run entirely.

• Reward repeat orders — a loyalty deal such as a free starter or £5 off on every fifth order gives regulars a reason to keep coming direct rather than drifting back to an aggregator app. The rule tracks orders and applies the reward automatically.
• Set a minimum for delivery, not collection — a £15 delivery minimum keeps small unprofitable orders off the road while still letting a single-curry collection order through. Apply the rule to the order type and zone, so it only bites where it should.
• Keep the margin the aggregator would take — on a £40 banquet, a 25-35% commission is £10 to £14 gone before you have paid for the chicken. On a flat monthly subscription with direct card payments, that whole amount stays with you. A few banquet orders a week covers the cost of the platform many times over.

Friday and Saturday nights are the whole game for an Indian takeaway, and they are also where an ordering system either holds up or falls apart. Forty tickets landing at 8pm, a kitchen that can only produce so many curries an hour, and a phone that will not stop ringing — the goal is to spread that load and keep every order accurate, not just take more of them.

Use prep times and lead times to spread the rush. Set how long an order takes to cook and how far ahead it can be placed, and the system offers customers bookable time slots — order now for 8:45, or schedule for later. Instead of every order demanding to be ready at once, the evening fills in manageable 15-minute windows, and the kitchen works to a queue it can actually clear.

Throttle orders when the kitchen is at capacity. Cap how many orders a slot accepts, and once it is full the next customer is offered a later time rather than a dish that will arrive cold and late. It is better to quote an honest 60 minutes at the peak than to accept an order you cannot cook on time and lose the customer for good.

• Put orders on a kitchen screen — a live display sorted by status, with the spice level and sides shown clearly, beats a paper spike every time. The chef marks each order preparing then ready, nothing gets lost under the next ticket, and front of house can see at a glance what is still to go out.
• Let updates go out automatically — a confirmed message when the order is accepted and an "out for delivery" or "ready for collection" alert cut down the "where's my order?" calls that tie up the phone when you can least afford it. The live order page updates in real time even without SMS, so for most nights email and the tracking page are enough.
• Run direct ordering alongside Just Eat and Deliveroo — you do not have to delete your aggregator listings. They are good for discovery; your own storefront is where you convert those diners into direct, commission-free regulars. Put your ordering link on the menu flyer, the carrier bag and your socials, and offer a discount for the first direct order to move them across.
• Keep delivery tight — draw your delivery zones on a map with a minimum, a fee and hours for each. A curry that travels too far turns up cold and earns a bad review, so a controlled radius protects both the food and your name.

Once a customer has ordered direct once — no app to install, no marketplace to scroll, the same menu they know at a better price — they tend to come back. Every one of those repeat orders is full margin you keep, and over a busy few weekends that is the difference between a takeaway that works for the aggregator and one that works for itself.