WhatsApp Shopify Integration: The Three Ways to Connect Your Store

There are three ways to build a WhatsApp Shopify integration, and what separates them isn't price — it's how far into the conversation your store actually reaches. You can copy your catalogue into Meta's Commerce Manager, you can fire recovery templates from a broadcast app, or you can put an agent in the thread that queries your live store while it answers.

All three work. They solve different problems, and picking the wrong one costs months of work you then have to redo. This guide separates the routes by what each can and can't do — according to Meta's and Shopify's own documentation, not anyone's brochure — and ends with the criteria for choosing.

Where Shopify stops and WhatsApp starts

Shopify doesn't treat WhatsApp as one of its own channels, and everything else follows from that.

Shopify Inbox, the conversation tool Shopify ships, is built to connect with customers who visit your online store, plus Shop app chat. WhatsApp isn't on that list. Which means the thread where your customer actually asks about the size, the shipping and the payment lives outside your Shopify admin — and anything you want to know about that conversation, you carry across yourself.

In Latin America the gap is wider still. Shopify's official list of supported countries for Shopify Payments includes Mexico and not Colombia, so a Colombian merchant already collects through a third-party gateway. When checkout is partly outside Shopify anyway, sending a payment link in the chat stops being exotic and becomes the obvious path.

And chat isn't a side channel here. Baymard Institute's aggregate of roughly 50 studies puts documented cart abandonment at around 70%: seven in ten people who filled a cart didn't finish. A share of them are recovered by answering one question rather than by discounting — and that answer happens on WhatsApp or it doesn't happen at all.

Route 1: copy the catalogue into Commerce Manager

This is the route Meta ships by default, and the operative word is copy.

A WhatsApp catalogue lives in Meta's Commerce Manager and connects to your WhatsApp Business Account. Per Meta's catalogue documentation, products are uploaded through Commerce Manager itself or through the Commerce API; that page mentions no Shopify integration. Your Shopify catalogue doesn't connect — it gets replicated.

What you get in return is a decent shop window:

• Full catalogue messages, single-product messages, multi-product messages — up to 30 products each — and product carousels.
• The customer builds a cart inside the thread, up to 99 units per item, and sends it to you as a message.
• When a product goes out of stock, Meta removes it from customers' carts automatically.

And here are the limits nobody mentions until they hurt: the cart exists per thread and per device — it isn't a session your customer resumes from another phone — and messages sent through the Cloud API don't show the cart icon in the thread header, so the buying experience isn't identical to the screenshots in circulation.

Our opinion, and it is an opinion: a replicated catalogue is a second inventory to maintain. With 40 stable SKUs it works fine. With 400, size and colour variants, and stock that moves hourly, the copy drifts — and the cost shows up in cancellations and refunds, not in the tool's invoice. If you're still working out what running on Meta's platform involves, the WhatsApp Business API guide covers the whole terrain.

Route 2: recovery templates and campaigns

This route solves a narrow problem and solves it well: reopening a conversation that already closed.

This is where broadcast and marketing-automation apps live. Cart recovery, shipping confirmations, repeat-purchase campaigns. The mechanism is always the same: a Meta-approved template going out to a customer who isn't messaging you right now.

Pricing is the part worth understanding before you switch anything on. Since 1 July 2025, Meta charges per delivered template message, not per 24-hour conversation. Marketing templates are always billed; utility templates are free inside an open customer service window, as are all your non-template replies while the customer is talking to you; authentication templates are always billed. Rates depend on the recipient's country, so Mexico, Colombia and Brazil don't cost the same.

Translated to a store: an abandoned-cart reminder sent to someone who didn't message you is marketing, and it's billed. The same information, said inside a conversation the customer opened, isn't. The difference between those two ways of operating is your month-end invoice.

The demand is real. Across 22 markets including Mexico and Colombia, 72.4% of consumers say they're more likely to buy from a brand that offers messaging (Kantar for Meta, The State of Business Messaging, n=11,056, fielded April–September 2025). But that's demand, not permission — the same person mutes you after three templates they didn't ask for.

The ceiling on this route is simple and decisive: the template brings the customer back, and it doesn't answer whatever they ask next. If your store staffs business hours and the customer replies at eleven at night, route 2 stops one step short of the sale. What the rest of that conversation looks like is in how to sell on WhatsApp.

Route 3: an agent connected to Shopify's Admin API

This is the only route where your store answers live, which makes it the only one that absorbs post-purchase support.

The architectural change is exactly the one route 1 lacks: instead of copying the catalogue, the agent queries it at the moment it replies. Products, inventory, orders, customers and collections are read straight from your store, so the stock the agent quotes is the stock you have.

That unlocks four conversations the other routes don't cover:

• “Do you have the M in black?” — real inventory, with variants, not a card replicated last week.
• “Where's my order?” — the single most repeated message any store receives, answered from live order status without opening the admin.
• “I need to change the address before it ships.” — writing to the order, not just reading it.
• Closing — a payment link generated inside the thread, which in Colombia is simply the only clean path.

What it demands in return: the WhatsApp Business API — not the WhatsApp Business app — a knowledge base holding your shipping, returns and warranty policies, and escalation rules written before the agent goes live.

That last point isn't bureaucracy. The same Kantar study found 67.7% of consumers consider a reply from an AI chatbot helpful, while only 42.9% believe AI would improve their experience. People accept AI as a speed mechanism and doubt it as a quality mechanism. An agent that answers instantly and hands off to a person the moment a conversation gets complicated is built on that distinction; one that insists on resolving everything isn't. Our integrations page shows how this layer connects to the rest of your operation.

Meta launched its own agent, and it doesn't speak Shopify yet

Since 3 June 2026, Meta has offered its Meta Business Agent across WhatsApp Business, Instagram, Messenger and Business Suite. It was free through 31 July 2026 and has been billed since at US$2.00 per million tokens. More than a million businesses are already using one.

It's worth taking seriously — and worth reading what Meta says it still doesn't do: no calendar management, and no shipped Shopify or Zendesk connectors. It answers questions and recommends from the Meta catalogue, which is the same replicated catalogue from route 1. It's a good responder. It doesn't operate your store.

For a Shopify merchant that draws a clear line: Meta covers the reply layer at close to zero cost, and anything that depends on data living inside your store still needs a real connection.

How to choose, in four questions

1. How many SKUs, and how fast does stock move? Under 50 and stable: the replicated catalogue is enough. More than that, or with variants: you need live reads.
2. Is your bottleneck traffic or response? If nobody messages you, route 2 moves the needle. If they do message you and you answer late, route 2 makes it worse — it sends more people to an inbox you already can't keep up with.
3. How heavy is post-purchase? If “where's my order?” is half your messages, route 1 doesn't touch it and neither does route 2.
4. Are you selling in Mexico or Colombia? With Shopify Payments live in Mexico, checkout can stay inside. In Colombia it's already outside, and an in-thread payment link stops being a nice-to-have.

The routes aren't mutually exclusive, but they have a sensible order: answer well first, reopen conversations second. A store that automates broadcasting before it automates replying ends up paying for templates that walk people into silence.

Starting without rebuilding the store

None of the three routes requires migrating Shopify or changing your checkout. The WhatsApp API connects to your number, the agent connects to your store with scoped permissions, and your catalogue stays exactly where it is.

xcale is route 3: AI agents on the WhatsApp Business API that read your Shopify store live, remember the customer between conversations, and escalate to a person when it matters. A 7-day free trial is enough to see, with your own products and real orders, how many of the questions you answer by hand today resolve themselves. If you sell on WhatsApp and through an online store at once, the ecommerce view walks through the full flow.