Skip to main content

Otto Store Management

The ECOSIRE Otto Store Management module connects your OTTO Market partner account to Odoo ERP. Its Odoo 19 build pushes your catalogue to OTTO (Products v5), imports orders (Orders v4) and sends stock (Availability v1) — every call addressed to OTTO's official Partner API, with an OWL dashboard in Odoo.

Compatibility: Odoo 19 for the connector described here — Community and Enterprise; self-hosted or Odoo.sh. Odoo Online (SaaS) cannot install third-party modules. Version you download today: 17.0 → 17.0.2.0.2, 18.0 → 18.0.2.0.1, 19.0 → 19.0.3.2.0 Price: $499 USD (one-time, per Odoo version) License (19.0 build): OPL-1 (Odoo Proprietary License)

The 19.0 build installs and runs standalone — no separate companion module to install first. The 17.0 and 18.0 builds are an older engine: they do not import orders, send stock or export products to OTTO, and their manifest lists the ECOSIRE licence client (ecosire_license_client) as a dependency. For the full installation and configuration reference, see the Otto Store Management guide.

Key Features​

These describe the 19.0 build (19.0.3.2.0).

  • OAuth2 client-credentials authentication — the documented POST /v1/token exchange
  • Product catalogue export to OTTO (Products v5), sent asynchronously in batches of up to 500 variations per request. A product shows Synced once its batch is submitted; see the known issue below
  • Order import from OTTO (Orders v4) with cursor pagination, so no page is truncated or skipped — on a schedule once Auto Sync Orders is on, or from the Import Wizard
  • Stock export (Availability v1), batched at 200 SKUs
  • 7 structured error classes with HTTP 429 / Retry-After handling, so throttling waits instead of failing the run
  • OWL dashboard with Chart.js charts

Known issue in 19.0.3.2.0​

When OTTO reports an earlier export task as finished, the next product export reads that task back with its arguments in the wrong order and stops with a TypeError before it sends anything. A build with the fix has not been released yet. See the guide, and contact support if you hit it.

What the OTTO Partner API does not offer​

So that you do not go looking for settings that do not exist, these are absent from OTTO's API and therefore absent from this module:

  • Webhooks — OTTO is poll-only. The module ships a /otto/webhook route that fails closed (HTTP 403) because no inbound payload to it could be authentic; there is nothing to register on the OTTO side. Sync runs on the module's scheduled actions.
  • A customer/consumer data API — buyer and address data is embedded in the order payload, so customers are created from imported orders.
  • A dispute API — disputes are handled in the OTTO Partner Portal interface.
  • Fulfilled-by-OTTO (FBO), reviews and messaging APIs.

Prerequisites​

  • Odoo 19 (Community or Enterprise edition), self-hosted or Odoo.sh
  • An OTTO Market partner account with API access
  • API credentials from the OTTO Partner Portal (client ID and client secret)
  • Outbound HTTPS from your Odoo server to api.otto.market

Installation​

  1. Download the module ZIP from your ECOSIRE dashboard or from your Odoo App Store purchase
  2. Extract it into your Odoo addons directory so that otto_store_management/__manifest__.py resolves
  3. Restart the Odoo service
  4. Navigate to Apps, click Update Apps List, search for "Otto Store Management" and click Install

Dashboard​

The OWL dashboard provides:

  • KPIs — total sales, order count and average order value (each with its change on the previous period), customers and new customers, products, out-of-stock products and the sync success rate
  • Charts — a sales trend, orders by status and top products
  • Recent activity — the latest sync runs, read from the module's own log records

Troubleshooting​

IssueSolution
Connection failedVerify the client ID and secret; the 19.0 connection form uses OTTO's production host, so use production credentials
A product export stops with TypeErrorThe known issue in 19.0.3.2.0; contact support
A product stays on Synced after OTTO rejected itIn 19.0.3.2.0, Synced means the batch was submitted; check the product in your OTTO Partner Portal
Sync not runningCheck that the module's scheduled actions are enabled and that Odoo's cron worker is running
Orders not importingCheck that Auto Sync Orders is on for the connection, or run the Import Wizard
Duplicate contacts or products after an importOrders are not imported twice: an order whose OTTO order id is already in Odoo is skipped. A new contact or product is created only when none matches the buyer's email or name, or the order line's Internal Reference, Barcode or name

Support​