If you sell on eMAG in Romania, Bulgaria, or Hungary and run ERPNext, the day-to-day reality is a lot of manual copy-paste. Orders arrive in the eMAG Seller/Marketplace dashboard and get keyed into ERPNext by hand; stock counts drift between what ERPNext thinks you have and what your eMAG offers advertise; price changes made in ERPNext never reach the marketplace until someone remembers to update each offer; and reconciling eMAG's commission and settlement statements against your Sales Invoices is a spreadsheet chore. ERPNext core has no concept of eMAG — there is no marketplace order source, no offer DocType, no AWB workflow — so out of the box you are bridging two systems with human effort, and every hour of lag is an oversell risk or a late dispatch.

ECOSIRE builds a proper Frappe application (its own installable app with a dedicated module) that turns eMAG into a first-class channel inside ERPNext. The connector talks to the eMAG Marketplace API and stores credentials and per-country settings (RO/BG/HU each have their own platform host) in an eMAG Settings DocType with encrypted password fields. Incoming orders are pulled on a Frappe scheduler_events cron into an eMAG Order DocType, then mapped to native ERPNext Sales Orders — with idempotent dedupe on the eMAG order id so a retried poll never double-books. Product catalog is modeled as an eMAG Offer DocType linked to your ERPNext Item; whitelisted server methods (@frappe.whitelist()) publish new offers and push edits (price, stock, handling time, status) to eMAG, while hooks.py doc events (on_update on Item / Item Price / Bin) fire the reverse direction so a stock or price change in ERPNext propagates back to the live offer. The eMAG courier/AWB workflow generates shipping labels and writes tracking numbers onto the Delivery Note, and a settlement routine reads eMAG's commission and payment statements to reconcile against Sales Invoices and flag mismatches.

Technically it is built the way a Frappe engineer would expect: custom DocTypes with controller classes, hooks.py for doc events and scheduler jobs, background workers (frappe.enqueue) for the API-heavy sync so the UI never blocks, retry-and-log handling for eMAG rate limits, and an eMAG Sync Log DocType for full auditability of every request and response. We expose the connector through whitelisted methods and the standard Frappe REST API, add Client Scripts for the buttons your operators press (Publish Offer, Fetch Orders, Print AWB), and wire a dedicated Role Profile plus permission rules so warehouse and finance staff only see what they should. It targets Frappe/ERPNext v15 and v16 and is delivered as versioned source you own.

Because every eMAG seller's ERPNext is configured differently — your Item naming, warehouses, tax templates, fulfilment model, and which of the three countries you sell in — this is build-to-order, not a marketplace download. We start with a short scoping call to confirm exact requirements, then build against your real field mappings, validate on a staging bench with your data, run UAT, and cut over with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the complete git repository, install and configuration, documentation, a training session, and a post-go-live support window — you are never locked to us.