WhatsApp template to confirm purchases in your ecommerce

Purchase confirmation queries are among the most common in ecommerce: the customer has already paid and wants to know that everything is in order. Responding quickly and clearly avoids anxiety, complaints, and returns. That's why we've put together a WhatsApp template ready to copy, with variables to personalize and tips for using it in Meta's official API.

• {{1}}: customer's name (e.g., Maria)
• {{2}}: order number or code (e.g., #1042)
• {{3}}: shipping city or location (e.g., Salta)

1. 1Copy the template and replace the variables with the real data for each purchase.
2. 2If you use WhatsApp Business, load it in 'Message templates' from the app. Remember that in Meta's official API, this type of message is in the 'utility' category and requires approval (it usually takes up to 48 hours).
3. 3If you use Wando, load it in the panel and the AI will use it on its own when appropriate, with your prior approval.

Using a template like this saves you time and gives a professional image. And if you load it into Wando, the AI learns it and uses it at the right moment, with your approval. That way, no confirmation slips through, not even in the middle of the night or on Sundays.

When to send this message (and when not to)

The right moment is as soon as the payment is confirmed. That is the customer's peak anxiety: they've already handed over the money and want to know it didn't vanish into thin air. If you wait hours or even until the next day, you lose the effect and generate avoidable complaints.

What this template is NOT for:

Don't use it to notify that the order has already been shipped. That warrants another message (of the 'shipping update' category, if you use the API). Don't use it to ask for a review, offer discounts, or do post-sale follow-up either: mixing purposes causes Meta to reject it or the customer to perceive it as spam.

If the purchase was a gift or the customer explicitly asked not to be contacted, don't send it. And if the payment isn't confirmed, don't use it: first resolve the charge, then confirm.

What to reply when the customer responds

The template opens the conversation, but the customer almost always responds. Here are the three most likely responses and a model message for each.

1. 'When will it arrive?' — the classic. Don't promise dates you can't handle. If you have the info, give it; if not, be honest.

Model: "Hi {{1}}, your order {{2}} is being prepared. Shipping to {{3}} takes between 3 and 7 business days, but we'll confirm as soon as the carrier dispatches it. Does that work for you?"

2. 'I want to change the address' — here you need to act fast before it ships.

Template: "Hi {{1}}! We still have time to change the address of your order {{2}}. Send me the correct address and we'll update it right away. Thanks for letting us know!"

3. 'Can I cancel?' — if it's already being prepared, it depends on your policy. Be clear and straightforward.

Template: "Hi {{1}}, your order {{2}} is already being prepared, so we can't cancel it from here. But as soon as it arrives, you can start a return without any problem. Can I help you with that?"

How to know if the message worked

A confirmation message is not measured by whether the customer replies. It's measured by what did NOT happen: complaints, returns, and 'where is my order?' messages.

Look at these three indicators:

First, the response rate. If the customer replies with 'thanks' or an emoji, the message got through well. If no one responds, it's not that it failed: it's that it didn't raise any doubts, which is exactly what you're looking for.

Second, the number of follow-up messages. If after confirmation you receive fewer inquiries like 'when will it arrive?', the template is doing its job. Before using it, note how many inquiries of that type you received per week; then compare.

Third, delivery rates on the platform you use. If you use Meta's API, check the message status: if it shows 'delivered' and 'read', the customer saw it. If you see many 'failed', check whether the numbers are valid or if the template has any issues with the variables.

If the message doesn't work, it's not that the template is bad: it's that the problem lies elsewhere, such as dispatch time or follow-up communication.

Why Meta may reject the template and how to fix it

Meta does not approve templates randomly. There are specific reasons for rejection, and almost all of them can be fixed.

The most common one: mixing categories. If you put a discount or a review request inside a 'utility' message, Meta rejects it because it's not a pure transactional notice. The solution is to separate: this template is only for confirmation. Offers and reviews go elsewhere.

Another reason: poorly used variables. If you put {{1}} for a long phrase or a URL, Meta may reject it. Variables are for short data: name, order number, city. Nothing else.

They also reject if the message sounds like spam or promotional. Words like 'Buy now!', 'Offer', or 'Last chance' in a utility template are a direct ticket to rejection. And if the text doesn't match the declared purpose, that's also a reason.

How to fix it: read the exact reason for rejection in the Meta panel, adjust the text, and resend. Approval usually takes up to 48 hours, but if the message is clear and well categorized, it shouldn't be a problem. If you use Wando, the panel notifies you of the status and helps you fix it.

Formal vs. friendly variant: which to use and when

You already have both variants. The question is when to use each one, because choosing wrong affects the customer's perception.

The formal one is for sectors where trust is built with distance: real estate, clinics, professional services. Also for high-ticket purchases, where the customer expects serious treatment. If you sell designer furniture or a subscription service, go with the formal one.

The friendly one is for mass-consumption ecommerce: clothing, accessories, food, cosmetics. There, the customer values closeness and speed more than formality. If your brand uses 'you' in the rest of the communication, the friendly variant is the consistent one.

A simple rule: if your customer writes 'Hi, how's it going?', respond friendly. If they write 'Dear sirs, I would like to inquire...', respond formal. The customer's tone sets the tone of the response.

And if you're unsure, test: use the friendly one for a month and measure the response rate. If it drops, switch to the formal one. Data rules.