If your brand sells through a distributor and dealer network, ERPNext core gives you Customers, Sales Orders and a Customer Portal — but nothing that models the primary-to-secondary sales flow your field teams actually run. Distributors email or WhatsApp their orders, secondary sales (distributor-to-retailer sell-out) live in spreadsheets that arrive weeks late, trade schemes are reconciled by hand, and every dealer call to your back office is another "what's my credit limit and outstanding?" query. ERPNext's stock Customer Portal exposes invoices and a generic order form, but it has no concept of dealer-specific price lists, scheme eligibility, secondary-sales returns or a claim-approval workflow. That gap is where margin leaks and where field visibility dies.

ECOSIRE builds a dedicated Distributor & Dealer Portal as a proper Frappe app installed on your own ERPNext v15/v16 site — not a bolt-on spreadsheet and not a hosted third-party tool. The portal is driven by real DocTypes: a Distributor Order (with the dealer's contract price list resolved server-side so nobody can order off-tariff), a Secondary Sales Entry for sell-out capture down to retailer and SKU, a Trade Scheme master with eligibility rules, and a Scheme Claim with a controlled Draft to Submitted to Approved to Settled workflow. Web pages built on Frappe's portal framework (www/ pages plus web-form DocTypes) give each distributor a login scoped by Role Profile and User Permissions, so a dealer only ever sees their own orders, ledger and claims. The dealer-facing catalog and price list are rendered per-account, and credit-limit plus outstanding balance are read live from the customer's GL — no stale numbers.

Under the hood the business logic lives where ERPNext expects it. hooks.py doc events (validate, on_submit, on_cancel) enforce credit blocks, scheme eligibility and secondary-sales-versus-primary reconciliation; server scripts and whitelisted methods (@frappe.whitelist()) back the portal's AJAX calls and the mobile field-app endpoints via the Frappe REST API; client scripts drive live price and scheme feedback as the dealer builds an order. Scheduler events run nightly to age claims, recompute scheme accruals and flag distributors breaching credit terms. Approved Distributor Order documents map cleanly onto standard ERPNext Sales Orders so your existing accounting, inventory and dispatch flows are untouched — the portal sits on top of ERPNext, it does not fork it. Dashboards and report views turn the captured secondary sales into primary-versus-secondary coverage, scheme cost and dealer-performance reporting you could never get from email.

Because this is build-to-order, we tailor the DocTypes, price-list logic, scheme formulas and approval hierarchy to how your channel actually operates before we write a line of production code. A scoping call and a short requirements pass produce a fixed scope; we then build on a staging copy of your ERPNext, run UAT with your channel and finance teams, and deploy with a rollback plan. Typical delivery is one working week from confirmed scope depending on the number of scheme types and integrations. You receive the full source app and git repository, so the portal is yours to keep, extend and self-host — with an agreed post-go-live support window from ECOSIRE.