How to start a tiffin business from home in India

Choose the customer you can serve well

Starting a tiffin business from home begins with a manageable promise: a specified meal, delivered to a defined place, within a realistic time window. Before buying containers or announcing a monthly plan, decide who that promise is for. A student in a paying guest accommodation and an office employee may need different portions, delivery times and payment arrangements.

Talk to people in one nearby area. Ask what time they actually eat, which days they need food, whether there is a place to receive deliveries and what makes their current arrangement difficult. Record their answers instead of asking only whether they like your cooking. An enthusiastic response is useful, but a clear delivery requirement gives you something you can plan.

• Choose one initial group: nearby office workers, students or households.
• Write down the buildings or streets you can reliably reach.
• Choose lunch or dinner first if operating both would stretch your kitchen.

Describe exactly what one tiffin includes

A dish name alone does not define a product. Decide the number and approximate size of rotis, the serving size of rice, the amount of dal and which accompaniments are included. Use the same ladle or measured container when packing a trial batch. This gives you a repeatable portion and makes your ingredient cost easier to understand.

Write a short description customers can recognise: four rotis, one serving each of dal and sabzi, rice and an accompaniment when available. State separately whether curd, sweets or extra rotis cost more. Avoid promising an unlimited choice of substitutions. A small kitchen needs a menu it can prepare consistently, not a new recipe for every individual order.

Check requirements for your actual kitchen

FSSAI provides registration and licensing services for food businesses through FoSCoS (opens in a new tab). Check the applicable category and current requirements for your premises through the official portal before starting paid food service. Use official guidance rather than assuming a threshold, fee or certificate from an old social media post applies to your business.

Also check requirements that depend on your location and premises, such as local permissions and the rules of a rented property or residential society. Keep the relevant records together and set reminders for any renewals. An OrderTiffin website provides ordering tools; it does not replace food-business permissions or certify your kitchen.

Cost a real batch before choosing a price

Prepare a batch at the portion size you intend to sell. Record ingredient quantities, the amount actually used and the yield after preparation. Include oil, spices and small accompaniments rather than counting only the largest ingredients. Keep the bill or purchase note so that you can repeat the calculation when your supplier changes a price.

Add packaging, delivery, fuel and a fair allowance for preparation and packing work. Set aside a share of recurring overheads, too. A meal can look profitable when your own time and travel are treated as free. Use the worked example in our tiffin pricing guide to build a cost sheet using your own numbers.

Make the delivery route part of the product

A small delivery area is easier to operate than a large circle drawn on a map. Test the route at the time you expect to deliver. Building entry procedures, lifts, parking and a customer who cannot answer the phone can change the timetable. Agree where an office or accommodation will receive a group delivery.

Choose an order cutoff that leaves enough time to buy, cook, pack and dispatch. Publish both the cutoff and the delivery window. Explain any fee for an additional area before accepting an order. If a new address falls outside your normal route, check the cost and capacity before offering a recurring plan there. Reliable expectations are more useful than a broad promise of delivery everywhere.

Build a weekly menu you can actually repeat

Plan the whole week before taking regular orders. Rotate the main sabzi and dal, and check whether your most labour-intensive dishes accidentally land on the same day. Think about preparation space and equipment, not only ingredient variety. A menu that requires all your burners during the final packing hour will be difficult to deliver on time.

Use our seven-day tiffin menu example as a starting point, then change it for your customers and working days. Keep supplier-dependent dishes flexible and write a simple substitution policy. If you close on Sunday, show the closure clearly instead of displaying seven days of food you do not offer.

Run a limited trial with clear expectations

Choose a trial batch small enough to prepare, pack and deliver without rushing. Tell participants the exact menu, price, portion, date and delivery window. A discounted trial can be useful, but calculate its cost separately. Do not use a temporary introductory price as the basis for a long subscription you cannot sustain.

Ask specific questions after delivery: Was the food received in the promised window? Was the portion enough? Did any item leak? Which dish would they order again? Separate comments about taste from issues with packing or timing. Correct one or two repeated problems before increasing the batch. A small repeatable service is a stronger starting point than a busy first day followed by inconsistent meals.

Put essential information in one place

Customers should be able to see your kitchen name, current menu, portion description, meal plans, delivery areas, fees, working days and contact number before ordering. Keep a single current source for those details. Repeatedly forwarding old menu screenshots makes it difficult to know which price or dish is still available.

An OrderTiffin website gives your kitchen a shareable menu and ordering page. Customers review their selection and prepare a WhatsApp request. You still need to confirm availability and fulfil the meal. Explore the sample kitchen to see that flow, then use the WhatsApp order guide to define your confirmation routine.

Write the few rules that prevent daily confusion

Decide how customers request a skipped meal, how much notice you need and what happens on kitchen holidays. State whether a plan is counted in meals, service days or calendar days. Explain whether delivery is included and whether a lunch-and-dinner plan covers one person or multiple boxes. Put the rules beside the plan rather than revealing them after payment.

Choose a method to record payments, pending balances and the next delivery date. If a customer asks for a change, acknowledge it and update your record before the packing list is made. An unread message is not a reliable pause instruction. Avoid automatic promises about refunds or carry-forward meals until you have decided what your kitchen can honour.

Use a launch-day checklist

• Confirm the menu and quantities you can supply.
• Check ingredients, food-contact packaging and the dispatch arrangement.
• Verify the correct customer names, phone numbers and delivery addresses.
• Confirm the final price and any delivery fee with each customer.
• Record which requests you have accepted and which are still pending.
• Publish closures and order cutoffs before people make plans around your food.
• Keep a way to contact customers if a delivery is delayed.

Keep a small operating log for the first week: orders accepted, boxes packed, meals delivered, complaints, actual spend and time taken. Review it at a quiet point each day. If the route is late or portions vary, solve that constraint before adding more customers.

Write a one-page service brief

Before publishing, try describing the service in one page that someone outside your household can understand. Include the kitchen name, who it serves, the meal window, a sample portion, the delivery area and the way to ask for an order. If you cannot explain a plan without a long phone call, simplify its wording before charging for it.

For example, a lunch-only service could offer a stated number of lunches on its working days, delivered to a small set of buildings. The description should say whether delivery is included, which dates the kitchen is closed and how a customer requests a change. Those are decisions for the owner to make; the example does not prescribe a universal plan.

Ask a potential customer to read the page and explain back what they would receive. Listen for different interpretations of words such as monthly, full meal and free delivery. Correct those ambiguities while the service is small. Keep a version of the brief with its effective date so that future changes can be explained to customers who joined under an earlier offer.

Use a photograph of your actual trial meal where you can, with the planned portion and packaging. Do not represent a stock photograph or sample website as a meal already cooked by your kitchen. A clear, ordinary picture of the food you intend to deliver sets a more useful expectation.

Grow from a routine, not a guess

At the end of the trial, compare what you expected with what happened. Did the batch yield the planned number of meals? Did delivery take longer than cooking? Were there frequent requests for extra rotis or a lighter meal? Those observations can guide a smaller menu adjustment or a separate paid option.

Add one new demand at a time: more customers on the same route, a second meal window or another nearby building. Each change has a different effect on capacity. Keep your published menu and prices current as you learn. When the service is ready to share, create your kitchen page and make the next order easier for both the customer and the person packing it.