Comarch e-Sklep is the natural candidate when your store has to work with data from an existing Comarch ERP. Shoper is a strong choice when its local sales tools, integrations, and editor matter more. But you don’t need an ERP to open an ordinary B2C store. For a new brand without that dependency, we recommend a third option, Setka, our product: a platform that builds the storefront around your catalog and brand direction. This comparison is for businesses selling in Poland.

The choice has two parts: data flowing correctly through the business, and the offer presented well to the customer. A working warehouse connection matters, but it doesn’t make the store good.

The case for Comarch e-Sklep

Its strongest argument is how closely it ties sales to the Comarch ERP environment. The vendor describes an integration covering stock levels, the customer database, orders, and logistics. For a business that already runs those processes there, the store becomes one more sales channel on top of the existing back office.

Take a distributor with one warehouse serving phone and online orders, where retail prices and availability are set in the ERP. Keeping a second copy of prices and stock in the store by hand would be the weak point of that process. Choose the system that handles the existing data flow correctly first, and refine the presentation after that.

Comarch e-Sklep is more than a window into the warehouse, though. The vendor offers ready-made templates and a design builder, plus payments and shipping, so you can set up a regular retail store without commissioning a custom design on day one.

That doesn’t make every setup free of implementation costs, extra services, or a partner’s work. Even a connection from the same vendor needs a decision about how it should work in your business. “Native” doesn’t mean it runs itself.

The case for Shoper

Shoper fits a business whose starting point is the retail store itself, with payments, shipping, and sales channels built around it. The subscription includes hosting, order management, integrations, and Polish-language support. That’s a sensible model if you want to grow sales inside Shoper’s environment. Shoper vs Shopify compares it with a global hosted platform.

Its editor lets you arrange ready-made modules by drag and drop, so a new collection that needs a different banner, content order, and descriptions doesn’t have to mean touching code. Custom modules and up to 50 custom page layouts come only with the Premium plan.

A business on Comarch ERP can choose Shoper too, if the chosen connection supports its process and someone is responsible for maintaining it. Don’t rule that route out just because another company provides the integration. What matters is whether the data flow you need works, and whether what you gain from Shoper is worth looking after that connection.

First, establish where your data originates

The example below is hypothetical. It shows a business with a working ERP and a B2C store, without customer-specific wholesale price lists.

InformationSource in this scenarioWhat the store connection has to do
Product identifier and basic detailsERPKeep the product consistent between sales and the warehouse
Retail priceERPSupply the price that applies in the store and set the rules for changing it
Available quantityERPPass on availability, accounting for reservations in other channels
Online orderStorePass on the data needed for fulfillment and billing
Collection story and buying guidanceStoreLet the presentation develop without changing product facts

This map gives you a decision rule: if Comarch e-Sklep handles the mandatory data flow better, it comes first. If both routes handle it correctly, compare how easy each makes selling and later changes.

Not everything has to come from the ERP. A stock level is an operational fact. Advice on which size to choose, or what a collection goes with, is work on the offer. You should be able to develop that second layer without disturbing the first.

Compare the right edition, and keep B2B a separate decision

Comarch distinguishes Light, Standard, Enterprise, and B2B editions. Its official table of edition differences covers currencies, languages, administrator permissions, and customer-specific price lists, among other things. A feature listed for one edition isn’t necessarily in the others.

For an ordinary retail store, start with the catalog and how you handle orders. If the store has to exchange data with an ERP, what matters is the specific system, its version, and the scope of connection you need. The description of the Comarch ERP XL integration covers XL; if you use a different system, ask about the connection to yours.

Individual customer prices, trade credit limits, or sales-rep workflows are a separate B2B decision. Don’t buy those capabilities just because some of your customers are companies. What counts is how orders are actually placed and billed.

Keep your own store separate from marketplaces in the same way. Comarch presents e-Sale as a separate service for managing those channels. In Shoper, the free Apilo Lite app gives you a two-way Allegro integration, and further marketplaces, such as Amazon, eBay, Empik, or OLX, go through the Apilo app. See also the integrations in Shoper’s plans.

The subscription is only part of the cost

For a store connected to an ERP, you pay for the platform, for building the connection, for maintaining it, and for work on the store itself. Payment fees and any extra services come on top. The first setup of the connection is only the start: catalog changes, pricing rules, and system updates cost time and money too.

So a cheaper subscription doesn’t automatically mean a cheaper setup. Nor does an integration from a single vendor always win on cost: if the store needs an expensive custom design, that work stays in the budget wherever the stock levels come from.

In Shoper’s price list checked on 16 October 2026, the promotional price is a net-of-VAT price for the first year paid upfront. That’s what the first year costs, not every year after it, and the crossed-out amount next to it isn’t a guaranteed renewal price.

Without an ERP, start with the store you want to run

A small soap brand with its own catalog doesn’t need the back office of a distributor with several order channels. If you manage products and orders directly on the store platform today, adding an ERP just to get a store makes the project bigger without solving a problem you have.

That’s the brand we recommend Setka for. On Comarch e-Sklep you start from a template and a builder; on Shoper you arrange modules, with custom layouts reserved for Premium. In Setka you bring the products, product details, photos, and brand direction, and Setka builds the storefront around them. When the season changes or a product needs better explaining, you open the page and describe the change, edit exact wording directly when you know it, preview the next version, and publish. There is no theme code for you to maintain.

Checkout, stock, and orders are part of the same platform. Payments run through your own Stripe account, and the methods you enable there, BLIK included, appear at checkout automatically. A paid order updates stock and sends the customer a confirmation, and you can refund all or part of a payment from the order. Each store currently sells in one currency. You set shipping rules in the Setka admin, and an InPost Paczkomaty plugin is available in Poland. The checkout guide shows the payment setup step by step.

Setka doesn’t connect to an ERP yet, Comarch ERP included, so this recommendation is for a store without mandatory ERP sync. If that requirement decides your launch, write to [email protected] and name the system and the data flow you need. Requests go straight to the people building Setka.

If what you need is a store for your brand rather than a new integration project, start in Setka: add your first collection and tell customers why it’s worth choosing.