A build-to-order Odoo integration that connects your handmade-marketplace shop to Odoo — syncing listings, importing paid orders, and pushing live stock levels. ECOSIRE scopes, builds, installs, and supports it; it is not an off-the-shelf download. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $299.00 USD; request a quote for a scoped proposal.

A build-to-order Odoo integration that connects your handmade-marketplace shop to Odoo — syncing listings, importing paid orders, and pushing live stock levels. ECOSIRE scopes, builds, installs, and supports it; it is not an off-the-shelf download.
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
If you sell on the handmade/vintage marketplace, your day likely fragments across two systems that never agree: orders and shipping labels live in the marketplace seller dashboard, while your real inventory, purchasing, accounting, and fulfilment live in Odoo. You re-key orders by hand, you oversell an item that was already picked in the warehouse, and your marketplace listings drift out of sync with the quantities in stock.quant. Odoo core has no native connector to this marketplace — the standard eCommerce app targets the Odoo Website shop, not third-party marketplaces — so out of the box there is no supported bridge for its OAuth 2.0 REST API, its listing/variant model, or its receipt/transaction feed. That is exactly the road-end this product is built for.
Dedicated Odoo module with its own `__manifest__.py`, depending on `sale`, `stock`, and `product`, supported on Odoo 17.0/18.0/19.0 (Community and Enterprise)
OAuth 2.0 connection to the marketplace REST API with encrypted token storage and automatic token refresh handling
New `models.Model` records for the marketplace account/config, listing mappings, and a per-run import log with status and error detail
Stored `marketplace_listing_id` / remote-SKU link on `product.template` and `product.product` tying each Odoo variant to its remote listing
`@api.depends` computed fields on the product form surfacing sync state, last-synced timestamp, and remote quantity
Order import that creates real `sale.order` / `sale.order.line` records, marketplace fee lines, and the buyer as a `res.partner`
ECOSIRE builds a dedicated Odoo module — its own technical package with a proper __manifest__.py, dependency chain on sale, stock, and product, and versioned support for Odoo 17.0, 18.0, and 19.0 — that talks directly to the marketplace REST API using your shop's OAuth credentials. New models (models.Model subclasses such as an account/config record, a listing-mapping record, and an order-import log) hold the connection, the field mappings, and the sync history. A stored marketplace_listing_id on product.template/product.product links each Odoo variant to its remote listing and remote SKU, with @api.depends computed fields surfacing sync status and last-synced timestamps directly on the product form. Order import creates real sale.order records (with sale.order.line, the marketplace fee lines, and the customer as a res.partner) so the order flows through your normal delivery, invoicing, and stock-move pipeline.
Technically, the connector runs on Odoo's own scheduler: ir.cron jobs poll the marketplace for newly-paid receipts on your chosen cadence and push inventory deltas back when stock.quant changes, with API calls wrapped in rate-limit-aware retry and every request/response logged for audit. We build the security layer properly — ir.model.access.csv for each new model plus record rules so multi-company or restricted users only see their own shop's data — and expose configuration through clean backend views (XML, with OWL components where an interactive mapping screen helps). Field mapping between marketplace listing attributes and Odoo variant attributes is configurable rather than hard-coded, idempotent imports use the remote receipt id as the dedupe key so a re-poll never double-creates an order, and a QWeb reconciliation report lets you see marketplace payouts against imported orders. Because it is a real module and not a script, it is also reachable over Odoo's XML-RPC/JSON-RPC API if you want to trigger a sync from outside. It works on both Community and Enterprise (Enterprise-only features like Studio are never a hard dependency).
Delivery is build-to-order: after a short scoping call we confirm exactly which flows you need (listing sync direction, order import rules, tax/fee handling, single vs multi-company), then design, build, and test on a staging database with your real data patterns before go-live. Typical delivery is 2–4 weeks from confirmed scope. You receive the installable source for your Odoo version, so you are never locked to us. Pricing starts from $299 (indicative, single-company base scope); multi-company rollout, additional marketplace shops or extra integrations, deeper tax/fee localization, and larger historical-order migration volume increase the quoted scope. You get a firm fixed quote after the scoping call — never a surprise on the invoice.
Runs a growing marketplace storefront and has moved core operations into Odoo. Needs paid orders to land in Odoo automatically and stock to stay in sync so they stop overselling and stop re-keying orders by hand.
Owns picking, packing, and shipping in `stock`. Wants marketplace orders to flow into the normal delivery and invoicing pipeline, with a clear import log and reconciliation report to catch anything that failed to sync.
Implementing Odoo for a client who sells on the marketplace and needs a supported, source-available connector rather than a brittle in-house script — with clean security rules and Community/Enterprise compatibility.
Needs marketplace fees and payouts represented on Odoo orders and a QWeb report to reconcile marketplace transactions against imported sales, so month-end matches the marketplace statements.
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Etsy Connector モジュールの ZIP をダウンロードします。
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Etsy Connector」を検索し、「インストール」を押します。
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| How you get it | Built to order, installed and supported by ECOSIRE | You hire/build in-house from scratch | Instant download, install it yourself | |
| Fit to your workflow | Scoped to your listing/order/fee rules | Fully bespoke if you have the time | Generic; you adapt to its assumptions | |
| Order import to Odoo | Real sale.order, idempotent by receipt id | Only what you build and test | Usually yes, mapping often rigid | |
| Inventory sync | stock.quant-driven push with retry | Depends on your build effort | Often one-way or scheduled-only | |
| Security & multi-company | ir.model.access + record rules per shop | Your responsibility to design | Varies; often single-company | |
| Odoo version coverage | Built for your 17.0 / 18.0 / 19.0 | Whatever you target and maintain | Per listing; upgrades lag | |
| Source & ownership | Full source + git repo handover | You own it | Usually source-available, vendor-locked | |
| Support after go-live | Support window + optional ongoing plan | You maintain it yourself | Vendor ticket queue, variable SLA |
No. This is a build-to-order module. ECOSIRE designs, builds, installs, and supports it for your specific shop and Odoo version. There is no instant download — we start from a scoping call, confirm the flows you need, and build against your real data patterns.
Typical delivery is 2–4 weeks from confirmed scope. After the scoping call we agree exactly which flows are in scope (listing sync, order import, inventory push, tax/fee handling, company count); the timeline depends on that scope, and we build and UAT on staging before go-live.
Pricing starts from $299 as an indicative single-company base scope. It is not a fixed price — drivers like multi-company rollout, extra marketplace shops or integrations, deeper tax/fee localization, and historical-order migration volume change the quote. You get a firm fixed quote after the scoping call, before any build work begins.
We build for Odoo 17.0, 18.0, or 19.0, on either Community or Enterprise. Enterprise-only tooling is never a hard dependency, so the connector runs on Community. We target one version per build; a multi-version build can be quoted if you need it.
Every build includes a post-go-live support window for bug fixes and sync adjustments after cutover. Because you receive the full source and git history, your team can also maintain and extend it. Longer-term maintenance, marketplace-API changes, and version upgrades can be quoted as an ongoing support arrangement.
Yes. Imported orders become real `sale.order` records with order lines, fee lines, and the buyer as a `res.partner`, so they flow through your standard delivery, invoicing, and stock-move pipeline. Imports are idempotent — keyed on the remote receipt id — so re-polling never double-creates an order.
An `ir.cron` job pushes available-quantity changes from `stock.quant` back to the linked marketplace listings on your chosen cadence, with rate-limit-aware retry. Each Odoo variant is mapped to its remote listing/SKU, so stock stays consistent between the two systems.
A build-to-order Odoo integration that connects your handmade-marketplace shop to Odoo — syncing listings, importing paid orders, and pushing live stock levels. ECOSIRE scopes, builds, installs, and supports it; it is not an off-the-shelf download.