Push Notifications (Web & Mobile/FCM) for ERPNext

ECOSIRE builds a proper Frappe app — its own module, DocTypes, and hooks.py wiring — that closes that gap end to end. On the browser side we register a Service Worker and capture the W3C Push subscription (endpoint plus p256dh/auth keys) against the signed-in user, storing each in a Push Subscription DocType with device metadata and an active flag. On the mobile side we integrate the Firebase Admin SDK server-side, store FCM registration tokens per device, and handle token refresh and invalidation (pruning NotRegistered/Unregistered tokens returned by Firebase so your audience stays clean). A Push Campaign DocType and a Push Template DocType give your marketing and operations teams a place to compose rich pushes — title, body, image, click-through deep link, and CTA buttons — and target them.

Delivery is driven two ways. Event-triggered pushes hang off doc_events in hooks.py (for example on_submit of Sales Order, on_update of Issue) and off scheduler_events for time-based sends like abandoned-cart or renewal reminders; the heavy lifting runs through the Frappe background queue (frappe.enqueue) so a large fan-out never blocks the web worker. Campaign pushes resolve their audience from saved segments — a Push Segment DocType backed by a report query or filter on Contact, Customer, Portal User, or any linked DocType — so a campaign can target "customers in UAE with an open subscription" without hand-built lists. Whitelisted API methods (@frappe.whitelist()) expose subscription register/unregister and a send endpoint over the Frappe REST API for your front-end and mobile clients, all gated by role-profile permissions so only authorized roles can broadcast. Every send is logged in a Push Log DocType with per-recipient status, provider response, and click-through tracking for open-rate reporting.

Because this is build-to-order, nothing ships as a one-click marketplace download. We start with a short scoping call to confirm which ERPNext events matter to you, your Firebase project details, the DocTypes to segment on, and your v15 or v16 target. We then build your version of the app against a staging bench, run UAT with you, and install it on production with a rollback plan. Typical delivery is 2 to 4 weeks from confirmed scope, and you receive the full source in a git repository you own, so you are never locked to us.