Integrating a Dropshipping Wholesaler with Allegro Step by Step

Importing from a wholesaler via XML or API, EAN codes, auto-listing and pricing rules decide whether dropshipping on Allegro makes money or generates complaints. Here's how to set up the integration on the technical side.

Integrating a dropshipping wholesaler with Allegro — what it really involves

In short: integrating a dropshipping wholesaler with Allegro is an automated flow of data between the supplier’s catalog and your seller account. From the wholesaler you download an XML/CSV file or connect via API, and the system on your side turns that data into Allegro listings, keeps an eye on stock levels, updates prices and — after a sale — passes the order to the supplier for fulfillment. You never touch the goods; you manage the data.

It sounds simple, but the whole model rests on four pillars that are easy to break: correct data import, EAN (GTIN) codes, pricing rules and synchronization frequency. If any one of them fails, the result is the same — invisible listings, selling at a loss, or orders that can’t be fulfilled. This article breaks each pillar down to its fundamentals, with the specifics usually missing from “set up an account and start selling” guides.

Data import: XML/CSV file or API — which to choose

Dropshipping wholesalers make product data available in two ways. The first is an XML or CSV file — a single URL where the supplier publishes the full catalog: names, descriptions, photos, wholesale prices, stock levels and (in a good file) EAN codes and attributes. The second is an API — an interface through which your system queries the wholesaler for specific data in near real time.

In practice both models do the same thing — they differ in how fresh the data is and how quickly they react when stock runs out. The table below shows when each makes sense.

The conclusion is simple: for slow-moving assortment, an XML file is entirely sufficient. With fast-selling goods and many sellers sourcing from the same wholesaler, a difference of a few dozen minutes in a stock update can mean an order for a product that’s already gone. Whatever the method, one question to the supplier is key: how often and in what way they update stock — because an integration is only as good as the data it receives as input.

Before you connect a file — check its quality

A bad source file is the most common — and at the same time the most overlooked — cause of problems. Before you run a bulk import, review a few records and ask yourself:

• Does every product have an EAN code, and is it a real GTIN rather than the wholesaler’s internal catalog number?
• Do variants (size, color) have separate EAN codes, or a single EAN for the whole family?
• Does the file include the wholesale price (net) and, separately, a suggested retail price?
• Is the “stock” field a number of units, or just an “in stock/out of stock” status?
• Are the photos links to downloadable files, not thumbnails blocked by hotlink protection?

If the file doesn’t answer yes to these questions, no integration will fix it — it will only carry the errors over to Allegro more faithfully.

EAN (GTIN) codes — the most common source of blocked listings

Since July 1, 2024, Allegro has required 100% of listings in most categories to be linked to the Product Catalog (so-called productization). A listing that isn’t linked to the catalog stops being visible to buyers in search results and, over time, is automatically closed. In practice, it’s the EAN (GTIN) code that serves as the key linking your listing to the product card in the catalog — which is why EAN errors are the number-one problem in dropshipping.

Allegro treats the EAN (GTIN) as “a unique, globally recognizable product number consisting of 8 to 14 digits.” Among other things, the platform verifies whether the first digits of the number (the so-called prefix) comply with the requirements of GS1 — the only entity authorized to assign GTIN codes. If you provide a nonexistent number, a reserved one, or an internal distribution number, Allegro will block the listing, relisting or editing of the offer and show why the value is incorrect.

Three typical EAN errors in wholesaler imports

It’s worth remembering that not every category requires an EAN. GTIN codes are mandatory in roughly half of categories (approximately — always check the current list in Allegro Help), mainly for brand-new products. Exempt categories tend to include handmade goods, antiques, used or personalized products, which by their nature don’t have a factory number. In dropshipping, however, almost the entire assortment is new and branded, so in effect an EAN becomes a requirement.

A practical rule: an EAN isn’t a formality but the key to automation. A single wrong number can generate an invisible listing, a mismatched product card and an order you can’t fulfill. Validate EANs before listing, not after the first complaint.

Auto-listing — how to list offers automatically and safely

Auto-listing is a feature that turns new products from the wholesaler’s file into Allegro listings right away, with the integrator pulling in attributes and assigning a product card from the catalog based on the EAN. When stock drops to zero, the listing is paused; once the supply is replenished, it’s resumed. It sounds like the holy grail of scaling, but without common-sense safeguards it can list several thousand weak offers in a quarter of an hour.

Before you turn on bulk listing, set up filters and rules:

• Availability filter — list only products with stock above a threshold (e.g., 3–5 units), so you don’t create listings for leftover stock.
• Margin filter — skip items where, after commission and shipping costs, the margin falls below a set minimum.
• Category mapping — check that the category from the wholesaler’s file maps to the right Allegro category; bad mapping means wrong attributes and rejections.
• Description quality control — remove links, the wholesaler’s contact details and any wording that breaches Allegro’s terms from descriptions.

A good practice is a pilot start: list a few dozen products first, verify how the product cards and attributes look, and only then open the integration to the whole catalog. The same automation logic comes in handy later on the fulfillment side — how to set it up, we describe in the article on e-commerce order automation.

Pricing rules — how to calculate margin and avoid selling at a loss

In dropshipping, the selling price is rarely a value entered by hand — more often it’s a rule applied to the wholesale price. And this is where the costliest mistake is made: calculating margin from the purchase price without accounting for Allegro’s commission and the shipping cost. The result is a seemingly profitable offer that actually loses money.

Allegro’s commission depends on the category and runs roughly from a few to a dozen-odd percent (in practice most often in the range of about 2.5–20%; check the exact rate for your category in Allegro’s price list). On top of that come shipping costs and any promotional packages. That’s why you should always build your pricing rule from a minimum price — below which you won’t go, even if the competition keeps driving prices down.

Only the sum of these components sets the threshold below which the pricing rule can’t drop. Commissions can be surprising — if you want to calculate them precisely, take a look at our breakdown of Allegro commissions in 2026.

Repricing and Allegro pricing rules

Allegro provides its own mechanism for automatic price management. Available options include the “Lowest price on Allegro” rule (which matches your price to the currently lowest offer for a given product, checked hourly), the “Top offer” rule and the “Price converter” for foreign markets, based on European Central Bank exchange rates. You can create up to 20 of your own rules based on the default types.

Every “lowest price” rule requires you to provide a price range — a minimum and a maximum. It’s the lower bound that protects you from selling at a loss when other sellers sourcing from the same wholesaler start a price war. The rules don’t apply to offers covered by campaigns that affect price (e.g., AlleObniżka, Allegro Ceny, Smart! Week), which is worth remembering when planning promotions. In addition, as of February 18, 2026, the automatic Price converter mechanism launches fully automatically for sellers who have this rule enabled (it’s worth confirming the details and subscription terms in Allegro Help).

MAP and legal limits on imposing prices

Some wholesalers expect you to maintain a minimum advertised price (MAP). In Poland, using MAP within a manufacturer–distributor agreement is permissible, but it’s subject to competition law. A manufacturer cannot impose a fixed resale price or forbid you from offering discounts — such arrangements may be deemed an unlawful price-fixing agreement (RPM). A suggested price and a minimum advertised price are something different from a ban on repricing. If a wholesaler forces a fixed price under threat of cutting off supply, it’s worth consulting on it rather than mindlessly entering it into a rule.

Stock and price synchronization — the frequency that saves your reputation

The most dangerous scenario in dropshipping on Allegro is overselling — selling a product the wholesaler no longer has. It ends with a canceled order, a lower seller rating and, if it recurs, account restrictions. The only real defense is frequent and reliable stock synchronization.

Modern integrations refresh stock roughly every 15–60 minutes, and for high-turnover assortment it’s worth aiming for the higher frequency. Check three things: how often the integrator pulls data from the wholesaler, how quickly it closes a listing once stock drops to zero, and what happens when the wholesaler’s file temporarily doesn’t respond (a good system doesn’t “zero out” all stock in that case). We’ve described the mechanics and pitfalls in more detail in our articles on warehouse stock synchronization and on how to avoid overselling.

When you sell from a single wholesaler on both Allegro and your own store at the same time, another layer comes in: the same stock has to decrease across both channels. That’s already a matter of consistency across the whole warehouse in a multichannel model — more in our guide to Allegro integration and on connecting Allegro with a warehouse.

Wholesaler → Allegro integration rollout checklist

Before you open the integration to the full catalog, go through this list:

1. Confirm with the wholesaler the method and frequency of data updates (XML/CSV vs API).
2. Verify the file’s quality: EANs, variants, net prices, real stock numbers, downloadable photos.
3. Check which of your categories require an EAN (GTIN) and whether every product has a correct, unique number.
4. Map the wholesaler’s categories to Allegro categories and verify the required attributes.
5. Set the pricing rule from a minimum price: wholesale price + commission + shipping + margin + returns buffer.
6. Configure the auto-listing filters (stock threshold, minimum margin, description control).
7. Set stock synchronization as often as the wholesaler allows, and safeguard the behavior when the file is missing.
8. Run a pilot on a few dozen products, check the cards and attributes, and only then scale.

As the model matures, it’s worth thinking of the integration as a single panel that ties together the wholesaler, the marketplace, stock and order fulfillment — that’s exactly the direction next-generation tools are heading, like the Nimo integrator in the works. But even the best tool won’t replace order in your source data: it’s the quality of the wholesaler’s file that determines whether automation earns money or just replicates errors faster.

Frequently asked questions

Do I need my own EAN codes for dropshipping on Allegro?

You don’t assign them yourself — correct EAN (GTIN) codes are supplied by the manufacturer or wholesaler, and the only organization authorized to issue them is GS1. Your job is to make sure that in the import file every product (and, where there are variants, every variant) has a correct, unique number. In categories covered by productization, without this the listing won’t be linked to the catalog and will become invisible.

How often should stock levels update?

The more often, the lower the risk of overselling. Roughly speaking, modern integrations refresh stock every 15–60 minutes; for fast-rotating goods, aim for the higher frequency. It’s also crucial how quickly the integrator closes a listing after stock drops to zero and how it behaves when the wholesaler’s file temporarily doesn’t respond.

Can a wholesaler impose a fixed selling price on me on Allegro?

It can suggest a price and set a minimum advertised price (MAP), but under Polish competition law it cannot forbid you from offering discounts or impose a fixed resale price — such an agreement may be deemed unlawful. If a supplier forces a fixed price under threat of cutting off supply, it’s worth verifying it legally.

XML file or API — which is better for dropshipping?

For slow-moving assortment, an XML/CSV file is enough. With fast-selling goods and many sellers sourcing from the same wholesaler, an API usually provides fresher data and a lower risk of stock drift. Ultimately, though, what matters is how often the wholesaler itself updates the data at the source.

Why are my imported listings invisible on Allegro?

The most common cause is the lack of a link to the Product Catalog — in practice, a wrong or missing EAN (GTIN). Since July 1, 2024, listings in most categories must be linked to the catalog, or they disappear from results and are eventually closed. Check that the EAN is correct, unique and consistent with the GS1 prefix.