If you sell on eBay and run ERPNext, the day-to-day reality is copy-paste. Orders land in Seller Hub, someone re-keys them as Sales Orders, stock counts drift between eBay and your Warehouse until you oversell, and at month-end the payout from eBay never matches the invoice totals because final value fees, insertion fees, and international selling costs were never booked anywhere. ERPNext core has no native eBay integration — there is no eBay Settings DocType, no listing sync, no scheduler job polling the eBay Sell APIs — so every one of those steps is manual or held together with spreadsheets. That is exactly where this connector picks up.

ECOSIRE builds a proper Frappe app (its own module, installed on your bench, not a fragile external script) that binds eBay's Sell APIs to ERPNext through clean DocTypes. You get an eBay Settings single DocType holding OAuth credentials, token refresh, and per-site configuration; an eBay Account DocType so a multi-site seller (US/UK/DE/AU) runs each marketplace independently with its own currency, Company, and Warehouse mapping; and mapping DocTypes that link ERPNext Items to eBay listings by SKU. Order import runs through the Fulfillment API on a scheduler_events cron and, depending on your process, creates a Sales Order or a Sales Invoice, matches the buyer to a Customer (creating one when needed), and records eBay fees as separate charge lines so your accounts reconcile against the actual payout. Inventory and price sync run the other direction: hooks.py doc events on Stock Ledger / Bin changes push updated quantities and prices back to the live listings via the Inventory API, keeping availability honest across every eBay site you sell on.

Under the hood it is engineered the way a Frappe app should be. Listing creation and revision are generated from ERPNext Item fields, so a merchandiser publishes or updates a listing from within ERPNext instead of the eBay UI. Whitelisted server methods expose the sync actions to buttons and the Frappe REST API; client scripts add the connect/sync controls to the relevant Item, Sales Order, and account forms; server scripts and background jobs handle throttling and retry so an eBay API hiccup or rate limit never corrupts a document. Returns and cancellations flowing in from eBay are captured and mapped to the right ERPNext credit/return flow. Access is governed by a dedicated role profile and DocType permissions so warehouse staff, accounts, and admins each see only what they should, and every sync writes to an error/activity log you can actually audit.

Because this is a scoped build rather than a generic download, we tailor it to how you actually run eBay: which sites, whether orders become Sales Orders or Invoices, how fees post to your Chart of Accounts, and how variations map to your Item structure. After a short scoping call we confirm the spec, build against Frappe/ERPNext v15/v16, and deliver on a UAT-first path: we install and demo on a staging bench, you sign off on real eBay data, then we go live with a rollback plan. Typical delivery is one working week from confirmed scope. You receive the full source code for your version, a git repository handover, install and configuration, technical and user documentation, a training session, and a post-go-live support window — so the connector is genuinely yours to run and extend.