Product details are displayed in English. Translations coming soon.
Quick facts
- Price
- $499.00 USD
- Odoo versions
- 17, 18, 19
- Setup time
- 20160 min
- License
- One-time perpetual
- Languages
- 11 languages
एक बार की खरीदारी
Marketplace Messaging & Buyer-Communication Inbox
Unify Amazon, eBay & Mercado Libre buyer messages, Q&A and claims into one Odoo inbox with SLA timers and AI-draft replies.
$499.00USD
अभी कोई भुगतान नहीं। यह हमारी टीम को एक कोटेशन अनुरोध भेजता है — हम कीमत और अगले चरणों के साथ ईमेल द्वारा संपर्क करेंगे।
प्रमुख सुविधाएँ
Unified inbox model (marketplace.message) that normalizes Amazon, eBay and Mercado Libre buyer messages into one threaded Odoo record with marketplace, order reference, buyer and direction
Mercado Libre pre-sale Questions & Answers sync — incoming questions land in the inbox and answers post straight back to the listing via the ML Questions API
Per-marketplace SLA timers with a computed status field (@api.depends on received-at and target) showing green/amber/red time-remaining, not a raw timestamp
Response-time compliance alerts via ir.cron and automated actions that escalate or notify a team lead before a marketplace SLA breaches
Claim and dispute tracking for Amazon A-to-z Guarantee, item-not-received (INR) and significantly-not-as-described (SNAD/SNAD) cases, each with stage, owner and resolution status
Canned replies and reusable message templates with QWeb/placeholder rendering so agents insert order-, buyer- and product-specific answers in one click
AI-draft reply suggestions that propose a first-pass response an agent can edit and approve before it posts back to the marketplace
Two-way send: agents reply inside Odoo and the module routes the message back to the correct Amazon SP-API, eBay or Mercado Libre channel and records the send time
Automatic linkage to sale.order and res.partner when the marketplace order reference resolves, giving agents order, product and shipment context inline
Scheduled polling (ir.cron) plus webhook ingestion where a marketplace supports it, so new messages appear without manual refresh
Team routing and assignment with kanban stages, plus record rules so agents only see the marketplaces and teams they are permitted to handle
Response-time and claim analytics through Odoo's native pivot/graph views and a QWeb PDF SLA-compliance report for weekly reviews
XML-RPC / JSON-RPC endpoints so external tools, dashboards or a helpdesk front-end can read threads and post replies programmatically
Full multi-marketplace, multi-account support — several seller accounts per marketplace, each with its own credentials, SLA policy and routing
Security-first design: ir.model.access.csv per group, record rules for marketplace/team isolation, and encrypted storage of marketplace API credentials
इस उत्पाद के बारे में
Your customer-service team is drowning in tabs. Amazon buyer-seller messaging in one window, eBay messages in another, Mercado Libre pre-sale questions in a third, and A-to-z / SNAD claims buried in seller-central dashboards nobody watches until a metric turns red. Every marketplace has its own SLA clock, its own reply UI, and its own way of penalizing a late response. Nothing lives in Odoo, so nothing is measurable.
Marketplace Messaging & Buyer-Communication Inbox क्यों चुनें
Unified inbox model (marketplace.message) that normalizes Amazon, eBay and Mercado Libre buyer messages into one threaded Odoo record with marketplace, order reference, buyer and direction
Mercado Libre pre-sale Questions & Answers sync — incoming questions land in the inbox and answers post straight back to the listing via the ML Questions API
Per-marketplace SLA timers with a computed status field (@api.depends on received-at and target) showing green/amber/red time-remaining, not a raw timestamp
Response-time compliance alerts via ir.cron and automated actions that escalate or notify a team lead before a marketplace SLA breaches
Claim and dispute tracking for Amazon A-to-z Guarantee, item-not-received (INR) and significantly-not-as-described (SNAD/SNAD) cases, each with stage, owner and resolution status
Canned replies and reusable message templates with QWeb/placeholder rendering so agents insert order-, buyer- and product-specific answers in one click
The Marketplace Messaging & Buyer-Communication Inbox is a build-to-order Odoo module that ECOSIRE designs, builds, installs and supports for you. It is NOT an off-the-shelf apps.odoo.com download — it is a net-new module scoped to your exact marketplaces, message types and SLA policies, then delivered as clean, versioned source code you own. Typical delivery is 2 to 4 weeks depending on the number of marketplace connections and the depth of automation you need.
At its core sits a new Odoo model (a models.Model such as marketplace.message) that normalizes every inbound message, question and claim from Amazon, eBay and Mercado Libre into a single threaded record. Each thread carries the marketplace, order reference, buyer, message body, direction, and a computed SLA status field driven by @api.depends and Odoo's fields.Datetime so agents always see time-remaining, not a raw timestamp. Threads link back to sale.order and res.partner where the order reference resolves, so an agent answering a buyer sees the order, the product, and the shipment without leaving the record.
Messages arrive through the marketplace APIs (Amazon SP-API messaging, eBay Post-Order / messaging, Mercado Libre Questions & Messages) via scheduled ir.cron polling and, where available, webhook ingestion — all exposed to your other systems over Odoo's XML-RPC / JSON-RPC API. Agents reply from Odoo; the module pushes the response back to the correct marketplace channel and stamps the response time against the SLA target. Because it is real Odoo, everything is governed by ir.model.access.csv and record rules, rendered in standard list/form/kanban views (with optional OWL components for the live inbox), and reportable through QWeb and Odoo's native pivot/graph analytics.
The result is one measurable inbox: every buyer message answered in time, every claim tracked to resolution, and response-time compliance you can actually prove to Amazon, eBay and Mercado Libre — instead of discovering a health-metric hit after the damage is done. Runs on Odoo 17, 18 and 19, Community or Enterprise.
What you get
- Complete, version-controlled Odoo module source code (models, security, views, data, __manifest__.py) that you own outright, compatible with Odoo 17, 18 and 19
- Configured marketplace connections for your Amazon, eBay and/or Mercado Libre seller accounts, including API credential setup and SLA-policy mapping
- Security configuration: ir.model.access.csv access rules and record rules for your customer-service groups, teams and marketplace isolation
- SLA-compliance QWeb report plus preconfigured pivot/graph analytics views for response-time and claim reporting
- Installation and deployment on your Odoo instance (self-hosted, Odoo.sh or ECOSIRE-managed), including scheduled-action (ir.cron) tuning
- Admin and agent documentation: configuration guide, template/canned-reply authoring, and a runbook for claim handling
- Live training session for your customer-service team and administrators on inbox workflow, templates and SLA alerts
- Post-delivery support and bug-fix window with a defined SLA, plus a written handover of credentials, source and architecture notes
Who this is for
Customer-Service Team Lead (multi-marketplace seller)
Manages a queue of agents answering buyer messages across Amazon, eBay and Mercado Libre. Needs every message in one place, SLA timers per marketplace, and proof of response-time compliance to protect account health metrics.
E-commerce / Marketplace Operations Manager
Owns marketplace account health and claim resolution rates. Wants A-to-z, INR and SNAD claims tracked to closure with owners and stages, and weekly SLA and claim analytics inside Odoo rather than scattered across seller dashboards.
Odoo Administrator / IT Lead
Responsible for the Odoo instance, integrations and access control. Wants a clean, maintainable module with proper ir.model.access.csv and record rules, cron-based ingestion, and XML-RPC/JSON-RPC hooks — not brittle scripts glued to the outside of Odoo.
Installation overview
Download from ECOSIRE
Buy the license on ecosire.com and download the Marketplace Messaging & Buyer-Communication Inbox module ZIP from your account dashboard.
Upload to Odoo
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Install the module
Activate Developer Mode, open Apps, click Update Apps List, search for Marketplace Messaging & Buyer-Communication Inbox, and press Install.
Configure settings
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Verify & go live
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
How Marketplace Messaging & Buyer-Communication Inbox Compares
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Fits your exact marketplaces, SLA policies and claim types | Scoped and built to your accounts (Amazon, eBay, Mercado Libre) and SLA targets | Possible but you specify and manage every detail yourself | Fixed feature set; you adapt to its assumptions | |
| Unified inbox across Amazon, eBay and Mercado Libre | Included | Partial support | Partial support | |
| Mercado Libre pre-sale Q&A sync | Included | Partial support | Not included | |
| Per-marketplace SLA timers and breach alerts | Computed SLA field + ir.cron escalations built in | Must be designed and coded from scratch | Sometimes, but rarely per-marketplace or configurable | |
| A-to-z / INR / SNAD claim tracking | Included | Partial support | Partial support | |
| You own the source code and can extend it | Included | Included | Not included | |
| Proper Odoo security (ir.model.access.csv + record rules) | Designed per team and marketplace | Depends on your team's discipline | Partial support | |
| Installation, training and supported delivery | Built, installed, documented and supported by ECOSIRE | Your team's responsibility end to end | Self-serve install; limited vendor support | |
| Time and cost to go live | Fixed 2-4 week build with defined scope and price | Unpredictable in-house engineering effort | Fast to install but often needs custom glue anyway |
Frequently Asked Questions about Marketplace Messaging & Buyer-Communication Inbox
How long does delivery take, and is this an instant download?
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.
What ongoing support and updates do I get after go-live?
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.
Which marketplaces and message types are supported?
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.
Does it work with Odoo Community, or do I need Enterprise?
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.
How do messages actually get in and out of Odoo?
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.
Can it enforce and prove SLA compliance to the marketplaces?
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.
Will it link buyer messages to my existing orders and customers?
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.
Related Modules
कोटेशन का अनुरोध करें
Marketplace Messaging & Buyer-Communication Inbox
Unify Amazon, eBay & Mercado Libre buyer messages, Q&A and claims into one Odoo inbox with SLA timers and AI-draft replies.
- Unified inbox model (marketplace.message) that normalizes Amazon, eBay and Mercado Libre buyer messages into one threaded Odoo record with marketplace, order reference, buyer and direction
- Mercado Libre pre-sale Questions & Answers sync — incoming questions land in the inbox and answers post straight back to the listing via the ML Questions API
- Per-marketplace SLA timers with a computed status field (@api.depends on received-at and target) showing green/amber/red time-remaining, not a raw timestamp
- Response-time compliance alerts via ir.cron and automated actions that escalate or notify a team lead before a marketplace SLA breaches