WhatsApp Marketing for Retail and Ecommerce: Campaigns That Sell
How retail and ecommerce run WhatsApp campaigns that sell: festive sales, back-in-stock, cart recovery, reorder reminders and loyalty - with templates.
Retail runs on events: the drop, the restock, the festive window, the season change. WhatsApp is the fastest way to tell the customers who care about exactly that event - and the only one where the message can be answered with an order in the same thread.
This guide is the retail system: the six campaigns that carry a store, templates per campaign, the segmentation that predicts what customers want to hear about, and the festive playbook that makes your biggest month your calmest.
Why retail and WhatsApp match
The channel’s properties line up with retail’s rhythms one by one.
Speed to the customer. A restock is perishable; the customers who wanted it should know within the hour. Campaign queues with live controls make the announcement a same-day move.
Rich media, native rendering. Catalogs, lookbooks, and single product shots arrive in the chat itself - images re-encoded per recipient so thousands of sends do not share one identical file, and PDF catalogs for the detail.
The conversation is the checkout. “Is the M in stock?” - “Yes, shall I keep one?” - is a sale. No channel besides WhatsApp lets a campaign become a transaction without leaving the thread.
Receipts. Delivered and read acknowledgements tell you the drop landed, per customer - the health report reads them back to you.
The six campaigns that carry a store
| Campaign | Trigger | Segment |
|---|---|---|
| Festive and seasonal sale | Calendar | Full active list, by tier |
| New arrival / drop | Inventory | Category buyers |
| Back-in-stock | Restock event | The waitlist for that item |
| Cart recovery | Abandonment, 24-48h | The cart’s owner |
| Reorder reminder | Usage cycle | Consumable buyers |
| Loyalty early access | Before public launch | Top tier only |
Four are event-triggered and expected; two are promotional. That ratio is why retail lists stay welcome where pure promo lists burn out - the deliverability pillar explains the engagement math behind it.
Templates, per campaign
Festive sale:
{Hi|Hello} {name}! {Diwali|Festive} sale is {live|on}: {flat 25% off| 25% off everything} {till Sunday|through the weekend}. {Shop: {link}|Show this message in store.} (Reply STOP to opt out.)
New arrival:
{Hi|Hey} {name} - {just in|fresh drop}: the new {winter collection| linen range} {landed today|is on the floor}. First look attached. Reply HOLD to keep one aside for you.
Back-in-stock:
{Good news|Great news}, {name}! {The|Your} {product} is {back|available again} - {only a few units|limited stock}. Yours here: {link}
Cart recovery:
{Hi|Hello} {name}, your cart is {still waiting|saved}: {items}. Checkout takes a minute: {link}. (Reply STOP to opt out.)
Reorder reminder:
{Hi|Hello} {name}, your {product} is {probably running low|about to run out} around now. {Reorder in one tap|Restock here}: {link}
Loyalty early access:
{Hi|Hello} {name}, as a {top customer|VIP} you get {24 early hours|first pick} on the {sale|new collection} - before everyone else: {link}
Segmenting by what they bought
The predictive column in retail is the last category purchased: the customer who bought running shoes wants the drop of running gear, not the saree sale. At import, carry category, recency, and spend tier as columns; build lists per category; send drops to the category’s list and festive sales to everyone active.
Two retail-specific rules keep the number healthy. Suppress the refunders quietly - returns happen; a contact who returned everything and went quiet belongs on the dormant list, not the promo list. And cap the festive overlap - a contact in the festive list, the loyalty list, and two category lists should still receive one message on Diwali, not four. Per-contact caps beat per-list enthusiasm; the segmentation guide shows the columns that make it enforceable.
The festive-season playbook
The biggest selling month is where pricing models betray retail: on metered platforms, your best month is your biggest bill. On flat yearly pricing it is not - which changes behavior in a subtle way. Stores on flat plans run the extra Diwali blast, the day-of reminder, the last-hours message, because none of it costs more than the campaign they sent in March.
The season itself, in four sends: the teaser to loyalty (early access), the launch to everyone active, the mid-window reminder to non-openers of the launch, and the last-day note - each spaced inside quiet hours, each with its timing matched to when your customers browse.
The reorder calendar by product type
Reorder reminders are only welcome when the timing matches the product’s real usage cycle, and that cycle is knowable:
| Product | Typical cycle | Reminder timing |
|---|---|---|
| Supplements / consumables | 30-45 days | Day 30 |
| Skincare routines | 60-90 days | Day 60 |
| Groceries / staples | 2-4 weeks | Week 3 |
| Apparel | Seasonal | Season change |
| Electronics accessories | 6-12 months | Month 9 (soft check-in) |
One usage-cycle column in the CSV turns this calendar into campaigns the customer is grateful for - you remembered what they would otherwise forget, which is the most welcome message in retail.
What to measure after each campaign
Four numbers, in the order they repay attention:
| Metric | What it tells you | Where it lives |
|---|---|---|
| Read rate | Whether the segment matched the offer | Read acknowledgements, per campaign |
| Reply and tap count | Whether the message asked for an action worth taking | The chat thread; UTM-tagged links |
| Show-this-message redemptions | Whether the campaign moved footfall, not just thumbs | The counter, at redemption |
| Opt-outs and blocks | Whether the calendar is drifting too fast | The suppression list’s weekly delta |
The discipline that makes these numbers compound: record them beside the campaign - segment, hour, offer - and read them as comparisons, not absolutes. Your back-in-stock reads against your festive reads, this Diwali against last Diwali, the loyalty early-access against the public launch. Three seasons of that ledger teaches a store more about its customers than any benchmark report, and the playbook’s measurement section generalizes the habit.
Keeping the number welcome
Retail’s temptation is volume, and the number’s survival depends on restraint the tooling should enforce: consent collected at checkout and the counter (the opt-in guide has the wording - and under laws like India’s DPDP Act, the records are the store’s proof), STOP honored instantly across every campaign, and warm-up ramps for any new number rather than a festival-day launch. Run on dedicated infrastructure so a neighbor’s festive spam never taxes your sending, and the list compounds the way retail lists should - every season bigger, and every season happier to hear from you.
The Automate overview is two minutes, the plans start at $180 a year flat, and the campaign library has every template above with its spintax written.