Shopify-Allegro Integration: Connectors and Sync

Shopify works great as a store, but it has no native connection to Allegro. See how to link the two platforms, how two-way synchronization works, and what it really costs.

Does Shopify have a native Allegro integration?

The short answer: no. Shopify is a global platform, while Allegro is a marketplace local to the Polish market — the official Shopify App Store has no “Allegro” app developed by Allegro itself, and there is no Allegro channel in the Shopify Markets module. In practice, this means that a Shopify-Allegro integration always requires an intermediate layer: a ready-made integrator, a connector app from a third-party provider, or your own connection via the Allegro REST API.

Before you choose a tool, answer one question for yourself: where should the “source of truth” about products, stock, and orders live? Everything else depends on that decision — how you map your assortment, the direction of synchronization, and how much manual work you actually take off your team. Below we walk through all the options, the mechanics of two-way synchronization, the technical side of the Allegro REST API, and approximate costs.

How to connect Shopify with Allegro – three routes

There are essentially three ways to link the two platforms. They differ in cost, implementation time, and flexibility.

1. A ready-made multichannel integrator (SaaS)

The most common choice among Polish sellers. Tools like Apilo, Sellasist, BaseLinker, or Base.com act as a central hub: you connect your Allegro account and your Shopify store to them, and the system synchronizes listings, stock, and orders across channels. Advantage: fast setup (hours, not weeks) and ready-made features — automations, courier label printing, invoicing. Downside: a monthly subscription and the fact that the data model is dictated by the provider. If you’re still choosing a tool, it’s worth comparing several providers on their Allegro and Shopify support, pricing, and extra features (couriers, invoices, automations).

2. A connector app from the Shopify App Store

In the App Store you’ll find apps built by third-party developers that add an Allegro channel to the Shopify admin. They tend to be lighter and cheaper than a full integrator, but usually cover a narrow scope (e.g., stock sync alone or pulling in orders). Always check three things: whether they support two-way synchronization, whether they handle product variants correctly, and how they map your assortment (by SKU or EAN). Also note how quickly the provider responds to changes in the Allegro REST API — their vigilance is what determines whether the integration keeps working after an update on the marketplace’s side.

3. Your own integration via the Allegro REST API

If you have a development team and unusual processes, you can build your own connector on top of the Allegro REST API and the Shopify Admin API. You gain full control over the logic, but you take on the maintenance: OAuth authorization, handling request limits, queuing, retrying failed calls, and monitoring. This is the most expensive route when measured in time — though without a recurring subscription fee for the integration itself.

What two-way synchronization actually is

“Two-way” means that data flows in both directions, not just from one system to the other. This is crucial in multichannel selling, because the same item leaves your warehouse regardless of whether the customer bought it on Allegro or in your Shopify store. Without instant stock updates, it’s easy to end up overselling — selling a product you no longer physically have. On Allegro, that ends in a cancellation, a negative review, and a drop in your seller rating.

You’ll find more about the mechanics themselves in our overview of stock synchronization. The principle is simple: the shorter the update interval and the more reliable the product mapping, the fewer fires you’ll have to put out. Be aware that some connectors sync stock on an interval (e.g., every few minutes) rather than in real time — with fast-moving popular goods, a stock buffer can save you from overselling.

Who is the “source of truth” for inventory

Before implementation, settle on the architecture, because changing it later without chaos is hard. In practice, you’ll encounter three models:

• Shopify as master. You maintain stock in Shopify, and the integrator “distributes” it out to Allegro. Good when Shopify is your main channel and new products are added there.
• Integrator/hub as master. Inventory lives in the intermediary tool, which levels stock across all channels at once. The most common arrangement in genuinely multichannel selling (Allegro + Shopify + others).
• Separate stock pools. A distinct pool of units for Allegro and for Shopify. Safe, but it wastes inventory and usually makes no sense outside of specific cases.

The foundation of each of these models is assortment mapping. Products are matched between systems by a unique SKU or EAN code — if these identifiers don’t line up, synchronization will attach stock to the wrong listing. A separate trap is variants: in Shopify a single product has many variants (size, color), whereas on Allegro each listing is usually a separate entity, so the connector has to split variants into listings correctly and maintain the link between them. We describe this same problem in more detail in our piece on integrating Allegro with your warehouse.

A practical rule: before you connect anything, tidy up your SKU/EAN codes and make sure they’re consistent in Shopify and in your Allegro listings. 80% of synchronization problems are mapping problems, not problems with the tool itself.

It’s worth adding that the market for tools in this class is growing — new Polish multichannel panels are also emerging (including Nimo, being built for 2026), which are meant to tie together Shopify, Allegro, couriers, and invoicing in one place. Whichever provider you choose, the evaluation criteria stay the same: two-way sync, mapping, variant handling, and update frequency.

Allegro REST API – what’s worth knowing technically

Even if you use a ready-made integrator, it’s worth understanding the constraints every tool operates within — because they explain why synchronization sometimes “thinks it over.” The values below come from the Allegro Developer Portal documentation; before building your own connector, check the current limits at the source, as they do get updated.

• Authorization: the Allegro REST API uses OAuth 2.0 (including the authorization code flow). The access token is valid for roughly 12 hours, while the refresh token lets you renew access for about 3 months — the integration has to be able to refresh tokens on its own.
• Rate limit: approximately 9000 requests per minute per Client ID. For bulk changes you have to queue operations rather than fire them synchronously — and respect the Retry-After header and apply exponential backoff.
• Listings: fetched in batches of up to 1000 listings per request; an account can hold up to about 20 000 draft listings.
• Orders: up to 100 items per request, where the sum of offset and limit cannot exceed 10 000 — large order histories have to be paged through by date.
• Matching and prices: the API allows, among other things, automatic matching of products to listings by EAN code and an automatic price change on Allegro when the price changes in your store — these options are worth enabling deliberately.

The practical takeaway: with a large assortment, what matters isn’t “whether it’s possible” but how the tool queues and prioritizes changes. A good integration updates the stock of bestsellers first, instead of blindly pushing the entire catalog on every change.

How much a Shopify-Allegro integration costs (approximately)

The total cost is made up of two or three layers: your Shopify subscription (you pay it for the store either way), the cost of the connector/integrator, and Allegro’s sales commissions. The amounts below are approximate, quoted net (23% VAT should be added to most of them), and subject to change — always verify the current pricing with the provider.

On top of that come Allegro’s commissions, which can be the largest single cost item on the whole bill — we break down how they actually add up in our article on Allegro commissions in 2026. The general rule for when an integrator pays off: it starts to make sense once you sell on at least two channels, or when order handling eats up a dozen-plus hours a month that could be automated.

KSeF and invoices when selling on Shopify + Allegro

When connecting channels, don’t forget about invoicing — in 2026 it’s not optional. The National e-Invoicing System (KSeF) is rolling out in stages: the obligation to issue e-invoices covers large companies (turnover above 200 million zl) roughly from February 1, 2026, and the remaining businesses from April 1, 2026. The obligation to receive invoices in KSeF applies to everyone as early as February 2026. A transition period is also provided for: until December 31, 2026 you can issue invoices outside KSeF if the monthly gross sales on such invoices does not exceed 10 000 zl, and the smallest companies come under the obligation from January 1, 2027. Confirm the dates at the source, as the details are still being refined.

For a Shopify + Allegro seller, this means that the system handling orders from both channels should be able to issue an invoice and send it to KSeF — otherwise you’ll have a separate, manual step. You’ll find practical tips for the marketplace in our guide KSeF and selling on Allegro.

Courier labels and order automation

Stock synchronization alone is only half the benefit. The real time savings appear when orders from Allegro and Shopify land in a single view, and the system assigns them statuses, generates labels, and notifies the customer on its own. With two channels the difference is tangible: instead of logging in separately to the Allegro panel and to Shopify, you handle everything from one place.

Two elements are worth configuring from the start. First, order automation — rules that change the status after payment, assign a shipping method based on the delivery option the buyer chose, and trigger invoice issuance — so the pile of manual operations shrinks to a minimum. Second, courier labels: instead of manually re-entering addresses into the courier’s panel, a good tool generates the label (e.g., InPost, DPD, DHL) straight from the order and sends the tracking number back to Allegro. Especially with InPost parcel lockers, which are popular on Allegro, automatically pulling the pickup point from the order eliminates frequent mistakes and shortens packing time.

All in all, it’s precisely these three layers — stock synchronization, status automation, and labels and invoices — that decide whether a Shopify-Allegro integration genuinely lightens your team’s load or merely moves the manual work somewhere else.

Step-by-step implementation – a checklist

1. Decide which system is the “source of truth” for inventory (Shopify, a hub, or separately).
2. Tidy up SKUs and EANs — consistent in Shopify and in your Allegro listings. This is the foundation of mapping.
3. Choose your route: a SaaS integrator, an App Store connector, or your own API.
4. Connect your Allegro account (OAuth authorization) and your Shopify store to the chosen tool.
5. Map products and variants; check a few items manually before switching things on en masse.
6. Set the synchronization directions: stock two-way, orders from Allegro into the panel, prices as needed.
7. Configure a stock buffer for fast-moving products to reduce the risk of overselling.
8. Connect couriers and labels, plus invoicing (KSeF), if the tool offers it.
9. Run a test on a narrow group of listings, verify stock and the first orders, and only then scale up.
10. Set up monitoring: what happens on API errors, what the queue looks like, and failure notifications.

The most common mistakes when connecting Shopify with Allegro

• Mismatched SKUs/EANs — stock lands on the wrong listing; the most common cause of “weird” synchronization.
• Ignoring variants — a single Shopify product with many sizes split incorrectly into Allegro listings.
• No stock buffer with fast turnover — overselling despite working synchronization.
• One-way synchronization where two-way is needed — stock drifts apart between channels.
• Skipping KSeF invoicing — issuing invoices manually undoes the time saved by automation.
• No test on a small sample — switching everything on across the whole catalog at once, and an avalanche of errors.

Frequently asked questions

Does Shopify have an official Allegro integration?

No. The Shopify App Store has no app developed by Allegro itself, nor an Allegro channel in Shopify Markets. The connection is made through a third-party integrator, an App Store connector, or your own integration with the Allegro REST API.

Does stock synchronization work in real time?

It depends on the tool. Some connectors update stock on an interval (e.g., every few minutes) rather than instantly. With fast turnover, it’s worth setting a stock buffer to avoid overselling in the window between updates.

What are products matched by between Shopify and Allegro?

Most often by a unique SKU or EAN code. If the identifiers aren’t consistent, synchronization will attach stock to the wrong listing. Tidying up SKU/EAN is the first step before any implementation.

How much does connecting Shopify with Allegro cost?

Approximately: the integrator subscription (e.g., from a few dozen to a few hundred zloty net per month, depending on the model and order volume) plus the Shopify subscription itself and Allegro’s commissions. Always check the specific rates with the provider, because pricing changes.

Do I have to issue invoices in KSeF when selling on Allegro through Shopify?

The obligation phases in during 2026 (receiving invoices from February, issuing from February/April depending on company size, with a transition period until the end of 2026). It’s good if the tool handling orders from both channels can issue and send the invoice to KSeF automatically. Confirm the dates at the source.