Zalando Store Management
The ECOSIRE Zalando Store Management module connects a Zalando Partner Program (zDirect) merchant account to Odoo. Zalando orders arrive as real Odoo sale orders, products are submitted and stock is pushed through the operations Zalando publishes, and a dashboard shows what the connection is doing. For installation and configuration step by step, see the installation and configuration guide.
| Technical name | zalando_store_management |
| Odoo versions | 17.0, 18.0, 19.0 (Community or Enterprise) |
| Current shipped version | 17.0 → 17.0.2.3.2, 18.0 → 18.0.2.3.2, 19.0 → 19.0.2.3.2 |
| Price | $599 USD — one-time, per Odoo version |
| Licence | OPL-1 — installs and runs on its own, with nothing to switch on afterward |
| Live demo | zalando.demo.ecosire.com |
What changed in 2.3.2 (
19.0.2.3.2, 18.0.2.3.2, 17.0.2.3.2)Hardened against 36 known real-world failure cases.
Every behaviour in this release comes from a defect a customer actually hit on one of our connectors, and each one is now proven by a named test that drives the case which used to break.
- Dashboard currency. The dashboard added foreign-currency orders to company-currency orders and labelled the total with your company's symbol, so a merchant selling in EUR read a euro amount as dollars. Each currency is now converted at your configured rate before it is summed and charted, and a currency with no exchange rate configured is left out and reported instead of being counted as 1:1.
- Offer health totals. The products-synced counter counted every product checked rather than every product changed, so running the sync several times inflated it. It now counts what actually changed.
- Zalando screens open Zalando views. Orders, Products and Customers fell back to the broad Odoo screens, which list every record in the database and hide the connector's own fields. They now open dedicated Zalando lists and forms showing the external order and article identifiers, the platform status and the sync state.
- A failed dashboard load is visible. The error banner now appears above the KPI cards, carries an alert role and a Retry button, the loading state announces itself, and a recoverable load failure is logged as a warning rather than an error.
What changed in 2.3.1 (
19.0.2.3.1, 18.0.2.2.3, 17.0.2.2.3)- Dashboard and sync endpoints now respect company boundaries. In a multi-company database they work only with the Zalando connections of the companies you are working in.
- Syncs, queue actions and the operation console need the Zalando Manager group. Zalando Users keep read access; scheduled jobs are unaffected.
- Dashboard fixes: today's orders are counted, Top Products lists your best sellers, the Order Status chart shows its data, and sync-log durations are shown in seconds.
What the module does
- Orders — imports Zalando orders into Odoo sale orders with their lines, buyer contact, amounts, currency and Zalando status. An order that is only partly present, or mixes currencies, is refused rather than imported wrong.
- Products — submits products to Zalando with the model, config and simple tiers Zalando requires, and checks them before anything is sent.
- Stock — pushes on-hand stock from the warehouse you choose for the connection; rows Zalando rejects are reported, not counted as updated.
- Dashboard — revenue, orders, customers, products, average order value, sync health, a sales trend, order status and top products, in your company's currency.
- Sync logs and queues — every sync is logged with its outcome and record counts; failed queue lines can be retried by a Zalando Manager.
- Webhooks — unsigned calls are refused.
- Multi-company — each connection belongs to one company, and users only see their companies' connections.
Only on 19.0
- Shipments and announced returns through Zalando's published operations.
- Offer health and stock reconciliation against Zalando.
- Run Zalando Operation — a console that reaches every operation Zalando publishes, and refuses any operation or parameter Zalando does not declare.
- Compliance records — EPR registration numbers, OSS and per-country VAT IDs, and the GDPR retention window applied to buyer contact data.
On 18.0 and 17.0 the shipment, returns and settlement requests are not available: asking for them stops before anything is sent to Zalando, so nothing is reported as done that did not happen.
Requirements
- Odoo 17.0, 18.0 or 19.0, Community or Enterprise, self-hosted or Odoo.sh (Odoo Online cannot install third-party modules)
- A Zalando merchant account with zDirect API access (Zalando approves merchants before granting API access)
- The Client ID and Client Secret of your zDirect API client, and your merchant ID