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.

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.