CRM & Integrations
How to Send Order Notifications on WhatsApp
Connect order systems with WhatsApp for confirmations, shipping updates, delivery information, and customer notifications.
Step 1
Choose Order Events
Order notifications should be generated from the order system's actual state, not from a timer that assumes the state changed. Connect to reliable events such as order created, payment confirmed, shipped, out for delivery, or delivered and map each event to a customer message that adds useful information.
Store the order ID together with the WhatsApp message ID so delivery problems can be traced back to a specific transaction. When an order event is retried, use the order ID plus event type as an idempotency key to avoid sending the same confirmation twice.
Implementation Checklist
- Choose order states that are meaningful to the customer.
- Use approved templates when the notification is business initiated and requires one.
- Include only verified order data such as order number, delivery window, or tracking link.
- Persist both the order event and WhatsApp message ID for support and status tracking.
Step 2
Connect Your Store Or Backend
Connect Your Store Or Backend should be driven by a real order state change from the store or backend. The WhatsApp workflow should receive a stable order ID, customer number, event type, and the small set of verified order fields needed for the notification.
Use an idempotency key such as order ID plus event type so a retried ecommerce webhook cannot send the same update twice. Store the returned WhatsApp message ID on the notification record so support can see whether that specific order message was delivered or failed.
Implementation Checklist
- Trigger from actual order events, not assumed timing.
- Validate the customer number and order state before sending.
- Use the appropriate approved template when required for business initiated messaging.
- Store order event, template, recipient, and WhatsApp message ID together for traceability.
Step 3
Map Customer Phone Numbers
Phone number configuration is part identity, part routing. The visible business number is what customers recognize, while the Phone Number ID is what the Graph API uses in message and registration endpoints. Make sure the number is attached to the intended WABA and is in the expected registration state.
Normalize customer numbers before sending and keep country code handling explicit. Avoid guessing a country code from local formatting in production workflows. A CRM should store phone numbers in a consistent international representation so the same customer is not created multiple times under different formats.
Implementation Checklist
- Confirm the business number belongs to the intended WhatsApp Business Account.
- Use the Phone Number ID in Graph API paths, not the display phone number.
- Normalize customer numbers consistently before matching or sending.
- When registration fails, check ownership verification and two step verification before changing code.
Step 4
Create Approved Templates
WhatsApp message templates are approved message structures with an exact name, language, category, and optional variables, headers, or buttons. Design the template so your backend can reliably provide every dynamic value when the message is sent.
Implementation Checklist
- Use the correct template category and clear recipient focused copy.
- Keep variable meaning and order stable.
- Record the exact approved name and language for your integration.
This guide only covers the part needed for the current workflow. For the complete setup, examples, and troubleshooting, continue with How to Create WhatsApp Message Templates.
Step 5
Send Order Confirmation
Order notifications should be generated from the order system's actual state, not from a timer that assumes the state changed. Connect to reliable events such as order created, payment confirmed, shipped, out for delivery, or delivered and map each event to a customer message that adds useful information.
Store the order ID together with the WhatsApp message ID so delivery problems can be traced back to a specific transaction. When an order event is retried, use the order ID plus event type as an idempotency key to avoid sending the same confirmation twice.
Implementation Checklist
- Choose order states that are meaningful to the customer.
- Use approved templates when the notification is business initiated and requires one.
- Include only verified order data such as order number, delivery window, or tracking link.
- Persist both the order event and WhatsApp message ID for support and status tracking.
Step 6
Send Shipping Updates
Order notifications should be generated from the order system's actual state, not from a timer that assumes the state changed. Connect to reliable events such as order created, payment confirmed, shipped, out for delivery, or delivered and map each event to a customer message that adds useful information.
Store the order ID together with the WhatsApp message ID so delivery problems can be traced back to a specific transaction. When an order event is retried, use the order ID plus event type as an idempotency key to avoid sending the same confirmation twice.
Implementation Checklist
- Choose order states that are meaningful to the customer.
- Use approved templates when the notification is business initiated and requires one.
- Include only verified order data such as order number, delivery window, or tracking link.
- Persist both the order event and WhatsApp message ID for support and status tracking.
Step 7
Send Delivery Updates
Order notifications should be generated from the order system's actual state, not from a timer that assumes the state changed. Connect to reliable events such as order created, payment confirmed, shipped, out for delivery, or delivered and map each event to a customer message that adds useful information.
Store the order ID together with the WhatsApp message ID so delivery problems can be traced back to a specific transaction. When an order event is retried, use the order ID plus event type as an idempotency key to avoid sending the same confirmation twice.
Implementation Checklist
- Choose order states that are meaningful to the customer.
- Use approved templates when the notification is business initiated and requires one.
- Include only verified order data such as order number, delivery window, or tracking link.
- Persist both the order event and WhatsApp message ID for support and status tracking.
Step 8
Store Message IDs
Store Message IDs should be driven by a real order state change from the store or backend. The WhatsApp workflow should receive a stable order ID, customer number, event type, and the small set of verified order fields needed for the notification.
Use an idempotency key such as order ID plus event type so a retried ecommerce webhook cannot send the same update twice. Store the returned WhatsApp message ID on the notification record so support can see whether that specific order message was delivered or failed.
Implementation Checklist
- Trigger from actual order events, not assumed timing.
- Validate the customer number and order state before sending.
- Use the appropriate approved template when required for business initiated messaging.
- Store order event, template, recipient, and WhatsApp message ID together for traceability.
Step 9
Track Delivery Status
The initial send response is not the final delivery result. Store the outbound WhatsApp message ID and update that record when webhook events report sent, delivered, read, or failed states.
Implementation Checklist
- Match events by WhatsApp message ID.
- Store timestamps and failure details.
- Make repeated status events safe to process.
This guide only covers the part needed for the current workflow. For the complete setup, examples, and troubleshooting, continue with WhatsApp Cloud API Message Statuses Explained.
Step 10
Handle Failed Notifications
The initial send response is not the final delivery result. Store the outbound WhatsApp message ID and update that record when webhook events report sent, delivered, read, or failed states.
Implementation Checklist
- Match events by WhatsApp message ID.
- Store timestamps and failure details.
- Make repeated status events safe to process.
This guide only covers the part needed for the current workflow. For the complete setup, examples, and troubleshooting, continue with WhatsApp Cloud API Message Statuses Explained.
Related Guides
Continue Learning
Need Implementation Help?
Need Help With Your WhatsApp or Automation Project?
If you need help building, integrating, troubleshooting, or improving a production system, you can discuss the project with me directly.