Connecting Allegro to PrestaShop, Shoper and Shopify is possible on all three, but each does it a different way - and the route you pick decides whether your stock levels stay honest. Allegro is Poland’s dominant marketplace, the local equivalent of eBay or Amazon in reach, so for most Polish stores it is the second sales channel by default. Integrating it with your store means offers, stock, prices and orders flowing automatically between your marketplace seller account and the store, instead of being retyped by hand. In PrestaShop this is done by a module from the marketplace or by a middleware system, because the platform ships no Allegro integration of its own. In Shoper the connection is part of the platform’s offer and you switch it on from the panel. In Shopify there is almost always a middleware system standing between the store and Allegro. A fourth route - your own integration on the Allegro API - comes into play when none of the off-the-shelf options match how you actually work.
Below: what each route gives you, how it looks on PrestaShop, Shoper and Shopify, and where these builds usually fall apart.
What “connecting the marketplace to the store” actually means
The integration is not one feature but four separate data streams - and you can switch on just some of them.
- Listing offers - products from the store go up on the marketplace with the description, images and attributes each category requires
- Stock sync - a sale in one channel reduces availability in the other, so you do not sell the last unit twice
- Prices - the marketplace price calculated separately, usually with a markup covering commission
- Orders - whatever someone buys on the marketplace lands in the store with shipping and invoicing details
Point two causes the most pain, point one takes the most work. Pulling orders in is the simplest thing to launch and I often start there - packing then happens from one place.
Three routes - which to choose
The choice depends on how many products you have and how unusual your warehouse logic is.
| Route | Who it fits | What it gives | Watch out for |
|---|---|---|---|
| Built into the platform | Up to a few hundred simple products, one warehouse | Fastest start, everything in one panel | Scope fixed by the vendor, little flexibility |
| Plugin or module | Stores with category quirks of their own | More control over mapping, cheap to start | Module quality varies, and you own the update burden |
| Middleware system | Several channels at once, couriers, warehouse | One dashboard for marketplace, store, couriers and documents | Subscription that grows with order volume, data outside the store |
| Custom API integration | Unusual logic: bundles, made-to-order, ERP | Does exactly what it is meant to do | Higher start cost, needs someone to maintain it |
Default recommendation: if you sell in more than two channels or ship dozens of parcels a day, start with a middleware system. If the marketplace is just an add-on to a store that stays your main channel, a plugin or the platform feature is enough. The middleware systems themselves I compared in the piece on Baselinker alternatives.
Allegro with PrestaShop
PrestaShop ships no marketplace integration, so the connection is always a module or a middleware system. Open source is an advantage, but it also means the quality of the solution depends on what you buy.
You have three realistic options:
- A module from the PrestaShop marketplace - bought once, updates usually included for a year, then a renewal fee. Module pricing changes and differs between vendors, so check at the source
- A middleware system with a ready-made connector - a subscription, but no worrying about compatibility with the next store release
- Your own connection to the Allegro API - when you have unusual variants, bundles or separate warehouses per channel
The biggest trap on PrestaShop is attribute combinations. Allegro has its own variant model and its own set of mandatory parameters in every category, while PrestaShop describes products its own way. With clothing or footwear, mapping sizes and colours takes real time - far more than switching the module on. Second trap: store upgrades, after which a module can simply stop working, which is why I plan the integration together with the update and testing rhythm rather than separately.
Allegro with Shoper
Shoper (a hosted Polish store platform, similar in model to Shopify) is the most out-of-the-box of the three - marketplace integration is part of the platform’s offer, and extra connectors sit in its app store. The start is fast: connect the seller account, pick products, set the listing template and go. Price depends on the plan and on whether the integration is included or an add-on - that changes, so check the current price list with the operator.
You pay for the convenience in scope. A built-in integration does what the vendor planned and not one step further. When you need a rule like “on the marketplace show only products from the main warehouse, priced with a commission markup, but never above the manufacturer’s list price”, you either find a third-party app or move to a middleware system. That is one of the more common reasons sellers later consider moving from Shoper to WooCommerce: not because Shoper is bad, but because unusual logic hits the ceiling fast.
Allegro with Shopify
Shopify is a global platform and Allegro is not a priority for it, so the natural route is a middleware system. Apps aimed at the Polish market do exist in the App Store, but there are fewer of them and you need to check whether the author is genuinely still developing them.
What that changes in practice:
- Marketplace orders land in Shopify as normal orders, but you settle numbering and invoicing data upfront, because Shopify has no Polish invoicing built in
- Stock levels must live in a single source of truth - either Shopify or the middleware; two sources of truth guarantee overselling
- Invoices and accounting get added separately; selling to businesses also brings in KSeF, Poland’s mandatory e-invoicing system, which now applies to every company
Five things that break these builds
Most common first.
- Treating sync delay as zero - data moves in cycles, not instantly. On last units keep a buffer instead of hoping stock updates in time
- Price with no commission markup - the marketplace takes a category-dependent commission, so a price copied straight from the store can eat the margin. The pricing rule has to exist before the first listing
- Category parameters filled in carelessly - the marketplace demands specific fields, and gaps push your listing down. A one-time job, done at the mapping stage
- Returns flowing one way only - orders come into the store, but a marketplace return never puts the unit back into stock. A month later the system disagrees with the shelf
- No single owner of product data - when descriptions get fixed sometimes in the store and sometimes on the marketplace, one day an export overwrites the manual edits
What it costs and how long it takes
The cost splits into four items and only some of them are one-off.
| Item | Type | Notes |
|---|---|---|
| Module, app or licence | One-off or yearly | Vendor pricing changes often - check at the source |
| Middleware subscription | Monthly | Grows with order volume and channel count |
| Build and mapping | One-off | The main cost is categories, parameters and variants, not the connection |
| Maintenance | Monthly or ad hoc | Changes to the marketplace API and categories happen without asking you |
I bill store work fixed-bid, usually 5,000-10,000 PLN net per project, with the number in writing before we start. Keeping these connections alive falls under ongoing support - Basic 1,000, Pro 2,000, Premium 3,500 PLN net per month, depending on how many systems need watching.
Timeline: a simple order hookup is days. Full listing with category and variant mapping is weeks, and most of that is data work, not code.
When to move from off-the-shelf to a custom integration
When you are topping up the off-the-shelf tool with human labour. Three signals: someone fixes something by hand every day after the sync, subscriptions have passed the cost of doing it once on your own terms, or your way of selling (bundles, made-to-order, per-customer pricing) does not fit the ready-made model.
Allegro publishes a REST API with a separate sandbox environment, so an integration like this can be built and tested without risking live sales. I usually wire it into the rest of the back office at the same time - stock, accounting and the e-invoicing flow - because separate integrations built one after another cost more than one designed as a whole.
How this works with me
I start with a free diagnosis: I look at your store, the product count, how variants are described and how you handle marketplace orders today. Out of that comes a recommendation for one route - not three to choose from - plus what can launch immediately and what needs the data tidied first.
For larger work you get a fixed bid in writing before we start: scope, price, deadline. If the diagnosis shows an off-the-shelf tool on a subscription is enough for you, I will say so plainly - that is also a result. I run these builds as part of building and growing stores.
FAQ
Can I integrate the marketplace with PrestaShop without a plugin? Yes, through a middleware system or your own integration on the Allegro API. A plugin is fastest but not the only route - with an unusual warehouse or several channels, an external solution is often more stable than a module inside the store.
Will stock levels update instantly? No, data moves in cycles - from a few to a dozen or so minutes depending on the tool and the product count. That is why you set a buffer on last units instead of assuming stock updates before the next order.
What is cheaper: a subscription or a custom integration? At a few dozen orders a month, almost always the subscription. A custom integration pays off when tool fees grow with turnover and someone in the company is fixing data by hand every day anyway.
Does connecting the marketplace to Shopify make sense? It does, but you plan invoicing and a single source of truth for stock upfront, because Shopify is not tailored to the Polish market. Most often a middleware system sits between them, handling couriers and sales documents too.
Running a store where something does not work the way it should? I build and rebuild WooCommerce stores - from a single fix to reworking the whole sales flow. Tell me what you are dealing with and I will send back a scope and a price.