ERPNext ↔ WhatsApp Integration
Transactional messaging and operational alerts tied to ERPNext events - with delivery evidence, queue-safe sending, and audit-grade traceability.
Why ‘sending WhatsApp’ becomes a production problem
In production, messaging is not about sending. It’s about proving delivery, preventing floods, handling failures, and linking evidence to business documents.
Without delivery evidence tied to ERP documents, finance and operations cannot resolve disputes efficiently.
- Customers claim they never received invoices/receipts/reminders.
- Teams forward screenshots instead of using system evidence.
- No traceability from a message back to the source document.
A naive integration spams the provider, drops messages, and hides failures in background jobs.
- Bulk messaging causes rate-limit throttling and unpredictable delivery.
- Background failures are missed until customers complain.
- Retries can create duplicate notifications without guardrails.
Queue-safe delivery with evidence trails
This integration treats WhatsApp as an operational rail: trackable, auditable, rate-limited, and linked to ERPNext events and documents.
Each message has a status lifecycle (queued → sent → delivered/failed) with reason codes and references back to ERP documents.
Messages are sent through controlled queues with throttling to avoid floods, bans, and silent drops during peak traffic.
Retries are deliberate and traceable. The system avoids duplicate “spam” retries and preserves a clean audit trail of what was attempted.
What it does in ERPNext
We focus on business-critical messaging: transactional documents and operational exceptions.
Send ERPNext documents via WhatsApp and keep evidence of delivery linked to the originating document.
- Invoices, receipts, statements, reminders, delivery updates.
- Evidence trail linked to the exact ERP document (Sales Invoice, Payment Entry, Delivery Note, etc.).
- Templates and controlled formatting to keep messaging consistent.
Route operational alerts to specific teams so failures don’t sit unseen in logs.
- Payment exceptions, posting failures, stock anomalies, pending approvals.
- Alerts targeted by role/team (finance, ops, dispatch).
- Throttle controls to prevent alert storms.
A message system is only useful when it’s operable. We surface delivery status and failures in a way teams can use.
- Status lifecycle: queued, sent, delivered, failed - with reasons.
- Search and filtering by document, customer, time, and status.
- Evidence payload retention for support and audits.
Messaging must be controlled: who can send, what can be sent, and how failures are handled.
- Role-based access to sending and templates.
- Rate limiting and batching to respect provider limits.
- Safe retry policies to avoid duplicate customer notifications.
The messaging realities we design for
WhatsApp messaging in production is constrained. The integration is designed for those constraints, not against them.
Delivery can be delayed. Status tracking and evidence help teams respond calmly and correctly.
Providers throttle. We design for controlled queues so you don’t get bans or silent drops.
“It failed in the background” is not acceptable. Failures are surfaced to teams with context.
How we implement without spamming customers
We start with controlled transactional messages, prove evidence and reliability, then expand into alerts and broader messaging.
Set templates, link evidence trails, and enable controlled sending for core documents.
- Pick the first documents (Invoice, Receipt, Statement, Delivery).
- Define template rules and recipient mapping per document.
- Enable message logging + status tracking + safe retries.
Add targeted alerts and scale throughput with throttling and queue controls.
- Enable operational alerts (exceptions, failures, anomalies).
- Configure team routing and alert throttling.
- Introduce batching/rate limiting tuned to your volume.
Frequently asked questions
Straight answers to the questions we hear most about this integration.
Any customer-facing update tied to an ERP document: order confirmations, invoices and receipts, payment confirmations, statement reminders, and delivery or dispatch updates. Each message is linked back to its source document (Sales Order, Sales Invoice, Payment Entry, Delivery Note) and keeps a delivery evidence trail. That means finance and operations can prove exactly what was sent, to whom, and when.
A personal or WhatsApp Business app number is meant for manual chats on a phone and is not built for automated, high-volume system messaging - and automating it risks being banned. The WhatsApp Business API (Cloud API) is the official channel for sending automated transactional notifications from software like ERPNext. We integrate through the Business API so sending is reliable, compliant, and rate-limited rather than fragile.
Yes. WhatsApp requires that recipients have opted in to receive business messages, and any business-initiated notification must use a message template that Meta has pre-approved. We help you structure opt-in capture and design templates for your order, payment, and delivery flows so they clear approval. Working within these rules is what protects your number from being blocked.
Every message runs through a controlled queue with rate limiting, so bursts do not trigger provider throttling or silent drops. Each message carries a status lifecycle - queued, sent, delivered, or failed - with reason codes, and retries are deterministic so customers are not spammed with duplicates. If a message fails, it is surfaced to your team with context instead of being lost in a background job.
Messages can be triggered by document events such as a submitted Sales Order, a paid Sales Invoice, a recorded Payment Entry, or a dispatched Delivery Note. Operational exceptions - posting failures, payment anomalies, or pending approvals - can also route alerts to the right internal team. Triggers are mapped explicitly per document and role, so only the intended events send messages.
You need a dedicated phone number that is not already active on a personal WhatsApp account, a Meta Business account, and a WhatsApp Business API (Cloud API) setup with a verified business profile. We handle the ERPNext side - template configuration, event triggers, queueing, and evidence logging - and guide you through the Meta onboarding and template approval. Once the number is verified and templates are approved, transactional sending can go live.
Related insights
Plain-language guides on automating customer messaging and retention over WhatsApp.
How to answer routine WhatsApp queries automatically without losing the human touch.
Bring WhatsApp, Instagram, and Facebook messages into a single place your team can work.
Turn order, payment, and delivery events into timely follow-ups that keep customers coming back.
Want WhatsApp messaging you can prove and operate?
We’ll review your documents, customer touchpoints, and internal alert needs - then propose a rollout that keeps delivery evidence, respects rate limits, and avoids silent failures.