Website and marketplaces department one of the departments in your AI company
Allegro integration connects your Allegro account to Elbuz: offers come in with category parameters and EAN, prices and stock go back in batches, and orders arrive with payment and delivery details.
Six jobs that otherwise happen by hand in the Allegro seller account.
Offers come in with the full category path, parameters, EAN and manufacturer. A card stays linked to its offer even after you rename it on Allegro, so repeated runs create no duplicates. Product data is kept once in the product catalog (PIM) and goes to every channel.
Your categories are mapped once to the Allegro category tree, and attributes to its required fields. A product that misses a required field is shown before export, not after a rejection. Category parameters are mapped once in the marketplace category window, and your cards carry them into Allegro offers.
Each export template takes its own price or calculates it by formula — for example your base price plus a markup that covers the Allegro commission. The catalog and your website keep their own prices. Markup rules.
Price and stock go back to Allegro through an export template of the Allegro type, 25 offers per request, on its own schedule. Stock comes from your warehouses and supplier price lists.
Allegro orders arrive as customer orders and keep updating with payment and delivery. Buyer messages from Allegro can be answered from the Elbuz helpdesk. 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. Shipping labels for Poland — InPost, DHL Parcel Poland and GLS — are created on your own carrier contract straight from the order.
Allegro 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 Allegro and change over time. Checked against the official pages on 30 October 2026: Allegro — registration for non-Polish companies.
It keeps your Allegro offers, prices, stock and orders in sync with one catalog. In Elbuz offers come in with parameters and EAN, prices and stock go back in batches, and orders arrive with payment and delivery and keep updating.
Yes, as a business. Allegro has a registration path for companies from other EEA countries and a separate one for sellers from outside the EEA; documents must be recent and in English or translated.
No. The card is linked to the Allegro offer itself, so it is found again after any rename and simply updated.
Create the InPost, DHL Parcel Poland or GLS label from the order in Elbuz on your own carrier contract.
Yes. Allegro messages come into the helpdesk next to email and chat, and you reply from there.
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.
