Connecting the WhatsApp Business Platform to an ERP: Architecture, Message Types and Pitfalls
November 11, 2026 · 6 min read · Etzal Group Team
A distributor's sales staff copy order details from the ERP into WhatsApp by hand, forty times a day. Delivery drivers phone customers to say they are on the way. Finance sends payment reminders one by one at month end. All the information already exists in the ERP. Connecting the ERP to the WhatsApp Business Platform lets the system send what it already knows, and bring replies back to where the team works.
Platform rules and pricing are set by Meta and change. What follows describes the structure as commonly implemented. Check Meta's current documentation and rate card before committing to a design.
The building blocks
- A WhatsApp Business Account and a verified business, with one or more phone numbers registered to the Platform. A number on the Platform is used through software, not through the phone app in the usual way.
- The messaging interface. Your software calls it to send messages.
- Webhooks. The Platform calls your software when something happens: a message arrives, or a sent message is delivered, read or fails.
- Message templates. Pre-approved message formats with placeholders, required for messages the business starts.
- Optionally, a solution provider between you and Meta.
Two kinds of conversation
This distinction drives the design.
The customer writes first. For a limited period after their last message, commonly 24 hours, the business may reply with free-form messages. This suits support and sales conversations.
The business writes first. Outside that window, the business may only send an approved template. Templates fall into categories, such as utility messages about a transaction, authentication codes and marketing. Category affects price and the rules that apply.
For an ERP, most outbound messages are business-initiated notifications, so most of the design is template design.
A reference flow
Outbound notification, for example "order confirmed":
- An event happens in the ERP: the order status changes to confirmed.
- The ERP, or an integration service watching it, places a message request on a queue: recipient, template name, values for the placeholders, a reference to the order.
- A sender service takes requests from the queue, checks consent and rate limits, and calls the messaging interface.
- The Platform returns a message identifier, which is stored against the order.
- Status webhooks arrive later: sent, delivered, read, or failed with a reason. The service updates the record.
- On failure, a rule decides: retry, fall back to SMS or email, or raise a task for a person.
Inbound message, for example a reply to that notification:
- A webhook delivers the customer's message.
- The integration service acknowledges at once and queues it for processing.
- It matches the sender's number to a customer in the ERP or CRM.
- It routes the message: to a shared inbox for staff, to an automated handler for simple replies such as "confirm", or to an AI assistant.
- The conversation is stored against the customer.
Put a queue between the ERP and WhatsApp. The ERP should never wait on an external service, and a burst of ERP events should never exceed the Platform's limits.
Designing templates
Good templates are specific, short and useful.
"Hello {{1}}, your order {{2}} has been confirmed. Total: {{3}}. Estimated delivery: {{4}}. Reply to this message if anything needs to change."
Guidance:
- One purpose per template.
- Variables for facts only. Name, order number, amount, date.
- A clear next step. A button or an invitation to reply.
- The right category. A transactional notice is not marketing, and promotional wording inside a utility template is likely to be rejected or recategorised.
- Each language as its own version.
- A short list. Ten well-designed templates serve most businesses. Fifty become unmanageable.
Templates are reviewed before use. Build the approval time into the project plan.
Notifications that commonly pay off
- Order confirmation.
- Payment received.
- Dispatch notice with tracking.
- Delivery today, with a time window.
- Invoice issued, with a document attached.
- Payment reminder before the due date.
- Appointment or service reminder.
- Stock back for a requested item, where the customer asked to be told.
Start with two or three. Measure replies and complaints before adding more.
Consent and opt-out
- Collect consent to receive WhatsApp messages, and record when and how it was given.
- Store it per customer and per purpose. Agreeing to order updates is not agreeing to promotions.
- Honour opt-out at once. A reply of "stop" must end messages of that kind, enforced by the sender service, not by someone remembering.
- Mind personal data law. Phone numbers and message content are personal data under Indonesia's law and Singapore's PDPA.
Customers who feel spammed block and report the number. Enough reports lower the number's quality rating and can restrict sending. Consent is what keeps the channel working.
Eight pitfalls
1. Phone number formats. ERPs hold numbers in every form: with a leading zero, with spaces, with the wrong country code. Normalise to the international format before sending, and expect to clean the data.
2. Duplicate sends. A retried job sends the same message twice. Give every message request a unique key and refuse duplicates.
3. Webhooks handled slowly. If your endpoint does heavy work before answering, deliveries time out and are retried. Acknowledge immediately and process from a queue. Expect the same webhook more than once, and out of order.
4. Unverified webhooks. Check the signature on incoming webhooks so that nobody else can inject messages.
5. Ignoring failures. Messages fail: the number is not on WhatsApp, the template is paused, a limit is reached. Record the reason and act on it.
6. Sending limits. New numbers start with a limit on how many customers they can message per day, which rises with good quality. Plan a gradual start, not a first-day blast to the whole customer list.
7. Treating inbound as an afterthought. Customers reply to notifications. If nobody reads the replies, the notification has made service worse. Decide where replies go before sending the first message.
8. One number for everything. Mixing support, notifications and marketing on one number ties their reputations together. Consider separating marketing.
Cost
Costs come from four places:
- Meta's message charges, which depend on message category and the recipient's country. Check the current rate card.
- A solution provider's fee, if used.
- Build and maintenance of the integration.
- Staff time handling replies.
Estimate volume per template per month before starting. Utility notifications are usually much cheaper than marketing messages, which is another reason to keep them distinct.
Build, or use a provider
- Direct to Meta's cloud interface: most control, lowest running cost, most engineering.
- Through a solution provider: faster start, a shared inbox included, support, a fee per message or per month.
- Through a CRM that already includes WhatsApp: suitable when the ERP only needs to pass events and the CRM handles conversations.
Whichever you choose, keep your templates, consent records and message history exportable.
We build integrations between business systems and messaging channels as part of Enterprise Software. If your team is still copying order details into chats by hand, contact us.
Summary
Use the Platform, not the phone app, for system integration. Design around the two conversation types: free replies within the service window, approved templates outside it. Put a queue between the ERP and WhatsApp, store message identifiers and statuses, and route replies to people. Collect and enforce consent. Normalise numbers, prevent duplicates, verify and quickly acknowledge webhooks, handle failures and start within the sending limits.
Frequently asked questions
What is the difference between the WhatsApp Business app and the WhatsApp Business Platform?
The app is a phone application for a small team to chat with customers by hand. The Platform is an interface for software: your systems send and receive messages programmatically through Meta's cloud service or a solution provider. Integrating with an ERP requires the Platform.
Can the ERP send any message it likes to a customer?
No. A business can reply freely only within a limited period after the customer's last message, commonly described as a 24-hour customer service window. Outside it, messages must use templates approved in advance, and the customer should have agreed to receive them. This shapes how notifications are designed.
Do we need a solution provider or can we connect directly?
Both are possible. Connecting directly to Meta's cloud interface gives more control and avoids a provider's margin, and requires your own engineering. A solution provider adds onboarding help, a dashboard, a shared inbox and support for a fee. Mid-sized companies often start with a provider and reconsider at volume.
Related service
WhatsApp AI Chatbot
We build, train, and run a WhatsApp AI agent that answers customers 24/7, qualifies leads, and follows up.
