WhatsApp marketing is now part of Shopify Messaging. Build campaigns from templates or your own branded content, and drive customers to act with media from your product catalog, interactive buttons, and keyword replies. Pricing is usage-based — you pay only for what you send.
WhatsApp joins Shopify Messaging as a destination for sending marketing and promotions.
The announcement's wording is "serve customers globally." No list of supported countries is given.
It's positioned not just as customer support but as promotion and sales driving — a way to send marketing campaigns.
| Aspect | WhatsApp marketing pricing |
|---|---|
| Billing unit | Usage-based Pay only for the messages you send |
| Peak season | Scale campaigns up (flexible pricing) |
| Slow season | Scale down as needed |
| Unit price / minimum spend | Not stated The post gives no specific pricing figures |
| Eligible plans | Not stated |
WhatsApp marketing ships as part of Messaging. The post doesn't say where exactly it lives in the admin.
Start from a ready-made template or build with your own brand content. Drop in media from your product catalog.
Decide what happens when customers tap or reply, then send. See the Shopify Help Center for detailed setup steps.
"WhatsApp marketing is now part of Shopify Messaging" — it rides on top of the existing Shopify Messaging. Design for it as an extension of channels you already operate, not as the adoption of a separate service.
Images and other media for campaigns are pulled in from the product catalog.the cleanliness of your product data (image quality, naming, variant organization) becomes the quality of what you send, so getting the catalog in order is an upstream step.
"Button clicks" and "keyword replies." The former is easier to reason about because the options are constrained; the latter is free-form input, so comprehensive keyword coverage and handling of wording variationsbecome necessary.
Usage-based pricing: you pay for what you send. If you can forecast send volume you can forecast cost, but conversely misdirected or duplicate sends translate directly into losses. Build test sends and volume caps into your workflow.
This announcement covers only the admin-facing feature, andsays nothing at all about Admin API, Webhook, or Flow integration, consent requirements for sending, or supported countries. For projects that assume automation or require legal review, always confirm in the Help Center and in the actual admin before including it in a proposal.