Selling on OTTO Market usually means running two systems that disagree with each other. Orders arrive in the OTTO partner portal, get copied by hand or by CSV into Odoo, and by the time the picking is validated the marketplace stock figure is already stale. Overselling on a fast-moving SKU triggers cancellations and performance penalties; underselling quietly hides inventory you already own. At month end, finance is left reconciling a single payout against dozens of order lines, commission charges, shipping fees and returns with no audit trail in account.move. Odoo core has no concept of a marketplace channel at all — sale.order has no external reference lifecycle, stock.quant has no notion of a channel-reserved buffer, and there is no scheduled job that talks to OTTO. Even the Enterprise e-commerce apps assume you own the storefront, which on a marketplace you do not.

What we build is a first-class Odoo integration, not a spreadsheet bridge. A dedicated otto.backend model holds credentials, environment and per-channel defaults, and every synced document carries an external identifier and a channel reference so a marketplace order is traceable back to OTTO forever. Order import runs on an ir.cron job (and can be triggered manually) that pulls new and updated orders, resolves or creates the customer partner, maps OTTO SKUs to product.product through a mapping model rather than by guessing on internal reference, and creates the sale.order with the right pricelist, fiscal position and warehouse. Marketplace statuses are mapped explicitly — announced, processable, sent, returned, cancelled — onto Odoo's own state machine plus a channel status field, so operations can filter a list view by what OTTO thinks is true, not just what Odoo thinks is true.

Stock and price synchronisation runs the other way. Computed fields with @api.depends on the relevant stock.quant and pricelist inputs derive the sellable quantity per listing, apply a per-SKU or per-warehouse safety buffer, and queue a delta push so OTTO is only told about SKUs that actually changed. Listing export builds the OTTO payload from product.template and product.attribute values through a configurable category and attribute mapping, so your Odoo attributes drive the marketplace variant structure instead of being retyped. When a picking is validated, shipment confirmation and the carrier tracking reference are pushed back automatically, which is what protects your on-time delivery metrics. Settlement files are imported and reconciled into draft journal entries with commission, fulfilment and return fees on separate accounts and analytic distribution, so the payout in your bank statement matches a posted entry line by line. Everything is wrapped in a request/response log model with retry and error queues, ir.model.access.csv entries plus record rules for a marketplace-operator group, and Odoo list/form/OWL views so no one has to read a log file to find out why an order failed. The module is delivered for your exact series — 17.0, 18.0 or 19.0 — with the __manifest__.py pinned to it, and it works on Community; where Enterprise features such as advanced accounting reporting or Studio-built fields exist, we integrate with them rather than duplicating them.

This is a build-to-order product. There is no instant download and we do not pretend otherwise. You request a quotation, we run a scoping call, and we confirm the specifics that actually change the code: your Odoo version and hosting, whether you are single- or multi-warehouse, how your OTTO SKUs relate to your Odoo variants, which OTTO API credentials and scopes you can provide, and how you want fees posted in your chart of accounts. From confirmed scope, typical delivery is one working week. We build against your Odoo version, deliver to a staging database first for UAT with your own catalogue and a real OTTO sandbox or limited-scope account, and only then go live with an agreed rollback plan.

You receive the full source, a git repository handover, and documentation written for both your developer and your operations team. Because the marketplace API and your business both move, we also agree a post-go-live support window up front and can quote an ongoing maintenance arrangement covering OTTO API changes and Odoo version upgrades.