WhatsApp Business API for online stores: setup, rules and real costs

The app is fine until these start happening to an online store:

• 68% of carts abandoned with no follow-up.
• Order tracking calls overload your support. "Where is my order?" is your most common support query. WhatsApp order updates answer it before customers ask.
• COD orders come back as returns. The order ships, the customer changes their mind, and you pay both legs of the shipping plus the packaging.

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: shoppers ask about delivery time to their pin code, cash on delivery, size and fit, return policy, and where their order is.

• A verified Meta Business account in the online store'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. Checkout is the natural opt-in point, alongside a WhatsApp chat button on product pages.

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 3 routine messages 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: the store platform — Shopify, WooCommerce or a custom stack — is the source of orders, carts and customer consent.
4. Put staff on one shared inbox, with conversations assigned so two people never answer the same customer.

A store shipping 100 orders a day with four updates each sends about 12,000 utility messages a month — roughly ₹1,380 in Meta fees on the July 1, 2026 India rate card, before GST. Cart reminders and campaigns cost ₹0.8631 each, so they are worth targeting carefully.

Cash-on-delivery orders that are refused at the door cost the store shipping both ways. A utility message before dispatch — "Please confirm your COD order of ₹1,499" with [Confirm] [Cancel] — lets the store ship only confirmed orders and cancel the rest before they cost anything. A cancelled order is also a chance to offer prepaid payment with a link, for customers who simply prefer not to pay cash.

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

• Cart abandon → WhatsApp recovery in 1 hour — marketing
• Order confirmation + shipping update on WhatsApp — utility
• Re-order prompt after delivery — utility
• Re-purchase sequence based on product lifecycle — utility

Timing matters as much as category. Order confirmations and shipping updates in real time, cart reminders within hours, and promotions around sales events.

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.

Most support messages to an online store are "where is my order?". A shipped message with the tracking link, an out-for-delivery message on the day, and a delivered message answer the question before it is asked. When a shipment is delayed, say so proactively with the new estimate; silence turns a delay into a complaint.

Returns are part of online retail, and a clear process keeps them from becoming disputes. Customers start a return in the chat with the order number, reason and photos; the store confirms eligibility under its policy, schedules the pickup, and sends updates until the refund is processed. Staff handle exceptions from the shared inbox with the order attached.

Meta rates every number on how customers react. For online stores, 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.

WhatsApp messages should fire from the store's own events — order placed, fulfilled, delivered — so there is no manual work and no mismatch. Reputoo connects to Shopify and WooCommerce for this; custom stores connect through the API. Customer consent from checkout travels with the order.

Shoppers ask about size, fit, material, delivery time to their pin code and return policy before buying. A WhatsApp button on product pages lets them ask in the moment; answering within minutes turns hesitations into orders. Product photos and videos can be shared in the chat.

Customers want to change an address, a size or cancel before dispatch. In the chat, the store can check the order status and make the change if it has not shipped, confirming in writing. After dispatch, the chat explains the options clearly.

1. Week 1: connect the store platform; get order, COD, shipping and delivery templates approved.
2. Week 2: order confirmations and shipping updates for every order.
3. Week 3: COD confirmation and returns in chat.
4. Week 4: cart reminders and back-in-stock alerts to customers who opted in.

• Order events from the platform trigger every update.
• Checkout collects WhatsApp consent, separately for offers.
• The COD confirmation cancels unconfirmed orders by your rule.
• The returns policy is written and the bot follows it.
• Support staff answer from the shared inbox with order details visible.

Return-to-origin shipments — orders that come back undelivered — eat margins. Most come from unconfirmed COD orders, wrong addresses and customers who were not reachable. The COD confirmation catches the first; a message asking the customer to confirm or correct an incomplete address catches the second; and an out-for-delivery message with the courier's number catches the third. Orders from numbers that never confirm can be held rather than shipped.

Some customers choose COD out of habit rather than distrust. The COD confirmation message can include a payment link — "or pay now and skip handing over cash" — so customers who prefer can switch in one tap. Prepaid orders are refused less often and settle faster.

Small stores often start by answering on the owner's phone. Once orders reach a few dozen a day, messages get lost, updates are sent by hand, and nobody else can help. The API sends every order update automatically from the store platform, and puts customer questions in a shared inbox the whole team can answer.

Keep order templates factual: order number, items, total, tracking link, expected date. Keep discount codes and "you may also like" out of them so they stay utility messages. Put cart reminders, back-in-stock alerts and sales in separate marketing templates.

Stores that ship abroad have customers in other time zones and languages. Order updates in the customer's language and an automatic acknowledgement of questions at any hour matter more for them, and delivery estimates should include customs time honestly.

When a courier marks a delivery as failed — customer unavailable, address not found — the store has a day or two to fix it before the parcel heads back. A WhatsApp message to the customer asking to confirm a new time or correct the address, fed back to the courier, rescues many of these orders.

Stores selling to shops and resellers handle bulk orders, price lists, credit terms and invoices. A thread with each trade buyer keeps orders, proforma invoices and dispatch updates together, separate from retail customers.

On a big sale day, orders and questions arrive in hours rather than days. Check before the sale that templates are approved, the platform triggers fire, the returns and offer rules are current, and support staff have the shared inbox open. Automated order updates carry most of the load; staff handle exceptions.

Order invoices can be sent as PDFs on delivery, with GST details for business buyers. Payment links for unpaid orders and COD-to-prepaid switches go in the chat. Keep payment messages separate from marketing and send them only to the customer's own number.