Marketplace Inventory Sync & Oversell Protection

Typical delivery is 2 to 4 weeks from kickoff, depending on how many channels and warehouses are in scope and the complexity of your bundle/allocation rules. This is a build-to-order module — it is not an instant apps.odoo.com download. After purchase we run a short discovery call to map your channels, warehouses and policies, then design, build and test the module against your Odoo version (17, 18 or 19), install it on your server, migrate your stock baselines and run a supervised go-live cutover with you.

Every build ships with a post-launch support and warranty window covering bug fixes, sync tuning and one Odoo point-release compatibility check. Because you receive the full source in a Git repository you own, there is no lock-in — any Odoo partner can maintain it. We also offer optional ongoing support and version-upgrade retainers if you'd like ECOSIRE to keep the module current as Odoo and your marketplace APIs evolve.

The module is built around your specific channel mix. Common targets include Amazon, eBay, Shopify, WooCommerce, Magento and Odoo's own eCommerce, plus custom or regional marketplaces exposed over a REST/GraphQL API. Each channel connects through its own API for outbound stock pushes and inbound order reservation. If a channel exposes an inventory API, we can integrate it — tell us your list during discovery.

Availability is computed from Odoo's true free-to-sell quantity (on-hand minus reserved, adjusted for inbound and your per-channel buffer) using computed fields with @api.depends. When a channel confirms a sale, the reservation is written under database-level row locking on stock.quant, so two concurrent orders cannot draw down the same unit. The first order commits; the second hits the oversell lock and follows the back-order or hard out-of-stock policy you set for that channel.

Yes. Multi-warehouse allocation rules let you aggregate stock across warehouses for a channel or dedicate a specific warehouse per marketplace or region. For bundles and kits, selling a bundle decrements every shared component's availability across all channels, and when any component hits its buffer the parent listing is automatically suppressed — preventing the classic oversell where two different bundles share one scarce part.

It runs on Odoo Community or Enterprise, versions 17, 18 and 19. The module is written as an idiomatic, upgrade-safe extension — a clean __manifest__.py, models that inherit rather than override core, security via ir.model.access.csv and record rules, and cron-driven sync — so it survives Odoo point upgrades. You own the source, so you're never blocked from upgrading or switching maintainers.

Yes. Available-to-promise quantities and sync status are exposed over Odoo's XML-RPC/JSON-RPC API and optional webhook/REST endpoints, so a 3PL, an external OMS, or another Odoo app can read live stock and trigger a re-sync programmatically — all governed by the same record-rule security so external callers only see what they're entitled to.