A build-to-order Frappe app that recurringly pulls your IndiaMART buyer inquiries into ERPNext as Lead records — mapping product interest, detecting duplicates, and auto-assigning to the right salesperson. ECOSIRE scopes, builds, installs, and supports it for you. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $149.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that recurringly pulls your IndiaMART buyer inquiries into ERPNext as Lead records — mapping product interest, detecting duplicates, and auto-assigning to the right salesperson. ECOSIRE scopes, builds, installs, and supports it for you.
Keine Zahlung jetzt. Dies sendet eine Angebotsanfrage an unser Team – wir melden uns per E-Mail mit Preisen und nächsten Schritten.
If you sell on IndiaMART, every inquiry that lands in your seller Lead Manager but never reaches ERPNext is a follow-up that happens late or never happens at all. Most Indian manufacturers and traders end up copy-pasting buyer names, phone numbers, and product interest from the IndiaMART panel into ERPNext by hand — or worse, working leads out of WhatsApp and a spreadsheet while their ERPNext CRM stays half-empty. ERPNext ships a capable Lead DocType, assignment rules, and a Sales pipeline, but it has no native connector to the IndiaMART Push/Pull Lead API, no scheduled ingestion, and no de-duplication logic tuned to how the same buyer re-inquires across multiple products. That gap is exactly where response time — the single biggest driver of B2B conversion — quietly leaks away.
Dedicated Frappe app with its own module, installed via `bench get-app` and `bench install-app` — no ERPNext core patches
IndiaMART Sync Settings DocType storing CRM API key and glusr credentials as encrypted `Password` fields, with configurable sync window and default lead owner
Recurring pull via a Frappe `scheduler_events` hook (hourly/daily cadence you choose) against the IndiaMART Push/Pull Lead API
On-demand `@frappe.whitelist()` "Sync Now" method exposed to an authorized client-script button for manual re-pulls
Automatic `Lead` creation and update carrying buyer name, mobile, email, city/state, query text, and enquired product
Source query-id stamped on every record so the same IndiaMART inquiry is never imported twice (idempotent ingestion)
We build a dedicated Frappe app (its own module, installed on your bench with bench get-app / bench install-app) that closes that gap. A settings DocType holds your IndiaMART CRM API key, glusr credentials, sync window, and default owner, encrypted as a Password field. A Frappe scheduler_events hook (hourly or at your chosen cadence, plus an on-demand "Sync Now" button via a whitelisted method) calls the IndiaMART pull-lead endpoint, normalizes each inquiry, and creates or updates a Lead — carrying buyer name, mobile, email, city/state, the IndiaMART query text, and the specific product enquired into standard and custom fields. Every record is stamped with the source IndiaMART query id so the same enquiry is never imported twice.
De-duplication runs on a configurable key — mobile number and/or email, with fuzzy handling for the +91/leading-zero variants IndiaMART returns — so a buyer who pings you about three products becomes one Lead with a threaded activity trail, not three orphan records. Product-interest mapping links the enquired product string to your ERPNext Item (or a lookup table you approve during scoping), so sales sees exactly what the buyer wants. Auto-assignment applies your rules — round-robin across a sales team, or territory/product-based routing using ERPNext Assignment Rules and ToDo — and can fire a notification so the owner acts within minutes. Everything is built on supported extension points: hooks.py doc events, server scripts, optional client scripts for the "Sync Now" UX, role-based permissions, and the Frappe REST API — no core patches — so it upgrades cleanly on Frappe/ERPNext v15 and v16.
Because this is build-to-order, we start with a short scoping call to confirm your IndiaMART API access, field mapping, dedupe key, and assignment logic, then build against your real (or a sandbox) inquiry payload. You get the installable app source for your version, deployment on your bench, UAT on a staging site with a rollback plan, and a handover of the git repository — not a black box. Typical delivery is 2–4 weeks from confirmed scope, and you own the code.
A B2B seller generating a steady stream of IndiaMART inquiries who wants every buyer to land in ERPNext automatically so no lead is worked out of the IndiaMART panel or WhatsApp.
Owns follow-up SLAs and needs inbound IndiaMART leads auto-assigned by territory or product, with duplicates merged, so reps act within minutes instead of hours.
Maintains the ERPNext instance and wants a clean, upgrade-safe Frappe app using supported hooks and the REST API — with source, docs, and a rollback plan — not a fragile core patch.
Pays for IndiaMART lead subscriptions and wants provable ROI: every purchased inquiry captured, assigned, and followed up inside the CRM they already run.
Kaufen Sie die Lizenz auf ecosire.com und laden Sie die ZIP-Datei der IndiaMART Lead Sync for ERPNext-App von Ihrem Konto-Dashboard herunter.
Extrahieren Sie die ZIP-Datei in den Apps-Ordner Ihrer Bank oder führen Sie „bench get-app“ mit dem Pfad zur extrahierten App aus.
Führen Sie „bench --site SITE_NAME install-app APP_NAME“ gefolgt von „bench migrate“ aus, um IndiaMART Lead Sync for ERPNext zu installieren und sein Schema anzuwenden.
Öffnen Sie die ECOSIRE-Lizenzeinstellungen auf Ihrer Website und aktivieren Sie Ihren Lizenzschlüssel. Erfordert die kostenlosen Apps ecosire_connect und ecosire_license_client.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| IndiaMART connectivity | Purpose-built pull against the IndiaMART CRM/Lead API, scoped to your account | You research and wire the API yourself | Generic connector, may not fit your fields or plan | |
| Recurring sync | Scheduler hook at your cadence plus on-demand Sync Now | You build and schedule the job yourself | Fixed cadence, limited control | |
| De-duplication | Source query-id idempotency plus configurable mobile/email dedupe | Must design and test dedupe logic yourself | Basic or absent; often creates duplicates | |
| Product-interest mapping | Enquired product mapped to your ERPNext `Item` or approved table | You define the mapping model | Stored as raw text, rarely mapped to Items | |
| Auto-assignment | Assignment Rules with round-robin or territory/product routing | You configure assignment yourself | Owner set to one static user | |
| Upgrade safety | Supported hooks/REST API, no core patches — clean v15/v16 upgrades | Depends on your engineering discipline | Varies; may lag on new ERPNext versions | |
| Ownership & docs | Full source, git repo, technical docs, and training handed over | You own it but carry all the effort | Closed app, limited or no source access | |
| Support | Post-go-live window plus optional maintenance retainer | Self-supported by your team | Vendor support tiers, variable responsiveness |
This is a build-to-order app, not an instant download. Typical delivery is 2–4 weeks from confirmed scope, depending on the complexity of your field mapping, dedupe rules, and assignment logic. We start with a short scoping call, build against your real or sandbox IndiaMART payload, run UAT on a staging site, and then deploy to production.
You need an IndiaMART seller account with CRM/Lead Manager API access enabled — specifically your CRM API key (and glusr credentials where applicable) for the Push/Pull Lead API. We confirm your exact access during the scoping call and can guide you through enabling it if it isn't active yet.
We build and test against Frappe/ERPNext v15 and v16 using supported extension points — `hooks.py` doc events, scheduler events, server/client scripts, and the Frappe REST API. Because we never patch core, the app upgrades cleanly. Tell us your exact version on the scoping call and we target it.
Every build includes a post-go-live support window for bug fixes and configuration tweaks. Because you receive the full git repository, your own team can extend it, or you can engage ECOSIRE for a maintenance retainer covering IndiaMART API changes, new mapping rules, and version upgrades. Support scope and duration are agreed in the quotation.
No. Ingestion is idempotent — every record is stamped with the IndiaMART source query id so the same inquiry is never imported twice. Beyond that, de-duplication runs on a configurable key (mobile and/or email, with `+91`/leading-zero normalization) so a buyer who enquires about several products becomes one Lead with a threaded activity trail rather than scattered orphan records.
Yes. We wire auto-assignment using ERPNext Assignment Rules and `ToDo`, supporting round-robin across a sales team or territory/product-based routing that you define. An email or system notification can fire on assignment so the owner responds quickly. The exact rules are captured during scoping.
You own it. We hand over the full app source and git repository with commit history, plus technical documentation, so your team can maintain and extend it independently. There is no runtime license lock and no dependency on ECOSIRE to keep it running.
A build-to-order Frappe app that recurringly pulls your IndiaMART buyer inquiries into ERPNext as Lead records — mapping product interest, detecting duplicates, and auto-assigning to the right salesperson. ECOSIRE scopes, builds, installs, and supports it for you.