If you sell on Mercado Libre and run ERPNext, the two systems don't talk to each other out of the box. Orders sit in the Mercado Libre seller panel while your ERPNext Sales Orders, Stock and accounting live somewhere else, so someone is re-keying every order by hand, stock counts drift between the marketplace and your warehouse, and reconciling Mercado Pago payouts against invoices is a monthly spreadsheet exercise. ERPNext core has no native Mercado Libre integration — no OAuth handshake, no listing publish, no Mercado Envíos label flow — and generic connectors rarely handle LATAM specifics like MLA/MLB/MLM site IDs, catalog vs. classic listings, or the Mercado Pago money-release lifecycle. That is exactly the gap this connector fills.

ECOSIRE builds you a proper Frappe application (erpnext_mercadolibre) with its own module, DocTypes and role profiles, installed directly on your bench. It authenticates to the Mercado Libre API using the OAuth 2.0 server-side flow, stores tokens in a dedicated Mercado Libre Settings single DocType, and refreshes them automatically via a scheduler_events cron job so the connection never silently expires. Incoming orders are pulled through the Orders API (webhook notifications plus a scheduled polling fallback) and mapped into ERPNext Sales Orders — creating or matching the Customer, resolving each item_id/SKU to the right ERPNext Item, and writing back the marketplace order reference for traceability. A Mercado Libre Order DocType keeps the raw payload and sync status so nothing is lost if a mapping needs review.

Technically, the sync is driven by Frappe primitives you can read and audit: hooks.py doc_events fire on Item and Stock Ledger changes to push price and quantity revisions back to Mercado Libre; whitelisted methods (@frappe.whitelist()) expose publish, revise and re-sync actions that Client Scripts and custom buttons call from the ERPNext desk; and server-side logic uses the Frappe REST/frappe.client layer and background jobs (frappe.enqueue) so bulk operations don't block the UI. Inventory is two-way: ERPNext stock movements update the listing's available_quantity, and marketplace sales decrement ERPNext stock, with a configurable buffer to avoid overselling. Listings can be published and revised from ERPNext, mapping your Item fields to category attributes, pictures and shipping mode. Mercado Envíos shipments sync labels and tracking back onto the Sales Order/Delivery Note, and Mercado Pago settlements are mapped to Payment Entries so finance can reconcile net payouts, fees and released balances against the originating order.

Because this is build-to-order, we start from your actual requirements rather than shipping a one-size box. After a short scoping call we confirm your Mercado Libre site (Argentina, Brazil, Mexico, Chile, Colombia, etc.), listing types, tax and warehouse setup, and which flows you need on day one. We then build against Frappe/ERPNext v15 (and forward-compatible with v16), test on a staging bench with your data, run UAT with a rollback plan, deploy to production, and hand over the git repository plus documentation. Typical delivery is one working week from confirmed scope, and every install includes a post-go-live support window so real-world edge cases get resolved, not just the happy path.