Most teams running Odoo alongside two or three sales channels end up reconciling orders by hand. A Shopify order lands, someone re-keys it into a sale.order; an Amazon shipment goes out, someone manually decrements stock; a price changes in Odoo and nobody remembers to push it to WooCommerce. Odoo core has no native multi-marketplace connector — the built-in website_sale covers the Odoo storefront only, and stitching external channels together with generic automated actions or a spreadsheet import breaks the moment SKUs, tax mappings, currencies or fulfilment states diverge. That manual layer is where oversells, delayed dispatch and mismatched inventory come from.

Connector Engine is a made-to-order Odoo module that ECOSIRE designs and builds around your specific channel mix. It introduces a channel-agnostic sync layer — a connector.backend model holding per-channel credentials and endpoints, connector.mapping records that bind an external SKU/ID to Odoo's product.product and sale.order, and a job-queue-backed engine so each import/export runs as an isolated, retryable task rather than a fragile cron burst. For each storefront we implement a dedicated adapter against that platform's own API (Shopify Admin REST/GraphQL, WooCommerce REST, Magento REST, Amazon SP-API, eBay Sell), normalising their payloads into Odoo records. Odoo's own sale.order, stock.quant, product.template and account.move stay the single source of truth; the connector only translates in and out.

Technically it is a proper Odoo app: a clean __manifest__.py declaring dependencies (sale, stock, queue_job where available), ORM models with @api.depends computes for sync status and mapping health, inbound webhook controllers plus scheduled ir.cron pulls for platforms without reliable webhooks, and full access control via ir.model.access.csv and record rules so channel credentials and logs are scoped by company and role. Order import creates or matches the customer, resolves each line to the mapped product with the right tax and UoM, and honours your fulfilment policy; inventory export pushes available quantity back per channel with configurable buffers to prevent oversell. Every operation writes to a sync-log model surfaced in list/form views (and OWL widgets where a live dashboard helps), and error states raise Odoo activities so nothing fails silently. We build against Odoo 17.0, 18.0 or 19.0 and respect Community vs Enterprise boundaries — no reliance on Enterprise-only modules unless you already run Enterprise and want us to.

Because it is build-to-order, delivery follows a defined path: a scoping call to fix your exact channels, SKU-mapping rules and edge cases, then development on an isolated branch, UAT on a staging database against sandbox/test stores, then production install with a rollback plan and a post-go-live support window. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); each additional storefront or marketplace integration, multi-company routing, marketplace-specific tax/fulfilment logic, and historical order/catalog migration volume increases the quoted scope — you get a fixed quote after the scoping call.