产品详细信息以英文显示。翻译即将推出。
速览
- 价格
- $249.00 USD
- ERPNext 版本
- —
- 设置时间
- 30分钟
- 许可证
- 一次永久
- 语言
- 11 语言
一次性购买
ERPNext OnBuy Connector
A build-to-order Frappe app that connects your OnBuy marketplace store to ERPNext — syncing orders, listings, inventory, prices, tracking and settlements. ECOSIRE scopes, builds, installs and supports it; it is not an off-the-shelf download.
$249.00USD
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
核心功能
Dedicated Frappe module with `OnBuy Settings` (single DocType) for API keys, channel defaults, tax templates and buffer rules — secrets stored in encrypted password fields
OnBuy order polling on `scheduler_events` (configurable cron) with dedupe against already-imported orders, creating ERPNext `Sales Order` documents with GBP currency and correct tax template
`OnBuy Order` mapping DocType linking each marketplace order to its ERPNext Sales Order, Delivery Note and invoice for full traceability
Listing publish and edit from ERPNext: `OnBuy Listing` DocType ties each OnBuy OPC/SKU to an `Item`, pushing title, price, condition and stock
Two-way inventory sync driven by `hooks.py` doc events on `Stock Ledger Entry`/`Bin`, with ring-fence buffers to prevent oversells across channels
Two-way price sync from ERPNext `Item Price` to OnBuy, with per-price-list mapping and optional min/max guard rails
Shipping and tracking writeback: a `Delivery Note` on_submit doc event posts carrier and tracking number to the OnBuy order and marks it dispatched
Settlement reconciliation: import OnBuy payout/settlement data and map commission, fees and payouts to the correct ERPNext accounts against source orders
Whitelisted server-side methods (`frappe.whitelist()`) exposing manual sync, retry and status endpoints via the Frappe REST API
`OnBuy Sync Log` DocType recording every API call, payload summary, outcome and error for auditing and support
Client scripts adding 'Sync now' buttons and live sync-status indicators on Item, Sales Order and Listing forms
Purpose-built role profile and permission rules so warehouse, finance and admin users each get least-privilege access
Idempotent, retry-safe sync with exponential backoff and per-record error isolation so one bad order never blocks the batch
Built and tested against Frappe/ERPNext v15 and v16, installed on your own bench with no third-party middleware
关于此产品
If you sell on OnBuy and run ERPNext, the two systems don't talk. New OnBuy orders get keyed into ERPNext by hand (or copied from a CSV export), stock counts drift between the marketplace and your Bin balances, and tracking numbers are pasted into two places. When a boxing week rush lands you get oversells, cancelled orders, and OnBuy performance-metric penalties — and ERPNext core has no OnBuy integration to fall back on, because OnBuy simply isn't a supported channel out of the box. This is the gap ECOSIRE closes.
为什么选择 ERPNext OnBuy Connector
Dedicated Frappe module with `OnBuy Settings` (single DocType) for API keys, channel defaults, tax templates and buffer rules — secrets stored in encrypted password fields
OnBuy order polling on `scheduler_events` (configurable cron) with dedupe against already-imported orders, creating ERPNext `Sales Order` documents with GBP currency and correct tax template
`OnBuy Order` mapping DocType linking each marketplace order to its ERPNext Sales Order, Delivery Note and invoice for full traceability
Listing publish and edit from ERPNext: `OnBuy Listing` DocType ties each OnBuy OPC/SKU to an `Item`, pushing title, price, condition and stock
Two-way inventory sync driven by `hooks.py` doc events on `Stock Ledger Entry`/`Bin`, with ring-fence buffers to prevent oversells across channels
Two-way price sync from ERPNext `Item Price` to OnBuy, with per-price-list mapping and optional min/max guard rails
We build a proper Frappe app — installed on your own ERPNext v15 or v16 bench — not a spreadsheet macro or a brittle Zapier chain. The app ships its own module with dedicated DocTypes: an OnBuy Settings single DocType holding your API credentials and channel defaults, an OnBuy Order / channel-order mapping so every marketplace order links back to the ERPNext Sales Order and Delivery Note it created, an OnBuy Listing DocType tying each OnBuy SKU/OPC to an ERPNext Item, and a OnBuy Sync Log for full auditability. Credentials and secrets are stored using Frappe's encrypted password fields, and access is governed by a purpose-built role profile so warehouse staff, finance, and admins each see only what they should.
Order ingestion runs on Frappe scheduler_events (configurable cron, typically every few minutes) via whitelisted server-side methods that call the OnBuy API, deduplicate against already-imported orders, and create Sales Order documents with the correct customer, currency (GBP), tax template and item lines. Inventory and price sync is two-way: hooks.py doc events on Stock Ledger Entry / Bin and on Item Price push updated available quantity and prices back to OnBuy, while inbound changes are reconciled on schedule — with buffer/ring-fence rules so you never publish more stock than you can safely fulfil. When you ship, a doc event on Delivery Note submission writes the carrier and tracking number back to the OnBuy order. Settlement files and payout data are imported and reconciled against ERPNext, mapping OnBuy commission, fees and payouts to the right accounts so finance can tie every payout to its orders. Optional client scripts add "Sync now" buttons and status indicators directly on the relevant ERPNext forms, and everything is exposed through the Frappe REST API for your other tooling.
Because this is build-to-order, we start from your actual OnBuy account, catalogue structure and ERPNext configuration rather than a one-size-fits-all binary. After a short scoping call we confirm exact field mappings, tax handling, warehouse/stock rules and edge cases, then build, test on a staging bench, run UAT with you, and deploy to production. Typical delivery is 2–4 weeks from confirmed scope. You receive the full source in a git repository you own, technical and user documentation, a training session, and a post-go-live support window — no lock-in, no black box.
你得到什么
- Installable source code for your commissioned version as a proper Frappe app (installable via `bench get-app` / `bench install-app`)
- Installation and configuration on your ERPNext bench, including OnBuy credential setup and field mapping
- Technical documentation: DocType schemas, hooks/doc events, scheduler jobs, whitelisted API methods and configuration reference
- User guide plus a live training session for your operations and finance teams
- UAT on a staging bench with a documented test plan and a rollback plan before production cutover
- Post-go-live support window for bug fixes and adjustments after launch
- Handover of the private git repository containing the full source, so you own and can extend the code
- Sync runbook covering monitoring the OnBuy Sync Log, retrying failed records and reconciling settlements
这是给谁的
OnBuy marketplace seller on ERPNext
A UK retailer or brand selling on OnBuy whose orders, stock and finances already live in ERPNext, and who wants OnBuy fully wired into that single source of truth instead of manual re-keying.
Operations / fulfilment manager
Owns dispatch accuracy and OnBuy performance metrics. Needs reliable order sync, automatic tracking writeback and oversell protection so late-dispatch and cancellation penalties disappear.
Finance / accounts controller
Responsible for reconciling OnBuy payouts. Needs settlement, commission and fee data mapped cleanly to ERPNext accounts so every payout ties back to the orders that generated it.
Multi-channel ecommerce lead
Runs OnBuy alongside other marketplaces and wants a maintainable, owned Frappe app on their own bench — not fragile third-party middleware — that ring-fences stock across channels.
安装概述
从ECOSIRE下载
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 ERPNext OnBuy Connector 应用程序 ZIP。
将应用程序添加到您的工作台
将 ZIP 解压到您的 bench 的 apps 文件夹中，或者使用解压缩的应用程序的路径运行“bench get-app”。
安装在您的网站上
运行 `bench --site SITE_NAME install-app APP_NAME`，然后运行 `bench migrate` 以安装 ERPNext OnBuy Connector 并应用其架构。
激活您的许可证
打开您站点上的 ECOSIRE 许可证设置并激活您的许可证密钥。需要免费的 ecosire_connect 和 ecosire_license_client 应用程序。
ERPNext OnBuy Connector 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| OnBuy order sync | Scheduled polling creates ERPNext Sales Orders automatically with dedupe | Possible but you build and maintain the poller yourself | Rare — few Frappe apps cover OnBuy specifically | |
| Inventory & price sync | Two-way via doc events with ring-fence buffers to prevent oversell | Depends entirely on your developer's design and testing | Often one-way or generic, not tuned to OnBuy | |
| Tracking writeback | Delivery Note submission posts carrier + tracking to OnBuy | Must be built and wired to Delivery Note events | Sometimes; varies by app | |
| Settlement reconciliation | Payouts, commission and fees mapped to ERPNext accounts | Bespoke work, often deprioritised | Usually out of scope | |
| Fit to your setup | Built from your catalogue, tax and warehouse rules | Fully bespoke but slower and higher risk | One-size-fits-all binary | |
| Code ownership | Full source handed over in a git repo you own | You own it, but bear full build cost and risk | Licensed; source usually closed | |
| Delivery time | 2–4 weeks from confirmed scope | Often months depending on dev capacity | Instant install but generic fit | |
| Support & updates | Post-go-live support window; v15/v16 tested | Self-supported unless you retain the developer | Vendor SLA, variable responsiveness |
关于ERPNext OnBuy Connector的常见问题
How long does delivery take?
This is a build-to-order product, so it isn't an instant download. After a short scoping call to confirm your OnBuy account, catalogue and ERPNext configuration, typical delivery is 2–4 weeks from confirmed scope — including a build phase, staging tests, UAT with you and production deployment.
How is this different from a Frappe Cloud Marketplace app I could just install?
It's built specifically for your setup. We start from your real OnBuy account structure, tax handling, warehouses and ERPNext configuration, then build, test and hand over the source in a git repo you own. There's no generic binary you self-install and hope fits.
Which versions of ERPNext do you support?
We build and test against Frappe/ERPNext v15 and v16 and install directly on your own bench via `bench get-app` / `bench install-app`. Tell us your current version at scoping and we target it; if you're on an older release we'll flag any upgrade needed.
How does inventory sync avoid overselling?
Stock sync is two-way and driven by `hooks.py` doc events on ERPNext stock movements plus scheduled reconciliation. You can set ring-fence buffers per item or warehouse so the quantity published to OnBuy is always your safe-to-sell figure, not raw on-hand — which keeps OnBuy performance metrics clean.
How do you handle support and updates after go-live?
Every build includes a post-go-live support window for bug fixes and adjustments. Because you own the git repository, you can extend it yourself or engage us for further work, including changes needed when OnBuy's API or a new ERPNext version ships. Ongoing support and maintenance can be arranged separately.
Where are our OnBuy API credentials stored?
In an `OnBuy Settings` single DocType using Frappe's encrypted password fields, with access restricted by a dedicated role profile. Nothing runs through third-party middleware — the app lives entirely on your own ERPNext bench and talks directly to the OnBuy API.
Can settlement and payout data be reconciled in ERPNext?
Yes. We import OnBuy settlement/payout data and map commission, fees and net payouts to the correct ERPNext accounts against the originating orders, so finance can reconcile each payout back to its source Sales Orders instead of eyeballing marketplace reports.
相关模块
申请报价
ERPNext OnBuy Connector
A build-to-order Frappe app that connects your OnBuy marketplace store to ERPNext — syncing orders, listings, inventory, prices, tracking and settlements. ECOSIRE scopes, builds, installs and supports it; it is not an off-the-shelf download.
- Dedicated Frappe module with `OnBuy Settings` (single DocType) for API keys, channel defaults, tax templates and buffer rules — secrets stored in encrypted password fields
- OnBuy order polling on `scheduler_events` (configurable cron) with dedupe against already-imported orders, creating ERPNext `Sales Order` documents with GBP currency and correct tax template
- `OnBuy Order` mapping DocType linking each marketplace order to its ERPNext Sales Order, Delivery Note and invoice for full traceability
- Listing publish and edit from ERPNext: `OnBuy Listing` DocType ties each OnBuy OPC/SKU to an `Item`, pushing title, price, condition and stock