E-commerce

Shopify WhatsApp Order Notifications: The Complete Guide for Indian Stores

The six WhatsApp messages every Shopify store should send, from order and COD confirmation to delivery and abandoned cart, with templates.

By the Repeat Grow team · · 9 min read

A Shopify order turning into WhatsApp messages: order confirmed, shipped and delivered

Your customer just paid. Now they wait and wonder. Is the order confirmed? When will it ship? Where is it now? Most stores answer those questions by email, but for a lot of Indian shoppers the inbox they actually check is WhatsApp. This guide covers exactly which WhatsApp messages a Shopify store should send, what each template should say, the rules that keep your number in good standing, and how to automate the whole thing in about fifteen minutes.

Why order updates belong on WhatsApp

Order updates are the messages customers want. They reduce “where is my order?” calls and chats, they make cash-on-delivery customers more likely to accept the parcel, and every message is a chance to bring the customer back. Sending them on WhatsApp has three practical advantages:

The 6 messages every store should send

Map your WhatsApp messages to the moments Shopify already tracks. Each one is triggered by a Shopify event, so once it's set up nobody on your team has to press send.

Timeline of six WhatsApp messages: abandoned cart, order placed, COD confirmation, shipped, out for delivery, delivered
The six WhatsApp moments in a Shopify order, and which template category each uses.
MessageShopify eventCategory
Order confirmationOrder creationUtility
COD confirmation (Confirm / Cancel buttons)Order creation, cash on deliveryUtility
Shipped, with courier and tracking linkFulfillment creationUtility
Out for deliveryFulfillment update (carrier status)Utility
Delivered, with a review requestFulfillment update (carrier status)Utility
Abandoned cart reminderCheckout creation / update, then idleMarketing

You don't need all six on day one. Start with the order confirmation and the shipped message. They answer the two questions customers ask most, then add the rest.

Template examples you can copy

Business-initiated WhatsApp messages must use a template that Meta has approved. Variables like {{1}} are filled from the order each time. Keep templates short, specific and clearly about the order; that's what gets them approved as Utility. (More on approvals in WhatsApp template rules explained.)

order_confirmationUtility

Hi {{1}}, thanks for your order {{2}}! 🎉 Total: {{3}} We'll message you here when it ships. View your order: {{4}}

order_shippedUtility

Good news, {{1}}, order {{2}} is on its way with {{3}}. Track it here: {{4}}

order_deliveredUtility

Your order {{1}} has been delivered. We hope you love it, {{2}}! Reply here if anything isn't right.

cart_reminderMarketing

Hi {{1}}, you left something in your cart 🛒 {{2}} Complete your order here: {{3}}

In Repeat Grow you map each {{n}} to a store value (customer first name, order number, total, items, tracking link, courier, order status link or checkout link) and see a live preview before switching the message on.

COD confirmation: fewer refused deliveries

Cash on delivery is popular in India, and every COD parcel that comes back unaccepted costs you shipping both ways. A COD confirmation message asks the customer to confirm the order before you ship it:

cod_confirmationUtility

Hi {{1}}, please confirm your cash-on-delivery order {{2}} for {{3}}. [ Confirm order ] [ Cancel ]

Add two quick-reply buttons to the template. When the customer taps one, the reply lands in your inbox and can trigger an automation, for example, tag the contact “COD confirmed” or alert your team to call the ones who cancelled. Ship the confirmed orders first; follow up on the silent ones before dispatch.

Rules to follow (so your number stays healthy)

How to set it up with Repeat Grow

  1. Connect WhatsApp. Sign up and connect your number on the official WhatsApp Business API in Settings → WhatsApp.
  2. Create your templates. In Settings → Templates, create the templates above (Utility for order updates, Marketing for cart reminders) and submit them to Meta.
  3. Connect your store. In Settings → Shopify, click Connect Shopify, or choose Connect with webhooks and paste your store's webhook signing key. Repeat Grow lists exactly which webhooks to add.
  4. Map each event. Switch on the events you want, pick the approved template, choose what fills each variable, and use Send test to see the real message on your phone.
  5. Watch it work. Every message appears in your shared inbox and in the “Recent messages” log, with a reason if anything was skipped.

Selling to other industries too? See how teams use WhatsApp CRM for e-commerce, and the Shopify section of the Help Center.

Launch checklist

Frequently asked questions

Can I send Shopify order updates on WhatsApp without an app on my store?

Yes. Shopify can send webhooks (Settings → Notifications → Webhooks) to a WhatsApp CRM like Repeat Grow, which turns each event into an approved WhatsApp template. A one-click app connection does the same without creating webhooks by hand.

Do I need the official WhatsApp Business API?

For automated, business-initiated messages at scale, yes. The official API (Meta Cloud API) lets you send approved templates to customers, track delivery and read status, and avoid the ban risk of unofficial automation tools.

Which template category should order updates use?

Order confirmations, shipping, delivery and cancellation messages are Utility templates: they update the customer about something they already did. Abandoned-cart reminders and offers are Marketing templates and need the customer’s opt-in.

What if the customer typed their number without +91?

Indian checkouts often store numbers like "98765 43210". A good integration adds the country code from the shipping address (or your store’s default) before sending, so the message still reaches the customer.

Will customers get the same message twice?

They shouldn’t. Shopify retries webhooks if it doesn’t get a quick response, so the integration must de-duplicate each event. Repeat Grow records every delivery and every send, so retries never produce duplicates.