Connector Engine

Name: Connector Engine
Brand: ECOSIRE
SKU: connector-engine

Key Features

Channel-agnostic `connector.backend` model storing per-store credentials, endpoints and sync toggles, so new channels are added as configuration rather than forked code

Per-platform adapters built against each vendor's own API — Shopify Admin REST/GraphQL, WooCommerce REST, Magento REST, Amazon SP-API and eBay Sell — normalised into standard Odoo records

`connector.mapping` records binding external SKUs and order IDs to `product.product` and `sale.order`, with idempotency guards so a re-delivered webhook never duplicates an order

Job-queue-backed sync (via `queue_job` where available) so each import/export is an isolated, retryable task with backoff instead of a monolithic cron that fails as a block

Inbound webhook controllers plus scheduled `ir.cron` pulls, chosen per platform, to cover both event-driven and poll-only channels

Order import that matches or creates the `res.partner`, resolves lines to mapped products with correct tax, UoM and currency, and applies your fulfilment/shipping mapping

Inventory export pushing `stock.quant` availability back to each channel with per-channel safety-buffer stock to prevent oversell across marketplaces

Bidirectional product/catalog sync for price, name, description and stock, with field-level control over which direction is authoritative per attribute

Fulfilment and tracking write-back — Odoo delivery validation pushes shipment status and tracking numbers back to the originating channel

Sync-log model with `@api.depends` status computes, surfaced in list/form (and OWL dashboard views where useful) for full auditability of every message

Automatic Odoo activities/exceptions raised on mapping or API failures so errors are actionable, never silent

Access control via `ir.model.access.csv` and record rules scoping credentials, logs and mappings by company and user role

Multi-company and multi-warehouse aware routing so orders and stock land in the correct company/warehouse per channel

Configurable rate-limit handling and pagination per adapter to stay within each marketplace's API quotas on large catalogs

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

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.

What you get

Installable, version-pinned Odoo module source code targeting your Odoo edition (17.0 / 18.0 / 19.0)

Production install and configuration of every agreed channel, including credential/webhook setup and SKU-mapping rules

Technical documentation: model/field reference, adapter architecture, cron/webhook design and sync-log schema

End-user guide plus a live training session for your operations and finance teams

Post-go-live support window for bug fixes and sync-monitoring assistance

UAT on a staging database against sandbox/test stores, with a documented rollback plan

Git repository handover with full commit history and branch/tag structure

Configuration workbook capturing per-channel settings, mappings and buffer rules for future maintenance

Who this is for

Multichannel retail operations lead

Runs Odoo as the back office while selling across a Shopify store plus Amazon and eBay. Needs orders to flow in automatically and stock to stay in sync across all channels so the team stops re-keying and stops overselling bestsellers.

Odoo-standardised finance controller

Wants every external sale to become a proper `sale.order` and `account.move` in Odoo with correct tax and currency, so revenue and inventory valuation reconcile without a monthly spreadsheet chase across marketplace exports.

In-house Odoo administrator / integrator

Owns the Odoo instance and will maintain the connector after handover. Needs clean ORM models, scoped access rules, a readable sync log and a git repo — not an opaque black-box that can't be debugged or extended.

Growing D2C brand scaling to new marketplaces

Adding a WooCommerce or Magento site or a new marketplace and needs a channel-agnostic layer where the next integration is a scoped add-on, not a rebuild of the whole sync.

How Connector Engine Compares

Criterion	ECOSIRE	Custom Build	Competitor
Channel coverage	Exactly your channels, each a scoped adapter	Whatever your devs finish before budget runs out	Fixed channel list, take it or leave it
Fit to your SKU/tax rules	Mapped to your edge cases in scoping	Possible but you fund the discovery	Generic mappings you bend to fit
Oversell protection	Per-channel stock buffers + idempotent orders	Only if your team builds it	Basic, rarely per-channel tuned
Error handling	Retryable jobs + Odoo activities on failure	Depends on developer discipline	Opaque logs, limited retries
Maintainability	Clean ORM, scoped rules, git handover	Varies; often undocumented	Black box, no source access
Odoo version support	Built for your 17.0 / 18.0 / 19.0 edition	Whatever you target and test	Lags new Odoo releases
Cost model	Fixed quote from $249 after scoping	Open-ended hourly, scope creep risk	Low licence + your integration time
Support	Post-go-live window + optional retainer	You are the support	Ticket queue, generic

Frequently Asked Questions about Connector Engine

Is this an existing app I can download and install today?

No. Connector Engine is build-to-order. ECOSIRE scopes it to your exact channel mix, builds it on an isolated branch, tests it on staging against your sandbox stores, then installs it on production. There is no instant apps.odoo.com download — you receive a module built and supported for your setup.

How long does delivery take?

Typical delivery is 2–4 weeks from confirmed scope. The clock starts once the scoping call has fixed your channels, SKU-mapping rules and edge cases. Larger channel counts, multi-company routing and historical data migration extend the timeline, which we confirm in the fixed quote.

Which platforms can it connect to?

We build dedicated adapters against each platform's own API — commonly Shopify, WooCommerce, Magento, Amazon and eBay. Each channel you need is implemented as a scoped adapter into the shared `connector.backend` layer, so your quote reflects exactly the storefronts and marketplaces you run.

How does pricing and scoping work?

Pricing starts from $249 as an indicative single-company base scope. The real number depends on how many storefronts/marketplaces you integrate, whether you need multi-company routing, channel-specific tax and fulfilment logic, and how much historical order and catalog data we migrate. After a short scoping call you get a fixed, written quote — no open-ended hourly billing.

What about support and future Odoo updates?

Every build includes a post-go-live support window for bug fixes and sync-monitoring help. Because we hand over the git repository and full technical docs, your team can maintain it, or you can retain ECOSIRE for enhancements and version upgrades. Odoo major-version upgrades (e.g. 18.0 to 19.0) are quoted as a scoped upgrade since APIs and the ORM change between releases.

Will it work on Odoo Community, or do I need Enterprise?

We build against Odoo 17.0, 18.0 and 19.0 on both Community and Enterprise. The connector does not require Enterprise-only modules; if you run Enterprise and want to leverage Enterprise features, we scope that in. We confirm your edition on the scoping call so no dependency surprises appear at install.

How do you prevent overselling and duplicate orders?

Inventory export pushes `stock.quant` availability to each channel with configurable per-channel safety buffers, so the same unit is not promised twice across marketplaces. Order import uses idempotency guards on the external order ID via `connector.mapping`, so a re-delivered webhook or re-run poll can never create a duplicate `sale.order`.