Skip to content

WhatsApp CRM · Home Bakers & Food Sellers

A WhatsApp CRM for home bakers and food sellers

The problem in a home kitchen is rarely too few orders. It is the tenth order for the same day arriving while the rice is already portioned, and saying yes anyway. InboxCRM gives you one menu message that goes out to your regulars at once, a cut-off you can actually hold, and a warm "this week is full" reply that is written before you are too tired to write it.

Written for how home bakers & food sellers actually work

Lunch-packet and office-delivery cooks, weekly bakers doing cupcake trays and cookie batches, achcharu, sambol and jam makers selling by the bottle, and dietary-niche sellers cooking oil-free or sugar-free for a small, loyal list.

The cycle here is the day and the week, not the month. An order is taken and fulfilled within hours, so there is nothing to nurture along a pipeline. What replaces follow-up is rhythm: menu out on the same evening every week, cut-off at the same time every day, full message sent the moment the ceiling is hit. Regulars come back because they can plan around you, not because you chased them.

The busiest week in the calendar is the Avurudu stretch in March and April, when kevili and sweets orders all land at once, and December brings a second wave for baked goods. Lunch-packet sellers see a real dip whenever their office or school customers are on holiday.

A normal day in your inbox

  • What's on the menu today?
  • I need 3 lunch packets for Friday, to the office.
  • I'm a regular — how does the monthly order work now?
  • Can you tell me by this evening? Are you closed on Monday?
  • Can you reduce the quantity? I only need 2.
  • The achcharu I got last week was lovely, I'd like another jar.
  • I saw the group post late — is that still available?

Where the deals leak

  1. Menu posted
  2. Order requests
  3. Quantity and day agreed
  4. Cooking and baking
  5. Packing
  6. Delivery or pickup
  7. Payment
  8. Next week

The moment an order is accepted without anyone checking it against what the kitchen can actually finish that day. This is not a lost sale, it is the opposite: too many sales taken at once, which turns into three late deliveries and one wrong item.

Saying no feels like refusing money or letting a regular down, and there is no visible count of what has already been promised for that slot. The second leak is quieter: after a good delivery, nothing brings that customer back next week unless she happens to see the next post.

A board that matches your job

Use the board as a day or week counter, not as a sales funnel. The point is simply that you can see how many orders are already in Ordered before you type "yes, no problem" to the eleventh one. Tagging weekly regulars separately from one-time Avurudu buyers matters more here than any deal value.

  1. Stage 1

    Asked about the menu

    Enquired but has not committed to a quantity or a day yet.

  2. Stage 2

    Ordered

    Item, quantity and day agreed. Count these against your ceiling before you accept another.

  3. Stage 3

    Cooking

    Past the cut-off, ingredients bought, changes no longer possible without cost.

  4. Stage 4

    Packed

    Ready and labelled, waiting on the delivery run or pickup.

  5. Stage 5

    Delivered and paid

    Closed for this cycle. These contacts are next week's menu list.

Tags worth having

  • Weekly regular
  • Office delivery
  • Pickup only
  • Achcharu and bottles
  • Oil-free
  • Sugar-free
  • Avurudu kevili
  • One-time buyer

Set it up once

Everything below happens inside WhatsApp Web, on the number you already use. No API, no new inbox.

Add InboxCRM to Chrome
  1. 1

    Broadcast the menu once, before the questions start

    Build a list of the regulars who asked to receive your menu and send it as one campaign the evening before, instead of answering "what's on the menu today" one chat at a time all morning. Orders then arrive in a plannable wave rather than a trickle.

  2. 2

    Say the cut-off out loud and put it in writing

    Save a quick reply that states the cut-off time and schedule it to go out a couple of hours before. Most sellers in this trade have never told customers a cut-off exists, which is why late changes keep landing after cooking has started.

  3. 3

    Write the "full" message while you are calm

    A short, warm, non-apologetic "this week is full, I'll put you first on next week's menu" is the single most useful quick reply in this kitchen. Saved once, it goes out the same way every time, including at 11am when you are already behind.

  4. 4

    Use status posts for the daily menu you already post

    You are already posting the day's tray to WhatsApp Status. Scheduled status posts let you line those up the night before, so the menu is live at 6:30am without you stopping mid-cooking to post it.

  5. 5

    Keep the standing order on the contact

    Note that this office takes three packets every Friday, or that this customer buys two bottles of achcharu a month. Custom fields on the contact turn a regular from something you remember into something you can actually plan the week's quantities around.

  6. 6

    Say the cancellation terms at order time

    Add one line to your order-confirmation quick reply about what happens if a cancellation lands after cooking has started. Stated up front, it is a rule. Invented mid-dispute, it is an argument.

The messages that stall a sale

  • What's on the menu today?

    Usually means
    Not really an objection. It means nothing central exists for them to check first.

    What works
    Post the menu once to the group, page or status before the morning questions start, then point late-askers to the same post. Answering it fresh twenty times is slower for you and gives everyone a different window to decide in.

  • Can you tell me this evening? Are you closed?

    Usually means
    They genuinely cannot tell whether today's or this week's slots are gone, because you have never said there is a limit.

    What works
    Send the "full" message once to everyone still asking. It protects your evening and it protects the customers who did order in time. Going quiet reads as rude, and taking "just one more" past the real limit costs you the ones already promised.

  • Can you reduce the quantity?

    Usually means
    A small, reasonable change, and usually fine — unless it lands after the cooking has started.

    What works
    Accept it warmly if you are still before the cut-off. If not, say so plainly and note it for next time. The problem is not the change itself, it is treating every change the same regardless of what time it arrives.

  • Do you have anything made without oil? Someone here is diabetic.

    Usually means
    A dietary request, usually for a family member, and a genuine buying signal.

    What works
    Say exactly what is and is not in the dish, then stop. Never say it is safe or suitable for a medical condition. That judgement belongs to the customer and their doctor, and an eager "yes, that will suit you perfectly" is a health guarantee you cannot back.

  • I ordered 3 and cancelled 2. Do I get a refund?

    Usually means
    Sometimes a real change of plan, sometimes a sign the original yes never felt binding.

    What works
    Have a calm policy that was stated at confirmation time, not invented on the spot. Being upfront that same-day cancellations after cooking has begun cannot be refunded protects both sides, and makes the confirmation feel like a commitment.

Quick replies to save first

Copy these, swap the details in [brackets], and save them as quick replies so you stop retyping them.

  • Weekly menu broadcast

    Good evening! 😊 Here's this week's menu 👇 [items]. Message me before [day] to order — anything after that goes onto next week's list.

  • Cut-off reminder

    Today's orders close at [time]. Message before then and I'll have it ready for you today.

  • This week is full

    Thanks so much for asking 🙏 I'm already full for this week — I'd rather keep the quality than squeeze in more. I'll put you at the top of next week's menu.

  • Dietary question, answered honestly

    There's no [ingredient] in the [item]. I can't tell you whether it suits a medical condition though — that's worth checking with your doctor before you decide.

  • Order confirmed, with the terms

    Order in ✅ [item] × [qty], ready [day] at [time], Rs. [X] on delivery. One thing so it's clear up front: once cooking has started I can't refund a cancellation.

Free tools that help here: WhatsApp Business Message Templates, WhatsApp Text Formatter.

The parts of InboxCRM you'll use most

  • Quick replies

    The menu reply, the cut-off reminder and the "full" message all get sent in the same warm tone whether it is your first order of the day or your fifteenth.

  • Campaigns to your regulars

    One weekly menu message to the list of customers who asked for it, sent slowly within the default caps, instead of posting and hoping.

  • Scheduled messages and status posts

    Line up tomorrow's menu and the cut-off reminder tonight, so nothing needs posting while your hands are in dough.

  • Contact notes and custom fields

    Which customers are weekly regulars, what they always order and where they collect from, held somewhere other than your head.

  • Order tracking

    A visible count of what has already been promised for today, which is the whole point when the question is how many more you can honestly take.

Questions from home bakers & food sellers

Can it tell me how many orders my kitchen can handle?

No. That number comes from your own experience of a bad day, not from software. What the tool does is make the number visible and repeatable: you decide the ceiling once, the board shows you how close you are, and the "full" message is already written so hitting the limit is not an awkward conversation each time.

I take orders in a WhatsApp group. Does this help with that?

The CRM works on individual chats in WhatsApp Web, so group ordering itself stays as it is. What changes is what happens after: the person who messages you privately gets tagged as a regular, their standing order is noted, and next week's menu can go to them directly rather than relying on them spotting a group post.

Is sending the weekly menu to everyone allowed?

Campaigns are for lists of people who agreed to hear from you, which in this trade usually means your existing customers. Sending is deliberately slow, with roughly 40 an hour and 250 a day by default, plus quiet hours and a cooldown per contact. Messaging people who never asked for your menu puts your number at risk.

Everything happens on my phone. Do I need a computer?

Yes, for the tool itself. It is a Chrome extension running on WhatsApp Web on a desktop or laptop, and anything scheduled only sends while that Chrome window is open. Many home kitchens are phone-only, and if that is you, the habits here — one menu post, one cut-off, an honest ceiling — work on their own.

Can it handle the money side, like who has paid?

It tracks orders and deliveries and lets you keep payment status as a note or custom field on the order, so you can see who is still to settle a COD. It is not an accounting system and it does not process payments. Payments stay as cash on delivery or a bank transfer against a receipt.