WhatsApp Business API: 2026 Costs and Integration With Your ERP

WhatsApp Business API is the official channel Meta offers so that a piece of software, such as your ERP or your CRM, can send and receive WhatsApp messages on your company number. For an SME that sells to other businesses, it is mostly good for one thing: automatically sending the right message when something happens in the ERP (the order is ready, the technician is on the way) and bringing the customer's reply back into the record it belongs to. If the plan is to send offers to your whole contact list, the API is the most expensive and most regulated tool you could pick.

This guide is for companies that already use WhatsApp with customers from the office phone. The rates quoted are Meta's prices for Italian numbers, in force from 1 October 2026.

What WhatsApp Business API is and how it differs from the app

There are two products with almost identical names. The WhatsApp Business app is free, runs on a phone and adds a business profile, a catalogue, quick replies and away messages to WhatsApp. The number can be used on up to four linked devices besides the main phone, as the WhatsApp help centre explains. Every message is typed by a person.

The WhatsApp Business Platform (what everyone calls the API) has no interface of its own. It is a service that software connects to: the ERP, a CRM, a helpdesk platform or a custom-built program. The software decides when to send a message and to whom, and it receives the replies.

One useful detail: Meta also lets you keep the same number on the app and connect it to the API at the same time. This is called coexistence. The Meta documentation on onboarding app users also lists the limits: broadcast lists become read-only, disappearing messages and live location are turned off, group chats are not synced, and throughput is capped at 20 messages per second. That speed is enough for any SME; losing broadcast lists is something to plan for if you use them today.

How much WhatsApp Business API costs in 2026

Since 1 July 2025 Meta charges for each delivered message, no longer per conversation. Messages your customers send you are always free. The price depends on two things: the message category and the country code of the number receiving it. A message to a German customer costs more than one to an Italian customer.

This is Meta's euro price list for Italian numbers, in force from 1 October 2026 (you can download it from the official pricing page):

On 1 October 2026 a rule changed that many guides written earlier do not mention. Until September, free-form replies to customers and utility templates sent inside an open conversation were free. Now they are charged. Service messages have a free allowance of 1,000 per month for each business number, and unused messages do not carry over to the next month. If the account has no payment method, service messages beyond that allowance are no longer delivered: the kind of detail you discover when a customer tells you they never got an answer.

Take a plumbing supplies distributor with 400 orders a month. For each one it sends an order confirmation and a shipping notice: 800 utility templates, or €19.84. Agents' replies to customer questions stay under 1,000 and cost nothing. Once a month it sends price list updates to the 300 customers who gave consent: 300 marketing templates, €19.74. The total paid to Meta is about €40 a month. Meta also has volume tiers for utility and authentication, but they start at volumes far above these: for an SME, the list price is what counts.

Then there is the software. Provider platforms charge a subscription, sometimes per agent, sometimes with a markup on Meta's message prices: compare offers on the same annual volume. If you connect the ERP directly to the Cloud API, Meta charges no access fee, but someone has to build and maintain the integration.

Templates and the 24-hour window

The first rule concerns the customer service window: when a customer writes to you, a 24-hour window opens, and it restarts with each new message from them. While it is open you can reply with free text, photos or PDFs. Once it closes you can only write to them with a template, a model message that Meta has approved in advance. A template can contain variables: order number, delivery date, technician's name.

The second concerns the template category: Meta decides it, and with it the price. The template categorisation guide is clear: a template counts as utility only if it is tied to a customer action or request and contains nothing promotional. A shipping notice that ends with ‘enjoy 10% off your next order’ becomes marketing, and costs more than two and a half times as much (€0.0658 instead of €0.0248). Since April 2025, if you submit it as utility and Meta judges it to be marketing, it is approved straight away as marketing. The practical rule: the service message does the service and nothing else, and the offer goes out separately, only to people who asked for it.

WhatsApp notifications to customers: B2B use cases that work

The WhatsApp notifications customers appreciate answer a question before they ask it: where is my order, when is the technician coming, can you send me the service report. A few examples:

• A wholesaler confirms the order as soon as the sales rep enters it, and sends the shipping notice with the tracking number when the warehouse closes the parcel.
• A maintenance company reminds the customer the day before a scheduled visit, with the time slot and the technician's name, and asks them to confirm with a button.
• A garage sends a ‘car ready’ message when the workshop manager closes the job, with a PDF summary of the work done.
• The accounts team sends a polite reminder three days after an invoice falls due, with a link to the document.

In every case the message starts from an event the ERP already knows about. If the information lives in an Excel sheet or in the warehouse manager's head, WhatsApp cannot send it to anyone. For the same reason, a customer portal that removes repetitive questions and WhatsApp notifications work well together: the portal holds the full status, the message tells the customer that something has changed. In the Dabe Connect project, for example, customers check the progress of the work and download reports from the private area without picking up the phone: in a project like that, an alert at the right moment is what gets the customer to look at it.

Integrating WhatsApp with your ERP: how it works in practice

Integrating WhatsApp with your ERP means connecting the ERP's events, the templates on Meta and the replies that come back. If the idea of an API is new to you, our plain explanation of APIs will make the rest easier to follow.

This is the typical flow for an order confirmation. When the order moves to ‘confirmed’, the ERP takes the order number, expected date and contact person, puts them into the approved template and calls the API. Meta replies that it has accepted the request, but that does not mean the message has arrived. The outcome comes later, via webhook: sent, delivered, read, or failed with an error code. A well-built integration saves every status on the order record, so whoever takes the ‘I never got anything’ call can see straight away whether it was delivered, and to which number.

When the customer replies (a question, a photo of damaged goods, ‘can you move it to Thursday?’) the reply has to land in the right record and with the right agent, not in a generic inbox nobody checks. Whether you need a shared chat or a note on the record is enough is decided case by case.

In integration projects, time is almost always lost here:

1. Phone numbers in the customer master data. Meta recommends sending numbers with the + and the international country code: without it, Meta adds the business number's country code and the message may not arrive, or may reach someone else. In many ERPs the ‘mobile’ field contains anything from the switchboard to ‘ask Mario’: clean it up first.
2. The right recipient. In a client company, the person who receives the order confirmation is not the one who receives the payment reminder. You need one contact per type of communication, not a single number per company.
3. Messaging limits. A new account can start conversations, outside the 24-hour window, with 250 different people a day. With business verification (or after 2,000 high-quality templates delivered in 30 days) the limit rises to 2,000; after that it grows on its own if quality stays good and you use at least half of the limit, as the Meta page on messaging limits explains. Your customers measure quality: blocks and reports over the last seven days weigh on the number's rating.

Connecting the ERP to an external service, handling errors and keeping a log of what was sent is the work we do in our integrations between ERP, CRM and e-commerce. WhatsApp is an integration like any other, with the extra constraint of templates that need approval.

Opt-in and privacy: what you need before the first message

The WhatsApp Business policy sets two conditions for contacting someone: they must have given you their number, and they must have given you permission to message them on WhatsApp. How you collect that consent is your responsibility, and you must honour every opt-out request, even if it comes by email or over the phone. Meta itself suggests asking for separate consent for each type of message.

In Italy there is also article 130 of Italy's Privacy Code: commercial and promotional communications by SMS, email ‘or other means’ require the consent of the person concerned. The exception for existing customers applies only to email. Service communications, such as confirming an order the customer placed, have a different purpose, but they must also be listed in the privacy notice you give your customers.

In the ERP this translates into specific fields on the contact: consent to receive service communications on WhatsApp, separate marketing consent, the date and channel through which consent was collected, and the date it was withdrawn. The software must check them before every send. For the wording of the privacy notice, talk to your privacy consultant; our job is to make sure the software follows what it says.

When you don't need WhatsApp Business API

If two people in the office answer a few dozen messages a day by hand, and you don't want to connect the ERP, the free app is enough. You would pay for messages that are free today, lose the freedom of free text on first contact, and have to get every template approved.

The API starts to make sense when at least one of these is true: messages come from ERP events and someone currently copies them out by hand; several agents need to see the same conversations; you need to know, for each customer, what was sent and whether it arrived; volumes exceed what one person can handle from a phone.

If you want an automated assistant that answers customers, the policy always requires a clear way to reach a human: we cover this in our guide to the business chatbot for customer support.

How to set up WhatsApp Business API

1. A business portfolio on Meta (formerly Business Manager) registered to the company.
2. A WhatsApp Business account inside the portfolio and a number that can receive a verification SMS or call. It can be the one you already use on the app, with coexistence, or a new number.
3. The display name, which Meta reviews: it must match your business.
4. Business verification. It is not required to get started, and it is the fastest way past the limit of 250 recipients a day; alternatively, Meta raises the limit to 2,000 after 2,000 high-quality templates delivered in 30 days to different numbers, outside the 24-hour window. If you work with a partner provider, they can handle verification for you.
5. A payment method, now required even just for service messages beyond the free allowance.
6. The templates: you write them, submit them for approval and link them to ERP events.
7. A test with colleagues and a few trusted customers before switching sending on for everyone.

Choosing between a provider and a direct connection depends on what you need. If you mainly want a shared chat for your agents, a ready-made platform is faster. If you want ERP events to trigger the messages and the outcomes to flow back into the records, the ERP integration has to be built anyway, and at that point the direct Cloud API cuts out an intermediary and its markup.

Let's talk

Before choosing a provider, it pays to do a simple calculation: which events in your ERP deserve a message, and how many they generate each month. In a 30-minute call we work it out together, looking at your real workflows, and tell you whether the app is enough or whether the integration is worth the work. You can book it from our contact page.