Shopify and WhatsApp: The Integration That Took Us 6 Months to Get Right

When we started building the Shopify-WhatsApp integration at Revvlab, we expected it to take four weeks. Six months later, we were still fixing edge cases. Here is everything we learned, so you do not have to go through the same process.

What the integration actually covers

A proper Shopify-WhatsApp integration is not one thing. It is a set of data flows that need to work reliably in both directions. From Shopify to WhatsApp: order confirmation messages, shipping updates, delivery notifications, refund confirmations, and abandoned cart triggers. From WhatsApp to Shopify: order lookups initiated by the customer, return requests that need to create a Shopify return object, and product queries that should pull from the live catalogue.

On top of that, you need the product catalogue to be accessible within the WhatsApp conversation, so the AI can answer "what sizes do you have in the blue kurta?" without the customer having to leave WhatsApp and go to the website. This requires a catalogue sync that stays current as inventory changes.

The common pitfalls that slow you down

The first pitfall is webhook reliability. Shopify fires webhooks when order events happen: order placed, order shipped, order delivered, refund created. But webhooks can fail. The delivery system at the receiving end needs to handle retries, deduplication, and failure logging. Most developers build the happy path first and discover the failure modes six weeks later when a customer complains they never received their shipping notification.

The second pitfall is order number format mismatches. Shopify order IDs are numeric. Your brand may show customers a formatted order number like #RL-2847. The system needs to handle lookups by both formats, because customers will use whichever one they have in front of them.

The third pitfall is WhatsApp template approval lag. Every outbound WhatsApp message that is not a direct reply to a customer message requires a pre-approved template. Meta's approval process takes 24 to 72 hours, and rejections are common on the first submission. This is a planning problem: you need to submit templates early, not the week before launch.

"We used a third-party connector for the first three months. Every time Shopify updated its API, something broke. We moved to a native integration and the maintenance burden dropped to near zero."

Why native integration matters vs third-party connectors

Third-party connectors for Shopify-WhatsApp integration are plentiful and often cheap. They work well for simple use cases: sending order confirmation and shipping notification messages. But they break down for anything more complex.

The specific problem with connectors is that they do not expose the full Shopify data model to the AI layer. A connector can send a shipping notification. It cannot answer "what is the return window on the product I ordered last month?" because it does not have the contextual product data joined to the order data joined to the customer data.

Native integration means your AI has live access to the full order object, the customer object, the product object, and the fulfilment object. That context is what enables genuinely useful conversations, not just notification dispatch.

How catalog sync works (and what goes wrong)

WhatsApp Commerce allows you to upload a product catalogue that is accessible within conversations. The catalogue is synced via the Meta Commerce API. Each product needs a title, description, price, image URL, and a unique content ID that maps back to your Shopify SKU.

The sync needs to run on a schedule that keeps pace with your inventory changes. For most D2C brands, a sync every two to four hours is sufficient. For brands running flash sales or limited drops, near-real-time sync is critical. Nothing damages trust faster than a WhatsApp bot offering a product that has been sold out for three hours.

The most common catalogue sync failure is image URL rot. Product images in Shopify have CDN URLs. When you change a product image in Shopify, the old URL breaks. If the catalogue sync does not pick up the new URL, the WhatsApp catalogue shows broken images. The fix is to pull images from the Shopify product object at sync time rather than storing URLs statically.

What we would do differently if we started again

We would build the failure handling before the happy path. Every webhook endpoint, every API call, every catalogue sync job should have logging and alerting before it goes to production. Discovering a sync failure three days later from a customer complaint is a solvable problem, but it is much more stressful than catching it in your monitoring dashboard five minutes after it happens.

We would also submit all WhatsApp templates in the first week of the project, not the last week. The approval timeline is not in your control. Everything else can wait. The templates cannot.

Ready to stop losing orders to unanswered messages?

Revvlab handles the entire Shopify-WhatsApp integration for you, natively.

More from the blog