Experience Lion CRM — The King of WhatsApp CRM 7 Days Free Limited Access
→ Request Access

WooCommerce WhatsApp Integration: The Complete 2026 Guide

WooCommerce WhatsApp integration in 2026: click-to-chat vs real API automation, the WP-Cron trap that silently breaks cart recovery, and true costs.

Search for a WooCommerce WhatsApp integration and you get a wall of plugins. Free ones, paid ones, a few with tens of thousands of installs, several on WooCommerce’s own marketplace. It looks like the easiest integration decision you will make all year. Pick a popular plugin, install it, done.

It is not that, and the reason is hiding in plain sight on that results page. The plugins listed there are not competing products. They are two entirely different products with the same name on the box.

Half of them put a WhatsApp button on your store so a shopper can tap it and start a chat with you. That costs nothing, needs no approval from anybody, and takes about ten minutes. The other half connect your store to the WhatsApp Business Platform so it can send order confirmations, dispatch alerts and cart reminders automatically. That one needs a Meta business account, approved message templates, per-message billing, and a working background job queue on your own server.

A store owner who wanted the second thing and installed the first will spend a fortnight wondering why no automated messages are going out. It is the single most common way this project goes wrong, and it goes wrong before anybody has written a line of configuration.

This guide separates the two properly, then goes into what almost nothing else ranking for this topic covers: what changes when the store is self-hosted. WooCommerce has no app tax and no platform gatekeeper, which makes it genuinely cheaper than the hosted platforms. It also hands you the plumbing, and the plumbing is where timed WhatsApp automations quietly die.

In this guide

The two things both called a WooCommerce WhatsApp integration

Get this distinction straight and most of the confusion in this topic disappears.

Click-to-chat. A link or button that opens WhatsApp with your number pre-filled, usually with the product name or cart contents dropped into the message body. Some versions replace the checkout entirely, so the customer taps “Order on WhatsApp” and their basket arrives in your inbox as a text message. This uses no API. It costs nothing per message. It works with the free WhatsApp Business app on a phone. Setup is a plugin install and pasting in your number.

For a small store selling a handful of orders a day, mostly through conversation, this is not a compromise. It is the right answer, and it is a genuinely popular one in India, Indonesia, Brazil and the Gulf. Nobody should be talked into an API project when a click-to-chat button covers the requirement.

The WhatsApp Business Platform, still widely called the API. Your store sends messages by itself, in response to store events, with no human tapping anything. Order confirmed. Payment received. Dispatched with a tracking link. Cart abandoned ninety minutes ago. It also gives you a shared inbox where several agents work one number, which the phone app cannot do.

This one needs a Meta business account, a phone number dedicated to it, message templates submitted for review, and a billing relationship for the per-message charges. Setup is days rather than minutes, mostly spent waiting for approvals.

The tell, when you are looking at any plugin listing, is whether the page talks about templates and approvals. If it never mentions them, it is a click-to-chat plugin no matter how it is titled. Automated messaging on WhatsApp cannot exist without approved templates, so a product that does not discuss them is not doing it.

One more thing worth naming early, because it catches people at the worst moment. A phone number can be on the WhatsApp Business app or on the API, never both. Moving a number from the app to the API means removing it from the app first, and the chat history on that device goes with it. Stores discover this on the day they try to connect, having used that number for two years. Plan for a second number, or export what you need before you start.

What a real integration actually does

Strip out the marketing and there are five distinct jobs people mean when they say they want WhatsApp on WooCommerce. They have different costs, different setup work and different failure modes, and picking a tool before you have picked your job is how stores end up paying for the wrong one.

Order and shipping notifications. WooCommerce already fires an event on every status change: order placed, processing, completed, refunded, plus whatever your shipping plugin adds when it gets a tracking number. Piping those into WhatsApp templates is the highest-value, lowest-risk job on the list. These are utility messages, which are the cheap category, customers genuinely want them, and delivery rates run far ahead of email. If you do only one thing, do this.

Cash-on-delivery confirmation. Specific to markets where COD is normal, and worth more than everything else combined in those markets. A WhatsApp message asking the customer to confirm before dispatch, with a yes or no button, cuts the return-to-origin rate that quietly eats Indian D2C margins. It is a small automation with a direct line to money.

Abandoned cart recovery. The headline feature and the one with the most exaggerated numbers attached to it. It works, it is worth doing, and the section below does the maths honestly rather than repeating a landing page.

A shared inbox. Several people answering one WhatsApp number, with conversations assigned to whoever owns them and the customer’s order history visible in the thread. The free Business app cannot do this at all. This is where a WhatsApp CRM starts to beat a notification plugin, and it is a requirement people forget to state until the second agent joins.

Broadcasts and campaigns. Sending an offer to your opt-in list. Marketing templates, the expensive category, and the one with the most rules attached.

There is a sixth possibility worth naming, because it fits more WooCommerce stores than anyone selling a plugin will admit. If WhatsApp is where your business actually happens and the store is mostly where the order gets recorded, the right tool is a WhatsApp CRM with WooCommerce connected to it, not a WooCommerce store with chat bolted on. If that sounds like your business, get the difference between a WhatsApp CRM and the raw WhatsApp Business API straight before you shop for anything.

The four ways to connect WhatsApp to WooCommerce

Route one: a click-to-chat plugin. Free or a few thousand rupees one-off. Ten minutes. No API, no approvals, no per-message cost. Covers pre-sale questions and, in the “order on WhatsApp” variant, replaces checkout for stores that sell conversationally. Does nothing automatic. Choose this if your requirement is a button, and be honest about whether it is.

Route two: a WhatsApp API plugin. A WordPress plugin that holds your API credentials and maps WooCommerce order events to approved templates. This is the mainstream answer and what most stores end up on. The plugin is usually a one-off licence or an annual fee, and the message charges are separate. Everything runs inside your WordPress install, which is both the appeal and the risk — see the next section.

Route three: a WhatsApp CRM or messaging platform with a WooCommerce connector. The platform lives outside your site and connects in, giving you a shared inbox, flow builder, contact management, campaign tools and analytics as well as the order notifications. Monthly subscription. This is the right route once more than one person is answering messages, once you want the conversation and the order in the same place, or once you are running several stores.

Route four: build it direct. WooCommerce webhooks or a small plugin calling Meta’s Cloud API yourself, with no vendor in between. Cheapest at scale because there is no software bill at all, and completely appropriate if you have a developer. You are then responsible for retries, error handling, template management, the inbound webhook and the inbox — which is to say you are building the plugin, and there is no inbox at the end of it unless you build that too. Worth it for a store with unusual logic. Rarely worth it just to save a licence fee.

An honest way to choose: if nobody needs an inbox and the requirement is notifications, route two is the best value on WooCommerce and it is not close. The moment a second person needs to answer the same number, route three stops being a luxury.

The self-hosted trap: you own the plumbing

This is the section that does not exist on the hosted-platform guides, because on Shopify it is not your problem. On WooCommerce it is entirely your problem, and it is the difference between a cart-recovery sequence that works and one that appears to be configured perfectly while sending nothing.

Timed messages do not send themselves. Something has to wake up ninety minutes after a cart is abandoned and decide it is time. In WooCommerce that something is Action Scheduler, the background job queue that also handles subscription renewals, coupon expiry, refund processing and a good deal else. Action Scheduler is solid software. What it depends on is not.

WordPress does not have a real scheduler. WP-Cron is a list of tasks that gets checked when somebody loads a page on your site. No visitors, no page loads, no checking, nothing runs. On a busy store this is invisible because there is always traffic. On a store doing thirty orders a day, particularly overnight and particularly in the small hours when a lot of carts are abandoned, the queue simply sits there until the next visitor arrives and wakes it up.

The failure mode is what makes this expensive. Nothing errors. No warning appears. Your ninety-minute cart reminder goes out seven hours later, addressed to somebody who bought the item elsewhere before breakfast, still costing you a marketing message. Order confirmations arrive after the parcel. Both look like the plugin working, just badly, and stores blame the plugin and switch to another one that has exactly the same dependency.

Check it before you blame anything. Go to WooCommerce, then Status, then Scheduled Actions. Look at the Pending and Past-due tabs. A handful of pending actions with recent timestamps is normal. A long list of past-due actions, or pending items scheduled for hours ago, means your queue is not draining and every timed feature you have configured is unreliable right now. Do this on day one of the project, not after the first failed campaign.

The fix is standard, permanent and takes ten minutes. Turn off the traffic-triggered version by adding define('DISABLE_WP_CRON', true); to wp-config.php above the “stop editing” line, then set a real server cron job in your hosting panel to hit https://yourstore.com/wp-cron.php?doing_wp_cron every five minutes. Every mainstream host has a cron section, and if yours does not, an external cron service does the same job. After that your scheduler runs on a clock instead of on hope.

Three related things bite on the same seam, and all of them are yours to manage on self-hosted:

Inbound webhooks have to reach you. Replies from customers arrive as a POST from Meta to a URL on your site. Aggressive security plugins, firewall rules, Cloudflare bot protection and some managed-host WAF defaults will block them. The signature is unmistakable: outbound messages send fine, inbound replies never appear. Whitelist the callback path before you conclude the integration is broken.

Caching does not know about your chat. Page caches and object caches are what make WooCommerce fast and are also what serve a stale cart to a session that has changed. If cart-recovery triggers fire against cached state, they fire on the wrong data. Exclude cart, checkout, my-account and any chat endpoint from caching, which your caching plugin already has a setting for.

Nobody is on the hook but you. No vendor monitors your uptime. If your host has a bad night, messages queue or drop and the first you hear of it is a customer asking where their order confirmation went. That is the genuine trade for having no platform fee.

None of this is difficult. It is simply work that a hosted platform does silently and WooCommerce does not, and it is the honest answer to why the cheapest platform on paper is not automatically the cheapest to run.

Before you start: what you need ready

Getting these lined up first turns a two-week project into a three-day one, because most of the delay is waiting for other people.

A Meta Business account with verification started. Business verification is the longest lead time in the whole project and it blocks the useful sending limits. Start it on day one. You will need your registration documents and a utility bill or bank statement showing the business address.

A phone number that is not on WhatsApp. Not on the consumer app, not on the WhatsApp Business app. If your only business number is already in use, either free it up and accept losing that device’s history, or buy a new number. A landline or toll-free number works if it can receive the verification call.

A display name Meta will approve. It has to relate plausibly to your business. Made-up names and keyword-stuffed names get rejected and the resubmission costs you days.

Clean phone numbers in WooCommerce. This one gets skipped and it breaks everything downstream. Matching a WhatsApp conversation to a customer happens on the phone number, so a leading zero, a missing country code or a stray space stops it. Export your customer and order data, normalise the billing phone field to full international format, and make the checkout field enforce it going forward. Doing this before you connect is an hour. Doing it afterwards is a data-migration project with live traffic on top.

Your scheduler already fixed. From the previous section. Do it now, before anything is timed, so you never have to work out whether a problem is the plugin or the queue.

A WooCommerce staging site. Every serious host offers one free. Test the plugin, the templates and the triggers there. Sending a test order confirmation to a real customer because you experimented on production is a bad first day.

Setting up WhatsApp on your WooCommerce store

The sequence below assumes route two or three. Route one is a plugin install and your number.

Step one: connect the number. Whether you are in a plugin’s setup wizard or a platform’s onboarding, this runs through Meta’s embedded signup: pick the business account, add the number, verify by SMS or call, set the display name. Ten minutes when the prerequisites are ready. A blocked afternoon when they are not, which is the entire reason for the section above.

Step two: install and authorise the plugin. Paste the API credentials, or complete the platform’s WooCommerce connection. Confirm the plugin can see your orders before you configure anything else — most have a test button, and the ones that do not will show a recent order in a dropdown.

Step three: add opt-in today. Do this before templates, before flows, before anything you consider the real work. A tick box at checkout saying the customer agrees to order updates on WhatsApp, plus a prompt on your chat widget. Opt-in coverage compounds from the day it goes live, and every day without it is audience you never get back. It is also the number that decides your cart-recovery revenue, as the maths below shows.

Step four: write and submit templates. Start with four: order confirmed, dispatched with tracking, delivered, and one cart reminder. Get the categories right, because that decides what they cost. Order updates are utility. Anything promotional is marketing, at roughly seven times the price. Submit early, since review takes anywhere from minutes to a day and nothing ships until they pass.

Step five: map events to templates. In the plugin, connect each WooCommerce order status to its template and its variables. Check the variable mapping on a real order rather than trusting the defaults. Order number, customer name and tracking link mapped to the wrong fields is the classic first-run bug and it is visible immediately if you look.

Step six: prove the inbound path. Message the business number from a phone and confirm the reply lands where it should — in the plugin, in the platform inbox, wherever you expect. Do it from a number that exists in your customer file and from one that does not, because customer matching fails differently in each case and you want to see both now.

Step seven: turn on one thing. Order dispatched only, on real orders. Watch delivery, watch replies, answer them. When that is boring, add the rest. Turning everything on at once means that when something misbehaves you have no idea which of six flows did it.

Abandoned cart recovery: the honest maths

This is why most stores start the project, so it deserves real numbers instead of the ones on plugin landing pages.

The headline figures are broadly true. WhatsApp cart recovery is reported in the fifteen to thirty percent range against roughly two to eight percent for email, on open rates near ninety-five percent, with most messages read within minutes. Those are not invented numbers.

They are also measured on a subset, and the subset is the whole story.

A recovery rate is calculated against the people who were messaged. To be messaged with a marketing template a customer must have opted in and left a usable phone number. Most abandoners have done neither. So the number that decides your revenue is not the recovery rate, it is the recovery rate multiplied by your opt-in coverage.

Work it through on a thousand abandoned carts a month. If thirty percent of your abandoners are opted in with a valid number, you can message three hundred. At a strong twenty percent recovery that is sixty orders back, which against the full thousand is an effective six percent. Real money, clearly worth doing, and about a third of the number on the plugin’s homepage.

Push opt-in coverage to seventy percent, which a checkout tick box and a widget prompt will do over a couple of months, and the same flow with the same recovery rate returns a hundred and forty orders. More than double the revenue, and the lever that moved it was consent collection rather than the plugin you chose.

Which is why comparing plugins on their claimed recovery rates is close to useless. They are all quoting the same industry range. Compare them on what actually differs: whether the sequence can send more than one reminder, whether it stops the moment the order completes, whether it attributes a recovered order back to the message so you can see the return, and whether it survives your scheduler being slow.

That last one is the WooCommerce-specific question and it is worth asking the vendor directly. A reminder that fires seven hours late because the queue was asleep is worse than no reminder — you pay for the message and you annoy someone who has already bought elsewhere. Ask whether the plugin uses Action Scheduler, what happens to a job that misses its window, and whether it will skip a stale reminder rather than send it anyway. Good ones skip. Most do not mention it.

On message economics: cart reminders are marketing templates, so they carry the higher rate. Three reminders to seven hundred people is two thousand one hundred marketing messages, which at Indian rates is under two thousand five hundred rupees including tax. Against a hundred and forty recovered orders that is trivial. The maths only turns bad when a store blasts a large unsegmented list and recovers nothing, which is exactly the behaviour Meta priced marketing templates to discourage.

What a WooCommerce WhatsApp setup costs in 2026

Here is where self-hosted genuinely wins, and it is worth being precise about why, because the saving is real but smaller than it first looks.

Bill one: WooCommerce itself. Zero. Core is free and there is no plan to upgrade, no transaction fee, and no feature held behind a tier. On Shopify this line is a monthly subscription and some WhatsApp capabilities are tied to it. This is a genuine structural advantage and it is why the platform comparison so often lands here.

Bill two: the plugin or platform. WooCommerce plugins are usually a one-off licence or a flat annual fee rather than a monthly subscription per store. Annual licences for capable WhatsApp API plugins commonly land in the region of eight thousand to forty thousand rupees a year depending on features and site count, and there are free tiers with small monthly message allowances that are fine for testing. A hosted WhatsApp CRM is a monthly subscription instead, typically priced per user, which buys you the inbox and flow builder the plugins do not have. Build it direct and this line is zero.

Bill three: Meta’s per-message charges. Unavoidable on every route because it is Meta’s charge, not the plugin’s. Since July 2025 Meta bills per delivered template message rather than per twenty-four-hour conversation. In India the rates are approximately eighty-six paise per marketing message and about eleven and a half paise for utility and authentication, before eighteen percent GST. Service messages inside the twenty-four-hour window after a customer writes to you are free.

Two things there matter more than the rates. Marketing costs roughly seven and a half times utility, which is the whole argument for getting template categories right on day one. And rates vary enormously by country, so a cost estimate from a US or European blog can be several times wrong for your market in either direction.

Bill four: markup on messages — and this is where WooCommerce is structurally different. On a hosted platform the app sits between you and Meta and can add a margin per message that you cannot escape without switching apps. On WooCommerce, plugins commonly connect your own Meta account directly, so Meta bills you at Meta’s rate and the plugin never touches the message economics. Not every plugin works that way, so ask the question before you buy: do I use my own WhatsApp Business account and get billed by Meta directly, or do messages route through yours? Your own account is the answer you want, and on WooCommerce you can usually get it.

Bill five: the one that is only yours. Hosting that can take webhook traffic, a real cron job, someone to look at Scheduled Actions when messages go quiet, and the time cost of a plugin conflict after a PHP update. Small in rupees, real in attention. This is the line that offsets some of what you saved on bills one and four, and pretending it is zero is how the comparison gets dishonest.

Put it together for a mid-sized Indian store sending fifteen thousand utility and five thousand marketing messages a month. Meta charges roughly seventeen hundred rupees plus GST for the utility volume and about forty-three hundred plus GST for the marketing, call it seven thousand all in. Add a plugin licence amortised at one to three thousand a month and the software bill is a fraction of the message bill. The number that moves your total is your marketing-to-utility ratio, not which plugin you picked.

If you are weighing this against a platform subscription you already pay for, the Lion CRM pricing page lists per-user costs for the CRM route, so you can compare a plugin licence plus your own operational time against a platform that includes the inbox.

Choosing a plugin without getting burned

WooCommerce’s plugin ecosystem is its greatest strength and the source of its most avoidable failures. A payment gateway that stops being maintained is a crisis you notice immediately. A WhatsApp plugin that stops being maintained is one you notice months later, when a WordPress update breaks it or Meta changes an API version and nobody ships a fix.

Six checks, none of which take more than a minute:

When was it last updated? On WordPress.org this is on the plugin page. Anything over six months on a plugin that talks to a fast-moving API is a warning. Meta deprecates Cloud API versions on a schedule, and an unmaintained plugin eventually stops sending on a Tuesday for no reason you can see.

Does it say which WordPress version it is tested up to? Trailing two or three major versions is a maintenance signal, not a compatibility one, and the maintenance signal is what you are buying.

Read the support forum, not the reviews. Reviews are gathered at install time when everyone is optimistic. The support forum tells you what breaks in month four and whether the developer answers. Unanswered threads going back a year is your answer.

Whose Meta account sends the messages? Covered above. Your own, ideally, so your billing and your quality rating are yours.

What happens to a late job? The Action Scheduler question from earlier. A vendor who has thought about it will have an answer ready.

Can you export? Templates, contacts, opt-in records, conversation history. If the plugin is the only place your opt-in list exists and it cannot export, you are locked in by your own data. Check before, not after.

One more, specific to self-hosted: install on staging and check for conflicts before production, particularly with your caching plugin, your security plugin and any other plugin that hooks order status changes. Two plugins both firing on woocommerce_order_status_completed is how customers get the same message twice.

What none of the routes will do for you

Some limits belong to WhatsApp itself, not to WooCommerce or any plugin, and paying more does not remove them.

You cannot message anyone who has not opted in. WhatsApp is not email. There is no cold outreach, no bought list, no legitimate broadcast to people who have not agreed. Your reachable audience is exactly your opt-in list.

Outside twenty-four hours, only templates. Once the window since the customer’s last message closes, free-form text will not send. Everything proactive has to be designed as a template from the start.

Templates are reviewed and review is not instant. You cannot ship a campaign this afternoon if the template does not exist yet. Build a small library before you need it.

Quality rating throttles you. Blocks and reports lower your number’s quality rating, and a low rating lowers your daily sending limit. It is entirely possible to spend a month building an opt-in list and lose the ability to message it by sending badly to it.

A plugin is not an inbox. Notification plugins send. They do not give three agents a shared workspace with assignment, internal notes and the customer’s order history in the thread. No setting turns one into the other.

Your WooCommerce data stays in WooCommerce. The conversation lives on WhatsApp and the customer record lives in your store, and a notification plugin does not merge them. If you want to see what someone bought while you are replying to them, that is a CRM job.

The customer sees the store’s brand, not yours as an agency. Fine for a merchant. A commercial problem if you build stores for a living, which is the next section.

The whitelabel route: selling this to clients

If you build WooCommerce stores for a living, the pattern here should be familiar. A client asks for WhatsApp. You evaluate plugins, install one, wire the templates, fix their phone-number data, fix their cron, test the flows, train the team, and bill for the project.

Then look at where the recurring money goes. The client renews a plugin licence to somebody else every year for something you built. You earned the implementation fee once. And you are the one who gets called when a WordPress update breaks the integration, because you are the one who installed it — support you do unpaid, on software that is not yours, for revenue that is not yours either.

There is a different shape available. Instead of configuring another company’s plugin for a one-off fee, you sell a WhatsApp CRM under your own brand, on your own domain, at prices you set, and keep the monthly margin. The client gets the shared inbox, the automations and the order-linked conversations they wanted. Your agency gets a subscription line that renews for as long as the client is happy, and the client never sees a vendor’s name.

It also solves a problem specific to WooCommerce work. When the messaging platform is hosted rather than a plugin on the client’s server, it is no longer hostage to their host, their cron, their caching plugin or whichever plugin they installed last Thursday. You stop debugging someone else’s WordPress install for free.

For agencies going that way, the requirements that decide whether it scales are unglamorous: your branding throughout with no vendor logo anywhere, the ability to create and manage client accounts yourself without raising a ticket, per-licence pricing you control, and a support path that never exposes the platform behind your brand. Lion CRM’s whitelabel programme is built around exactly that, starting at a minimum of ten licences with a reseller admin panel for running client accounts under your own name.

The commercial difference is the point. A WooCommerce WhatsApp implementation is a project with an end date. A branded platform is a subscription that pays every month you keep the client. Agencies weighing platforms to resell usually start with the whitelabel WhatsApp CRM comparison for India, which lays the options out side by side.

Common problems and how to fix them

Automated messages are not sending at all. Check Scheduled Actions first, every time. WooCommerce, then Status, then Scheduled Actions, then the Past-due tab. A backlog means your queue is not draining and the plugin is innocent. Fix the cron as described above before changing anything else.

Messages send, but late. Same cause, milder. A queue that only drains when a visitor arrives will always be late overnight, which is exactly when carts get abandoned.

Messages send but replies never arrive. A webhook problem, not a settings mystery. Outbound working while inbound is silent is the signature. On self-hosted the usual culprits are a security plugin, a firewall rule or a WAF blocking Meta’s POST. Whitelist the callback path, then confirm the verify token and the subscribed message fields in the Meta console.

The number will not connect. Almost always because it is still active on WhatsApp or the WhatsApp Business app. Delete it there first, accept that the on-device history goes with it, then retry. Second most common cause is unfinished business verification.

Conversations do not show the customer’s orders. Phone-format mismatch, nine times out of ten. Matching happens on the number, so a leading zero, missing country code or stray space stops it. Normalise the billing phone field across your whole customer file and retest with a number that already exists in WooCommerce.

Customers get the same message twice. Two plugins hooked to the same order status change, or an order status that flips back and forth. Disable the other plugin’s notifications and add an idempotency check if you built it yourself. Sending duplicates is a fast route to a damaged quality rating.

Templates keep getting rejected. Vague promotional wording, variables with no surrounding context, or a category that does not fit the content. Rewrite as something specific and genuinely useful, make every variable obviously meaningful, and resubmit. Write like a dispatch notification, not a banner ad.

Cart-recovery messages are not sending. Check opt-in before anything technical. The flow is usually working correctly and finding almost nobody eligible. If coverage is fine, check the trigger fires on cart abandonment rather than checkout abandonment — different events, and stores routinely wire the wrong one.

Everything broke after a WordPress or PHP update. The self-hosted tax. Roll back on staging, identify the conflict, and if the plugin has not been updated in a year, treat that as the real finding rather than the immediate error.

The bill is higher than expected. Almost always template categories. Pull a breakdown of marketing versus utility volume. Order updates sitting in the marketing category cost roughly seven and a half times what they should, and because each message is a fraction of a rupee nobody notices until the invoice arrives.

The team is not using the inbox. Not a technical problem. Either conversations are not reaching the right person or the tool does not match how the team works. Watch someone use it for an hour and the answer is usually obvious in ten minutes.

A 14-day rollout plan

Days 1 to 3: paperwork and plumbing. Start Meta business verification, because nothing ships without it and it is the longest lead time. Free up the phone number. Fix the cron and confirm Scheduled Actions is draining. Begin normalising the customer phone field. All of this runs in parallel and none of it blocks the rest.

Days 4 to 6: connect and prove. Complete the connection, get the display name approved, confirm a message travels both ways. Add the WhatsApp opt-in at checkout today rather than later, because coverage compounds from the moment it goes live.

Days 7 to 9: templates. Write and submit the first four: order confirmed, dispatched with tracking, delivered, and one cart reminder. Check every category assignment before submitting. While they sit in review, test the inbound path hard from numbers inside and outside your customer file and fix the matching failures it exposes.

Days 10 to 12: pilot on utility. Turn on order dispatched only. Real customers, real volume, no marketing. Watch delivery rates and watch the replies, because there will be replies and somebody must be answering them. This is where you find out whether your team is ready, at a point where the only thing at risk is a shipping notification.

Days 13 to 14: marketing and measurement. Switch on cart recovery and the first campaign. Record your baseline now: current cart abandonment rate, current email recovery rate, current first-response time, current opt-in coverage. In a month those four numbers are the only evidence of whether this worked, and nobody ever remembers what they were beforehand.

Frequently asked questions

Does WooCommerce have a native WhatsApp integration?
No. WooCommerce core has no WhatsApp feature, so every route goes through a plugin, an external platform or your own code. What it does have is an open extension model and no gatekeeper, which is why there are so many options and why nobody takes a cut of your messages the way a hosted app store can. The WooCommerce marketplace lists WhatsApp extensions, but those are third-party products sold there rather than anything built into WooCommerce itself.

What is the difference between a click-to-chat plugin and a WhatsApp API integration?
Click-to-chat puts a button on your store that opens a chat with your number, with the product or cart pre-filled. It is free, instant, needs no approvals, and works with the WhatsApp Business app on a phone. It does nothing automatically. An API integration connects your store to the WhatsApp Business Platform so it can send order confirmations, dispatch alerts and cart reminders on its own, and gives you a shared inbox for multiple agents. That needs a Meta business account, approved templates and per-message billing. Both are commonly labelled “WooCommerce WhatsApp integration”, which is why so many stores install the wrong one.

Why are my WooCommerce WhatsApp messages sending late or not at all?
Nine times out of ten it is WP-Cron rather than the plugin. WordPress only checks its scheduled tasks when someone loads a page, so on a low-traffic store the queue that drives timed messages can sit for hours, especially overnight. Check WooCommerce, then Status, then Scheduled Actions, and look for a backlog of past-due actions. The permanent fix is to add define('DISABLE_WP_CRON', true); to wp-config.php and set a real server cron job to hit wp-cron.php every five minutes. Do this before you evaluate any plugin, or you will be judging the plugin on your scheduler’s behaviour.

How much does a WooCommerce WhatsApp integration cost?
WooCommerce itself is free, so there are three real lines. The plugin or platform, which on WooCommerce is often a one-off or annual licence rather than a monthly subscription, commonly in the region of eight to forty thousand rupees a year, or a per-user monthly fee for a hosted CRM. Meta’s per-message charges, which apply on every route because they are Meta’s, at roughly eighty-six paise for marketing and eleven and a half paise for utility in India before eighteen percent GST. And your own operational cost — hosting that handles webhooks, a real cron job, and the time to keep plugins current. The message bill usually overtakes the software bill sooner than people expect.

Can I do abandoned cart recovery on WhatsApp with WooCommerce?
Yes, and it is one of the better reasons to do this project, but set the expectation properly. Published recovery rates of fifteen to thirty percent are measured against customers you were able to message, not everyone who abandoned. Multiply that rate by your marketing opt-in coverage to get your real number, and treat growing opt-in as the priority rather than shopping for a better plugin. On WooCommerce specifically, confirm your scheduler is running on a real cron job first, because a timed sequence on an unreliable queue sends reminders hours late to people who have already bought elsewhere.

Do I need the WhatsApp Business API or is the WhatsApp Business app enough?
The free WhatsApp Business app is enough for manual chat from a single phone, and a click-to-chat button on your store costs nothing and needs no approvals. Anything automatic needs the WhatsApp Business Platform: order notifications triggered by WooCommerce events, cart reminders, broadcasts, approved templates and a multi-agent inbox all sit on that side of the line. The two are not compatible and a number can only be on one of them, so moving to the API means removing the number from the Business app and losing that device’s history.

Should I build a client’s WooCommerce WhatsApp setup on a plugin, or resell my own branded CRM?
Both can be right, and it depends on where you want the recurring revenue and the support burden to land. For a single store that needs order notifications and basic recovery, a plugin is the fast honest answer and you bill for the implementation. If the client works out of chat, runs several stores, or you are building the same setup repeatedly, the branded route is the better business: an implementation fee is earned once while a monthly per-licence margin keeps paying, the platform is not hostage to the client’s hosting, and the client never sees a vendor’s name. Agencies comparing platforms usually start with the whitelabel WhatsApp CRM comparison for India.

Become a Reseller