WhatsApp Business API for cafes: setup, rules and real costs

The app is fine until these start happening to a cafe:

• Customers visit once, never return. They loved the oat latte. They just forgot you exist by next weekend. No reason to come back specifically.
• New menu items reach nobody. You launched a seasonal special. Instagram showed it to a fraction of followers. WhatsApp reaches them directly.
• Regulars drift away without anyone noticing. A daily customer stops coming and nothing flags it. By the time you notice, they have a new cafe.

The app cannot send on a trigger, share one number across staff, or read your records. The API can. And customers keep asking the same things: regulars ask what the special is today, whether you have oat milk or gluten-free options, whether they can pre-order for pickup, and whether the space is free for a small meeting.

• A verified Meta Business account in the cafe's legal name, backed by a registration, GST or utility document.
• A number not active on the WhatsApp app — your current one works once it is removed from the app.
• A display name matching the business, and a website or public page Meta can check.
• Opt-in from every customer you message first. A loyalty card is the obvious hook: customers give their number to collect stamps on WhatsApp instead of a paper card that ends up in the wash.

1. Connect the number through Meta's embedded signup inside Reputoo, and submit business verification — you can start sending within Meta's starting limit while it is reviewed.
2. Get your first templates approved for the 1 routine message listed below; anything outside a customer's 24-hour reply window must be a template.
3. Wire the triggers to your records. What to connect: A POS with a customer list and, often, a delivery-app tablet; the POS is where loyalty data should sync to.
4. Put staff on one shared inbox, with conversations assigned so two people never answer the same customer.

A cafe with 80 WhatsApp pickup orders a day sends about two utility messages each — roughly 4,800 a month, around ₹552 in Meta fees on the July 1, 2026 India rate card, before GST. Promotional messages cost ₹0.8631 each, which is why daily-special broadcasts need a small, willing list.

Morning regulars want their coffee without the line. An order sent on WhatsApp — "one flat white, oat milk, and a croissant" — is confirmed with the total and a ready time, paid by link if you like, and the customer walks in, picks it up and leaves. Staff see orders in a shared inbox or on a screen behind the counter, not on a manager's phone, and "ready" goes out with one tap.

Meta charges per delivered template message, and the price depends on the category. For cafes, the day-to-day messages sort like this:

• First visit — customer enrolled in loyalty — marketing
• Every visit earns points via WhatsApp — utility
• New menu & offers broadcast — marketing
• Reward redeemed → next-visit nudge — marketing

Timing matters as much as category. Morning messages before the commute and a mid-afternoon nudge for the slow slot work; late-evening promotions for a cafe that closes at six do not.

A service reply answers a customer who wrote first; from 1 October 2026 Meta charges those at the utility rate. Utility messages (confirmations, reminders, status updates) cost a fraction of marketing messages, so keep them strictly transactional — a discount line inside a reminder makes Meta classify the whole template as marketing.

Meta list rates, July 1, 2026. India in INR, plus 18% GST.

Paper stamp cards get lost in wallets and washed in pockets. A WhatsApp loyalty card records a stamp with each purchase, tells the customer how close they are to a free coffee, and sends the reward when it is earned. Customers join by scanning a QR code at the counter — which is also the moment you ask whether they would like to hear about new drinks and events.

Birthday cakes and office catering orders involve details that go wrong on the phone: the name on the cake, the flavour, eggless or not, the size, the pickup time. Taking them in chat gives a written record, and a reference photo if the customer has one. Confirm the details back, send a deposit link, and send a reminder the day before pickup. Allergy and dietary requirements should be confirmed by a person.

Meta rates every number on how customers react. For cafes, the risk is usually messaging the whole contact list about something only some of them asked for. Send reminders only to people with a booking or order, promotions only to people who opted in to them, and never use a bulk-sender tool on the ordinary app — that is the route to a banned number. The full list of what Meta checks is in our WhatsApp Business API guide.

Cafes are booked for small meetings, birthdays, book clubs and study groups. Bookings by message — date, time, number of people, any minimum spend — are confirmed in writing, and a reminder on the day reduces empty reserved tables at peak times. For private use of the space, the rules and deposit go in the confirmation.

Delivery apps bring new customers but take commission and keep the customer's contact. Regulars who order often can be invited to order directly by WhatsApp from your menu, for pickup or your own delivery. The cafe keeps the relationship and the margin on those orders.

Bakeries share most of this with cafes, with one addition: pre-orders. Customers who want a specific loaf or pastry for the morning can order the evening before and collect fresh. The bakery bakes to the orders and wastes less, and the customer is sure to get what they came for.

Cafe chains usually give each outlet its own number and display name under one business account, so customers order from the outlet they visit. The loyalty programme should work across outlets, with stamps recorded centrally.

1. Week 1: move the number to the API; get order, ready, booking and loyalty templates approved; set up the order screen.
2. Week 2: pickup orders by WhatsApp for regulars; QR code at the counter.
3. Week 3: the loyalty card and cake orders.
4. Week 4: the first message about a new drink or event to customers who opted in.

• Orders appear where the baristas can see them, not on one phone.
• "Ready" messages go out with one tap.
• Cake orders are confirmed back in writing with a deposit link.
• Loyalty stamps are recorded centrally.
• Marketing goes only to customers who opted in.

Offices nearby order coffee for meetings, snacks for events and cakes for birthdays. A thread with each office's admin — orders, delivery times, monthly invoices — turns occasional orders into a steady account. Send invoices in the company's name at month end, and give regular offices a simple way to reorder their usual meeting order.

Many cafes take orders on the owner's phone. It works until the owner is away, until two baristas need to see orders at once, or until orders get lost between chats. The API puts orders on the cafe's number, visible to the whole team on a screen or shared inbox, with "ready" messages sent in a tap.

Keep order, ready, booking and loyalty templates short and specific: the items, the total, the ready time, the outlet. Keep offers out of them so they stay utility messages. A separate marketing template carries the new drinks and events.

A cake is usually for an occasion the customer cares about. A short message the day after — "Hope the birthday went well! How was the cake?" with [Loved it] [Could be better] — catches problems while you can still make amends, and "Loved it" is the moment to ask whether they would like a reminder before next year's birthday.

Pickup orders can be paid by link before arrival, cake orders take a deposit, and offices can pay monthly. Receipts go back in the chat. Keep payment messages separate from marketing, and send them only to the customer's own number.

An automatic reply outside hours should say when the cafe opens and, if you take pre-orders, let customers order for the morning. Update it before holidays and event days so nobody walks to a closed door.