A catalog with a performance signal on every product
eMAG reads your products from the feed. Feedance sends a complete, valid feed plus the signals eMAG does not have on its own.
eMAGChannel · Marketplaces and appsFeedance builds your eMAG feed and adds product-level labels for score, 4T segment, price position and broken sizes, so every product carries its own performance signal.
eMAG reads your products from the feed. Feedance sends a complete, valid feed plus the signals eMAG does not have on its own.
eMAG is the largest e-commerce marketplace in Romania, and it runs equivalent Marketplace platforms in Bulgaria (emag.bg) and Hungary (emag.hu) under the same seller program. Third-party sellers don't sell through a separate storefront — they list offers directly against eMAG's own product catalog through the eMAG Marketplace, and every offer competes on the same product page as eMAG's own retail listings and other marketplace sellers. eMAG gives sellers two ways to publish and maintain that catalog: the eMAG Marketplace API (JSON, currently documented at version 4.5.1) or a hosted XML/CSV Feed Import that eMAG fetches and reprocesses on a schedule.
Manually re-entering products and re-typing stock or price changes in the eMAG seller panel does not scale once a catalog passes a few dozen SKUs, and it is the single biggest source of stale prices and overselling on a fast-moving marketplace. Feeding eMAG programmatically lets you push new offers, price changes, and stock levels from your own PIM or storefront the moment they change, rather than on whatever cadence someone remembers to log in and edit listings by hand. It also lets you reach three markets — Romania, Bulgaria, and Hungary — from the same underlying product data, since all three run on the same Marketplace API and Feed Import mechanics.
eMAG does not charge a signup fee, a monthly subscription, or a per-listing fee. Sellers pay a category-based commission only on completed sales, and eMAG's own seller documentation states the commission 'varies between 7 and 25%, depending on the category' the product is listed in — the exact rate for each category is set out in the seller's Marketplace contract. Commission is deducted automatically before payout, and sellers are paid twice monthly. Sellers who opt into Fulfilled by eMAG (FBE) pay additional storage fees based on how long inventory sits in an eMAG warehouse, plus a per-order processing fee that starts at 3.99 RON and scales with package size and weight.
eMAG supports two distinct integration paths, and Feedance is built around the API path because it gives the tightest control over validation and update timing:
product_offer, category, and order (e.g. product_offer/save, product_offer/read, product_offer/count). Every response is standardized JSON containing an isError boolean and a messages array, and a single save call is capped at 50 entities (10-50 is the range eMAG recommends for reliable processing), with a hard ceiling of 4000 elements per call.Both paths ultimately populate the same underlying product/offer records, so the choice comes down to how much real-time control you need over validation responses and error handling — which is why Feedance defaults to the JSON API.
| Attribute | Required? | Format / notes |
|---|---|---|
id | Required | Integer 1-16,777,215 — your own internal product ID, used as the primary key for every future update to this offer. |
category_id | Required | Integer identifying the eMAG product category; sellers cannot create or modify categories, only select from eMAG's existing tree via the category resource. |
name | Required | String, 1-255 characters. |
part_number | Required | String, 1-128 characters — the manufacturer's part/model number, used by eMAG to detect duplicate products. |
brand | Required | String, 1-255 characters. |
sale_price | Required | Decimal, must be greater than 0, up to 4 decimals; price without VAT. |
vat_id | Required | Integer referencing the applicable VAT rate. |
stock | Required | Array of warehouse_id/value objects — numeric stock per warehouse. |
min_sale_price / max_sale_price | Required on first save | Decimal bounds; every later sale_price update must fall inside this band or the offer is rejected. |
ean | Conditionally required | Array of barcodes, 6-14 numeric characters (EAN-8/13, UPC-A/E, GTIN-14, etc.); the category/read response tells you per-category whether EAN is mandatory or optional. |
images | Optional but effectively required | Array of image URLs; max 6000x6000 px and 8 MB per image, JPG/JPEG/PNG only. |
characteristics | Optional but effectively required | Array of id/value pairs; each characteristic ID must be valid for the chosen category_id, or the save is rejected as a category/characteristic mismatch. |
warranty | Optional | Integer, months of warranty, 0-255 (default 0). |
handling_time | Optional | Array of warehouse-specific shipping/handling days. |
product_offer schema — name, part_number, brand, sale_price, vat_id, stock, EAN, images, and the category-specific characteristics eMAG requires for each category_id you sell into.min_sale_price / max_sale_price bounds so future price updates don't get silently rejected once the offer is live.save call, and push it — while automatically pacing requests to stay under eMAG's rate limit rather than firing everything at once.isError / messages responses Feedance surfaces back from each push so rejected offers (bad category-characteristic pairing, price out of band, invalid EAN, etc.) get flagged for a fix rather than silently disappearing.eMAG's own guidance is explicit about pacing: the Marketplace API allows a maximum of 1 request every 3 seconds and 20 requests per minute per account, and eMAG recommends against scheduling calls at round, fixed clock times (for example starting a batch at 12:04:42 rather than 12:00:00) so that many sellers' jobs don't collide on the same second. Within that ceiling, price and stock are the fields worth updating most aggressively — ideally every time they change on your side, and at minimum several times a day — since a stale stock figure on a fast marketplace directly costs you orders you can't fulfill or your ranking against competing offers on the same product page. A full catalog re-sync (new products, updated descriptions, images, characteristics) is reasonable on a daily cadence for most sellers; if you're using Feed Import instead of the API, the file is only as fresh as the last time eMAG's Feed Import module re-fetched your hosted URL, so check the refresh interval you configured in the seller panel.
The most common rejections documented in eMAG's Marketplace API reference are:
sale_price update falls outside the min_sale_price/max_sale_price band set on the offer's first save.characteristics entry whose ID isn't valid for the offer's category_id causes that save to be rejected.X-RateLimit-Limit-3second / X-RateLimit-Remaining-3second headers you can use to back off before hitting the ceiling again.part_number_key instead of submitting a brand-new product — this skips re-validation and gets your offer live faster.min_sale_price/max_sale_price bounds up front; too narrow a band means routine repricing gets rejected later, and eMAG only lets you set these on the first save.product_offer/save calls in the 10-50 entity range eMAG recommends, and stagger your job's start time away from round clock minutes to avoid rate-limit collisions with other sellers' scheduled jobs.Does eMAG use an XML feed or a JSON API?
Both exist. The Marketplace API is JSON over authenticated POST requests and is the path Feedance automates. eMAG also offers a separate Feed Import option that accepts a hosted XML or CSV file, capped at 100 MB, 100,000 products, and 150 categories.
Can one feed cover Romania, Bulgaria, and Hungary at once?
Each country runs its own Marketplace account and its own API/seller-panel instance (emag.ro, emag.bg, emag.hu), so you connect to each separately, though the schema and mechanics are the same across all three.
What happens if I exceed eMAG's API rate limit?
You get an HTTP 429 response with a rate-limit-exceeded message. eMAG's limit is 1 request every 3 seconds and 20 requests per minute per account.
Is there a cost to use the eMAG Marketplace API itself?
No — there's no separate fee for API access. eMAG's revenue comes from the category-based commission (roughly 7-25%) charged on completed sales, not on integration or listing activity.
How many products can I include in a single API save call?
Up to 50 entities per product_offer/save call, with 10-50 recommended for reliable processing, and an overall cap of 4000 elements per call.
Emag is an e-commerce platform that offers a wide range of products to consumers. It was launched in the year 2001, making it one of the oldest and most established online marketplaces. Emag's country of origin is Romania, and it has since expanded its operations to other countries in Central and Eastern Europe.
The platform provides customers with a diverse selection of products including electronics, home appliances, fashion, beauty, sports equipment, home and garden items, and much more. With a user-friendly interface and a wide array of products, Emag aims to cater to the diverse needs and preferences of its customers.
One of the key features of Emag is its strong focus on customer service and satisfaction. The platform prioritizes providing a seamless and reliable shopping experience through features such as secure payment methods, efficient delivery services, and a responsive customer support team. This commitment to customer satisfaction has been instrumental in gaining a loyal customer base over the years.
Emag has also established partnerships with various brands and sellers to offer customers a vast selection of products. This helps in providing customers with multiple choices and competitive prices. Additionally, the platform often runs promotional campaigns, discounts, and exclusive deals to further attract and retain customers.
In recent years, Emag has further expanded its services by launching additional features such as Emag Pay, a digital wallet that allows customers to make fast and secure payments, and Emag Marketplace, which enables third-party sellers to list and sell their products on the platform.
As a prominent e-commerce platform, Emag has received several accolades and awards for its contribution to the industry. Its growth and success can be attributed to its dedication to customer satisfaction, commitment to quality, and continuous innovation in providing a seamless online shopping experience.
In conclusion, Emag is an established e-commerce platform that originated in Romania in 2001. It offers customers a wide variety of products and focuses on providing excellent customer service. Emag's steady growth and expansion have made it a popular choice for online shopping in Central and Eastern Europe.
Connect your feed and GA4. We show Product Score, 4T, Price War and Broken Size on your own catalog.