Guides, glossaries and calculators to help you scope, cost and run an ERPNext implementation — from GST and e-invoicing setup to module-by-module walkthroughs.
Quick definitions of key terms
Expert insights and updates
Simple step-by-step resources
Easy explanations through videos.
Complete IRN flow in ERPNext (2026)
ERPNext HRMS for India's Labour Codes
ERPNext for Indian hospitals (NABH, ABDM, DPDP)
DPDP Act 2023 Compliance in ERPNext
Reach customers where they actually reply. Email gets to a spam folder, a printed invoice gets to a filing tray, and neither gets read on a shop floor. WhatsApp does. Which is exactly why it needs discipline: the same reach that makes a dispatch update useful makes an unwanted broadcast a reason to block you.
This uses the official WhatsApp Business Platform through a provider, not an unofficial automation of a personal account.
Yes, through the WhatsApp Business Platform via an approved provider. Document events in ERPNext — a submitted invoice, a dispatched delivery note, a payment request — trigger pre-approved message templates to the customer's number, with the document attachable as a PDF and delivery status written back.
The technical side is simple. The ways businesses get this wrong are almost entirely about policy and judgement.
Automating a personal or business app account through an unofficial library breaches the platform's terms. It works until the number is restricted, at which point you lose the channel and the conversation history with it. There is no recovery worth planning around.
Business-initiated messages have to use templates approved by the platform. Discovering that mid-project, or having a template rejected days before go-live, is the most common cause of delay on this integration.
Having someone's number because they bought from you is not the same as having permission to message them. Without a recorded opt-in and a working opt-out, complaints accumulate and quality rating falls.
Once it works, the temptation is to send every status change. Recipients mute or block, and the messages that genuinely matter — a dispatch, a payment link — stop being seen.
A small number of messages that people are glad to receive beats a comprehensive notification scheme nobody reads.
Submitting an invoice, dispatching a delivery note or raising a payment request sends the matching template to the party's number, with the document attached as a PDF where the template allows.
Triggered from the document event itself, so nobody has to remember to send anything.
Templates are written to fit both the platform's rules and how you actually speak to customers, then submitted for approval early enough that rejection is not a go-live risk.
Variables are mapped to document fields, so one approved template serves every invoice rather than needing one per case.
Opt-in is recorded against the contact with its source and date, and an opt-out keyword stops messaging immediately and permanently for that number.
This is what protects the channel. A falling quality rating restricts your ability to message everyone, not just the complainant.
Sent, delivered, read and failed statuses return to the document, so a failed dispatch notification is visible rather than assumed successful.
Useful in collections particularly — knowing a payment reminder was read changes the follow-up conversation.
The same channel carries approval requests, stock alerts and exception notifications to your own team, which is often where it earns its keep fastest.
Internal messaging to opted-in staff avoids most of the consent complexity while solving a real response-time problem.
Each trigger is switched on deliberately. The default position is that a message is not sent.
| ERPNext event | WhatsApp message | Direction | Notes |
|---|---|---|---|
| Sales Order submitted | Order confirmation template | ERPNext → WhatsApp | Order number, value and expected date as variables |
| Sales Invoice submitted | Invoice template + PDF | ERPNext → WhatsApp | Attachment subject to template type and size limits |
| Payment Request raised | Payment link template | ERPNext → WhatsApp | Works with the payment gateway setup |
| Delivery Note submitted | Dispatch template | ERPNext → WhatsApp | Vehicle and docket number where captured |
| Payment overdue | Reminder template | ERPNext → WhatsApp | Scheduled, throttled, and skipped for opted-out numbers |
| Approval required | Internal alert | ERPNext → WhatsApp | To opted-in staff numbers |
| Delivery status | Written back to the document | WhatsApp → ERPNext | Sent, delivered, read or failed |
| Opt-out keyword | Contact marked unsubscribed | WhatsApp → ERPNext | Immediate and permanent for that number |
| Inbound reply | Comment on the document or contact | WhatsApp → ERPNext | Optional; keeps the conversation with the record |
Template approval sits on the critical path, so it starts first regardless of what else is happening.
A short list, decided by whether a recipient would be glad to receive it. Everything else stays off. This conversation determines whether the channel stays valuable.
Templates are drafted and submitted for approval before configuration begins, because approval time is outside anyone's control and rejection means a rewrite.
Your WhatsApp Business account and provider credentials are configured, with the number verified and the display name approved. The account is contracted in your own name.
Opt-in capture, the opt-out keyword and suppression on send are configured together, and tested by opting a number out and confirming it stops receiving.
One template goes live to a limited group for a fortnight. Delivery rates, replies and complaints are reviewed before anything else is switched on.
Timeline shown is indicative and excludes template approval and business verification, both of which sit with the platform rather than with us.
Most of these are platform rules rather than integration choices, which means no amount of engineering changes them.
The channel is worth protecting. Almost everything on this list exists to stop a short-term gain costing you the ability to reach customers at all.
Yes, a WhatsApp Business Platform account with a verified number and approved display name, contracted in your own name through a provider. The ordinary WhatsApp Business app is a different product and is not what this integrates with.
Yes, subject to the template type and the platform's attachment size limits. For larger documents the common pattern is a secure link rather than an attachment, which also lets you see whether it was opened.
Outside a customer-initiated conversation window, business messages must use templates approved in advance. Within that window free-form replies are allowed. It is a platform rule, and working around it is what gets numbers restricted.
A keyword reply marks the contact unsubscribed immediately and permanently for that number, and every subsequent send checks that flag. Honouring opt-outs properly protects your quality rating, which governs your ability to message everyone else.
Yes, and it is one of the more effective uses. Reminders are scheduled, throttled so a customer is not messaged repeatedly, and suppressed for opted-out numbers. Delivery and read status returning to the document changes how collections follows up.
The platform charges per conversation, billed to your own account, with rates varying by conversation category and country. That is separate from implementation. Choosing a small number of high-value messages keeps the running cost proportionate.
A short call about which updates your customers actually want and which ones would just get you muted.
WhatsApp and the WhatsApp Business Platform are products of Meta Platforms, Inc. ERPNext and Frappe are trademarks of Frappe Technologies Pvt. Ltd. These names are used here only to identify the services described. Finstein is not affiliated with or endorsed by Meta Platforms, Inc., and WhatsApp Business accounts are contracted directly in your own name.
