Choosing an e-commerce platform for the Polish market

Store platforms are usually compared on themes, page builders and app counts. In Poland none of those decide it. Three local integrations do, and a platform that is weak on any of them will cost you more in workarounds than it saves on licence fees.

Payments: BLIK and pay-by-link, not cards

Polish online shoppers reach first for BLIK and for instant bank transfers initiated from the checkout — the pay-by-link model offered by the Polish payment gateways. Cards work, and plenty of people use them, but a checkout that offers cards and PayPal and nothing else is asking a Polish customer to do something other than what they usually do, at the exact moment you least want friction.

• Check that the platform integrates with at least one of the established Polish gateways, and that it is a supported integration rather than a community plugin.
• Check how refunds work through that gateway from inside the admin, not just how payments arrive.
• If you plan on cash on delivery, check that the courier integration and the payment reconciliation both handle it. It is the most common source of accounting mismatches in Polish stores.
• Deferred and instalment payment options are widely used; if they matter to your basket size, confirm which are available before you commit.

Delivery: the parcel locker is the default

Parcel lockers changed Polish e-commerce logistics, and the checkout has to reflect that. What the platform needs is not "shipping methods" in general but the specific pieces:

1. A locker picker in the checkout — a map, searchable, that returns a point identifier to the order. A free-text field is not this.
2. Label generation from the order, in the admin, without retyping the address into a courier portal.
3. Tracking back onto the order and into the customer email.
4. Multiple carriers at once. Most stores end up with a locker network plus at least one door-to-door courier, and the platform has to price and present both.
5. Returns. A return label a customer can generate themselves removes a large share of support email.

Marketplaces: Allegro is a channel, not a competitor

For a great many Polish stores, the marketplace is where the volume is and the own store is where the margin is. Treating them as one operation is the difference between a store you can run with two people and one you cannot.

• Offer and stock synchronisation, in both directions, with a defined behaviour when stock hits zero.
• Order import, so fulfilment happens in one place.
• Consistent delivery promises across channels — marketplace buyers have expectations set by the marketplace, not by you.
• Either a native integration or a multichannel connector. Many Polish stores run the second, and that is a fine answer as long as you know which system is the source of truth for stock.

Invoicing and KSeF

Orders have to become accounting documents without a person in the middle. Two Polish specifics catch people out. First, a VAT invoice for a sale recorded on a receipt depends on the buyer's tax number being captured at the point of sale, so the checkout has to ask for it at the right moment, not afterwards. Second, structured invoicing under KSeF changes how the invoice is issued, not merely how it is delivered — our KSeF checklist covers what the invoicing side has to support.

If you sell to consumers in other EU countries, check the OSS handling before your first cross-border order rather than after your first quarter.

The legal furniture

• Terms of sale and a privacy policy, both reachable from every page.
• The consumer right of withdrawal, with a working returns flow behind it rather than an email address.
• Price-history presentation for promotions, as required by the Omnibus rules.
• The current consumer-conformity regime for the goods, services or digital content you actually sell — the rules were rewritten when the EU directives were implemented, so check which applies to you.
• A cookie and consent banner that genuinely blocks scripts before consent, not one that only records the click.

Three shapes of platform

Shoper is a Polish SaaS platform, listed in our catalogue with local payment, courier and marketplace integrations built in and Polish-language support. That is the shortest path to the three integrations above being somebody else's problem.

Shopify is fully hosted with a very large third-party app market, and its Polish integrations generally exist — through that app market. The question to ask for each one is who maintains it, what it costs on top, and what happens when the platform changes an API.

WooCommerce is open source with a free core, paid extensions and your own hosting. It gives you the most control and hands you the most responsibility: hosting, performance under a campaign, plugin conflicts and security patching all become yours. It is an excellent answer for a team with a developer and a poor one for a team without.

Questions to ask before you commit

1. Show me a full order: locker chosen, paid with BLIK, label generated, invoice issued, tracking sent. On a trial account.
2. What is the total monthly cost with the payment gateway, courier integration and the two apps I will need?
3. What happens to my URLs if I migrate in? Broken product URLs are the most expensive part of a store migration.
4. What is the export, and does it include orders and customers, not just products?

The platform decision is really a decision about who maintains your integrations. Everything else can be changed later; that cannot, cheaply.

Compare the field in our e-commerce platforms category.