WhatsApp Business API for Indian D2C

WhatsApp Business API connects a store's customer and order events to WhatsApp messaging. For an Indian D2C brand, use it to send accurate order updates, handle replies in a shared support workflow and follow up with relevant offers. Start with order status and support, then add cart recovery and repeat-purchase messages once consent and purchase exits work.

Budget per delivered message. Meta replaced conversation billing on 1 July 2025, according to its Business Platform FAQ. A Business Solution Provider, or BSP, adds its own charges for software and message handling. Compare the full bill before choosing the provider.

What is WhatsApp Business API?

The API is the programmatic route to the WhatsApp Business Platform. It connects messaging to a store, customer database and support system. The WhatsApp Business app suits manual conversations; the Platform suits a team that needs events to trigger messages and replies to reach the right person.

Choose it when a clear operational problem needs solving. Perhaps dispatch updates require manual copying, recovery messages continue after purchase, or support staff cannot see which order a reply concerns. Write down that problem before comparing inbox features.

A shared inbox, campaign builder and ecommerce connector are usually parts of the provider's product. Inspect them during selection. Ask a staff member to find an order, reply to the customer and suppress a promotion in the proposed workflow. That exercise reveals more than a feature checklist.

WhatsApp Business API pricing in India

Meta's pricing page explains that charges depend on delivery, recipient market and message category. The India figures below come from Meta's INR rate-card PDF hosted by Gupshup, effective 1 October 2026 and checked 6 November 2026. They are Meta list rates, with provider fees and applicable taxes added separately.

The card also lists authentication-international at ₹2.4971. Check the applicable authentication classification if the sending business operates across countries.

Meta's FAQ pricing section dates the service-message change to 1 October 2026: each business phone number receives 1,000 free service messages monthly, then charges start with the next service message. Gupshup's October implementation update confirms that utility templates inside the customer service window also became chargeable.

Use the dated rate card when comparing quotes. A quote described as “per conversation” needs its billing unit explained: ask whether that means a provider session fee, message handling or Meta delivery. Record how inbound messages, agent replies and failed deliveries affect the invoice.

Separate BSP pricing from Meta delivery fees

A provider quote should split Meta delivery, software subscription and usage charges. Ask which inbox seats, store connections, automation features and support services are included. Check whether the provider adds a markup to Meta's card or charges a separate handling fee.

For a published BSP example, Twilio's WhatsApp pricing, marked current as of September 2026 and checked 6 November, lists US$0.005 for each inbound or outbound message, plus Meta fees. Keep that fee in its quoted currency when comparing proposals; use your invoice's conversion terms for a rupee budget.

A free Meta allowance can coexist with a provider handling charge. Ask the provider to price the same planned mix of service and promotional traffic, then show the applicable tax treatment. Have the quote state what happens when usage exceeds the plan.

Worked example with assumed volumes: a store delivers 10,000 marketing messages and 4,000 utility templates at the India list rates above, outside any free entry-point treatment or volume discount. The Meta delivery subtotal is:

Add service and authentication usage, the provider's plan and handling charges, and applicable taxes to produce the full budget. Reducing irrelevant marketing sends is a direct saving because each delivered promotion has a delivery charge.

How to set up WhatsApp Business API integration

Meta's Developer Hub provides the direct setup route, test resources and webhook documentation. Its Platform FAQ also explains the partner route. For a store without a team maintaining messaging software, choose a BSP with a working store connector and shared inbox.

1. Keep ownership with the business. Use business-controlled administrator accounts and a phone number the business can retain. Confirm the account owner, billing party and migration route before accepting a provider contract.
2. Complete the provider or direct setup. Prepare the business details, website and support contact. Follow the selected route's number registration and verification prompts. If the number already serves customers, agree the migration or supported coexistence process before changing it.
3. Connect events and consent. Map order creation, dispatch, cancellation and purchase completion. Save the signup wording, source and permission status with the contact. Give support a way to update exclusions.
4. Submit message templates. Match the content to its category and use the fields your store actually provides. Preview missing tracking links and unavailable product variants before submitting.
5. Route incoming replies. Assign a support owner, make the order context visible and create a clear escalation path. A reply about a damaged parcel should pause the relevant promotion.
6. Run staff tests before enabling customer sends. Use labelled test orders and staff-owned contacts. Inspect delivery status, message content, purchase exits and opt-outs through the complete integration.

For a direct Cloud API integration, assign an engineering owner for webhook processing, retries, access control and monitoring. For a BSP, ask who fixes a connector when an event changes. Keep a record of the event mapping so the next flow uses the same definitions.

What should an Indian D2C store send?

Give each message a trigger, a reader benefit and an exit. Meta's category descriptions put abandoned cart reminders and offers under marketing, while utility content concerns a specific transaction or request. Keep promotions out of order-status templates.

Example dispatch copy: “Your order has shipped. Use the tracking button to see its progress. Reply here if the tracking details need a check.” Populate it from the shipment event and submit the final template through the selected provider.

For recovery, check stock and purchase status immediately before sending. The abandoned cart recovery guide gives the sequence and test cases. For repeat purchases, group customers by the product they bought and adjust for pack size. Use the retention strategy guide to choose the next useful offer.

Keep email and WhatsApp on the same contact calendar. Give a checkout reminder priority over a generic promotion, and pause sales messages when support is resolving an order. The ecommerce email plan provides a flow map you can apply across both channels.

Check permission, replies and purchase exits

The WhatsApp Business Messaging Policy, updated 23 September 2026, requires contact details and opt-in permission for subsequent contact. It requires approved templates to initiate conversations. Free-form replies are allowed during the 24-hour customer service window, which resets with a user message; outside it, use approved templates.

Store the permission record where the automation can read it. Let the customer decline optional marketing and honour stop requests across the connected systems. A phone number supplied for an order needs the appropriate permission record before it enters a promotional flow.

Test a purchase during the delay, an opt-out before the send and a reply requiring support. Confirm that each reaches the intended exit. Test duplicate shipment events so the same update reaches the customer once. Keep the workflow paused if purchase or permission changes fail to reach the messaging platform.

Measure the full messaging bill and settled orders

Review delivered messages by category beside the provider invoice. Investigate category changes, duplicate events and campaigns that reach customers with a recent purchase. Compare the billed currency and unit with the signed quote.

For promotional flows, measure settled orders and contribution after discounts, returns, delivery and messaging charges. Keep essential service updates in place when testing a promotional holdout. Record the audience, offer and timing for each version so the next review can connect the result to a specific change.

Put a monthly spend limit and a named owner on campaigns. Before broadening the audience, read replies and opt-outs alongside orders. If customers repeatedly ask the same delivery question, repair the checkout information and dispatch messages before adding another reminder.