E-Commerce Platforms & Shop Systems
Shoper
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Shoper S.A. · www.shoper.pl
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Shoper at a glance
- Vendor
- Shoper S.A.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Shoper 0.5/5, the mean of 6 judges. Shoper S.A., an e-commerce shop-system vendor presenting as a Polish joint-stock company on a Polish-language site, was judged from a thin capture: two help articles on CSV import/export and store backups. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Shoper S.A., an e-commerce shop-system vendor presenting as a Polish joint-stock company on a Polish-language site, was judged from a thin capture: two help articles on CSV import/export and store backups. Strongest is data control and exit at 2-3, where a documented CSV profile moves products, language phrases and discount codes with UTF-8 encoding and URL-based image copying, and the vendor creates and can restore backups — though judges noted a restore is not a copy the merchant takes away. Operations and extensibility sit at 0-1, with no public information on order management, stock, returns, shipping or ERP links, and with the CSV profile itself the only developer-adjacent surface. Tax and legal and pricing transparency land at 0: the judges found no public information on VAT determination, OSS or reverse charge, and the captured pages carry no prices of any kind. Sovereignty is the genuine split, spanning 0-3 — some judges credited the Polish identity as an EU-base hint, others gave nothing because hosting location, the contracting entity and subprocessors are not on record.
Speaks for it
- A documented CSV profile imports and exports products, language phrases and discount codes
- The vendor creates store backups and can restore them
- Product images are copied in from an external server by URL during import
- An import event log shows which products arrived without photos
- Support is available 24/7 for setting up a trial store
Held against it
- Tax and legal scored 0, with no public information found on VAT determination, OSS or reverse charge
- Pricing transparency scored 0 — the captured pages carry no prices, tiers or fees of any kind
- Operations scored 0-1, with no public information found on order management, stock, returns, shipping or ERP links
- Extensibility scored 0-1, with the CSV profile described as a data bridge rather than a developer surface
- No sovereignty attributes are on record — hosting location, contracting entity and checkout-path subprocessors are unevidenced
Best for
- You need to move catalogue data in and out — products, language phrases and discount codes — through a documented CSV profile
- You want the vendor to hold and restore backups of your store
- You want round-the-clock help while setting up a trial store
- You sell into the Polish market and a Polish-language vendor presence matters to you
Avoid if
- You need verified VAT, OSS or reverse-charge handling for an EU checkout before going live
- You must budget before committing — the captured pages carry no prices
- Your business depends on order management, stock, returns, shipping or ERP links
- You must verify hosting location or the subprocessors in the checkout path before customer data flows
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 0.5 of 5 |
| Tax & German legal correctness | 0 of 5 |
| Extensibility & developer surface | 0.5 of 5 |
| Order operations & back office | 0 of 5 |
| Data ownership & exit | 1 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 0 of 5 |
Catalogue & checkout
Show reasoningHide reasoning
How this is scored
Products, variants, pricing rules and the path to payment — the part that either converts or does not.
0 — Flat product list with one price and no variants; checkout is a form and one payment method.
3 — Variants and categories with a standard checkout and two or three payment methods, but no bundles, no tiered pricing and no guest checkout worth the name.
5 — Full variant matrix, product bundles, tiered and customer-group pricing, guest checkout, and the payment methods a German shop needs including invoice and direct debit.
8 — Configurable products, per-channel pricing, promotions and vouchers with rules, a checkout that can be customised without a rebuild, and payment via the major providers plus buy-now-pay-later where offered.
10 — Merchandising and checkout are the product: rule-driven pricing and promotions, A/B-testable checkout, multi-currency and multi-language as standard, and conversion features (abandoned cart, one-page checkout) shipped rather than bolted on.
The Merchant
The captured pages show products and discount codes moving through a CSV import with images copied from an external server — real catalogue data handling, and vouchers exist at least as codes. I found no public information on variants, bundles, guest checkout, or any payment method, let alone the invoice terms German shoppers expect, so the conversion path is entirely unevidenced. 1
The B2B Seller
The only catalogue machinery in the captured pages is CSV import of products and discount codes; I found no public information on variants, bundles, customer-group or tiered pricing, or on the checkout path and its payment methods. For a trade buyer I cannot confirm from these pages that net prices are even shown to a business customer. 1
The Developer
The captured pages cover only CSV import of products and store backups; we found no public information on variants, bundles, pricing rules, the checkout flow or payment methods, so I can only score what the weakest case describes. 1 2
The Operations Lead
The only catalogue facts captured are a CSV import that moves products, language phrases and discount codes, with product images copied in from external URLs. We found no public information on variants, bundles, tiered or customer-group pricing, the checkout flow or payment methods, so nothing beyond a product list with vouchers is evidenced. 1
The Data Protection Officer
The only catalogue facts on record are that products, language phrases and discount codes can be imported via CSV profiles with URL-based image copying; we found no public information on variants, bundles, tiered pricing, guest checkout or which payment methods the checkout offers. Discount codes hint at a voucher mechanic, but the conversion path itself is entirely unevidenced. 1
The Skeptic
The only product-side fact captured is that products and discount codes are importable via a CSV profile, which hints voucher-style features exist but evidences nothing about the selling path. We found no public information on variants, bundles, tiered or customer-group pricing, guest checkout, or payment methods, so there is nothing here to judge a conversion story against. 1
Tax & German legal correctness
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, and the checkout requirements German law actually imposes — judged on what the platform does, not on a plugin someone could buy.
0 — A single VAT rate applied everywhere; no B2B handling, no country logic, no legal-text handling in checkout.
3 — Per-country VAT rates configurable by hand, net prices for B2B possible with effort, and legal texts as free-form pages.
5 — Automatic VAT by destination and customer type, VAT-ID validation with reverse charge, gross and net display per customer group, and the mandatory checkout elements (order button wording, withdrawal policy, price indications) handled.
8 — OSS thresholds tracked and reported, correct invoicing per case including reverse-charge notes, small-business and third-country handling, and e-invoicing (XRechnung/ZUGFeRD) for B2B orders.
10 — Tax and legal correctness are maintained by the vendor rather than the merchant: rates and thresholds updated as the law moves, OSS reporting produced, every invoice case correct out of the box, and documented conformity a lawyer could review.
The Merchant
I found no public information on VAT determination, OSS, reverse charge for B2B, or the legal texts a German checkout must carry; the pages on record are help articles about CSV imports and backups. Tax risk lands on the merchant's invoices, so unevidenced handling gets nothing from me. 1 2
The B2B Seller
I found no public information on VAT determination, VAT-ID validation, reverse charge for cross-border business customers, OSS, or the legal texts a German checkout must carry. Every check I run before recommending a shop to an EU trade customer is unverified here, which places this at the lowest position. 1 2
The Developer
Nothing in the captures touches tax or legal correctness: we found no public information on VAT determination, OSS, reverse charge, VAT-ID validation or the checkout texts German law requires. 1 2
The Operations Lead
We found no public information on VAT determination, OSS, reverse charge, B2B net pricing, invoicing or the legal texts a German checkout must carry. Nothing captured touches tax or legal handling in any form, and that absence is the entire picture. 1
The Data Protection Officer
We found no public information on VAT determination, OSS, reverse charge, VAT-ID validation or the legal texts a German checkout must show; the captured help pages cover CSV encoding and store backups only. Judged on that absence, this sits at the bottom of the scale. 1 2
The Skeptic
We found no public information on VAT determination, OSS reporting, reverse charge for B2B, gross and net display per customer group, or any German checkout requirement such as order-button wording or a withdrawal policy. The captured help pages are confined to CSV mechanics and store backups. 1 2
Extensibility & developer surface
Show reasoningHide reasoning
How this is scored
Themes, apps, APIs and headless — whether the shop can be shaped to the business, and at what cost in lock-in.
0 — Fixed templates, no app ecosystem, no API.
3 — Theme editing within limits and a small app store; a read-mostly API and no local development story.
5 — Custom themes with a template language, an app or plugin ecosystem, a documented REST API, and webhooks for the core order events.
8 — Full storefront API for headless builds, an extension framework with its own lifecycle, staging environments, version control for themes, and documented rate limits.
10 — A platform a team can own: headless-first APIs, open-source or source-available core, plugin architecture with a real dependency model, local development and CI supported, and upgrade paths that do not orphan customisations.
The Merchant
What is evidenced is a worked CSV profile system — field mapping, UTF-8 encoding, URL-based image copying, an import log — which is a data interface rather than a developer surface. I found no public information on themes, an app ecosystem, APIs or webhooks, so nothing shows the shop can be shaped to the business without a rebuild. 1
The B2B Seller
The only developer-adjacent surface in evidence is a CSV profile with a strict field order, UTF-8 encoding and URL-based image copying; I found no public information on theme editing, an app or plugin ecosystem, a documented API, or webhooks. That is a data bridge, not an extensibility story. 1
The Developer
This is the criterion I weigh hardest and there is nothing to evaluate — we found no public information on theming, a template language, apps, API surface, local development or how upgrades treat customisations. For a five-year maintenance commitment, an unevidenced extension surface has to be priced as a rewrite-or-migrate risk, which lands it at the bottom. 1 2
The Operations Lead
The only data interface evidenced is the CSV profile — fixed field order and names, UTF-8, three importable entity types and an event log for products that arrived without photos. We found no public information on theme editing, an app or plugin ecosystem, APIs, webhooks or headless builds. 1
The Data Protection Officer
The developer surface on record is a CSV profile mechanism with UTF-8 encoding rules, URL-based image import and an import event log; we found no public information on themes, an app ecosystem, a documented API or webhooks. A data-interchange profile is not a surface a team can build a shop on. 1
The Skeptic
We found no public information on themes, an app or plugin ecosystem, a documented API, webhooks, or headless builds. The nearest thing to a developer surface in the captures is a CSV profile whose field order and names must match exactly, which is data entry, not extensibility. 1
Order operations & back office
Show reasoningHide reasoning
How this is scored
What happens after checkout: order management, stock, returns, shipping, and the link to ERP or accounting.
0 — An order list and an email; stock is a number nobody trusts, returns are manual.
3 — Order statuses and basic stock, one shipping integration, and returns handled by hand.
5 — Order workflow with partial shipments, multi-warehouse stock, named carrier integrations with label printing, and a returns process in the system.
8 — Multi-channel order intake, automated fulfilment routing, supplier and dropshipping flows, and maintained interfaces to named ERP and accounting systems.
10 — The shop is the front of an operation: real-time stock across channels and warehouses, returns and refunds fully worked including partials, ERP integration the vendor maintains, and operational reporting a merchant runs the business from.
The Merchant
The captured material covers vendor-created backups with restore and around-the-clock help setting up a trial store, and nothing else about the back office. I found no public information on order management, stock, returns, shipping integrations or ERP links, so the entire after-checkout half of the business is unevidenced. 2
The B2B Seller
I found no public information on order management, stock, returns, shipping integrations or ERP and accounting links. What the pages do document is store backups that can be restored and round-the-clock help with setting up a trial store — comfort, not operations. 2
The Developer
We found no public information on order management, stock, shipping, returns or ERP interfaces; the only operations-adjacent fact is that the vendor creates and can restore store backups, which is continuity, not back office. 1 2
The Operations Lead
We found no public information on order management, partial shipments, returns and refunds, multi-channel stock, carrier label printing or a single ERP or accounting interface — the after-checkout half of the business is invisible. The only operational facts captured are vendor-run backups that can be restored and 24/7 support for trial setups, which is continuity, not fulfilment. 2
The Data Protection Officer
We found no public information on order management, stock, returns, shipping integrations or ERP links; the captured material covers store backups and 24/7 support, neither of which is post-checkout operations. 2
The Skeptic
The captured pages address store backups and round-the-clock support availability, and we found no public information on order management, stock, returns, shipping integrations, or ERP and accounting connections. What happens after checkout is simply not documented here. 2
Data ownership & exit
Show reasoningHide reasoning
How this is scored
Whether the catalogue, customers and order history remain the merchant's: export completeness, hosting choice, and what leaving actually costs.
0 — Export is a partial CSV; order history and customer records cannot leave intact, and hosting is the vendor's alone.
3 — CSV export of products and customers, order history partial, no self-hosting, no documented migration path.
5 — Complete export of catalogue, customers and orders via API or dump, documented deletion, and a stated data-return commitment.
8 — Full-fidelity export including media and order documents, self-hosting or a choice of hosting partner, and no metering that prices a migration out of reach.
10 — Ownership is structural rather than promised: open-source or source-available platform the merchant can run anywhere, database-level access, documented migration in both directions, and contractual data return.
The Merchant
Products, language phrases and discount codes move through a documented CSV export and import process, so the catalogue can leave, and the vendor creates backups — though a restore in place is not a copy the merchant takes away. I found no public information on customer or order-history export, self-hosting, or a documented migration path. 1 2
The B2B Seller
CSV export is documented, but the import/export article names only products, language phrases and discount codes in its scope, and I found no public information on exporting customers or order history intact, on self-hosting, or on a documented migration path. The pages do show backups that can be created and restored, which is more than a bare partial export, yet the true cost of leaving remains unknown from what is public. 1 2
The Developer
Product data moves through a documented CSV profile with UTF-8 and a strict field-order contract, which is real but narrow — the documented importable set is products, language phrases and discount codes, and we found no public information on exporting customers or order history intact, on self-hosting, or on a migration path. The vendor's backup and restore capability protects continuity, but a backup I cannot take with me is not an exit. 1 2
The Operations Lead
The one exit mechanism evidenced is a CSV profile limited to products, language phrases and discount codes, requiring exact field-order matching, UTF-8 encoding and URL-based image copying. We found no public information on exporting customer records or order history, on self-hosting, on deletion or on a documented migration path, and the restorable backup is the vendor's continuity tool rather than a merchant's handover. 1 2
The Data Protection Officer
CSV import and export runs through profiles, but the documented importable entities stop at products, language phrases and discount codes, and we found no public information on exporting customer records or order history, on documented deletion, or on any migration path or hosting choice. Backups are created and restored by the platform, so the recovery copy sits with the vendor rather than the merchant — exactly the arrangement I want to see reversed before trusting a shop's exit story. 1 2
The Skeptic
A CSV import and export mechanism exists for products, language phrases and discount codes, with an event log and images copied by URL, and the vendor creates and can restore store backups. We found no public information on exporting customer records or order history, on self-hosting or a choice of hosting, or on any documented migration path — so the cost of leaving with your own data intact is not addressed in the captured pages. 1 2
European sovereignty
panel opinion
panel disagrees
Show reasoningHide reasoning
How this is scored
Where customer and order data live, who the contracting entity is, and which subprocessors sit in the checkout path. Independently sourced by the sovereignty pipeline.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — CDN, analytics, payment routing, support tooling — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, complete subprocessor list published, any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor European, certification published, and a self-hosted option that puts the shop entirely under the merchant's control.
The Merchant
The vendor is a Polish company whose service pages are in Polish, which points to an EU contracting entity, but I found no public information on hosting location, the subprocessors in the checkout path, or certification — none of it is on record. EU roots with an unnamed processing chain sits at the level where disclosure stops short of what a buyer can verify. 1 2
The B2B Seller
No sovereignty attributes are on record: I found no public information on where customer and order data are hosted, on the contracting entity, or on any subprocessor in the checkout path. The vendor operates a Polish-language shop for the Polish market, which suggests an EU base, but nothing in the captured pages verifies hosting, certification or the processing chain. 1 2
The Developer
No sovereignty attributes are on record: we found no public information on where customer and order data are hosted, on the contracting entity's jurisdiction beyond the vendor's name and.pl domain, or on any subprocessor in the checkout path, so the chain cannot be assessed and this sits just above the floor only on the Polish identity hints. 1 2
The Operations Lead
We found no public information on hosting location, contracting entity jurisdiction or subprocessors — no sovereignty attributes are on record. Nothing captured speaks to where customer and order data are processed, so the checkout chain cannot be assessed at all. 1 2
The Data Protection Officer
The vendor presents as a Polish joint-stock company on a Polish-language site, but we found no public information on hosting location, the contracting entity's registered seat, certification, or any subprocessor in the checkout path — the list I would demand before letting customer data pass through this platform. We likewise found no public information on where the CDN and analytics sit, and no self-hosted option to fall back on. 1 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a merchant can compute the real annual cost — licence, transaction fees, apps, hosting — from public pages alone. The category where the headline price is least often the invoice.
0 — No public prices at all; every tier is a sales conversation.
3 — A monthly headline exists, but transaction fees, mandatory apps or hosting costs are unstated — the invoice is unknowable from the page.
5 — Tier prices public with billing period stated and transaction fees given, but at least one commonly needed piece (a required app, hosting, payment gateway rate) is unpriced.
8 — Every tier priced publicly including transaction or revenue-share rates, order or GMV limits, and the cost of the extensions most shops need; VAT treatment and minimum term stated.
10 — Complete price computability: annual cost derivable for a given order volume and GMV including licence, transaction fees, hosting and typical extensions — and for open-source platforms, an honest statement that the licence is free and where the money actually goes.
The Merchant
The captured pages — CSV import help and backup help — carry no prices, and I found no public information on tiers, billing periods, transaction fees, order limits or term lengths. I judge price against contribution, and with nothing public the annual cost cannot even be attempted. 1 2
The B2B Seller
The captured pages state no prices at all — no plan costs, billing period, transaction fees, app or hosting charges — and the only commercial mention is help setting up a trial store. A merchant cannot begin to compute an annual cost from what is public. 2
The Developer
We found no public information on licence cost, billing period, transaction fees, order limits or extension pricing, and a merchant cannot compute any annual cost from the captured pages. 1 2
The Operations Lead
We found no public information on pricing — no licence tiers, transaction or revenue-share rates, order limits, hosting or app costs, VAT treatment or minimum terms. A merchant reading the captured pages cannot derive any annual cost, headline or otherwise. 1 2
The Data Protection Officer
We found no public prices at all on the captured pages, which are help articles on CSV import and backups — no licence tiers, billing period, transaction fees or hosting costs. A merchant cannot compute an annual cost from this. 1 2
The Skeptic
We found no public prices of any kind — no licence or tier fee, no transaction or revenue-share rate, no order or GMV limits, no hosting or extension costs. The only commercial-adjacent fact captured is that support answers 24/7, and it says nothing about what a year actually costs. 2
Questions about Shoper
Is Shoper European?
Not determined: the vendor’s pages as captured do not say where Shoper is based.
Where does Shoper store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Shoper have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Shoper?
As of 21 Oct 2026, the panel rates JTL-Shop (3/5), Medusa (3/5) and Shopify (3/5) highest among the other 25 E-Commerce Platforms & Shop Systems products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is JTL-Shop (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Shoper alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (shoper.pl/learn/artykul/opis-import-eksport-csv, shoper.pl/learn/wsparcie/kategoria/ustawienia/ustawienia-sklepu/kopia-bezpieczenstwa-backup). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 2 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (2)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Data ownership & exit — found from sitemap www.shoper.pl Checked 13 Oct 2026 Details →
- 2 Data ownership & exit — found from sitemap www.shoper.pl Checked 13 Oct 2026 Details →