Seven in ten online baskets are abandoned[1], a return still starts with an email chain, and "where is my order?" fills the support inbox. WhatsApp Flows for ecommerce give shoppers a short, structured form inside the chat they already use, and the answers can go straight to the store that holds the order.
Most WhatsApp tools for online stores stop at basket reminders and shipping notifications. This guide goes further: six journeys step by step, how to connect a Flow to Shopify or WooCommerce through an API, n8n or an AI assistant, and the rules that keep a store on the right side of WhatsApp's policies.
The short answer. A WhatsApp Flow collects a return request, a product preference or a delivery change as taps inside WhatsApp. The answers arrive as structured data, so your store can raise the return, pick the products or update the order, and the result comes back in the same chat. Start with returns or a product finder, and connect it to the store API you already have.
The word "flow" is doing a lot of work in ecommerce. Shopify Flow is an automation tool. Several WhatsApp vendors call their chatbot builders or message sequences "flows". Meta's WhatsApp Flows are something else: native forms that open inside the chat, with option lists, dropdowns, date pickers, text fields and photo upload.
The difference matters when you compare tools. A chatbot asks one question at a time and leaves you with a conversation to interpret. A Flow returns one field per answer. We set out the trade-offs in the real problem with WhatsApp chatbots.
| Name you will see | What it is | What the shopper sees |
|---|---|---|
| WhatsApp Flows (Meta) | A native form inside WhatsApp | A screen with options to tap and one Submit button |
| Chatbot or automation "flows" | A scripted sequence of messages | Questions and buttons, one message at a time |
| Shopify Flow | Automation inside Shopify's admin | Nothing: it runs behind the scenes |
Meta's own guide to connecting WhatsApp and Shopify, published in March 2023, shows how to send an order confirmation when Shopify reports a new order[2]. It is a useful start, and it is one-way: the store talks and the shopper reads. It was written before WhatsApp Flows launched later that year.
The results Meta has published since suggest the bigger gain is in what shoppers can do, not only what they are told. Turkish fashion retailer Sefamerve used Flows for account creation, product search and adding to the basket, and reported a 158% increase in conversions[3]. Lenovo Indonesia moved service bookings into Flows and reported 8.2 times the conversion of its website[3].
Each journey follows the same shape: something starts it, a Flow collects the facts, your store does the work, and the shopper gets the result in the chat.
Flowella does not have a native Shopify app today. What it has is a WhatsApp Flow builder, a native HubSpot integration, an open REST API and signed webhooks, which is enough to connect any store that has an API of its own. The pattern is the same for every journey above.
Meta also lets a Flow call your server between screens, to show live data such as the items in an order. It is powerful, and Meta's own advice is to use it only when live data is required: your endpoint has to answer within seconds every time, or Meta limits and then blocks the Flow[5]. For most stores the simpler pattern is the right place to start.
| Journey | Shopify | WooCommerce |
|---|---|---|
| Product finder | Read products from the Admin or Storefront API, and tag the customer with their answers | Read products and update the customer through the REST API |
| Returns | The returnRequest call in the Admin GraphQL API raises a return for the merchant to approve. Only fulfilled items can be returned |
Add an order note and create a refund through the REST API, or call your returns platform |
| Delivery changes | A fulfilment webhook starts the message. The change goes to your carrier or delivery tool | An order status webhook starts the message |
| Back in stock | An inventory webhook tells your middleware when stock returns | A product webhook does the same |
Shopify documents its returns calls and webhooks for app developers[6], and WooCommerce documents orders, order notes, refunds and customers in its REST API[7].
A request that tells a shopper their return is set up looks like this:
POST https://api.flowella.io/v1/templates/send
Authorization: Bearer flo_your_api_key
{
"templateId": "your_return_exchange_template_id",
"whatsappChannelId": "your_whatsapp_number_id",
"recipients": [
{
"phone": "+447700900417",
"bodyParameters": ["Maya", "1042"]
}
]
}HubSpot's own Shopify sync brings orders and abandoned checkouts into HubSpot and matches customers by email address[10]. WhatsApp identifies people by phone number. Ask for the email address in the customer's first Flow, or make sure the phone number on the Shopify order reaches the HubSpot contact, so the two records meet. HubSpot's built-in WhatsApp channel cannot use templates with Flow buttons[11], which is the gap Flowella fills.
Two different things share the label. Shopify's agent tools let an AI assistant search a catalogue and build a basket, but its order tool only covers orders placed through that assistant, so it is not a way to answer "where is my order?"[12]. Flowella's MCP server lets assistants such as Claude, ChatGPT and Cursor work with your Flowella account[13]: drafting the returns messages, creating the Flow, checking which templates Meta has approved and reporting on delivery, with a confirmation before anything is sent or changed. It is a building and operations tool. The order lookup still belongs to your store.
Meta's published stories are self-reported, so read them as direction, not a forecast:
We have not found a published case study of a returns Flow from a named brand. If you run one, measure the share of returns that become exchanges or credit against your current returns page.
Through its API, yes. There is no native Shopify app today. A Flow's answers reach Shopify through a HubSpot workflow, n8n or your own code, using Shopify's Admin API.
Yes. A Flow collects the reason and the outcome they want, and your store or returns platform raises the return and sends the label.
Not in the UK or Europe. Send shoppers to your own checkout with a link or a product card.
No. HubSpot is Flowella's native integration, and Flows can be built from HubSpot forms on any plan. Other systems connect through the REST API and signed webhooks.
Yes. The Flow collects preferences, your catalogue chooses the products, and the picks arrive as a carousel in the same chat.
Basket reminders and shipping updates are the easy part of WhatsApp for a store. The harder and more valuable part is letting shoppers do things: find the right product, send one back, move a delivery. A WhatsApp Flow turns each of those into a form that takes seconds, and your store's own API does the rest.
Flowella turns your store's forms into WhatsApp Flows, with an open API for the systems that hold your orders.