Skip to Content

E-Commerce Connector Engine (Miko)

by
Odoo
v 19.0 Third Party 9
Download for v 19.0 Deploy on Odoo.sh
Versions 16.0 17.0 18.0 19.0
You bought this module and need support? Click here!
Versions 16.0 17.0 18.0 19.0

The engine every Miko store connector runs on

Free and open (LGPL‑3). The two things every e‑commerce connector needs and nobody should write twice: remembering which Odoo record is which store record, so a sync can be re‑run safely, and keeping failures in a queue that can actually be retried.

Odoo 16.0Odoo 17.0Odoo 18.0Odoo 19.0LGPL-3
This module does nothing on its own, and that is deliberate. It is the engine, not the car. Install a platform connector and this comes with it automatically. On its own you get an empty Store Sync menu that tells you exactly that, and which connector to add.

What it provides

Identity mapping

One row per record that crosses the boundary, with a unique index behind it. Turns an import into an upsert, so a re-run is a no-op instead of a second set of orders, deliveries and invoices.

A queue that is actually drained

Jobs dispatch back to the connector, so Retry re-runs the code that failed against the payload that failed. Transient failures retry on a backoff; ones needing a person wait and say why.

The connected store record

Company, warehouse, pricelist, journal and fallback customer, plus the safety switches. Everything that writes starts switched off.

Field mapping

Which store field lands in which Odoo field, validated the moment it is typed. Identity fields are deliberately not mappable.

Tax mapping

Every tax a store sends is listed the first time it appears, for your accountant to match to a real Odoo tax.

One implementation, every platform

Shopify and WooCommerce already share this. Each new connector is an API client and a field mapping, not another copy of the hard part.

How it works

  • 1
    Install a platform connector
    Odoo pulls this in automatically as a dependency.
  • 2
    Add your store
    The connector adds its own tab with credentials and settings.
  • 3
    Import and review
    Nothing is confirmed, invoiced or written back until you say so.
  • 4
    Watch the job queue
    Sync Jobs shows what worked, what is retrying, and what needs you.

Detailed capabilities

When something fails
  • Failed is transient — a dropped connection, a rate limit, a 502. Retried automatically with exponential backoff.
  • Needs attention means something has to change first: a tax with no mapping, a product not in Odoo, a revoked key. Never retried on a timer, because a timer cannot fix it, and each one carries the sentence saying what to do.
  • Every job keeps the exact payload that caused it, so a retry replays the failure without asking the store for the data again.
  • A Retry button on every job, and a dashboard filtered to what still needs a person.

Requirements

  • Odoo 16, 17, 18 or 19, Community or Enterprise.
  • Depends on Sales and Inventory, both standard.
  • Odoo Online cannot run third-party modules containing Python, so this needs Odoo.sh or a self‑hosted install.

Support

Email support for every version listed above, from the people who wrote it. Every release is certified against real Odoo images before it ships, and the test count is stated on this page rather than implied.

21 automated tests, run against Odoo 16.0, 17.0, 18.0, 19.0 on every release. A version is only listed once it passes.

Questions

Why is this a separate module?
  • So every connector shares one implementation of duplicate prevention and retry, tested once, instead of each carrying a divergent copy. It is free precisely because it is a dependency rather than a product.
Which Odoo versions are supported?
  • Every listed version is certified on each release by installing the module into a real Odoo image of that series and running the full test suite. A version is only listed once it passes.
Does this work on Odoo Online?
  • No. Odoo Online cannot run third-party modules containing Python, which is Odoo's rule rather than ours. Odoo.sh and self-hosted installs are fine.
What does support cover?
  • Installation problems, defects, and questions about how the module behaves, by email, for the versions listed on this page. Custom development and changes to Odoo core behaviour are separate work.
How do I report a problem?
  • Email support@tripsterdevelopers.com with your Odoo version, the module version, and what you did. If a job failed, the job record holds the exact payload and the error, which answers most questions immediately.

Explore our other Odoo apps

Shopify Odoo Connector
USD 449
Orders, products, customers, stock, fulfilment
miko_shopify
WooCommerce Odoo Connector
USD 399
Orders, products, customers, stock, status
miko_woocommerce
Barcode Validator & Catalog Audit
Free
Barcodes that will never scan
miko_catalog_health
Email Validation & Duplicate Contacts
USD 19
Contacts that can never be emailed
miko_contact_health
Margin Control & Sold Below Cost
USD 49
Products sold at a loss, blocked before the order
miko_margin_health
Vendor Price Check & Supplier Audit
USD 29
Products you cannot actually reorder
miko_supplier_health
MCP Server for AI
Free
Claude, ChatGPT or Copilot reading Odoo safely
miko_mcp_server

Search the Apps store for the technical name, or open Tripster Developers at the top of this page to see everything we publish.

Questions before you buy?

Email support@tripsterdevelopers.com and a developer who wrote this will answer, usually the same working day (New Zealand time).

Built by Tripster Developers.

Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Inventory (stock)
• Sales (sale_management)
• Discuss (mail)
• Invoicing (account)
Lines of code 743
Technical Name miko_ecommerce_core
LicenseLGPL-3
Websitehttps://tripsterdevelopers.com/odoo/

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.