Elbuz pulls offers and orders from your eMAG seller account (Romania, Bulgaria, Hungary) via the Marketplace API into your base catalog, so every country's range lives in one place.
When you need this:
- Your catalog is already on eMAG — offers arrive with photos and attributes, no files.
- You sell in several eMAG countries — one template per country, one catalog.
- Orders go alongside other channels — each becomes a “Customer order” and is confirmed on eMAG.
- You price in Elbuz — an export sends prices back to eMAG.
Where to start: add the Elbuz IP to the whitelist in your eMAG account, then create an “eMAG” template.
What the eMAG connection does
- Connection with an API login, password and country — no tokens or developer apps.
- Offers transferred into cards — name, description, price without VAT, stock, category, attributes, photos and variant family.
- Repeat runs without duplicates — matched cards are updated, and the “Do not update” flag protects your edits.
- Orders — as a “Customer order” document, confirmed on eMAG.
- Several countries — one template per country, all into one catalog.
- Export back — price and stock, plus publishing new products.
What you need from eMAG
eMAG does not use tokens or “developer apps” — you connect with three values:
- API login — a separate login from your eMAG seller account (not the login you use for the web account; API access is issued separately).
- API password — the password for that API access.
- Marketplace (country) —
ro(Romania),bg(Bulgaria) orhu(Hungary). Elbuz uses this value to pick the right eMAG API domain.
The API login and password are created in the eMAG seller account, in the Marketplace API access section. They are separate credentials just for integrations — don't confuse them with your web account login.
IP whitelist — required
eMAG accepts API calls only from allowed IP addresses. Until the Elbuz IP address is on the whitelist in your eMAG account, even the correct login and password won't work — eMAG rejects the request.
So the first step is to add the Elbuz IP to the whitelist in your seller account's access settings. Elbuz support will give you the IP address.
GPSR requirement
Products on eMAG's European marketplaces fall under the GPSR product safety regulation: cards must carry details of the responsible person and the manufacturer. You enter these details with a separate GPSR settings button in the template form.
GPSR is not required to import the catalog into Elbuz. You'll need it as soon as you publish products back to eMAG.
Connecting step by step
- Add the Elbuz IP to the whitelist in your eMAG account.
- Create a template of the “eMAG” type, enter the API login and API password, and choose the country. “Active” and “Orders” are already on in a new template: within 5 minutes of saving, Elbuz starts fetching orders and confirming them on eMAG. Elbuz maps marketplace statuses to yours automatically, by name; the template's “Order statuses” window shows what came in and how it was mapped. Want to check first? Clear “Orders”.
- Click “Test connection” — a light request immediately shows whether eMAG accepts your access and whether the whitelist works.
- In the “Select data to import” card, turn on products.
- Save the template and run it.
What goes into the product card
Each eMAG offer is spread across the Elbuz card fields like this:
| eMAG data | Elbuz card field |
|---|---|
| offer name | Product name |
| description | Full description |
| brand | Manufacturer |
part_number | SKU |
ean | Barcode (digits only) |
sale_price — price without VAT | Price |
recommended_price, if higher than the price | Old price |
general_stock | Stock |
| offer status | Card activity |
| offer category | Category |
| offer attributes | Attributes |
product family (family) | Family (link between variants) |
| images (main one first) | Images — when the “Photo” checkbox is on |
part_number_key (PNK) | eMAG card key |
The eMAG API returns the price without tax, and that is what goes into the card. Shoppers on eMAG see the price with VAT, so Elbuz will differ by exactly the tax amount. Keep this in mind in your markup rules and when exporting prices back.
eMAG does not send a cost price. Base catalog markup rules calculate the selling price from the cost price, so right after import the “Price” field holds exactly what the marketplace returned. The post-import markup runs only on newly created cards.
Elbuz takes the category from the offer and creates it if the catalog has no category with that name. Offers without a defined category go into the service category “Products - emag”, which is disabled and has no export flag. What to do with it: service categories and brands. Manufacturers are created from the offer's brand name.
Attributes and variants
eMAG sends attributes as codes. To give the card readable labels, Elbuz separately reads the attribute directory of the offer's category. If a code's name could not be fetched, the attribute is saved with a technical label like “#123” — this means the category directory did not respond; no data is lost.
On eMAG, variants are grouped into a “family”: items of one family arrive in Elbuz linked into a variant family.
eMAG card key (PNK)
PNK (part_number_key) is the code of a product page in the eMAG catalog, shared by all sellers. Elbuz stores it with the product: the PNK links your offer to the marketplace product page, and you need it to publish a product on an existing eMAG product page.
What a repeat run overwrites
Every run reads the eMAG catalog again from the first page. Elbuz finds an existing card by the name fingerprint calculated during the first import. This leads to three cases:
- Start or end
- Action or result
- Decision: the path depends on the answer
- You renamed the product in Elbuz — the fingerprint is still the old one, the card is found, and the run restores the name from eMAG. No duplicate appears.
- The offer name was changed in the eMAG account — the fingerprint doesn't match, and Elbuz creates a second card. The old one stays in the catalog with its previous data and no marker.
- The same name already exists in the catalog from another source — the offer may attach to that card and overwrite its fields. This happens when that card was created under this name without a “Manufacturer SKU (MPN)” and without an external link: the fingerprint is calculated from these three values.
| What the run does | Fields |
|---|---|
| Overwrites with the eMAG value | Name, Full description, Manufacturer, SKU, barcode, Price, Old price, Quantity, Activity, Family name |
| Does not overwrite with an empty value | all fields above except quantity and activity: zero and a disabled offer are written as is |
| Does not touch | photos (only when the card is created), attributes, main category, cost price, tags, other fields |
To lock your own value, use the “Do not update” flag in the product card: the run skips such a card entirely. General field protection rules: how to lock your own value.
1
Do not update2
Fixed Price- Do not update — closes the whole product card from the eMAG import run.
- Fixed Price — protects only the price and old price from the eMAG import run.
The “Fixed Price” flag protects only the price and old price from the run. The eMAG run overwrites the name, description, stock and activity even with that flag set — only “Do not update” locks the whole card.
If an offer disappeared from eMAG or changed status
The run doesn't touch a card whose offer was missing from the eMAG response: it stays active with the last known price and stock, and the log has no line about it. Taking an offer off sale on eMAG disables nothing in Elbuz — such cards are removed by hand.
If the offer is still there but has changed, the run reacts:
- eMAG returned the offer as disabled — Activity is turned off in the card;
- stock dropped to zero — the card gets 0 and the “Out of stock” status; stock above zero brings back “In stock”.
Turn off “Activity” or delete the card
Turning off “Activity” deletes nothing: fields, photos, attributes and the link to the eMAG offer stay, and you can turn the checkbox back on. The product simply stops passing the filters in exports: a new export template has the “Product enabled” rule from the start.
On eMAG itself the offer stays on sale; Elbuz just stops sending it price and stock. You take a product off the storefront in the seller account. The next import restores “Activity” the way eMAG sees it; to keep the card disabled, use the “Do not update” flag.
Along with the card, the description, photos, attributes and link to the eMAG offer are gone — the next run creates the product again. Lines of documents already issued are not affected: a document keeps its own copy of the name, SKU, price and quantity.
How eMAG orders arrive
With the “Orders” checkbox on, the same template pulls orders; if you only want products, leave it off. Each order becomes a “Customer order” document:
- the eMAG number is saved as the document's external number;
- the buyer is created as a contact;
- lines find their cards by the offer set by the catalog import;
- Elbuz maps the document status to yours by itself, by the eMAG code (finalized — “Done”, canceled — “Canceled”), and the status mapping button in the template form lets you adjust it; the payment status is “Pending”.
A product not yet in the catalog is created by Elbuz from the order line data in the service category “Products - emag - template name”, which is disabled and has no export flag.
Order import doesn't touch stock — no write-off and no reservation. Only the product's sales counter changes. Your documents further down the chain move the stock.
Elbuz pulls orders in pages of 100. Each page is first saved in Elbuz, and only then is each of its orders automatically confirmed on eMAG. If a page could not be saved, its orders stay unconfirmed, a red line goes into the log, and the run stops.
A repeat import doesn't wipe out the operator's work: your processing status changes only when the status changed on the eMAG side, and a posted document isn't touched at all. Payment, delivery and payment method are taken from the marketplace as is.
- Start or end
- Action or result
- Decision: the path depends on the answer
Several eMAG countries in one catalog
Each country gets its own template, and each pulls its catalog into the same base catalog. The result depends on the offer names:
- the name is the same in both countries — one card for two countries; each run in turn overwrites the price, stock, description and name, and the last run's value stays;
- the names differ (Romanian and Bulgarian) — two separate cards, independent of each other.
A card has one offer link for all of eMAG: it is set by the template that created the card first. So exporting price and stock back goes to the offer of whichever country got there first.
The price arrives in the marketplace currency and goes into the field as a plain number. In a shared card for ro and bg, lei and leva take turns in the same “Price” field, with no currency marker. That's one more reason to keep countries in separate cards.
How prices and stock go back to eMAG
Import sends nothing to eMAG. The return path is a separate template in the “Data export” window, of the “eMAG” type, with its own API login and password. It takes the country from the “API version (marketplace parameters)” field: enter the same code as in the import template (ro, bg or hu); an empty field means Romania.
With the “Products” checkbox on, the export sends price and stock in batches of 50 offers. It updates the offer whose ID is stored in the card after import — even if another template set the link.
The export includes a product that:
- has the “Export to file (to website)” flag;
- is in an enabled category allowed for export;
- passes the template filter — a new template has the “Product enabled” rule there.
The price goes as a number from the “Price” field, that is, without VAT — exactly how eMAG expects it.
Publishing new products
A product without an offer link (created by hand or from a supplier price list) is skipped by the export while the “Publish new products” checkbox is off. With the checkbox on:
- a product with an EAN barcode (8 digits or more) becomes an offer on an existing eMAG product page;
- a product without an EAN goes to moderation as a new product page — it needs a category mapped to eMAG, all required attributes and the GPSR details.
Products that are missing something are skipped; their count is shown in the log. A published product gets an offer link, and from then on its price and stock update like all the others.
Scheduled updates
Elbuz fetches and confirms orders by itself every 5 minutes if “Orders” is checked and the login and password are filled in. The shared “Marketplace orders” task in the “Job schedule” window does this; the interval is set there. This pass skips the catalog, and orders also picked up by the template schedule aren't duplicated.
The catalog is updated by the template's own schedule — the “Schedule setup” button in the “Related settings” card. Set it to run rarely, for example at night: while the catalog is running, the orders pass is skipped until the next one. How scheduling works for all sources: data import overview.
Every run leaves a trail in the log: a line for each page read (“eMAG: catalog page 3, offers received: 300”), a summary line with the number of offers, and red lines for API errors. The run log is in the Operations Center, so you don't need to keep the template window open.
How long it takes
There is no cap on the number of offers. Elbuz reads the catalog in pages of 100 offers until eMAG returns an incomplete page, and writes to the catalog in portions of 500.
- Start or end
- Action or result
- Decision: the path depends on the answer
eMAG sets the pace: no more than one request per 3 seconds (and no more than 20 per minute). Elbuz pauses three seconds between requests, plus one request to the attribute directory for each new category. On “too many requests”, Elbuz waits and retries — up to three attempts with an increasing pause.
The “Last import” column in the template list shows how long your run took, and the “Run history” button in the form header shows all previous runs.
1
Last import- Last import — date and time of the template's most recent run; “never imported” means it has not been run yet.
Scenarios
The result depends on the checkboxes in the “Select data to import” card of the template form and on the flags in the product card.
1
Products2
Photo3
Orders- Products — import the offers (prices, stock) into the catalog.
- Photo — import product photos.
- Orders — receive eMAG orders.
Keep prices and stock in Elbuz the same as on eMAG
What to turn on. An “eMAG” type template with its own marketplace; in the “Select data to import” card — “Products”, and for the first run also “Photo”. After testing — a schedule via the task settings button in the template form.
What you get. Each run overwrites the name, description, price without VAT, stock, stock status and activity in matched cards with what eMAG returned. Photos and attributes of existing cards are not updated; the card of a vanished offer stays active.
Keep your own name or price instead of the eMAG one
What to turn on. In the product card, “Statuses and flags” section, “Import protection” group — the “Do not update” flag.
What you get. The run skips this card: the name, price, stock, manufacturer and activity don't change. Stock from eMAG no longer reaches it either — the flag protects the whole card.
Accept eMAG orders but run the catalog from supplier price lists
What to turn on. “Orders” on, “Products” off. Elbuz maps eMAG statuses by itself; you can adjust them with the status mapping button in the template form. The template needs no schedule: orders arrive by themselves every 5 minutes.
What you get. Each order becomes a “Customer order” document, the buyer becomes a contact, and once saved, the order is confirmed on eMAG. Stock is neither written off nor reserved — only the sales counter changes.
Sell in Romania and Bulgaria from one catalog
What to turn on. Two “eMAG” type templates: one with the ro marketplace, the other with bg.
What you get. Offers with different names become separate cards; offers with the same name share one card, which keeps the last run's values. Currency is not converted, and the offer link comes from the template that created the card first.
What to do when eMAG does not return data
| What you see | Why | What to do |
|---|---|---|
| The login and password are correct, but “Test connection” fails | The Elbuz IP is not on the whitelist in your eMAG account | Add the Elbuz IP to the whitelist; support will give you the address (IP whitelist) |
| Authorization fails, although the IP is on the whitelist | The web account login and password were entered instead of the API access | Take the separate API login and password from the seller account (what you need from eMAG) |
| “eMAG: API error - …” after choosing another country | The request goes to the chosen country's domain, but the API access was issued for another one — eMAG rejects it, and nothing is imported | Fix the country code in the template. “Connection works. eMAG RO” shows the code from the template field, not the marketplace's response |
| The run broke off or stopped on an API error halfway through the catalog | What was written before the break stays in the catalog; the rest didn't arrive | Run the template again — it starts from the first page and finds the same cards (if a run breaks off) |
| The run created or overwrote the wrong cards | The template was run with the wrong settings | Find what was created with the “Source: name” filter; a run of the correct template restores what was overwritten (if the wrong data was imported) |
| Products sit in the “Products - emag” category and are not exported | The offer's category could not be determined; the service category is disabled | Move the products into your own categories, then delete the empty service category (service categories) |
| The price in Elbuz is lower than on the eMAG storefront | The eMAG API returns the price without VAT | Nothing — this is how it should be (what goes into the card) |
| Prices changed in Elbuz, but eMAG shows the old ones | Import only reads from eMAG | Create an export template of the “eMAG” type (sending prices back to eMAG) |
| An attribute labeled “#123” | The category's attribute directory did not respond | Nothing: the value is saved; only the label directory didn't respond (attributes) |
FAQ
What do I enter in the country field?
The marketplace code: ro (Romania), bg (Bulgaria) or hu (Hungary). If you sell in several countries, create a template for each (several countries).
Can I pull only orders from eMAG?
Yes. The template has separate “Products” and “Orders” checkboxes — turn on only “Orders”, and they will arrive by themselves every 5 minutes (scenario).
I corrected a price in Elbuz — will the next import change it back?
Yes. To keep only the price, set “Fixed Price” in the card; to keep the whole card unchanged, use “Do not update” (repeat run).
A product disappeared from eMAG. Will it be disabled in Elbuz automatically?
No. The card of a vanished offer stays active with the last price and stock; you remove it by hand (vanished offers).
I changed photos on eMAG — why does Elbuz show the old ones?
Photos and attributes are taken only when the card is created; a repeat run doesn't update them (what a run overwrites).
How many offers can I import at once?
There is no limit. eMAG sets the pace — no more than one request per 3 seconds (how long it takes).
Where it is and who has access
- Menu
- Directories → Operations → Data import → new template of the “eMAG” type
- Access right
- the “Import” window in “Group permissions”
- Have ready
- the eMAG API login and password, and the Elbuz in your account's whitelist
One template is one connection to one eMAG country. No file is needed: this is an API source.
1
eMAG API login2
eMAG API password3
Marketplace (ro/bg/hu)- eMAG API login — the login from your eMAG seller account.
- eMAG API password — the API password from the same account; it is shown masked.
- Marketplace — enter ro (Romania), bg (Bulgaria) or hu (Hungary).
Related topics
- If you need the general import mechanics — schedule, breaks, service categories: data import overview.
- If you're just starting and looking for what to do after import: where to start and where to go next.
- If you need to connect another API source: catalog import via API.
- If you also sell in Poland: connecting Allegro.
