Order and Delivery Notifications via the Official WhatsApp API: the sequence that ends the 'where's my order?'

The Six-Notification Sequence

A sequence covering the journey of an online store order from payment to delivery. Not every store needs all, but the order and content serve as a foundation.

1. Order confirmed

Right after payment approval. Order number, main items, value, payment method, and estimated delivery time.

'Hi, Juliana! Your order #48213 has been confirmed. Items: 2 products, total of R$ 289.90 via Pix. Estimated delivery time: 5 to 7 business days. We'll notify you here at each step.'

2. Pending payment (when applicable)

For boleto or Pix generated but unpaid, with payment link and due date. This is the notification that recovers the most sales — and requires a neutral tone, without promotional pressure.

3. Order shipped

Carrier, tracking code, and tracking button, updated deadline.

'Your order #48213 has been dispatched and is now with the carrier. Tracking code: BR123456789. Estimated delivery: by Friday, 18/09.' Button: Track delivery.

4. Out for delivery

On delivery day, when the carrier informs. Reduces failed delivery attempts because the customer can prepare to receive.

5. Delivered

Confirmation with exchange instructions and help channel. This notification opens space for post-sale service.

6. Exception

Delay, address not found, failed delivery attempt, item out of stock. This is the most important notification in the sequence: a problem communicated before the customer notices builds trust; a problem discovered by the customer becomes a complaint.

How to write an approved and effective notification

• Identify the transaction right at the start: order number, so the customer recognizes it and Meta sees the message is linked to a purchase.
• One main piece of information per message. Confirmation is confirmation; tracking is tracking.
• Variables with context. A template that is just '{{1}}' says nothing to the reviewer. Fixed text explaining each variable gets approved more easily.
• Useful buttons: track delivery, view order, contact support.
• No offers, coupons, or calls to buy inside utility messages.
• Simple language, without logistics jargon like 'item in transit to processing unit.'

Integration: where the data comes from

Order notifications only work automatically. No one can manually send each shipping update. The integration components:

• Store platform or ERP reporting order status changes — paid, invoiced, shipped, canceled.
• Carrier or freight intermediary reporting tracking events — posted, en route, out for delivery, delivered, failed attempt.
• WhatsApp platform receiving these events and sending the correct template for each, with variables filled in.
• Conversation and customer record logging, so the agent can see the order history when the customer replies.

An important technical caution: avoid duplicate notifications. Carriers sometimes repeat events, and a customer receiving 'your order is out for delivery' three times may start blocking the number.

Consent: where and how to ask

Utility messages also require that the customer has agreed to receive communications from the company via WhatsApp. The natural place is at checkout:

• Phone field with a clear checkbox: 'I want to receive updates about my order via WhatsApp.'
• Separate and optional authorization for offers and news — which is marketing and should not be bundled.
• Recording the date, channel, and accepted text to prove consent.

Separating the two consents protects the store: those who only want order updates don't receive promotions, and utility messages reach an audience expecting them — which keeps the number's quality high.

The account: how much notifications save and sell

With illustrative numbers from a store with 4,000 orders per month:

• Today: 22% of orders generate at least one contact asking for status — 880 conversations.
• Each status conversation takes on average 4 minutes of service: about 59 hours per month.
• With the sequence: if status questions drop to 8% of orders, that's 320 conversations — 560 fewer and about 37 hours freed.
• Pending payment: 600 orders per month have Pix or boleto unpaid. If the notification recovers 12% of them, with a ticket of R$ 250, that's 72 orders and R$ 18,000 per month.
• Cost: five notifications per order in 4,000 orders are 20,000 utility messages. With a hypothetical cost of R$ 0.05 each — some free due to the open window — the expense is under R$ 1,000.

Actual values depend on Meta's current pricing and the store's operation, but the proportion usually holds: message costs are small compared to hours saved and sales recovered.

How to communicate problems: the exception notification

The sequence shows real value when something goes wrong. A good exception notification has four parts:

• What happened, straightforward: 'Your order #48213 experienced a delay with the carrier.'
• The new deadline or next step: 'The new estimated delivery is Wednesday, 23/09.'
• What the store is doing: 'We are already following up with the carrier.'
• How to ask for help: 'If you need anything, reply to this message and our team will assist you.'

If the delay is significant, offer a concrete alternative — cancellation with refund, product exchange, or returned shipping — instead of just apologizing. When the customer replies, the 24-hour window opens and service happens in the same conversation, with the order history visible.

After delivery: where utility ends and marketing begins

The natural temptation is to use the delivery message to sell again. This is exactly where many stores mix categories. The safe path:

• Delivery message (utility): confirmation, exchange instructions, and help channel. No coupons.
• Satisfaction survey: can be sent next, linked to the order, with a simple question.
• Repurchase (marketing): in another message, days later, only to those who authorized offers — for example, replenishing a consumable product.

Beyond online stores

The same sequence applies to any business with orders and delivery:

• Infoproduct and course: purchase approved, access granted with instructions, first access reminder.
• Subscription: renewal processed, card declined, next box shipped.
• Restaurant and delivery: order received, preparing, out for delivery.
• Services: service order opened, technician en route, service completed.
• Distributor and B2B: order invoiced, invoice issued, shipment dispatched.

Ready-to-adapt texts

Besides the sequence examples, three templates often missing:

• Pending payment: 'Hi, Juliana! The Pix for your order #48213, amounting to R$ 289.90, has not yet been identified. The code expires today at 23h59. If you have already paid, you can disregard this message.' Button: View Pix code.
• Out for delivery: 'Your order #48213 went out for delivery today. If no one is at the address, the carrier will attempt delivery again on the next business day.'
• Delivered: 'Your order #48213 has been delivered. If something is not right, you have 7 days to request an exchange by replying to this message.'

Adapt the exchange period to the store's actual policy and what the Consumer Protection Code guarantees for distance purchases. A utility message with incorrect information causes complaints precisely when the store wants to build trust.

Who handles what

• Operations or logistics: ensures order and tracking statuses are correct and updated at the source.
• Customer service: responds to those who react to notifications, especially exceptions, and records contact reasons.
• Marketing: manages repurchase messages, separate from the utility sequence.
• Management: reviews sequence metrics monthly and approves text changes.

What to measure

• Notification delivery rate, by notification type.
• 'Where's my order?' conversations per 100 orders, before and after the sequence.
• Recovery of pending payments.
• Failed delivery attempts, which the 'out for delivery' notification should reduce.
• Blocks and unsubscribes after notifications — signs of too many or duplicate messages.
• Complaints about delays compared to delays communicated beforehand.

Common mistakes in order notifications

• Including offers in utility messages.
• Sending duplicate notifications due to repeated carrier events.
• Not notifying when there are problems and only when everything is fine.
• Not requesting consent at checkout or mixing consent for orders with offers.
• Messages without order number, which customers don't recognize.
• Sending without anyone to respond. The notification opens the conversation; someone must be there.
• Templates too generic, only with variables, which get rejected.

Where to start

Identify how many conversations per month are status questions and how many orders have pending payments. First create three utility templates — order confirmed, order shipped, and pending payment — add separate consent at checkout, and connect store and carrier events. Run for a month, compare status conversations per 100 orders and payment recovery, then complete the sequence with 'out for delivery,' 'delivered,' and exception notifications.