WhatsApp Ordering & POS Notifications for ERPNext

Key Features

Dedicated Frappe app (`whatsapp_ordering_pos`) with `WhatsApp Ordering Settings` single DocType for Cloud API/BSP credentials, template mapping and business-hours rules

Whitelisted inbound webhook (`@frappe.whitelist(allow_guest=True)`) with HMAC-256 signature verification and idempotent message de-duplication

Chat-to-order parser that maps WhatsApp catalog selections to ERPNext `Item` records and drafts a `Sales Order` or POS `Sales Invoice` for one-tap staff confirmation

`WhatsApp Order Inbox` DocType so pending chat orders queue inside ERPNext instead of a phone screen

`hooks.py` `doc_events` on `Sales Invoice` submit that renders your Print Format to PDF and delivers the digital receipt over WhatsApp

Order-status automation firing ready-for-pickup, out-for-delivery and completed updates on document state transitions

Reservation and booking reminders built on ERPNext `Appointment`/`Event` (or a `Table Reservation` DocType) with timed re-confirmation prompts

`scheduler_events` cron jobs for reminder dispatch, retry of failed sends and daily broadcast windows

Segmented loyalty and promo broadcasts off `Customer` and `Loyalty Program` data via approved WhatsApp template messages

Background dispatch through `frappe.enqueue` with per-number rate limiting, exponential-backoff retry and delivery-status callbacks written back to `WhatsApp Message Log`

Opt-in/opt-out consent tracking and quiet-hours enforcement to stay within WhatsApp Business policy

Client Scripts adding a `Send on WhatsApp` action inside POS, Sales Order and Sales Invoice forms

Whitelisted REST methods for send, template-send and delivery-status so external channels or a kiosk can trigger messages

Role Profiles and DocType permissions isolating cashier, floor-manager and marketing access to messaging

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

If WhatsApp is where your customers actually place orders, ERPNext leaves a gap. Native ERPNext POS is a fast in-store checkout, and Sales Order/Sales Invoice model the transaction cleanly, but there is no built-in bridge to a WhatsApp Business number: no way to turn an inbound chat into a POS order, no automatic digital receipt over WhatsApp, and no ready-for-pickup or reservation reminder driven by document state. Teams end up re-keying chat orders into POS by hand, screenshotting receipts, and chasing no-shows — errors, delays and lost repeat business that grow with every order.

ECOSIRE builds a proper Frappe app that closes that gap end to end. We add a WhatsApp Ordering Settings single DocType for your WhatsApp Business Cloud API (or approved BSP) credentials, message-template mapping and business-hours rules, plus WhatsApp Message Log and WhatsApp Order Inbox DocTypes so every inbound and outbound message is auditable inside ERPNext. Inbound messages arrive on a whitelisted webhook endpoint (@frappe.whitelist(allow_guest=True)) with HMAC signature verification; a catalog/order parser maps chat selections to Item records and drafts a Sales Order or POS Sales Invoice, so staff confirm rather than retype. Outbound messaging is driven by hooks.py doc_events — on Sales Invoice submit we render and send the digital receipt (with the print format PDF attached), and on status transitions we fire ready-for-pickup and out-for-delivery updates.

The build reuses ERPNext primitives instead of shadowing them. Reservations and bookings ride on ERPNext Appointment/Event (or a lightweight Table Reservation DocType when needed), and a scheduler_events cron sends timed reminders and re-confirmations without anyone watching the clock. Loyalty and promo broadcasts are segmented off Customer and Loyalty Program data and dispatched via approved WhatsApp template messages through the background queue (frappe.enqueue) with per-number rate limiting and opt-out handling, so you stay inside WhatsApp policy. Client Scripts add a "Send on WhatsApp" action to POS and Sales documents, whitelisted methods expose send/status endpoints to the Frappe REST API, and Role Profiles plus DocType permissions keep messaging scoped to cashiers, floor managers and marketing separately.

Because this is build-to-order, nothing here is a generic download you configure alone. After a short scoping call we confirm exact flows, message templates and the WhatsApp number/BSP you use, then build against your target ERPNext version — full support for Frappe/ERPNext v15 and the v16 line. You get the installable app source for your version, installation and configuration on your bench, a UAT pass on staging with a rollback plan, and a git repository handover. Typical delivery is 2–4 weeks from confirmed scope.

What you get

Installable Frappe app source code for your target ERPNext version (v15 or v16), built to your confirmed scope

Installation and configuration on your bench — app install, site config, WhatsApp Cloud API/BSP webhook wiring and template registration

Technical documentation: DocType reference, `hooks.py` doc-event map, scheduler events, whitelisted endpoints and env/credential setup

End-user guide plus a live training session for cashiers, floor staff and marketing users

UAT on a staging site with signed-off test cases and a documented rollback plan

Post-go-live support window for fixes and adjustments after launch

Git repository handover with full commit history and README

Message-template pack and consent/opt-out policy notes aligned to WhatsApp Business rules

Who this is for

Restaurant owner running orders on WhatsApp

Takes most takeaway and delivery orders through a WhatsApp Business number and re-keys them into ERPNext POS by hand. Needs chat orders to land as draft POS invoices, receipts sent automatically, and ready-for-pickup pings that cut counter crowding and missed collections.

Retail store manager

Runs a counter on ERPNext POS and wants order confirmations, digital receipts and back-in-stock or promo broadcasts on WhatsApp without exporting customer lists to a separate blast tool. Needs marketing access scoped away from the cashier till.

ERPNext administrator / systems owner

Owns the bench and cares about a clean, upgrade-safe Frappe app: proper DocTypes, `hooks.py` doc events, scheduler jobs, signature-verified webhooks and role permissions — not brittle customizations that break on the next v15/v16 update.

Multi-branch F&B operations lead

Coordinates reservations, pickups and loyalty across several outlets. Needs booking reminders on ERPNext `Appointment`/`Event`, per-branch templates, and delivery reporting from `WhatsApp Message Log` to see what actually reached customers.

How WhatsApp Ordering & POS Notifications for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor
Chat-to-POS order capture	Inbound WhatsApp parsed to draft Sales Order/POS invoice for staff confirmation	Possible but you design and maintain the parser and webhook	Usually one-way notifications only, no order capture into POS
Digital receipts over WhatsApp	Auto-sent on `Sales Invoice` submit with Print Format PDF attached	Build the doc-event hook and PDF render yourself	Sometimes, but often generic and not tied to your print format
Order-status & pickup alerts	Fired on document state transitions (ready, out-for-delivery, done)	Custom status mapping and triggers to write and test	Limited fixed statuses, rarely POS-aware
Reservation / booking reminders	Built on `Appointment`/`Event` with scheduled re-confirmations	Bespoke scheduler and reminder logic	Rare; usually a separate booking product
Loyalty / promo broadcasts	Segmented off `Customer`/`Loyalty Program`, queued approved templates with opt-out	Segmentation, rate-limiting and consent all DIY	Broadcast add-on, often ignores loyalty data and consent
ERPNext version fit (v15/v16)	Built and tested against your exact target version	Depends entirely on your team's discipline	Whatever the vendor last supported; may lag your version
Delivery & ownership	2–4 weeks from scope; git repo handover, code is yours	Timeline and cost open-ended; you own it but carry all risk	Instant install but a black box you cannot extend
Support after go-live	Included support window plus optional maintenance	Only your in-house team	Vendor tickets, roadmap not yours to steer

Frequently Asked Questions about WhatsApp Ordering & POS Notifications for ERPNext

How long does delivery take?

This is a build-to-order app, not an instant download. After a short scoping call to confirm your flows, message templates and WhatsApp number/BSP, typical delivery is 2–4 weeks from confirmed scope. Tighter or larger scopes are quoted individually, and you approve the plan before we build.

What do I get for support and updates after go-live?

Every build includes a post-go-live support window for bug fixes and adjustments, plus a git repository handover so the code is yours. We build against your target version and can quote ongoing maintenance or a version-compatibility update when you upgrade ERPNext. You are never locked to us for future changes.

Which ERPNext versions are supported?

We build for Frappe/ERPNext v15 and the v16 line. We confirm your exact bench version during scoping and target that, using upgrade-safe patterns — a dedicated app, `hooks.py` doc events, DocTypes and scheduler events — rather than in-place core edits.

Do I need the WhatsApp Business API, and can I use my existing provider?

Yes — the app connects to the official WhatsApp Business Cloud API or an approved Business Solution Provider (BSP). You supply (or we help you obtain) the number, credentials and pre-approved message templates. We wire the signature-verified webhook and template mapping into `WhatsApp Ordering Settings`.

Will chat orders create real ERPNext documents or a separate silo?

Real ERPNext documents. Inbound orders are parsed against your `Item` list and drafted as a `Sales Order` or POS `Sales Invoice` in a `WhatsApp Order Inbox`, where staff confirm them. Nothing bypasses ERPNext stock, pricing or accounting — WhatsApp is the channel, ERPNext stays the system of record.

How do you keep broadcasts compliant with WhatsApp policy?

Loyalty and promo messages go out only as approved template messages, dispatched through the background queue with per-number rate limiting, opt-in/opt-out tracking and quiet-hours enforcement. Every send and delivery status is written to `WhatsApp Message Log` for a full audit trail.

Can messaging access be restricted by role?

Yes. We ship Role Profiles and DocType permissions that separate cashier, floor-manager and marketing access — so a till operator can send a receipt but cannot launch a promo broadcast, and marketing cannot touch POS invoices.