| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Sales (sale_management) • Discuss (mail) • Invoicing (account) |
| Lines of code | 1499 |
| Technical Name |
mp_emag_connector |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Sales (sale_management) • Discuss (mail) • Invoicing (account) |
| Lines of code | 1499 |
| Technical Name |
mp_emag_connector |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
eMAG Romania Marketplace Connector
Direct eMAG v4 Marketplace API connector for Odoo — orders, stock, price and AWB across Romania, Bulgaria and Hungary
Connect Odoo straight to your eMAG Marketplace seller account. Import eMAG orders into Odoo sales, keep stock and prices in sync by part number, drive the eMAG order status machine and generate courier air waybills (AWB) — for eMAG Romania, eMAG Bulgaria and eMAG Hungary, all from one Odoo app and driven entirely by your own eMAG API credentials.
Key Features
Order Import (pull)
A scheduled job and an on-demand button read recent eMAG orders through the order/read RPC, page by page, filtered by eMAG status and creation date. Each order becomes an Odoo sale order with customer, shipping address and lines.
Order Lines Mapping
Order products are resolved to your Odoo products by part number, Odoo internal reference or barcode. Quantity and unit sale price are carried straight into the Odoo sale order line.
Acknowledge & Status Machine
Acknowledge new orders (so eMAG stops the new-order alert) and move orders through the eMAG status flow — new, in progress, prepared and finalized — with one click. Status changes do a proper read-modify-write (re-read the full order, then order/save) as eMAG requires, alongside order/acknowledge.
Stock Sync (push)
Push available quantity to eMAG by product id through product_offer/save — per product, in bulk, or via an hourly cron. Stock and handling time are declared against your configured eMAG warehouse id.
Price Sync (push)
Push your Odoo sales price and VAT id to eMAG offers — per product, in bulk, or via an hourly cron. Recommended price and per-product VAT id are supported, with a per-account default VAT id fallback.
AWB Generation
Generate a courier air waybill (AWB) for an eMAG order through awb/save using your eMAG courier account id. Parcel weight is computed from the order lines and the COD amount is filled automatically for cash-on-delivery orders.
Multi-Country (RO / BG / HU)
Run eMAG Romania, eMAG Bulgaria and eMAG Hungary side by side. Each platform is one account with its own API credentials and official api-3 endpoint, so a single Odoo can sell across all three eMAG marketplaces.
Test Connection & API Log
One button validates your credentials with a real lightweight API call. Every call is recorded in a unified API log with operation, platform, status, duration and error excerpt for fast troubleshooting.
How It Works
| 1. Add an account | Create one eMAG account per country (Romania, Bulgaria, Hungary) with your own API username and password. |
| 2. Map products | Set the eMAG product id and part number on your Odoo products and mark them as synced to eMAG. |
| 3. Sync | Pull orders and push stock and price on demand or on a schedule; acknowledge, advance and ship. |
| 4. Fulfil | Generate the AWB, finalize the order on eMAG and keep the Odoo sale order in step. |
eMAG API Coverage
| eMAG Resource | Action | Used For |
|---|---|---|
order | read / count | Import & count marketplace orders |
order | acknowledge / save | Acknowledge and advance order status |
product_offer | save / read | Push stock, price, VAT id, handling time |
awb | save / read | Generate and read courier waybills |
category | read | Read the eMAG category tree |
vat | read | Read the VAT id rate table |
Bring Your Own Key (BYOK)
This is a seller-API connector. You paste the API username and password from your own eMAG Marketplace account. Requests are sent only to the official eMAG api-3 endpoint of the platform you select; the base URL is an editable default so you can point at a reverse proxy without code changes. This module does not impersonate any certified courier or fiscal device — it builds and transmits the marketplace payloads your eMAG account consumes.
Requirements
- Odoo 18.0 or 19.0 (Community or Enterprise).
- An active eMAG Marketplace seller account with API access enabled (RO, BG and/or HU).
- IP whitelisting: eMAG applies IP-level filtering, so your Odoo server's public (outbound) IP must be whitelisted in your eMAG Marketplace account (Profile → API) before any API call is accepted — even with valid credentials.
- The Python
requestslibrary (bundled with standard Odoo deployments).
Screenshots
Accounts
Api Log
Emag Orders
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module