Website and marketplaces department one of the departments in your AI company
eMAG Marketplace integration connects your seller account by API login: offers come into one catalog per country, prices and stock go back in batches, and eMAG orders are confirmed from Elbuz.
Six jobs that otherwise happen by hand in the eMAG seller account.
Offers come in with name, description, price without VAT, stock, category, characteristics, photos and the variant family. Your own edits are protected by the “do not update” flag. Product data is kept once in the product catalog (PIM) and goes to every channel.
Your categories are mapped once to the eMAG category tree, and attributes to its required fields. A product that misses a required field is shown before export, not after a rejection. With publishing on, a product with an EAN becomes an offer on the existing eMAG product page; a product without one goes as a new product for moderation and needs a mapped category, all mandatory characteristics and GPSR details.
Each export template takes its own price or calculates it by formula — for example your base price plus a markup that covers the eMAG commission. The catalog and your website keep their own prices. Markup rules.
Price and stock go back to eMAG through an export template, 50 offers per request. The price goes without VAT — the way eMAG expects it. Stock comes from your warehouses and supplier price lists.
eMAG orders arrive as customer orders in Elbuz and are confirmed on eMAG. From there they are processed like any other order — see order management.
Marketplace order statuses map to your own Elbuz statuses, and shipping details stay on the order. Romania, Bulgaria and Hungary each get their own template, all in one catalog. eMAG accepts one request every three seconds, and Elbuz keeps to that pace.
eMAG does not need a separate product database: it takes products from the catalog you already keep.
The same catalog also feeds your website, other marketplaces and product feeds for Google Shopping, Meta and TikTok.
The same windows run every marketplace: the product card, the export templates and the order list.
The same path as every Elbuz integration: a template, access to the seller account, a check and a schedule.
No coding is needed. Support moves your data from another program or website free of charge. All marketplaces — marketplace integrations.
What the marketplace asks for before your first listing goes live.
Requirements are set by eMAG and change over time. Checked against the official pages on 30 October 2026: eMAG Marketplace — start selling.
With an API login and password created in the eMAG seller account, plus the country code. eMAG only accepts API calls from whitelisted IP addresses, so the first step is to add the Elbuz IP address to the whitelist in your eMAG account.
Yes. Each country gets its own template in Elbuz and all of them use one catalog. Keep country offers in separate cards if their names differ, so lei, forints and euros (Bulgaria has used the euro since 1 January 2026) never mix in one price field.
The EU General Product Safety Regulation requires the responsible person and manufacturer details for products sold in the EU. In Elbuz they are set once in the eMAG template and go with new products.
Without VAT. Elbuz reads and sends the eMAG price without VAT, as the marketplace expects.
eMAG allows one request every three seconds, and Elbuz reads 100 offers per page, so a large catalog takes a while. The run continues on the server — you can close the window.
14 days free
The website and marketplaces department joins your AI company along with every other department. €50 on your balance after sign-up and 14 days to test the integration on your own products.
