Elbuz pulls offers and orders from your Allegro.pl seller account via the API into your base catalog: prices, stock and assortment for all channels in one place.
When you need this:
- Your catalog is on Allegro — offers arrive as cards with the full category path, parameters, EAN, manufacturer and photos.
- You write descriptions and prices — a repeat run keeps your description; “Fixed Price” locks the price.
- You process orders in Elbuz — each becomes a “Customer order” document.
- You calculate prices in Elbuz — an export template sends price and stock back to Allegro.
Where to start: create an “Allegro.pl” template and link the store with a code.
What the Allegro connection does
- App link by code — access renews itself, no token to enter.
- Offer import — with the full category path, parameters, and manufacturer.
- Updates without duplicates — the card is found by the offer link, even after the offer is renamed on Allegro.
- Orders — as a “Customer order” document, with payment and shipping updates.
- Export back — price and stock through the same link.
What you need from Allegro
The main method is the app link by code. With it, the token is issued and renewed automatically: Allegro access is short-lived, and renewing it by hand is a chore. The token field stays empty.
The second method is a manual access token, for development or a test environment. A manual Allegro token lives about 12 hours, so it is no good for everyday work.
Access is taken from the app link only when the “Allegro access token (not needed when connected via the app)” field is empty. A filled field takes priority: a manual token left in the form keeps getting in the way even after linking.
How to connect, step by step
- Create a template of the “Allegro.pl” type. “Active” and “Orders” are already on in a new template: 5 minutes after linking, Elbuz starts picking up orders. Elbuz maps marketplace statuses to yours automatically, by name; what arrived and how it was mapped is shown in the template's “Order statuses” window. Want to check first? Untick “Orders”.
- Click “Connect”, sign in to the marketplace and approve access.
- Enter the short code shown into the “Link code” field and click “Link store”.
- Click “Test connection” to confirm that access works.
- In the “Select data to import” card, turn on products, then save and run.
There is one link per Allegro account: connect it in the import template and the export template works with the same access, and vice versa. The “Connect” button and the “Link code” field are in both templates.
What goes into the product card
| Allegro data | Elbuz card field |
|---|---|
| offer title | Product name |
| selling price | Price |
| available stock | Quantity |
seller's own code (external id) | SKU |
publication status ACTIVE | Card activity |
| offer category | Category — with the full path |
| offer parameters | Attributes |
| “EAN (GTIN)” parameter | Barcode (digits only) |
| “Marka” / “Producent” parameter | Manufacturer |
| offer images | Images — when the “Photo” checkbox is on |
| offer ID | Link key |
The description and old price do not come from Allegro. Allegro stores descriptions in its own block format: fill the description in the catalog or pull it from another source.
Barcode, manufacturer and variants
On Allegro, the barcode and manufacturer are ordinary offer parameters. Elbuz finds them by name: “EAN” or “GTIN” becomes the barcode (digits only), “Marka”, “Producent” or “Brand” the manufacturer. An unfilled parameter leaves the field empty. When an offer has no parameters, Elbuz takes them from the Allegro product card the offer is linked to.
Allegro has no variants in the usual sense: every size or color is a separate offer, so in Elbuz they arrive as separate cards, not as a variant family.
Categories
Allegro returns only a category code, so Elbuz queries the category directory and walks up the tree (no more than twelve levels) to build the full path. Branches already fetched are not requested again during the run.
If the category cannot be determined, the product goes into the service category “Products - allegro”, which is disabled and excluded from exports. Move the products into your own sections; to remove the service category, see service categories and brands.
What a repeat run overwrites
Every run fetches all offers again, not just changed ones. Elbuz stores the offer ID as the template's link, and a repeat run of the same template finds the card by that link. If the template was deleted and created again, there is no link yet, and the run looks for the card by name.
- You renamed the card in Elbuz — the run finds it by the link and restores the Allegro name without warning.
- The offer was renamed on Allegro — the card stays the same and its name updates. A second card appears only when there is no link and the name no longer matches; the old one keeps its old figures.
| What the run does | Fields |
|---|---|
| Overwrites with a non-empty value from Allegro | name, price, SKU, barcode, manufacturer |
| Always overwrites, even with zero | stock and activity |
| Leaves yours | description, old price, tags — Allegro does not return them |
| Does not touch | photos (new cards only), existing attributes, position in the category tree, page URL |
To lock a whole card, use the “Do not update” switch — in the product card, or via the “Do not update (flag)” column in the “Products” window for filtered rows. “Fixed Price” protects only the price.
“Do not update” protects the card's fields, but not the link. If you delete the Allegro template and create it again, the new run looks for cards by name: offers renamed on Allegro become second cards, whatever flags the old ones have.
- Action or result
- Decision: the path depends on the answer
Two sources with the same IDs
The Allegro template has no “Check uniqueness of records based on this import source” switch — file templates and the tunnel have it. Nor is it needed: the offer ID is this template's own link, so another source cannot find the card by it. Sources collide only by name: protect cards with “Do not update” or keep names different.
An offer disappeared from Allegro or was unpublished
The card of an offer that was missing from the run stays as it was — with the last price and stock, and no line in the log. The Allegro form has no checkbox for deleting missing items, so remove discontinued items by hand.
For an offer that arrived but is not on sale: ACTIVE means the card is enabled, any other status means it is disabled. Stock is overwritten with what Allegro returned: zero gives “Out of stock”, more than zero gives “In stock”.
Turning off “Activity” by hand is mostly pointless: the next run restores it while the offer is ACTIVE; only “Do not update” keeps it off. Disabling deletes nothing and does not control exports: products are selected by the “Export to file (to website)” flag, so a disabled card can still send prices to Allegro. Elbuz's own storefront hides disabled products.
How Allegro orders arrive
Allegro returns orders as checkout forms; the “Orders” checkbox turns them on. Each form becomes an unposted “Customer order” document: stock and reservations do not change until the document is posted.
- The source number is the form ID; on a repeat run the document is found by it, so there are no duplicates.
- Currency comes from the order total, PLN by default.
- The buyer is created as a contact by Allegro login; the phone comes from the shipping address, or from the profile if the address has none.
- Lines look for cards by offer ID, then by name; if nothing is found, a new card goes into the disabled category “Products - allegro - ‹template name›”.
The “Import orders from date” field in the “Advanced” section decides what the run does:
- The field is empty — the run fetches orders in sequence and only adds new ones.
- A date is set (Elbuz sets it itself from the last imported order) — the run takes what changed since that date and updates existing documents: payment, shipping, payment and shipping methods.
Your processing status changes only when the status has changed on Allegro's side. Posted documents are never updated by the run.
1
Import orders from date- Import orders from date (YYYY-MM-DD) — orders are loaded starting from this date.
- Action or result
- Decision: the path depends on the answer
Allegro returns no more than 10,000 orders per pass (in pages of 100). When it reaches this limit, the run stops; the next one starts from the date of the last imported order.
How prices, stock and new products go to Allegro
Import fills the base catalog and stops there. To send prices and stock back to Allegro, create a separate template of the “Allegro.pl” type in the “Data export” window. It updates price and stock through the same offer link, in batches of 25 items per request, and has its own schedule.
Old figures on Allegro — check the export template rather than rerunning the import.
How to list new products on Allegro
With the “Publish new products” checkbox, the export template lists products that do not have an Allegro offer yet:
| Product | What Elbuz creates | What is required |
|---|---|---|
| with a barcode that exists in the Allegro catalog | an offer for the existing Allegro catalog product | the product's EAN |
| not in the Allegro catalog | a new product card in an Allegro category | a category mapped to an Allegro category, and the category's required parameters — from product attributes with the same name |
Any publishing needs sale conditions in the Allegro account: shipping (rates), returns and warranty. Otherwise the log says “Allegro: publishing new offers is not possible — the Allegro account has no sale conditions…”. Missing parameters give the line “Allegro: “‹name›” — required category parameters are missing: ‹list›”; a published offer gives “Allegro: new offer published “‹name›” (ID ‹number›)”.
Build the Allegro commission into the price with the price field formula of the export template; the Allegro commission calculator helps you work it out.
Scheduled updates
Elbuz picks up orders itself every 5 minutes if “Orders” is ticked in the template and there is access (a code link or a token). It's the shared “Marketplace orders” task in the “Job schedule” window, where the interval is set. This pass doesn't import the catalog, and orders also taken by the template's own schedule aren't duplicated.
The catalog is updated by the template's own schedule — the “Schedule setup” button in the “Related settings” card. Run it rarely, for example at night: while the catalog is running, the orders pass is skipped until the next one.
At the end of a run, Elbuz applies markup rules to added products and recalculates formula fields (the line “Updating values based on formulas”); the last log line is “Data import completed!”. General schedule rules: data import overview.
How many offers one pass handles
There is no cap on the number of offers. Offers are fetched in pages of 1,000, and each one gets a separate request for the full card with parameters and photos — a catalog of a thousand offers means over a thousand requests. Products are written to the catalog in batches of 500.
The log has a line for each page (“Allegro: catalog page N, offers received: M”) and the summary “Allegro: catalog imported, offers: N”. The run lives in the Operations Center, so you can close the template window.
- Action or result
- Decision: the path depends on the answer
If a run breaks off or is stopped
- An error on a catalog page breaks off the import: a red line “Allegro: API error —” with the refusal text, and the remaining pages are not fetched.
- An error on one offer's full card does not stop the run: the offer is created from the list data — without attributes or photos, and with no line in the log.
- “Too many requests” — up to three retries with pauses of 3, 6 and 9 seconds, then “HTTP 429: retry limit reached”.
- “Stop” in the Operations Center takes effect at a page boundary: the run finishes reading and writing the current page (up to 1,000 offers or 100 checkout forms) and performs the final step.
What was written in batches stays in the catalog; a retry starts from the first page and creates no duplicates. General rules: if a run breaks off.
Scenarios
1
Products2
Photo3
Orders- Products — import offers into the product catalog.
- Photo — import product photos.
- Orders — import Allegro orders as documents.
Allegro looks at exactly three checkboxes in the “Select data to import” card: “Products”, “Photo” and “Orders”. Categories, manufacturers and attributes come along with the offers.
Keep the Allegro catalog in Elbuz up to date without a manual token
What to turn on. The app link by code, with the token field empty; “Products” and, for images, “Photo”; then a schedule.
What you get. New offers become cards with photos and attributes; existing ones get updated price, stock and activity. New photos do not reach existing cards, and offers removed from Allegro are not disabled.
Write your own descriptions and prices, take stock and status from Allegro
What to turn on. For the description, nothing. For the price, “Fixed Price” in the cards; to keep the run off a card entirely, “Do not update”.
What you get. The description, old price and tags stay yours. With “Fixed Price” the price holds, while stock and activity update.
Take only orders from Allegro
What to turn on. “Orders” on, “Products” off; no template schedule is needed, orders arrive on their own every 5 minutes.
What you get. Each checkout form becomes an unposted “Customer order”. Without the catalog, lines look for cards by name and, if none is found, create new ones in the disabled category “Products - allegro - ‹template name›”. After the first run a date appears, and from then on payment and shipping update in unposted documents.
You ran the wrong template — stop it
What to click. “Stop” in the Operations Center.
What you get. The run finishes reading the current page (up to 1,000 offers), writes it and does not take the next one. What was written stays in the cards — to clean it up, see the troubleshooting table.
What to do when Allegro does not return data
| What you see | Why | What to do |
|---|---|---|
| Updates stopped going through after a few hours | The manual access token expired — it lives about 12 hours | Connect with the app link and clear the token field (what you need from Allegro) |
| Access still does not work after linking | An old manual token is left in the token field — it takes priority | Clear the “Allegro access token” field and click “Test connection” |
| “Allegro: API error —” and a refusal text | Allegro refused a catalog page; most often the manual token has expired | Fix the access and run again — a retry is safe (run breaking off) |
| A new card without attributes or photos | The request for the offer's full card failed, so it was created from the list data | A repeat run will not add attributes — fill them in the card (run breaking off) |
| The wrong data was imported | Import has no rollback | Filter what was created by “Source: name” and “Source: code” = allegro, and what was overwritten by “Update date” (if the wrong data was imported) |
| Products in the “Products - allegro” category are not exported | The offer's category could not be determined; the service category is disabled | Move the products into your own sections (categories) |
| Allegro shows old prices and stock | Import only reads from Allegro | Check the “Allegro.pl” export template and its schedule (sending prices back) |
| Second cards appeared after the template was recreated | The new template cannot see the old template's links and searches by name | Do not delete a working template; remove the duplicates by filtering on “Source: name” (repeat run) |
FAQ
Where do I get an Allegro token?
With a normal connection, nowhere: the app link by code issues access and renews it itself. A manual token is only needed for testing (what you need).
Will a repeat run overwrite the description I wrote?
No. Allegro does not return descriptions, and an empty value is never written over a filled one (repeat run).
Will a repeat import duplicate offers?
No, the card is found by the offer link, even after a rename. A duplicate is possible only after the template is deleted and recreated (repeat run).
What happens to the card if an offer is taken off sale?
If the offer is not ACTIVE, the card is disabled. If the offer disappeared from the list, the card stays with the old price and stock (missing offer).
Why did sizes and colors arrive as separate cards?
On Allegro every variant is a separate offer; there are no families (variants).
Two sources return products with the same IDs and overwrite each other — what do I do?
In file templates and the tunnel, turn on “Check uniqueness of records based on this import source”. Another source can touch Allegro cards only through a matching name — protect them with “Do not update” (same IDs).
Where it is and who has access
- Menu
- Directories → Operations → Data import → new template of the “Allegro.pl” type
- Other entry points
- Directories → Operations → Data export — a template for prices and stock
- Access right
- the “Import” window in “Group permissions”
- Have ready
- sign-in to your Allegro seller account to approve access
One template is one connection to one Allegro seller account. No file is needed.
1
Allegro access token2
Test connection- Allegro access token — paste a token here; not needed when you connect through the app.
- Test connection — checks the connection (do not click it while only reviewing the form).
Related topics
- If you need the general import mechanics — schedule, breaks, service categories: data import overview.
- If you are just starting and want the order of steps after import: where to start and where to go next.
- If orders from Poland also come from Ceneo: Ceneo orders.
- If you also sell on Kaufland: connecting Kaufland.
- If you are deciding what Elbuz gives an Allegro seller: Allegro integration.
