WhatsApp Bot for Shopify & WooCommerce: 5 Store Workflows

A WhatsApp bot can add a direct conversation layer to a Shopify, WooCommerce, or Wix store. The five workflows below cover cart reminders, order updates, post-purchase offers, review requests, and support. Each one needs consent, attribution, and a measurable baseline.

WhatsApp and Email Serve Different Jobs

Email remains useful for newsletters and longer campaigns. WhatsApp is a direct conversation channel with separate consent, template, quality, and provider rules. Compare delivery, response, completed orders, opt-outs, and support workload using the store’s own data instead of a generic open-rate claim.

“About 70% of online shopping carts are abandoned before checkout.” — Baymard Institute, Cart Abandonment Statistics (their rolling average across 49 studies)

The smart move isn’t to ditch email — it’s to add WhatsApp on top of what’s already working. See our WhatsApp automation guide for the broader patterns.

Scenario 1: Cart Abandonment Recovery

The problem: A customer adds items and leaves before completing checkout. According to Baymard Institute’s rolling compilation, cart abandonment is common across ecommerce studies, but each store should use its own checkout data as the baseline.

WhatsApp solution:

1. At checkout start, ask the customer to enter their WhatsApp number (optional) → agree to receive order updates
2. If they abandon before completing → bot sends a Utility message after 30 min: “Hi [name], saw you added [item] but didn’t finish. Want to complete? [link]”
3. If there is no reply, send a Marketing message later only if the customer explicitly agreed to marketing; a store may include a time-limited offer under its own promotion rules

Integration:

• Shopify webhook carts/update (an automatic notification your store sends when a cart changes) → n8n → timer → if 30 min without order → send WhatsApp
• WooCommerce hook woocommerce_cart_updated → same flow
• Wix Velo function → same flow

What to measure: eligible carts, reminders delivered, completed orders linked by a documented attribution window, discounts, refunds, message fees, and opt-outs. A reminder sent before a purchase does not prove it caused the purchase.

Scenario 2: Order Updates (Utility — cheap and compliant)

The problem: A customer buys something, then hears nothing. The “Shipped” status on your website tells them nothing useful — they still don’t know where the package is or when it’s arriving.

Solution:

1. Order created → WhatsApp Utility: “Thanks [name]! Got order #[order_id] for $[total]. You’ll get an update when it ships.”
2. Order fulfilled → WhatsApp Utility: “Your order is on the way! [tracking_url]”
3. Order delivered (if carrier supports it) → WhatsApp Utility: “Your order arrived. If something’s wrong — just reply here.”

Cost and measurement: use Meta’s official WhatsApp pricing for the current market and category. Track delivered updates, related support contacts, cancellations, and staff handling with the same definitions used before launch.

Scenario 3: Post-Purchase Cross-Sell

The problem: A store may have complementary products but no documented post-purchase flow. Any promotional follow-up needs explicit consent and clear frequency limits.

Solution:

1. After delivery → WhatsApp: “[name], how’s your [item] working out? I have a related item you may find useful. If you opted in to offers, you can view the current promotion here: [link]”
2. If positive reply → cross-sell 2 more matched items

What to measure: eligible recipients, messages delivered, clicks, attributed completed orders, discounts, refunds, opt-outs, and message cost. Keep the attribution window fixed.

Same idea, different channel: in the affiliate bot I built on Telegram, a group member asks for a product in free text and the bot returns recommendations with affiliate links.

Scenario 4: Automated Reviews Collection

The problem: Most customers don’t leave reviews, even when they’re happy. The store ends up relying on the same 10-15 reviews that were written two years ago.

Solution:

1. 14 days after delivery → WhatsApp: “[name], want to share how it went with [item]? One click here and it helps us a ton: [link to review form]”
2. If high rating (4+) → “Thank you. Would you share this on Google? [link]”
3. If low rating (3-) → “Thanks, important for me to understand what wasn’t great. Can we chat? [link to chat]”

What to measure: requests delivered, responses, public reviews, opt-outs, and complaints. Do not assign a sales or conversion value to a review unless the store has its own attribution evidence.

Scenario 5: Returns / Support Chat

The problem: A customer has an issue, but the support request may sit in a separate inbox without order context or a clear owner.

Solution:

1. Bot checks approved FAQ content first and records whether the issue needs a person
2. If customer wants a human — routes to support agent with full history already loaded (name, order, item, status)
3. Agent responds in the configured channel with the order context available

What to measure: conversations resolved by the approved flow, human handoffs, response-time distribution, repeat contacts, refunds, and customer feedback.

The 5 scenarios side-by-side — effort, cost, and where ROI shows up first

Quick read: Start with Scenarios 2 (Utility) and 4 (Reviews) — lowest legal risk, lowest build effort, fastest signal. Layer Scenarios 1 and 3 once opt-in volume is healthy. Scenario 5 is the last one to add because it touches human workflows.

How to start — 3 practical steps

Step 1: Technical integration

1. Connect WhatsApp Business API — via Meta Cloud API (Meta’s official channel) or WAHA (self-hosted alternative)
2. Connect your store — Shopify/WooCommerce/Wix via webhooks (automatic notifications the store sends when something happens)
3. Set up n8n workflows — 5 automated flows, one per scenario
4. Message templates — Utility (3-4) + Marketing (2-3) submitted for Meta approval

Step 2: Opt-in flow in the store

Add a checkbox at checkout: “I want to receive order updates via WhatsApp” (legally OK without extra opt-in if it’s status only) + separate checkbox “I also want sales and discounts”

Step 3: Launch + iteration

• Limited rollout: the store agent monitors every selected flow
• Analysis: review completion, failure, attribution, and opt-out data
• Iteration: change one timing, template, or rule at a time and measure again

Warnings — what NOT to do

🔴 Don’t send Marketing without explicit opt-in — most countries have anti-spam laws with serious fines (e.g. Israel’s Amendment 40 to the Communications Law). Only Utility (order status) is typically OK automatically.

“Businesses must obtain users’ opt-in before sending them messages. Opt-ins must clearly state that a person is opting in to receive messages from the business over WhatsApp.” — WhatsApp Business Messaging Policy, Meta

🔴 Don’t turn WhatsApp into a spam channel — Meta documents a quality rating for business numbers and may limit or block messaging when quality falls. Set frequency from consent, relevance, and actual complaint data rather than a universal threshold.

🔴 Always offer easy opt-out — in every Marketing message: “Reply STOP to unsubscribe”. Required by law.

🔴 Don’t blast all customers at once — start with 100 customers, see results, then expand. A bot that performs poorly damaging experience for 1,000 customers at once is a disaster.

Want integration for your store?

Send a message on WhatsApp — we’ll talk about:

1. Which platform you use (Shopify/Woo/Wix/other)
2. Roughly how many orders/month
3. Biggest pain point (cart abandonment? support? leads?)
4. Tailored quote

Start with an introductory call to map the current process.

Related reading

• WhatsApp bot cost 2026 — full pricing — what basic vs advanced scenarios cost
• WhatsApp Bot for Business: complete guide — patterns by industry and business size
• WhatsApp automation guide — broader automation patterns beyond ecommerce
• Chatbot for customer service — handling support at scale
• WhatsApp Bot ROI framework — how to calculate results from a measured baseline
• Should you build a WhatsApp bot at all? — the 5-question test before you start