This is a build-to-order module, not an instant apps.odoo.com download. After purchase, ECOSIRE builds it against your eMAG Marketplace API credentials, your Odoo version and your catalog, then installs it on your instance. Typical lead time is one working week depending on how many countries (RO/BG/HU) are active and how much category/characteristic mapping your catalog needs. We start with a short scoping call, build on a staging database, run a full offer-to-order-to-AWB-to-return test with you, then deploy to production.

Every build includes a post-launch support window for bug fixes and adjustments, plus documentation and a training session so your team is self-sufficient. Because the module talks to the eMAG Marketplace API, we track relevant API changes and can update the connector under a support or maintenance agreement so it keeps working as eMAG evolves. We also support you across Odoo 17, 18 and 19, including help when you upgrade your Odoo version — the code is written to be upgrade-safe rather than a one-off hack.

Odoo 17, 18 and 19, on both Community and Enterprise. The module is a standard Odoo application — versioned __manifest__.py, ORM models extending product, sale.order and stock.picking, ir.cron scheduled jobs, security via ir.model.access.csv and record rules, and QWeb for AWB documents — so it installs cleanly on a properly maintained instance. If you're on Odoo.sh, an on-prem server, or ECOSIRE managed hosting, we deploy to your environment.

Yes. The connector supports per-country account configuration, so each active marketplace (eMAG.ro, eMAG.bg, eMAG.hu) has its own API credentials, currency and VAT handling. You can start with one country and add others later. Offers, orders, AWBs and returns are all handled per country while consolidating into your single Odoo database.

Stock published to eMAG is driven by Odoo's available-to-promise using @api.depends computed fields and multi-warehouse-aware sourcing, so eMAG offer quantity reflects real availability net of reservations. Because your orders — eMAG, POS, other channels — all reduce the same Odoo stock, the connector re-syncs offer quantities on a schedule and pushes only the changed offers. This keeps eMAG availability current and stays within eMAG's API rate limits.

That's the point of build-to-order. We map eMAG pricing to whichever source you choose — list price, a specific pricelist, or a dedicated eMAG price field — so marketplace prices don't disturb your other channels. We source stock from the specific warehouse(s) you fulfil eMAG from, and we build around your existing Odoo customizations rather than fighting them. During scoping we review your models and workflows so the connector slots into your instance cleanly.

Yes. All eMAG data lands in standard Odoo models, so it's fully available through Odoo's XML-RPC and JSON-RPC external APIs and any of your existing integrations, reports or automations. Offers, orders, AWBs and returns are first-class Odoo records — you can build dashboards, connect BI tools, or trigger your own automated actions on them just like any native Odoo data.