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

Shopify WhatsApp Integration: The Complete 2026 Guide

Shopify WhatsApp integration in 2026: what the new native channel does, what still needs an app, the real cost stack and honest cart-recovery maths.

A store owner does the sum that every Shopify merchant eventually does. Seventy out of every hundred carts are abandoned. The recovery emails go out and almost nobody opens them. WhatsApp gets opened by nearly everyone within minutes. So the plan writes itself: put the cart reminders on WhatsApp and take back some of the lost revenue.

Then the research starts, and the advice contradicts itself. Half the internet says Shopify has no native WhatsApp and you must install an app. The other half points at a Shopify announcement from a fortnight ago that says the opposite. Both are quoting something true. Neither is telling you the whole thing.

Here is the state of play in August 2026. Shopify added WhatsApp to Shopify Messaging on 29 July 2026, so marketing campaigns over WhatsApp are now a native Shopify feature for the first time. That is a real change and it makes most of the guides currently ranking for this topic out of date. It is also narrower than it sounds, because a campaign tool is not a support inbox and it is not an event-driven flow engine. The parts of a WhatsApp setup that most stores actually need are still app territory.

This guide covers what changed, what the native channel does and does not do, the four honest routes to connect WhatsApp to Shopify, what the whole thing really costs once you stack every bill, the setup sequence, the cart-recovery maths done properly rather than with headline numbers, and how agencies sell this work under their own brand instead of billing it once.

In this guide

What changed in July 2026

For years the answer to does Shopify support WhatsApp was a flat no. There was no WhatsApp sales channel, no WhatsApp surface in the admin, and every merchant who wanted it went to the App Store. That is why the ecosystem of WhatsApp apps for Shopify grew so large, and it is why almost everything written about this topic starts by telling you to install one.

On 29 July 2026 Shopify added WhatsApp marketing to Shopify Messaging. Merchants can now build WhatsApp campaigns inside Shopify itself, using pre-built templates or their own branded content, pull media straight from the product catalogue, add interactive buttons, and set up keyword replies. Billing is per message sent, so a store can push hard through a sale period and drop back to almost nothing in a quiet month.

Two things follow from that, and it is worth being precise about both because the difference decides your budget.

The first is that WhatsApp is no longer outside Shopify. A merchant who only wants to broadcast offers, announce a drop or run a festival campaign can now do that natively, without a subscription to anybody, paying only for the messages that go out.

The second is that this is a marketing channel, not a messaging platform. Campaigns go out to a list. That is a genuinely different job from handling the reply when a customer asks whether the blue one is back in stock, from confirming a cash-on-delivery order before it ships, from routing a conversation to whichever of your three agents is free, or from firing a reminder ninety minutes after a specific cart was abandoned. Those are conversation and automation jobs, and a campaign tool does not do them.

So the honest summary is that Shopify closed the easiest part of the gap and left the harder part open. Which side of that line your requirement sits on is the first question to answer, and most of this guide is about answering it before you spend anything.

What a Shopify WhatsApp integration actually does

Strip away the app marketing and there are four distinct jobs people mean when they say they want WhatsApp on Shopify. They are not variations of one feature. They have different costs, different setup work and different failure modes, and mixing them up is the single most common reason a store ends up paying for the wrong thing.

Chat on the storefront. A WhatsApp button on your product pages so a shopper can ask a question before buying. This is the simplest job in the list and it needs almost nothing. A click-to-chat link with your number in it does the whole thing for free, and any of a dozen free apps will add a floating widget. If this is all you want, stop reading after the setup section.

Order and shipping notifications. Automatic messages when an order is placed, paid, dispatched or delivered. These are triggered by Shopify events and sent as approved utility templates. They are cheap per message, they get read, and they cut down the where is my order tickets that eat a support team’s day. For most stores this is the highest return per rupee in the whole list.

Abandoned cart and marketing campaigns. Reminders about a specific abandoned cart, plus broadcasts to a list. Marketing templates cost several times what utility templates cost and they need explicit marketing opt-in from the customer. This is the job everybody starts with and the one with the most misleading numbers attached to it, which is why it gets its own section below.

A shared team inbox. One business number that several agents work from, with conversations attached to the customer and their order history, assignment between agents, notes and a reply history that survives someone leaving. This is the job that most looks like a CRM, and it is the one the native Shopify channel does not cover at all.

Write down which of these four you actually need before you look at a single pricing page. A store that needs the first two and thinks it needs all four will pay roughly ten times more than necessary. A store that genuinely needs the fourth and buys a campaign tool will be back in the App Store within a month.

Native Shopify Messaging versus a third-party app

With the native channel live, the comparison is finally a real one rather than a formality. Here is how it splits on the jobs above.

Native Shopify Messaging handles campaigns properly. It is inside the admin, so there is no second login and no separate subscription. Product media comes from your own catalogue rather than being uploaded twice. You pay per message with no monthly floor, which is a meaningful advantage for a seasonal store because a quiet month genuinely costs nothing rather than costing a subscription. And because it is Shopify’s own surface, your customer data does not leave for a third party’s database.

Third-party apps still own everything conversational. A shared inbox with agent assignment, cart-recovery flows tied to specific carts with timed follow-up sequences, cash-on-delivery confirmation and the order-cancellation logic behind it, chatbots and keyword flows deeper than simple auto-replies, WhatsApp catalogue and in-chat checkout, and reporting that ties a message to a recovered order. These are not gaps Shopify has hinted at closing.

The practical read is that native and app are not really competing yet for most stores. If your only requirement is broadcasts, native wins outright on cost and simplicity. If you need the inbox or event-driven flows, you need an app regardless, and once you are paying for one its campaign feature is included, so running both is usually redundant.

There is a third possibility worth naming, because it is the one that fits a surprising number of stores and nobody selling a Shopify app will mention it. If WhatsApp is where your business actually happens, and the store is where the order gets recorded, then the right tool is a WhatsApp CRM with the store connected to it, not a store with a chat feature bolted on. Indian and Middle Eastern D2C brands doing most of their selling in chat sit in this category more often than not. If that sounds like your business, the difference between a WhatsApp CRM and the raw WhatsApp Business API is the distinction to get straight before you shop for anything.

The four ways to connect WhatsApp to Shopify

Route one: a click-to-chat link or free widget. You add a wa.me link with your number to the storefront, or install a free chat-button app. No API, no verification, no approval, no per-message cost. Your team answers on the WhatsApp Business app on a phone. It works from the moment you paste it in.

The ceiling arrives fast. One device, no automation, no Shopify events, nothing that starts a conversation the customer did not start, and no history that survives the phone. This is the correct choice for a store doing a handful of enquiries a day, and the wrong one the moment you want a reminder to go out on its own.

Route two: native Shopify Messaging. Connect WhatsApp in the Shopify admin and run campaigns from inside Shopify. No subscription, per-message billing, product media from your catalogue, interactive buttons and keyword replies. For broadcast-only requirements this is now the default answer and it was not available two weeks ago.

The ceiling is the one described above: campaigns, not conversations. No shared inbox, no cart-specific recovery sequences, no cash-on-delivery flow.

Route three: a Shopify App Store WhatsApp app. The mainstream route and, for most stores that need more than broadcasts, still the right one. Install from the App Store, connect your WhatsApp Business Account through the app’s onboarding, and you get a shared inbox, cart-recovery flows, order notifications, campaign tools, chatbots and reporting. Setup is genuinely quick because the app hides the Meta plumbing behind an embedded signup.

The cost is a subscription on top of Meta’s message charges, and in many cases a markup on the messages themselves. It also means your conversation data lives in the app vendor’s system, and migrating away later is real work. Pricing across the well-known apps in 2026 runs from about six or seven dollars a month at the entry level to fifty or sixty dollars a month for plans with proper automation, before a single message is paid for.

Route four: a dedicated WhatsApp CRM with Shopify connected to it. Instead of adding chat to the store, you run a WhatsApp platform as the primary workspace and connect Shopify to it for order and customer data. Conversations, pipeline, agents, automation and campaigns all live in one place, and the store becomes the system of record for orders rather than the place your team works.

This is the right shape when chat is the main sales channel rather than a support afterthought, when you sell across more than one storefront or marketplace, or when you are an agency running this for clients and need it under your own brand. It is the wrong shape for a store where WhatsApp is a minor support channel, because you would be paying for a platform to do a widget’s job.

Most stores land on route two or three. Read the cost section before you decide between them, because the pricing pages compare badly against each other.

Before you start: what you need ready

Three of these take days rather than minutes and none of them depend on each other, so start all three now and do the actual connection later in the week.

A phone number that is free. A number can only exist in one WhatsApp product at a time. If the number you want is currently signed in to WhatsApp or the WhatsApp Business app, it must be deleted from there before it can be connected to the API, and the chat history on that device goes with it. Export anything you need first. Most stores use a fresh number for this reason, which also keeps a personal phone out of the business workflow permanently.

Meta business verification. You need a Meta Business account and, for anything beyond the smallest sending limits, your business verified. Verification wants documents that match your registered business name exactly, and mismatched paperwork is the usual cause of a rejection. It can clear in a day or take a couple of weeks. Start it first.

A tidy customer phone field. This one gets skipped and then causes the failure that looks like a bug. WhatsApp matches customers by phone number, so a Shopify customer record with a missing country code, a leading zero or a stray space will not match the WhatsApp conversation. Messages then arrive with no order attached to them and your team cannot see who they are talking to. Standardise the whole customer file to full international format before you launch, not after.

Marketing opt-in, if you plan to market. Utility messages about an order the customer placed are one thing. Promotional broadcasts need explicit marketing consent, and the checkout consent you collect for email does not automatically cover WhatsApp. Add a WhatsApp opt-in at checkout and, if you can, at the chat widget. Do this on day one, because opt-in coverage compounds and it is the number that decides whether any of this works. The next section explains exactly how much it decides.

Setting up WhatsApp on your Shopify store

The exact clicks differ by route, but the sequence below is the same in all of them and the order matters. Doing it out of order is what turns a two-hour job into a two-week one.

Step one: connect the number. For native Messaging, this happens in the Shopify admin under Messaging, where you connect a WhatsApp Business Account and pick the number. For an app, it happens inside the app’s onboarding, which usually embeds Meta’s own signup flow so you never touch the developer console. Either way you are creating a WhatsApp Business Account under your Meta Business account and attaching a phone number to it, and either way the number must be free of the consumer apps first.

Step two: verify the display name. The name customers see next to your messages goes through Meta review. It must plausibly match your business. Made-up names and keyword-stuffed names get rejected and slow everything down.

Step three: confirm a message travels both ways. Send one to a test number and reply to it. Nothing else matters until this works. If outbound sends and inbound never arrives, you have a webhook problem, and that is a specific fault with a specific fix rather than a configuration mystery.

Step four: connect Shopify events. This is what makes the setup useful rather than decorative. Map the store events you care about to messages: order placed, order confirmed, payment received, order dispatched with the tracking link, delivered, and cart abandoned. Each one becomes a template. Native Messaging covers the campaign side of this; event-driven order notifications and cart triggers are where an app earns its subscription.

Step five: write and submit templates. Anything sent outside the twenty-four hour window after a customer’s last message must be a pre-approved template. Write them like a useful transactional email and not like an advert. Rejections almost always come from vague promotional wording, variables with no surrounding context, or a category that does not match what the message says. Submit early, because approval takes time and it is a hard dependency for launch.

Step six: set the categories correctly. Utility and marketing are billed very differently and the gap is large. An order update is utility. A discount is marketing. Miscategorising a promotional message as utility gets it rejected; miscategorising an order update as marketing quietly costs you several times more per message than it should, forever, and nobody notices because each individual message is a fraction of a rupee.

Step seven: pilot on one flow. Pick order dispatched, because it is useful, uncontroversial, high volume and needs no opt-in. Run it for a week. Watch the delivery rate and watch what customers reply. They will reply, and if nobody is watching the inbox that first week does more damage than the flow does good.

Step eight: add the marketing flows last. Once opt-in is being collected and the utility flows are steady, turn on cart recovery and campaigns. Doing this first, before opt-in coverage exists, is the standard mistake and produces the disappointing numbers people then blame on WhatsApp.

Abandoned cart recovery: the honest maths

This is the reason most Shopify merchants come to WhatsApp, so it deserves real numbers rather than the ones on the app landing pages.

The headline figures are genuinely impressive and broadly real. 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 against twenty to thirty percent for email, and with most messages read within minutes rather than hours. Those numbers are not invented.

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

A recovery rate is measured against the people who were messaged. To be messaged with a marketing template, a customer must have given marketing consent for WhatsApp and must have left a usable phone number. Not everyone who abandons a cart has done either. So the number that decides your revenue is not the recovery rate at all, 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 of them. At a strong twenty percent recovery you get sixty orders back. Against the full thousand abandoned carts, that is an effective six percent. Real money, clearly worth doing, and roughly a third of the number on the app’s homepage.

Now push opt-in coverage to seventy percent, which is achievable with a checkout tick box and a chat-widget prompt but takes a couple of months to build up. Seven hundred messaged, twenty percent recovered, one hundred and forty orders. Same tool, same flow, same recovery rate, more than double the revenue. The lever that mattered was consent collection, not the app you chose.

This is why the earlier advice to add opt-in on day one is the most valuable sentence in this guide. It is also why comparing apps on their claimed recovery rates is close to useless, since they are all quoting the same industry range measured on their best customers. Compare them on the things that actually differ: whether the flow can send more than one reminder, whether it stops when the order completes, whether it attributes a recovered order back to the message so you can see the return, and what the messages cost.

One more caution on message economics. Cart reminders are marketing templates, not utility, so they carry the higher rate. Sending three reminders to seven hundred people is two thousand one hundred marketing messages. At Indian rates that is under two thousand five hundred rupees including tax, which against a hundred and forty recovered orders is trivial. The maths only turns bad when a store blasts a large unsegmented list with marketing templates and recovers nothing, which is exactly the behaviour Meta priced marketing templates to discourage.

What a Shopify WhatsApp setup costs in 2026

Almost every guide quotes one number, the app subscription, and stops there. There are four bills and the ones nobody quotes are the ones that scale.

Bill one: your Shopify plan. Unchanged by any of this. Native Messaging does not sit behind a plan upgrade the way some platform features do, so this line is usually zero incremental.

Bill two: the app subscription, if you use an app. Entry-level WhatsApp apps on the App Store start around six to seven dollars a month, several have free tiers with a monthly message allowance, and the plans with real automation, a proper shared inbox and analytics run from roughly twenty-one dollars to sixty dollars a month at the well-known vendors. Take the native route and this bill is zero.

Bill three: Meta’s per-message charges. This is the one that scales with your business rather than sitting flat, and it is charged whichever route you pick, because it is Meta’s charge and not the app’s. Since July 2025 Meta bills per delivered template message rather than per twenty-four hour conversation window. In India the current 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 details in there matter more than the rates themselves. Marketing costs roughly seven and a half times what utility costs, which is the entire argument for getting your template categories right. And rates vary enormously by country, so a cost estimate from a US or European blog can be several times wrong in either direction for your market. Check your own country’s rate card.

Bill four: the app’s markup on messages. The line that is easiest to miss and hardest to escape later. Some apps pass Meta’s rate through at cost and make their money on the subscription. Others add a per-message or per-order margin on top. At a thousand messages a month the difference is noise. At fifty thousand it is larger than the subscription. Ask the direct question before you install: do you charge Meta’s rate at cost, and can I see the rate card for my country.

Put it together for a mid-sized Indian store sending fifteen thousand utility messages and five thousand marketing messages a month. Meta’s charges are roughly one thousand seven hundred rupees plus GST for the utility volume and about four thousand three hundred rupees plus GST for the marketing volume, call it seven thousand rupees all in. A mid-tier app subscription adds two to four thousand. So six figures a year, most of it message cost rather than software, and the number that moves it is your marketing-to-utility ratio, not which app you chose.

If you are working out where this sits against other tools you are already paying for, the Lion CRM pricing page lists per-user costs for the CRM route so you can compare a platform subscription against an app subscription plus markup on the same message volume.

What none of the routes will do for you

Some limits belong to WhatsApp itself, not to Shopify or to any app, and no amount of paying more removes them. Knowing which is which saves you a support ticket and a wasted evaluation.

You cannot message anyone who has not opted in. WhatsApp is not email. There is no cold-outreach mode, no bought list, no legitimate way to broadcast to people who have not agreed. Your reachable audience is exactly your opt-in list and it grows only as fast as you collect consent.

Outside twenty-four hours, only templates. Once the window since the customer’s last message closes, free-form text will not send. Everything proactive must be a pre-approved template, which means every automation has to be designed as a template from the start rather than written as a message and converted later.

Templates are reviewed, and review is not instant. You cannot ship a campaign in the next hour if the template does not exist yet. Build a small library of approved templates before you need them.

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

Native Messaging does not give you an inbox. Repeating it here because it is the assumption most likely to break a plan. If your requirement includes several agents working one number with conversations attached to customers, the native channel is not the answer and no setting turns it into one.

Everything the customer sees is your storefront’s identity, not yours as an agency. Fine for a merchant. A commercial problem if you are the agency running this for a client, which is the next section.

The whitelabel route: selling this to clients

If you build Shopify stores for a living, the pattern in this guide should look familiar. A client asks for WhatsApp. You research the apps, install one, configure the templates, wire up the flows, train their team, and bill for the project. The work is real and the client is happy.

Then look at where the recurring money goes. The client pays the app vendor every month, forever, for something you built. You earned the implementation fee once. And the app is not yours, so when it raises its prices, changes its interface or breaks a flow, you handle the support conversation while somebody else keeps the subscription.

There is a different shape available. Rather than configuring another company’s product 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.

For agencies going that way, the requirements that decide whether it scales are unglamorous and practical: 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 entire point. A Shopify 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

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. The second most common cause is Meta business verification that has not finished.

Messages send but replies never arrive. A webhook problem, not a settings mystery. Outbound working while inbound is silent is the signature of this exact fault. If you are on an app, its support can fix it in minutes because it is their webhook. If you built direct, check the callback URL and verify token in the Meta console and confirm you subscribed to the message fields.

Conversations do not show the customer’s orders. Phone-format mismatch between Shopify and WhatsApp, nine times out of ten. Matching happens on the number, so a leading zero, a missing country code or stray spaces stop it finding the customer. Normalise the whole customer file to international format and retest with a number that already exists in Shopify.

Templates keep getting rejected. Vague promotional wording, variables with no context around them, 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 like a banner ad.

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

Recovery revenue looks lower than the dashboard claims. Attribution. Many apps count any order from a messaged customer within a long window as recovered, including ones that would have completed anyway. Compare against your own Shopify order data over the same period before you judge the return.

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 spots it 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. The answer is usually obvious in ten minutes and is almost never the one raised in the meeting.

A 14-day rollout plan

Days 1 to 3: paperwork and cleanup. Start Meta business verification, because it is the longest lead time and nothing ships without it. Free up the phone number. Begin normalising the customer phone field in Shopify. Decide which of the four jobs you actually need, and from that, which route you are taking. All of this runs in parallel and none of it blocks the others.

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

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 and 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 Shopify have a native WhatsApp integration?
Partly, and this changed recently. Since 29 July 2026 Shopify Messaging supports WhatsApp marketing, so you can build and send WhatsApp campaigns from inside the Shopify admin with per-message billing and no separate subscription. That is genuinely native and it is new. What it does not include is a shared team inbox, cart-specific recovery sequences tied to Shopify events, cash-on-delivery confirmation flows or agent assignment. For those you still need a third-party app or a dedicated WhatsApp CRM. Guides that say Shopify has no WhatsApp at all were written before this change and are out of date.

How much does a Shopify WhatsApp integration cost?
Budget four lines. Your Shopify plan, which does not change. An app subscription if you use one, from about six or seven dollars a month at entry level up to fifty or sixty for full automation, or zero on the native route. 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 per message in India before eighteen percent GST. And any markup the app adds on those messages, which is the line nobody quotes and the one that grows fastest. For most stores the message bill overtakes the software bill well before it feels like it should.

Can I recover abandoned carts on WhatsApp from Shopify?
Yes, and it works well, but not through the native channel. Cart recovery needs a flow that triggers on a specific abandoned cart, sends a timed sequence and stops when the order completes, which is what third-party apps and WhatsApp CRMs do. The honest expectation is important here. Published recovery rates of fifteen to thirty percent are measured against customers you were able to message, not against 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 app.

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 storefront costs nothing and needs no approvals. Anything automatic needs the WhatsApp Business Platform, which is the API product: order notifications triggered by Shopify 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 the history on that device.

Will one WhatsApp number work across several Shopify stores?
Technically yes on most platforms, but think carefully before doing it. Customers see one business identity, so orders from different brands arrive in the same thread with the same display name, which confuses shoppers and support alike. If the stores are genuinely different brands, use separate numbers. If they are regional storefronts of one brand, one number is usually fine and simpler. Multi-store setups are also where a dedicated CRM starts to beat a per-store app, because you are otherwise paying and configuring separately for each storefront.

Should I build a client’s Shopify WhatsApp setup on an app, or resell my own branded CRM?
Both can be right and it depends on where you want the recurring revenue to land. If the client is a straightforward single store needing order notifications and basic recovery, an App Store app is the fast honest answer and you bill for the implementation. If the client works out of chat, runs several storefronts, or you are building the same setup repeatedly for different clients, the branded route is the better business, because an implementation fee is earned once while a monthly per-licence margin keeps paying 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