Yes, you can integrate WhatsApp with your ERP or CRM, and the safe route is Meta's official API (the WhatsApp Business Platform, Cloud API version). The ERP does not talk to WhatsApp on its own: between them sits an integration layer that listens to what happens in the system, sends the right message and passes the customer's reply back to the ERP.
Quick answer
- Do you need the official API? Yes. Tools that automate WhatsApp Web or the regular app break Meta's rules and expose the number to blocks and bans.
- Does my ERP need an API? It helps, but it is not required. You can read the database or exported files, with extra care on syncing.
- Do I need a new number? Not necessarily. Meta now lets you use the same number on the WhatsApp Business app and the API at the same time.
- What does it cost? Platform access is free. Meta charges per delivered message, by category and recipient country, and since October 1, 2026 it also charges replies sent inside the customer service window.
What to automate first
Start with events your ERP already records and that today trigger calls, emails or manual messages:
- Orders: confirmation, approval and status changes.
- Billing: invoice or payment link, due-date reminders and copies.
- Invoicing and logistics: invoice issued, tracking code and delivery notice.
- Self-service: the customer checks balance, order status or stock, and the answer comes straight from the ERP.
- CRM: the conversation becomes a lead or opportunity with its source recorded, no typing needed.
These flows have clear rules and high volume, so they give the team time back from the first month. To put numbers on it before investing, try our automation ROI calculator.
How the integration works
There are three pieces:
- ERP or CRM: the source of data and events (order created, bill coming due, invoice issued).
- Integration layer: a small service that receives those events, picks the message template, calls the WhatsApp API and stores the result. This is where the queue, retries, the log of every send and the rule that blocks duplicate messages live.
- WhatsApp Cloud API: delivers the message and notifies the integration layer, by webhook, when it is delivered, read or answered.
Wiring the ERP straight into the API, without that layer, usually fails on the details: expiring tokens, messages sent twice when the ERP reprocesses, customer replies that never make it back. It is the same principle as any systems and API integration.
Requirements
- A Meta business portfolio (formerly Business Manager), ideally with the business verified, which unlocks higher sending limits.
- Phone number: a dedicated number or the same one used on the WhatsApp Business app. In shared mode, the last 6 months of chats are synced, but sending is capped at 20 messages per second.
- Approved message templates for everything the business sends on its own initiative.
- Access to ERP data: REST API, the ERP's own webhooks, database queries or exported files.
- Customer consent to receive WhatsApp messages, recorded in their profile.
Step-by-step integration
- Map the events. List what triggers each message, who receives it and what they can reply. Start with two or three flows.
- Set up the account and number on Meta's platform, directly or through a solution partner.
- Write and approve the templates. Each template falls into a category: utility (order, billing, delivery), authentication (login code) or marketing (offer). The category sets the price, and Meta reclassifies marketing templates disguised as utility.
- Connect the ERP to the integration layer through whatever access is available, logging every processed event.
- Apply WhatsApp's rules. Free-form messages only within 24 hours of the customer's last message. Outside that window, approved templates only.
- Test with Meta's test number before switching to the real one, including failures: ERP down, customer without WhatsApp, invalid phone.
- Monitor. Track deliveries, reads, failures and replies through webhooks, and send back to the ERP or CRM whatever belongs in the customer history.
What the official WhatsApp API costs
- Access: free. Meta charges no monthly fee to use the Cloud API.
- Template messages: billed per delivered message, priced by category and recipient country. Marketing costs several times more than utility and authentication.
- Replies inside the 24-hour window: since October 1, 2026, Meta charges these at the same utility rate for each country. If your support team replies a lot, including through AI, redo the math.
- Ads that open WhatsApp: a conversation started from a click-to-WhatsApp ad opens a free 72-hour window.
- Outside Meta: the solution partner's fee, if any, and building the integration layer.
Rate cards change a few times a year, so check the current values on Meta's pricing page before closing the budget.
FAQ
My ERP has no API. Can I still integrate?
Yes. The integration layer can read the database (ideally a read-only replica or view) or files exported on a schedule. The care point is not resending messages when the same record is read again.
Can I message customers at any time?
Only with approved templates. Free-form messages are allowed only within 24 hours of the customer's last message.
Can AI answer?
Yes, inside the service window and through the official API. Now that replies are billed, measure how many messages the AI exchanges per conversation.
How long does it take?
It depends on access to ERP data and the number of flows. A pilot with two or three events is the best start: it proves the result before you expand.
Want to connect WhatsApp to your system?
ERP integration is something we already deliver, as in JPEC's ERP-integrated order portal. For AI-powered WhatsApp support, see ZapnIA. And if you also need to connect your website and CRM, read how to connect website, CRM, ERP and WhatsApp. To review your case, talk to our team.