Skip to main content
IndiaMART Lead Sync for ERPNext — A build-to-order Frappe app that recurringly pulls your IndiaMART buyer inquiries into ERPN — 1/1Illustrative preview

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.

What is IndiaMART Lead Sync for ERPNext?

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 $999.00 USD; request a quote for a scoped proposal.

Key Features

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)
Configurable de-duplication on mobile and/or email with `+91`/leading-zero normalization to merge repeat enquiries into one Lead
Product-interest mapping from the IndiaMART product string to your ERPNext `Item` or an approved lookup table
Auto-assignment via ERPNext Assignment Rules and `ToDo` — round-robin or territory/product-based routing
Owner notification (email/system notification) on new-lead assignment so response time stays low
Custom fields and a mapping child table added through fixtures so they survive migrations and redeploys
Structured sync run logging (records pulled, created, updated, skipped, errored) for auditing and troubleshooting
Graceful handling of IndiaMART API rate limits, empty windows, and transient errors with retry-safe re-runs
Role and permission setup so only authorized profiles can edit sync settings or trigger manual pulls
Built and tested against Frappe/ERPNext v15 and v16 using supported `hooks.py` doc events and the Frappe REST API

Built to order, done for you

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

  1. 1

    You order

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

  2. 2

    We build & install

    ECOSIRE builds, configures and installs it on your ERPNext.

  3. 3

    Go live + support

    You go live in about one working week, with two weeks of go-live support. Defects in the code we deliver are fixed free of charge.

Technical Specifications

ERPNext Compatibility
—
License
Licence confirmation required
Python Requirement
Python 3.10+
Database
MariaDB 10.6+

About this Product

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.

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 one working week from confirmed scope, and you own the code.

What you get

  • Installable Frappe app source code for your ERPNext version (v15 or v16), scoped to your field mapping and rules
  • Deployment and configuration on your bench, including scheduler activation and IndiaMART API key setup
  • Technical documentation: architecture, DocTypes, hooks, scheduler cadence, dedupe/assignment logic, and config reference
  • End-user guide plus a live training session for your sales and admin team
  • UAT on a staging site against real or sandbox IndiaMART payloads, with a documented rollback plan
  • Git repository handover with full commit history so you own and can extend the code
  • Post-go-live support window for bug fixes and configuration adjustments after launch

Who this is for

IndiaMART-active manufacturer or trader

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.

Sales manager running an ERPNext pipeline

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.

ERPNext / bench administrator

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.

Business owner / founder

Pays for IndiaMART lead subscriptions and wants provable ROI: every purchased inquiry captured, assigned, and followed up inside the CRM they already run.

How IndiaMART Lead Sync for ERPNext Compares

CriterionECOSIRECustom BuildCompetitorERPNext Native
IndiaMART connectivityPurpose-built pull against the IndiaMART CRM/Lead API, scoped to your accountYou research and wire the API yourselfGeneric connector, may not fit your fields or planNone — no IndiaMART integration in ERPNext core
Recurring syncScheduler hook at your cadence plus on-demand Sync NowYou build and schedule the job yourselfFixed cadence, limited controlManual copy-paste from the IndiaMART panel
De-duplicationSource query-id idempotency plus configurable mobile/email dedupeMust design and test dedupe logic yourselfBasic or absent; often creates duplicatesNo inquiry-aware dedupe
Product-interest mappingEnquired product mapped to your ERPNext `Item` or approved tableYou define the mapping modelStored as raw text, rarely mapped to ItemsNot applicable
Auto-assignmentAssignment Rules with round-robin or territory/product routingYou configure assignment yourselfOwner set to one static userManual assignment per Lead
Upgrade safetySupported hooks/REST API, no core patches — clean v15/v16 upgradesDepends on your engineering disciplineVaries; may lag on new ERPNext versionsN/A
Ownership & docsFull source, git repo, technical docs, and training handed overYou own it but carry all the effortClosed app, limited or no source accessN/A
SupportPost-go-live window plus optional maintenance retainerSelf-supported by your teamVendor support tiers, variable responsivenessCommunity/self-support

Frequently Asked Questions about IndiaMART Lead Sync

How long does delivery take?

This is a build-to-order app, not an instant download. Typical delivery is one working week 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.

What do I need from IndiaMART for this to work?

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.

Which ERPNext and Frappe versions are supported?

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.

How does support and updates work after go-live?

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.

Will it create duplicate leads if the same buyer inquires multiple times?

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.

Can leads be auto-assigned to the right salesperson?

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.

Do I own the code, or is it a locked black box?

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.

Request a quote

IndiaMART Lead Sync

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.

  • 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

Request a Quotation

Tell us about your IndiaMART Lead Sync requirements and we'll send pricing, licensing options and a tailored proposal — usually within one business day.

No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.