A build-to-order ERPNext app that connects your WhatsApp Business (Cloud API) account directly to ERPNext, so invoices, quotations, order updates, and payment alerts reach customers on the channel they actually read. ECOSIRE builds, installs, and supports it for your ERPNext v15/v16 site. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $249.00 USD; request a quote for a scoped proposal.

A build-to-order ERPNext app that connects your WhatsApp Business (Cloud API) account directly to ERPNext, so invoices, quotations, order updates, and payment alerts reach customers on the channel they actually read. ECOSIRE builds, installs, and supports it for your ERPNext v15/v16 site.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
Most SMBs that live on WhatsApp still email PDF invoices and quotations that sit unread, then chase payment and delivery status over a phone that has nothing to do with ERPNext. Out of the box, ERPNext ships email and SMS notification channels plus print formats, but there is no first-class WhatsApp Cloud API sender, no template-message registry, no attachment delivery of the auto-generated invoice PDF, and no way to see the customer's reply next to the Sales Order it belongs to. Teams end up copy-pasting order numbers and totals into a personal WhatsApp, which is slow, error-prone, and invisible to the rest of the business.
Dedicated Frappe app with its own module, `hooks.py` doc events, and `scheduler_events` — no monkey-patching of ERPNext core
`WhatsApp Settings` single DocType storing phone number ID, WABA ID, and access token in an encrypted `Password` field
`WhatsApp Template` DocType that mirrors your Meta-approved templates, their language codes, and ordered variable placeholders
Automatic send on `on_submit` doc events for Sales Invoice, Payment Entry, Delivery Note, Sales Order, and Quotation (mapped to your chosen triggers)
Invoice and quotation PDFs rendered from your existing ERPNext print format and delivered as WhatsApp document attachments
Whitelisted, signature-verified webhook endpoint for inbound messages and Meta delivery/read receipts
ECOSIRE builds a proper Frappe app — its own module, DocTypes, and hooks.py wiring — that turns ERPNext into a WhatsApp sender and receiver against Meta's official WhatsApp Cloud API. We add a WhatsApp Settings single DocType (phone number ID, WABA ID, and encrypted access token stored as a Password field), a WhatsApp Template DocType that mirrors your Meta-approved message templates and their variable placeholders, and a WhatsApp Message log DocType that records every outbound and inbound message, its Meta message ID, and delivery status. Doc events registered in hooks.py (for example Sales Invoice: on_submit, Payment Entry: on_submit, Delivery Note: on_submit) trigger server-side sends; the invoice or quotation is rendered from your existing print format to PDF and uploaded as a WhatsApp document attachment, so the customer receives the real branded document, not a link.
On the technical side we keep everything inside Frappe's conventions so your site stays upgrade-safe. Outbound sends run through the background queue (frappe.enqueue) so a slow Meta response never blocks a submit; retries and scheduled digests hook into scheduler_events. Inbound messages and delivery receipts arrive on a whitelisted webhook endpoint that verifies Meta's signature, then upserts the WhatsApp Message log and links it back to the customer and the relevant transaction. Role profiles and DocType permissions control who can send, who can only view the chat, and which templates each role may use. A client script adds a "Send on WhatsApp" button to Sales Invoice, Sales Order, and Quotation, and a lightweight two-way chat view lets your team reply from within ERPNext. Everything is exposed through the standard Frappe REST API and whitelisted methods, so your other tools can trigger sends too.
Because this is build-to-order, you are not downloading a generic marketplace add-on and hoping it fits. After a short scoping call we confirm exactly which documents trigger which templates, your language and branding, and your Meta WhatsApp Business setup. We build against your ERPNext v15 or v16 site, test on a staging copy, run UAT with your team, then install on production with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope, and you receive the full source code and git repository so you are never locked in.
Runs a small trading, retail, or services business where nearly all customer contact happens on WhatsApp. Wants invoices, quotations, and order updates to go out automatically from ERPNext instead of being retyped into a personal phone.
Owns the ERPNext site and needs a channel that is auditable, permissioned, and upgrade-safe. Cares that sends are logged, roles are enforced, and the app follows Frappe conventions so v15/v16 upgrades don't break.
Sends quotations and chases payment daily. Wants one-click 'Send on WhatsApp' from the Sales Order or Sales Invoice, automatic payment-received confirmations, and replies visible next to the transaction.
Fields 'where is my order' questions. Needs delivery and dispatch notifications sent automatically and a two-way chat inside ERPNext so replies are handled without leaving the system.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل تطبيق WhatsApp Business Integration for ERPNext ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد تطبيقات مقعدك، أو قم بتشغيل "bench get-app" مع المسار إلى التطبيق المستخرج.
قم بتشغيل `bench --site SITE_NAME install-app APP_NAME` متبوعًا بـ`bench migrate` لتثبيت WhatsApp Business Integration for ERPNext وتطبيق مخططه.
افتح إعدادات ترخيص ECOSIRE على موقعك وقم بتنشيط مفتاح الترخيص الخاص بك. يتطلب تطبيقي ecosire_connect وecosire_license_client المجانيين.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Fit to your workflow | Built around your exact document triggers, templates, and branding | Fully bespoke but you define and maintain everything | Generic feature set; you adapt your process to it | |
| WhatsApp Cloud API integration | Official Cloud API with templates, attachments, and webhooks | Depends on your team's Meta API expertise | Often present but varies in depth and template handling | |
| Invoice/quotation PDF delivery | Renders your print format to PDF as a WhatsApp attachment | Possible with in-house effort | Sometimes text-only or link-only | |
| Two-way chat inside ERPNext | Inbound webhook + chat view linked to transactions | Buildable but significant effort | Varies; often outbound-only | |
| Upgrade safety | Separate Frappe app, standard hooks, no core edits | Depends on discipline of your build | Depends on the vendor's app quality | |
| Source code ownership | Full git repository handed over to you | You own it by definition | Usually closed-source, license-locked | |
| Delivery time | 2-4 weeks from confirmed scope, build-to-order | Weeks to months depending on hiring and scope | Instant install, but integration work still needed | |
| Support and accountability | Post-go-live support window plus optional ongoing support | Your team or contractors own all support | Ticket-based, tiered by plan |
No. This is a build-to-order engagement. ECOSIRE builds the app against your specific ERPNext v15 or v16 site, your document triggers, and your WhatsApp Business account, then installs and supports it. There is no instant download.
Typical delivery is 2-4 weeks from confirmed scope. The timeline starts once we've agreed on which documents trigger which WhatsApp templates, your branding and languages, and your Meta WhatsApp Business setup. Simpler scopes finish faster; heavy customization or many templates can extend it.
Yes. The app uses Meta's official WhatsApp Cloud API, which requires a verified WhatsApp Business Account and a registered phone number. Business-initiated messages must use Meta-approved message templates. We assist with WABA onboarding and template submission, but the account and number are yours.
It is built as a separate Frappe app using standard conventions — its own DocTypes, `hooks.py` doc events, scheduler events, whitelisted methods, and client scripts — with no edits to ERPNext core. That keeps your site upgrade-safe across v15/v16 patch releases.
Every build includes a post-go-live support window for bug fixes and adjustments. Because you receive the full git repository, your own team can extend the app, and ECOSIRE offers ongoing support or enhancement engagements beyond the initial window if you want them.
Yes. The app renders your existing ERPNext print format to PDF and delivers it as a WhatsApp document attachment, so customers receive the real branded invoice or quotation alongside the template message.
Yes. Inbound messages arrive on a signature-verified webhook and are logged in the `WhatsApp Message` DocType, linked to the customer and relevant transaction. Your team can read and reply from a two-way chat view inside ERPNext, with permissions controlling who can respond.
A build-to-order ERPNext app that connects your WhatsApp Business (Cloud API) account directly to ERPNext, so invoices, quotations, order updates, and payment alerts reach customers on the channel they actually read. ECOSIRE builds, installs, and supports it for your ERPNext v15/v16 site.