A build-to-order Frappe app that syncs eBay orders, listings, and inventory with your ERPNext instance across US/UK/DE/AU sites, with automatic fee reconciliation. ECOSIRE builds, installs, and supports it on your bench. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $499.00 USD; request a quote for a scoped proposal.

A build-to-order Frappe app that syncs eBay orders, listings, and inventory with your ERPNext instance across US/UK/DE/AU sites, with automatic fee reconciliation. ECOSIRE builds, installs, and supports it on your bench.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
`eBay Settings` single DocType storing OAuth 2.0 credentials, refresh-token rotation, and per-environment (sandbox/production) toggles
`eBay Account` DocType for multi-site selling (US/UK/DE/AU), each mapped to its own Company, currency, price list, and default Warehouse
Scheduled order import via the eBay Fulfillment API on a configurable `scheduler_events` cron, with idempotent dedupe by eBay order ID
Configurable order flow: incoming eBay orders create a Sales Order or Sales Invoice, with Customer auto-match/creation from buyer details
Built-in fee reconciliation — final value, insertion, and international selling fees posted as itemized charges so ERPNext totals match the eBay payout
Listing creation and revision generated from ERPNext Item fields via the eBay Inventory/Trading APIs, published without leaving ERPNext
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 2 to 4 weeks 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.
Runs high listing volume across one or more eBay sites and needs orders, stock, and prices to stay in sync automatically instead of re-keying from Seller Hub — without overselling when a SKU sells on two channels at once.
Owns fulfillment across eBay plus other channels and wants every eBay order to land in ERPNext as a Sales Order or Invoice with correct Customer, Warehouse, and returns handling, all governed by role-based permissions.
Needs the eBay payout to reconcile against ERPNext. Cares that final value, insertion, and international selling fees post as itemized charges to the right accounts so month-end matches the marketplace statement.
Wants a clean, upgradeable Frappe app — proper DocTypes, hooks.py events, scheduler jobs, whitelisted methods — with source code and a git handover, not an opaque script that breaks on the next v15/v16 update.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 ERPNext eBay Marketplace Connector 应用程序 ZIP。
将 ZIP 解压到您的 bench 的 apps 文件夹中,或者使用解压缩的应用程序的路径运行“bench get-app”。
运行 `bench --site SITE_NAME install-app APP_NAME`,然后运行 `bench migrate` 以安装 ERPNext eBay Marketplace Connector 并应用其架构。
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| eBay order sync | Scheduled Fulfillment API import to Sales Order/Invoice, deduped by order ID | Possible, but you design and maintain the polling and mapping yourself | Usually order import, but often on the vendor's fixed flow | |
| Fee reconciliation | Final value/insertion/international fees posted as itemized charges to your accounts | Only if you scope and build it | Often partial or fees lumped into one line | |
| Multi-site support (US/UK/DE/AU) | Per-site eBay Account with own Company, currency, Warehouse | Buildable, adds significant effort | Varies; extra sites often cost more | |
| Inventory & price push | Real-time via hooks.py on Stock Ledger/Bin, prevents overselling | You build the event hooks and throttling | Common, but sync cadence may be fixed/batched | |
| Fit to your process | Scoped to your Item structure, order flow, and Chart of Accounts | Fully bespoke — and fully your maintenance burden | Configure within the vendor's assumptions | |
| Source code & ownership | Full source + git repository handover, yours to extend | You own it, and you own every future fix | Often closed-source or license-locked | |
| v15/v16 compatibility | Built and verified against your target Frappe/ERPNext version | Depends on your team's testing | Depends on vendor's release cadence | |
| Support after go-live | Post-go-live support window + optional ongoing engagements | Whatever your internal team can cover | Subscription support, tied to their roadmap |
This is build-to-order, not an instant download. Typical delivery is 2 to 4 weeks from confirmed scope. After a short scoping call we lock the spec (eBay sites, order flow, fee posting, Item/variation mapping), build against your Frappe/ERPNext version, and deliver via a staging UAT before go-live. Complex variation structures or many eBay sites push toward the upper end of that range.
No. ECOSIRE builds this connector to order and installs it on your bench. There is no instant-download version — you receive source code tailored to your process, installed and configured on your ERPNext instance, with a git repository handover so the app is genuinely yours.
The connector supports multi-site selling out of the box — US, UK, DE, and AU are the standard set, each mapped to its own Company, currency, and Warehouse — and we can add other eBay marketplaces during scoping. It is built and verified against Frappe/ERPNext v15 and v16; tell us your target version on the scoping call.
eBay charges (final value fees, insertion fees, international selling fees, and similar) are pulled with each order and posted as itemized charge lines against accounts you choose in your Chart of Accounts. That means the total booked in ERPNext matches the net payout eBay actually deposits, so your accounts team reconciles the marketplace statement instead of guessing at the difference.
Every build includes a post-go-live support window covering bug fixes and configuration adjustments. Because you receive the full source and git repo, your own team can extend it, and we offer ongoing support or upgrade engagements (for example, adapting to a future eBay API change or an ERPNext major-version upgrade) beyond the initial window.
No — inventory sync is driven by hooks.py doc events on Stock Ledger / Bin changes, so when stock moves in ERPNext for any reason, the available quantity is pushed to the matching eBay listings in near real time. ERPNext stays the source of truth for availability across every eBay site you map.
Yes. You receive installable source code for your version plus a git repository handover with full history. There is no per-seat lock-in or obfuscation — your team (or any Frappe developer) can read, deploy, and extend the app.
A build-to-order Frappe app that syncs eBay orders, listings, and inventory with your ERPNext instance across US/UK/DE/AU sites, with automatic fee reconciliation. ECOSIRE builds, installs, and supports it on your bench.