TradeIndia / ExportersIndia Lead Connector for ERPNext

Key Features

Server-side TradeIndia inquiry/lead-pull API client with API-key auth, pagination, and rate-limit backoff, invoked from a background job (never the browser)

ExportersIndia lead capture into the same `CRM Lead` pipeline via API pull and/or email-parse fallback, both stamped with a distinct `Lead Source`

`Marketplace Sync Settings` singleton DocTypes holding per-portal credentials, seller/user IDs, and sync window — no secrets in code

Scheduler event registered in `hooks.py` (`scheduler_events`, configurable hourly/cron) that runs the recurring sync unattended

`Marketplace Product Map` DocType that translates the portal's free-text product string into your ERPNext `Item` / `Item Group`

Configurable duplicate filtering in a `before_insert` doc-event hook keyed on email + phone + normalized product or the portal inquiry ID — merges cross-portal RFQs into one Lead with both source references

Custom fields on `CRM Lead` for buyer country, original inquiry ID, portal-searched keyword, and inquiry timestamp for filtering and reporting

Auto-routing of new leads to the right export sales owner via ERPNext Assignment Rule keyed on mapped Item Group / country

Whitelisted `@frappe.whitelist()` method + client-script 'Sync now' button and REST endpoint for on-demand manual pulls

`Marketplace Sync Log` DocType plus Error Log entries recording each run, records created/updated/skipped, and API failures for audit and troubleshooting

Idempotent, restart-safe sync using a stored high-water mark / last-synced timestamp so a re-run never double-creates leads

Role Profile and permission rules so only export sales and CRM managers can view portal credentials and marketplace leads

Optional lead-to-`Opportunity` promotion rules and mapping so qualified marketplace inquiries flow into your existing sales stages

Tested and packaged for Frappe/ERPNext v15 and v16 as an installable bench app with migrations

Built to order, done for you

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

You order

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

We build & install

ECOSIRE builds, configures and installs it on your ERPNext.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Indian exporters listing on TradeIndia and ExportersIndia live with the same daily leak: hot buyer inquiries arrive in a portal inbox or a marketing email, and someone has to hand-copy the buyer name, country, product interest, and phone number into ERPNext before a salesperson can act. By the time the inquiry is retyped — if it is retyped at all — a competitor listed on the same catalog page has already replied. ERPNext ships a solid CRM Lead and Opportunity pipeline, and the Web Form / email-to-lead paths exist, but ERPNext core has no idea these B2B marketplaces exist. There is no Lead Source for TradeIndia, no client to call the TradeIndia inquiry API, no field to hold an ExportersIndia inquiry ID, and no dedup logic that knows the same buyer often blasts the identical RFQ across both portals.

ECOSIRE builds a proper Frappe app — a real app installed in your bench with its own module, not a spreadsheet macro or a browser plugin — that closes the gap. The app adds a Marketplace Lead Source DocType and per-portal credential/setting singletons (API key, seller/user ID, sync window) so nothing sensitive lives in code. A scheduler event registered in hooks.py (scheduler_events, typically an hourly cron) invokes a server-side sync job that calls the TradeIndia inquiry/lead-pull API and ingests ExportersIndia leads, normalizes each payload, and creates or updates CRM Lead records. Every inbound inquiry is stamped with source = TradeIndia/ExportersIndia, the original inquiry ID, buyer country, and the raw product/keyword the buyer searched — so your export team can filter the Lead list view by portal and by product line on day one.

Product and category mapping is a first-class feature, not an afterthought. We build a Marketplace Product Map child-table/DocType that translates the free-text product string the marketplace sends (e.g. "SS 304 seamless pipe") into your ERPNext Item / Item Group, so leads route to the right sales owner via an Assignment Rule and feed clean data into Opportunity and later Quotation. Duplicate filtering runs on a configurable key (email + phone + normalized product, or the portal's own inquiry ID) inside a before_insert doc-event hook, so a buyer who submits the same RFQ on both TradeIndia and ExportersIndia becomes one Lead with both source references attached — not two competing records two reps chase separately. A whitelisted method also exposes a manual "Sync now" button (client script) and the Frappe REST API endpoint for on-demand pulls, and all sync activity, errors, and API rate-limit backoffs are written to the Error Log and a dedicated Marketplace Sync Log for auditability.

Because this is build-to-order, nothing is a generic download. It starts with a short scoping call where we confirm which portals and seller accounts you use, your exact product-to-Item mapping rules, dedup policy, and which role profiles should see and own marketplace leads. We then build against your Frappe/ERPNext v15 or v16 instance, validate on a staging bench with your real catalog and a sample of live inquiries during UAT, and only then install on production behind a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source in a Git repository you own, so you are never locked to us.

What you get

Installable Frappe app source (your build) delivered as a bench app installable on Frappe/ERPNext v15 or v16

Installation and configuration on your instance, including portal credentials, product mapping, dedup key, and scheduler setup

Technical documentation: DocType reference, hooks/scheduler design, API-client behavior, and mapping/dedup configuration

End-user guide plus a live training session for your export sales and CRM team

Post-go-live support window for bug fixes and adjustments after production launch

UAT on a staging bench with your real catalog and sample inquiries, plus a documented rollback plan before production install

Full Git repository handover with commit history — you own the code, no vendor lock-in

Configured Lead Source, Assignment Rules, custom fields, and Role Profiles applied to your ERPNext instance

Who this is for

Export sales manager at an Indian manufacturer

Runs a team responding to overseas RFQs from multiple B2B portals and needs every inquiry in ERPNext CRM within minutes — attributed by portal and product — instead of scattered across TradeIndia and ExportersIndia inboxes.

ERPNext-first exporter listed on multiple B2B marketplaces

Already runs sales, quotations, and inventory in ERPNext and wants TradeIndia and ExportersIndia to feed the same Lead-to-Opportunity pipeline rather than being a separate manual data-entry chore.

Operations / IT lead owning the ERPNext instance

Responsible for the bench and data quality, wants a proper installable Frappe app with scheduler-driven sync, dedup, audit logs, and clean permissions — and the source in a repo they control.

Inside-sales / lead-desk executive

Handles first response to buyer inquiries and needs deduplicated, product-mapped leads auto-assigned to the right owner so no cross-portal RFQ is answered twice or missed entirely.

How TradeIndia / ExportersIndia Lead Connector for ERPNext Compares

Criterion	ECOSIRE	Custom Build	Competitor	ERPNext Native
Marketplace inquiry capture	Scheduler-driven API pull from both portals into CRM Lead	Depends on your dev team building the API client	Rarely covers Indian B2B portals at all	No awareness of TradeIndia or ExportersIndia
Product-to-Item mapping	Configurable `Marketplace Product Map` to Item / Item Group	Buildable but must be designed from scratch	Generic field mapping, seldom to ERPNext Items	Manual retyping into each Lead
Duplicate filtering	before_insert dedup, cross-portal RFQs merged	Only if you specify and build the logic	Basic or none; usually per-source	Duplicates land as separate Leads
Recurring sync	hooks.py scheduler event, idempotent, restart-safe	You own the cron and failure handling	Sometimes polling, quality varies	None — fully manual
Version fit (v15/v16)	Built and tested for your exact version	Whatever your team targets	May lag ERPNext releases	N/A
Auditability	Marketplace Sync Log + Error Log per run	Only what you choose to log	Limited visibility	No sync to audit
Code ownership	Full Git repo handover, no lock-in	You own it fully	Licensed, often closed or subscription	N/A
Support	Post-go-live window + optional maintenance	Your team maintains it	Vendor SLA, variable	Community only

Frequently Asked Questions about TradeIndia / ExportersIndia Lead Connector for ERPNext

How long does delivery take?

This is a build-to-order app, not an instant download. After a short scoping call to confirm your portals, product mapping, and dedup rules, typical delivery is 2–4 weeks from confirmed scope. Complex mapping across many product lines or additional portals can extend that, and we will tell you the estimate before you commit.

Which Frappe/ERPNext versions are supported?

We build and test for Frappe/ERPNext v15 and v16. Tell us your exact version and hosting (Frappe Cloud, self-hosted bench, or Docker) during scoping and we build against that target, validating on a staging bench before touching production.

Do you need my TradeIndia and ExportersIndia API access?

Yes. TradeIndia inquiry pulls require your seller API key/credentials; ExportersIndia can be pulled via its API where your plan provides it, with an email-parse fallback otherwise. Credentials are stored in a settings DocType on your own instance — never hard-coded — and we will confirm exactly what access each portal plan exposes during scoping.

How does duplicate filtering actually work?

Dedup runs in a `before_insert` doc-event hook on a key you approve — typically email + phone + normalized product, or the portal's own inquiry ID. When the same buyer submits the same RFQ on both portals, we merge it into a single `CRM Lead` and attach both source references rather than creating two competing records.

What about support and updates after go-live?

Every build includes a post-go-live support window for bug fixes and adjustments. Because a portal's API can change, we also offer ongoing maintenance so the sync keeps working across ERPNext upgrades and marketplace API changes. You own the Git repository, so you or any Frappe developer can maintain it too.

Will this interfere with my existing CRM workflow?

No. It writes into standard `CRM Lead` and can promote to `Opportunity` using your existing stages, sources, and assignment rules. We add fields and a marketplace module rather than replacing core CRM, and we validate the whole flow on staging during UAT with a rollback plan before production install.

Do I own the code, or am I locked in?

You own it. We hand over the full Frappe app source in a Git repository with commit history. There is no license server and no vendor lock-in — you are free to maintain, extend, or hand it to another developer.