WhatsApp for Ecommerce: What to Automate and How to Stay Compliant

Ecommerce is the vertical where WhatsApp economics work hardest, because the volume is high, the events are already instrumented, and the difference between wholesale conversation rates and a marked-up per-message price compounds fast at scale.

Abandoned cart recovery

The highest-return automation you can build. A cart-abandoned webhook triggers a marketing template after a delay you choose — typically an hour, then a second touch the next day — carrying the product name, the price and a deep link back to the checkout. Because the reply arrives in a real thread rather than a no-reply mailbox, "is the blue one still available?" becomes a conversation an agent can close. Build it in automations and track click-through with the link shortener.

Order and delivery updates

Confirmation, dispatch, out-for-delivery, delivered. Utility templates keyed to your order state machine, sent to the number the customer already checks. This is the cheapest support deflection available: "where is my order?" is usually the single largest ticket category, and it disappears when the answer arrives unprompted. Utility conversations are also the cheapest category in Meta's pricing.

Catalogue and in-chat purchase

A connected Meta catalogue lets an agent or an automation send single-product or multi-product messages, with the customer building a cart inside WhatsApp and returning it as an order message. Pair that with payments — UPI in India, Pix in Brazil, or a Stripe payment link elsewhere — and the path from question to paid order never leaves the thread. Setup is covered in the catalog docs.

Post-purchase and win-back

Review requests a week after delivery, replenishment nudges on a consumption cycle, back-in-stock alerts for the size someone asked about. Segment these from your contact data rather than blasting the list — WhatsApp punishes irrelevance with blocks, and blocks drive your quality rating down, which throttles your sending limits.

The compliance note

Capture marketing consent separately from the transactional relationship, at checkout or through a QR or form, and record it. Honour opt-out immediately at send time. Order-status messages generally rest on contract performance rather than consent, but Meta's opt-in requirement still applies. The detail is in opt-in and opt-out requirements.

Why ownership matters at ecommerce volume

Most platforms add a per-message fee on top of Meta's conversation price. At a few thousand messages a month that is noise; at ecommerce peak volumes it becomes one of your larger line items, and it scales with your success rather than with the vendor's cost. An owned instance passes Meta rates through and charges for the platform, not per message — the arithmetic is in the WhatsApp pricing guide. You also keep the order and contact history in your own EU database rather than a shared tenant.