If you sell on ERPNext and want partners driving your growth, you quickly hit a wall. ERPNext core has no concept of an affiliate, a referral link, click-to-sale attribution, or a commission ledger that ties a payout back to specific Sales Invoices. Teams end up stitching this together in spreadsheets, running a separate SaaS affiliate platform that never reconciles against actual paid invoices, and manually calculating who is owed what at month end. Attribution disputes, double-counted conversions, and payouts that do not match booked revenue are the predictable result — and none of it lives inside the system where your orders, invoices, and customers already are.

ECOSIRE builds the Affiliate & Referral Program as a proper Frappe app installed onto your ERPNext bench (v15/v16). It introduces first-class DocTypes — Affiliate, Referral Link, Referral Visit/Referral Click, Referral Conversion, Commission Rule, Commission Tier, and Affiliate Payout — so every partner, link, click, attributed sale, and payment is an auditable record with its own permissions and reports. Affiliates register through a Frappe Web Form and manage their own account in a portal built on the Frappe website framework, where they generate unique referral links and coupon codes, watch clicks and conversions in real time, and download their statements.

Technically, the tracking loop is wired the way ERPNext expects. A whitelisted, guest-accessible REST endpoint captures inbound clicks and drops a first-party attribution cookie; a hooks.py doc_events handler on Sales Order and Sales Invoice on_submit reads that attribution (or a matched coupon code) and creates the Referral Conversion, applying your attribution model — last-click, first-click, or a configurable cookie window. Commission Rule records evaluate tiered and category-specific rates via server scripts, so a partner who crosses a revenue threshold moves to a higher band automatically. A scheduler event (scheduler_events in hooks.py) runs the periodic payout cycle: it aggregates approved conversions, nets refunds and cancellations, generates Affiliate Payout statements, and can post the corresponding Journal Entry or Payment Entry against your configured expense account. Role profiles keep affiliates scoped to only their own data, while your finance team approves and settles from the desk.

Because it is native, everything is reportable through ERPNext's own Report Builder and Query/Script Reports, exposed on the Frappe REST API for your storefront or app, and governed by the same permission and audit-log model as the rest of your data — no external system to reconcile.

This is build-to-order, not an instant download. We start with a short scoping call to lock your commission structure, attribution rules, payout cadence, and storefront integration, then build the app to that spec, test it on a staging bench, and install it on your ERPNext instance. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source code, documentation, a training session, and a post-go-live support window — and you own the git repository at handover.