Marketplace Messaging & Buyer-Communication Inbox

This is a build-to-order module, not an instant apps.odoo.com download. After a short scoping call we build, install and test the module for your specific marketplaces and SLA policies. Typical delivery is 2 to 4 weeks, depending on how many marketplace accounts you connect and how much automation (AI drafts, claim workflows, escalations) you need. You will have a fixed scope and timeline in writing before we start.

Every build includes a post-delivery support and bug-fix window with a defined SLA, plus a written handover of the source code, credentials and architecture notes. Marketplace APIs (Amazon SP-API, eBay, Mercado Libre) change over time, so we also offer optional ongoing maintenance to keep connectors, SLA rules and claim types current across Odoo 17, 18 and 19. Because you own the code, you are never locked in.

The core build covers Amazon buyer-seller messaging and A-to-z / INR / SNAD claims, eBay buyer messages and cases, and Mercado Libre messages plus pre-sale Questions & Answers. We scope the exact channels to your accounts during discovery, and the model is designed so additional marketplaces or message types can be added later without a rewrite.

It runs on both. The module is built on standard Odoo primitives — models.Model, ir.model.access.csv, record rules, ir.cron, QWeb and standard views — so it works on Odoo Community 17, 18 and 19. Enterprise-only features (such as certain UI or reporting enhancements) are used only if your instance has Enterprise; we confirm your edition during scoping.

Inbound messages are pulled through the marketplace APIs on a scheduled ir.cron cycle, with webhook ingestion where a marketplace supports it, and normalized into the marketplace.message model. When an agent replies inside Odoo, the module routes the response back to the correct marketplace channel and stamps the response time against the SLA target. Everything is also reachable over Odoo's XML-RPC / JSON-RPC API for external tools.

Yes. Each thread has a computed SLA status field (using @api.depends on the received-at time and your per-marketplace target) so agents see time-remaining at a glance. Automated actions escalate or alert a team lead before a breach, and a QWeb report plus native pivot/graph views give you response-time and claim analytics you can present in weekly reviews or use to defend account-health metrics.

Where the marketplace order reference resolves, each thread links automatically to the matching sale.order and res.partner, so an agent answering a buyer sees the order, product and shipment context on the same record. This linkage is part of the standard build and keeps your customer-service data connected to the rest of your Odoo ERP.