WhatsApp for e-commerce: order updates, delivery tracking, and returns

Customers default to WhatsApp for the same reason they default to it everywhere else: it is fast, it is already on their phone, and they expect a reply the same day. For e-commerce in particular, the post-purchase questions are short and frequent. "Did my order ship?" "Can I change the address?" "I received the wrong size." These are not questions a customer wants to compose an email about. They want to send a message and get an answer.

For small online stores, this is self-reinforcing. The founder shares a WhatsApp number on Instagram or the website, one customer messages and gets a fast reply, and the word spreads. WhatsApp open and response rates for transactional notifications run significantly higher than email for the same reason: the customer already uses it daily and checks it constantly. Email order confirmations get filtered, forwarded, or missed. A WhatsApp message typically does not.

The practical effect is that WhatsApp becomes the de facto support channel whether the team planned for it or not. The problem is not that it happened. The problem is that a personal phone is the wrong tool for a channel handling 50 or 100 conversations a week.

Every "where is my order?" message your team answers manually is a customer who did not get a proactive update. For a team of three to five handling 50 orders a week, that pattern accumulates quickly. If a quarter of customers send one follow-up message about shipping status, that is more than a dozen conversations a day that exist purely because the outbound communication did not land.

The cost is not just time. It is also timing. A customer who has to ask where their order is was already anxious enough to send a message. That is a different emotional state from a customer who got a shipping notification before they thought to ask. The first customer is already mildly dissatisfied. The second is reassured.

For a team without a shared inbox, inbound order questions also create visibility problems. A return request that arrives on one person's phone and gets answered informally, with nothing recorded, can result in a customer chasing the same issue a week later with someone who has no idea the first conversation happened. That is the kind of failure that produces a refund request, a chargeback, or a public review.

Proactive order updates do not eliminate inbound questions, but they reduce the volume of reactive "where is my order?" messages. And when something does go wrong, a shared inbox ensures the whole team can see the history instead of piecing it together from screenshots.

Order update messages are Utility templates under Meta's message template classification. That distinction matters practically and financially.

A Utility template is a pre-approved message a business sends to confirm a transaction the customer already initiated or to provide an update directly tied to an existing interaction: an order confirmation, a shipping dispatch notice, an out-for-delivery notification, a delivery confirmation. The customer does not need to message first for a Utility template to be sent. The business initiates it, and it arrives as a message on the customer's phone.

A basic order confirmation template looks like this: "Your order {{order_number}} is confirmed. Expected delivery: {{delivery_date}}." The variables in double curly braces are filled in per message. A shipping update might read: "Your order {{order_number}} has been dispatched. Track it here: {{tracking_link}}." Before any Utility template can be sent, it goes through Meta's approval process. The WhatsApp message templates guide covers how that approval works and what to include for first-pass approval.

Utility templates cost less per message than Marketing templates under Meta's per-message pricing. They are not free after the first 1,000 delivered service messages per number per month, but the rate is lower than the rate for promotional sends. For a full breakdown of what each message type costs, see the WhatsApp Business API pricing guide. The short version: use Utility templates for transactional updates and Marketing templates for promotions, and keep them in the right category because Meta will reject a promotional message filed as a Utility template.

From October 1, 2026, Meta also charges per delivered service message after 1,000 free per number per month. The WhatsApp service message pricing post covers that change fully. The takeaway for e-commerce teams is that high-volume transactional sends warrant a quick estimate of monthly message volume before assuming the cost is zero.

One scoped note for US-focused stores: Meta paused marketing message delivery to US phone numbers from April 1, 2025, and that pause remained in place as of mid-2026 with no announced end date. Utility templates for order confirmations and shipping updates are unaffected. Promotional broadcast campaigns to US customers are not. If your customer base is primarily US-based, plan your broadcast strategy accordingly.

Meta's Utility Template Library lists pre-built approved templates for common e-commerce use cases including order confirmations, delivery updates, and payment receipts, which can be a faster path than building templates from scratch. WhatsApp also supports document messages up to 100MB in PDF, Word, and Excel formats, per the document message specs, which means an e-commerce team can send a PDF invoice or a return label directly in the chat if the workflow calls for it.

Return requests almost always arrive as inbound messages. The customer messages first: "I received the wrong size" or "the item arrived damaged, I want to exchange it." That first message opens a 24-hour customer service window, during which the team can reply freely with normal messages, without a pre-approved template. That window is where the conversation happens.

The shared inbox matters most for returns. A return request needs exactly one owner, a clear status, and a record of what was agreed, because returns often span more than one shift. The customer messages at noon. The agent who picks it up asks for a photo of the damaged item. The photo arrives at 3pm. The same agent approves the exchange, but their shift ends before the prepaid label is sent. If no note was left, the next person to open the conversation sees a thread with an approved exchange and no record of whether the label was sent.

A real return workflow on a shared inbox looks like this. The customer's message arrives and is assigned to the agent currently handling returns. The agent responds inside the 24-hour window, gets the details, approves the return or exchange, and leaves a private note: "Approved exchange for size L, photo confirmed, prepaid label to be sent by Friday." The conversation is tagged "return in progress" so it is visible in the team's filter view. The contact's record shows the tag, so anyone who picks up the thread sees the status without digging through the history. When the label is sent, the agent closes the thread and updates the tag to "resolved."

That sequence sounds obvious written out. What makes it work is that the steps happen inside one shared workspace, not across two people's phones and a group chat where the label confirmation gets buried under fourteen other messages.

The 24-hour window rule is simple but easy to misapply in an e-commerce context because the team is often doing both inbound and outbound messaging on the same number.

If a customer messages your team first about their order, a 24-hour window opens from that message. Inside it, the team can reply with any normal message, no template required. The agent can ask follow-up questions, send a photo, confirm a return, schedule a redelivery. That is a free-form conversation.

If the team wants to send a proactive order update, a shipping notification, or a follow-up to a customer who has not messaged yet, that requires a pre-approved Utility template. The customer did not initiate the exchange, so there is no open window.

If a customer replied yesterday but has gone quiet today, the window may have already closed. Sending another message once the window closes requires a template. Sending a casual follow-up text after 24 hours will not be delivered. This is the rule that catches teams who are used to personal WhatsApp: there is no equivalent on a personal number, which makes it easy to forget that a business number operates differently once the window expires.

The WhatsApp 24-hour window and opt-in rules guide covers all of this in more detail. For an e-commerce team, the practical habit to build is this: when a customer messages you, reply as fast as possible inside the window. For anything proactive (shipping notifications, dispatch updates, follow-ups after a window closes), use your approved Utility template.

Order communication in a small e-commerce operation typically crosses more than one person. The ops person packs and dispatches. The support person handles complaints and returns. The founder fields escalations. The customer messages one WhatsApp number without knowing or caring which of those people picks up.

When ownership is unclear, customers feel it. A customer who asks "has my order shipped" and gets "let me check with the team" has correctly identified that nobody in the company has a fast answer. If they follow up two days later with the same question to a different person who also has to check, the impression compounds.

The problem is not that multiple people need access to the same number. That is unavoidable. The problem is that multiple people accessing the same number without a system for ownership creates invisible gaps: the message one person saw but decided was not theirs, the thread that got a partial answer before the conversation went quiet, the return approval that existed in one agent's memory but nowhere else.

This is the same pattern that shows up in any team sharing a phone number, and it gets worse as order volume grows. The WhatsApp multiple agents guide covers the full workflow of assignment, notes, and handoffs. For an e-commerce team, the specific pinch points are the fulfillment-to-support handoff (when an order question escalates into a return) and the shift boundary (when overnight orders land in a queue the morning team inherits without context).

Picture a five-person team handling 60 to 80 orders a week on one WhatsApp number. Two people handle order queries and dispatch. One handles returns and exchanges. The founder checks in on escalations. All of them used to be forwarding screenshots to each other over a group chat.

One WhatsApp number is connected to the Clapvo workspace. Every incoming message lands in the shared inbox, visible to the whole team. Nobody has to forward a screenshot; the thread is just there.

Utility templates are set up in Clapvo for the four standard touchpoints: order confirmed, order dispatched, out for delivery, delivery confirmed. When an order ships, the ops person opens the contact, selects the dispatch template, fills in the order number and tracking link, and sends. The customer gets a proactive notification before they think to ask. That one action removes most "where is my order?" messages from the inbound queue.

For dispatch batches, the team uses campaigns. Once a batch of orders is shipped, the ops person filters contacts tagged "dispatched today," selects the shipping template, and sends a campaign to the whole group. The broadcast campaigns and sender rotation guide covers how to set up a campaign; for e-commerce the key setting is choosing a template approved as Utility, not Marketing.

For post-purchase sequences, message sequencing runs a three-step flow automatically: the order confirmation message, then a shipping update sent with a delay, then a "how did we do?" message a few days after the estimated delivery date. The message sequencing docs show how to configure the delays between each step.

For the most common inbound query ("where is my order?"), the Message Bot handles it without an agent. A customer who messages with a keyword like "track" or "where is my order" gets an automatic reply using the tracking template, with no agent needed. The bot runs on 1:1 chats and can be deactivated per conversation the moment a human needs to take over. The Message Bot docs cover the keyword configuration.

For returns, each thread is assigned to the agent handling it, with a private note recording what was agreed. Contact tags ("return requested", "exchange approved", "resolved") give the team a real-time view of open return cases without a separate spreadsheet. The kanban board tracks return conversations by stage if the team wants to see them as a pipeline: open, in progress, awaiting label, resolved.

Role-based permissions mean the ops team sees fulfillment threads and the support team sees returns, without needing access to each other's work or to the admin settings. Phone number masking can be applied per role, which matters when part-time staff are rotated in during peak periods.

The Android app means the team is not tied to a browser, and scheduled messages let the team compose a follow-up now and deliver it when the timing is right.

What Clapvo does not do here is worth being clear about. It does not connect directly to Shopify, WooCommerce, or any storefront. Order data does not flow in automatically. The team copies order details into templates and pastes tracking links manually, or uses the API to send messages programmatically if the team has a developer who can set that up. The API reference covers what the API can do; programmatic sends require an integration the team builds or commissions. For businesses that need native Shopify-to-WhatsApp automation without any development work, tools like Zoko or DelightChat were built specifically for that. Clapvo is the right fit when the team needs a shared inbox, broadcast capability, and template-driven communication, and does not need deep storefront integration out of the box.

The pricing fits this shape of team. The Gold plan is $15 a month per WhatsApp connection, with 1 connection and 5 team members included. Annual billing is $149. A second number, if the team later wants to separate a support line from a sales or dispatch line, is another $15 a month. Extra team members beyond the 5 included are $15 a month each. The quickstart guide walks through connecting a number and inviting the team; most setups send their first message within an hour. The pricing page has the current plan details and the 7-day free trial with no credit card required.

The customer is not going to stop using WhatsApp. What changes is where those messages land and who owns them. When order updates go out proactively, when return requests get assigned to one person with a note on what was agreed, and when the whole team can see the queue without forwarding screenshots, the number stops being the founder's phone and starts being a channel the business actually runs.

For a 3-to-15-person e-commerce team, that shift does not require a dedicated chatbot platform or a Shopify plugin. It requires a shared inbox, a set of approved Utility templates, and the habit of sending the update before the customer asks. The team inbox guide and the post on WhatsApp number ownership cover the broader setup questions. The multiple WhatsApp numbers guide is worth reading once order volume grows to the point where one number is not enough.

The conversations stay with the team. Not a phone.