Sync eMAG Romania, Bulgaria and Hungary offers, orders, AWB labels and RMA returns with Odoo 17/18/19. Built and installed by ECOSIRE. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $499.00 USD; request a quote for a scoped proposal.
App manifest
Built around your workflow
Sync eMAG Romania, Bulgaria and Hungary offers, orders, AWB labels and RMA returns with Odoo 17/18/19. Built and installed by ECOSIRE.
No DIY setup — a working app, built, installed and supported by ECOSIRE.
Start with a one-time build price. We scope it with you at kickoff.
ECOSIRE builds, configures and installs it on your Odoo.
You go live in about 2–4 weeks, with a post-launch support window.
Selling on eMAG across Romania, Bulgaria and Hungary means living inside eMAG Marketplace's seller panel — updating offers, acknowledging orders inside the tight SLA window, printing AWBs for the eMAG-integrated couriers, and processing returns — while your inventory, invoicing and accounting truth actually lives in Odoo. Doing this by hand, or through generic CSV exports, guarantees oversells, missed acknowledgment deadlines, mispriced offers and a warehouse team that works off two screens.
The eMAG Marketplace Connector (CEE) is a build-to-order Odoo application that ECOSIRE designs, develops, installs and supports specifically for your account and catalog. It is not an off-the-shelf apps.odoo.com download — there is no instant download. Our engineers build it against your eMAG Marketplace API credentials, your product data model and your CEE country footprint, then deploy it to your Odoo 17, 18 or 19 instance (Community or Enterprise) within a typical 2-4 week lead time.
Under the hood it is a proper Odoo module: a versioned __manifest__.py, new models extending product.template/product.product, sale.order and stock.picking via the ORM (models.Model, typed fields, and @api.depends computed fields that keep eMAG-synced stock and status in step with Odoo), backed by ir.cron scheduled jobs and ir.actions.server automated actions that talk to the eMAG Marketplace API over JSON-RPC. Access is locked down with ir.model.access.csv and record rules so warehouse staff, sellers and accountants each see only what they should. eMAG connection settings and mapping data live in dedicated backend views (XML/OWL), and AWB documents render through QWeb.
Offer publication pushes your product, price and available-to-promise stock to eMAG on a schedule you control, so you stop overselling. Orders flow the other way — imported into Odoo as native sale orders, auto-acknowledged inside eMAG's SLA so you protect your seller metrics. AWB / courier labels are generated and tracked for eMAG's integrated couriers straight from the delivery order, and returns come back as structured RMA records you actually process instead of chase. Category and characteristic mapping bridges the gap between your Odoo catalog and eMAG's rigid taxonomy once, so every future offer inherits the correct classification.
Because ECOSIRE builds it, we own the fit: your exact price rules, your multi-warehouse stock logic, your VAT and country splits across RO/BG/HU, your existing customizations. You get clean, upgrade-safe code, full handover documentation, a team walkthrough and a post-launch support window — not a black box you have to reverse-engineer.
An online retailer in Romania, Bulgaria or Hungary whose main revenue comes from eMAG but whose stock, purchasing and accounting run in Odoo. They need offers, stock and orders to stay in perfect sync so they stop overselling and losing SLA points, without hiring a full-time person to babysit the seller panel.
The person responsible for picking, packing and shipping eMAG orders on time. They want AWBs and courier labels generated straight from the Odoo delivery order, live tracking on each shipment, and returns coming back as clean records they can receive and process — all from one Odoo screen instead of switching to eMAG for every step.
An operations or finance owner running eMAG across two or three CEE countries who needs each country's orders, VAT and currency to land correctly in Odoo accounting. They care about accurate invoicing, reconciled returns and refunds, and reliable data they can report on — not manual spreadsheets bridging eMAG and the ERP.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| eMAG offer, order, AWB and return sync out of the box | Included | Partial support | Partial support | |
| Built and configured for your exact catalog, pricing and RO/BG/HU footprint | Included | Included | Not included | |
| AWB / courier label generation from the Odoo delivery order | Included | Partial support | Partial support | |
| Return (RMA) import and processing tied to the original order | Included | Partial support | Partial support | |
| Category and characteristic mapping to eMAG taxonomy set up for you | Included | Partial support | Partial support | |
| Upgrade-safe code across Odoo 17, 18 and 19 (Community & Enterprise) | Included | Partial support | Partial support | |
| Installed, tested end-to-end and deployed by the vendor | Included | Not included | Not included | |
| Post-launch support window, docs and training included | Included | Partial support | Partial support | |
| No upfront in-house Odoo/eMAG-API development effort required | Included | Not included | Included |
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 2-4 weeks 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.
Sync eMAG Romania, Bulgaria and Hungary offers, orders, AWB labels and RMA returns with Odoo 17/18/19. Built and installed by ECOSIRE.