E-Commerce Platforms & Shop Systems
ePages
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by ePages GmbH · www.epages.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
The captured pages for ePages GmbH, an e-commerce platform vendor, present a website builder: a drag-and-drop editor with flexible content blocks, automatic translations, a personal design service and an app store with native integrations. The bench scores that storefront surface where the product is strongest — extensibility at 2-3 and sovereignty at 2-3, the latter resting on the German GmbH contracting entity and German-language offering, since we found no public information on hosting location or a subprocessor list and the sovereignty attributes on record are empty. Behind the storefront, scores sit near the floor: operations 0-1, tax and legal 0-1, data control and exit 0-1, catalog and checkout 0-2, with judges finding no public information on variants, payment methods, VAT and OSS handling, order workflow, shipping, ERP links or data export. Pricing transparency sits at 0-1 — a free trial is the only pricing fact published — and that criterion is not counted in the weighted verdicts. Scores cluster within a point or two on every criterion, and the flagged splits came back empty.
Speaks for it
- App store and native integrations are confirmed on the vendor page
- Drag-and-drop editor, flexible content blocks, automatic translations and a personal design service are confirmed
- Extensibility scores cluster at 2-3 on the strength of the app store and native integrations
- Sovereignty scores cluster at 2-3, resting on the German GmbH contracting entity and German-language offering
- A free trial is offered publicly
Held against it
- Catalog and checkout scores run 0-2, with no public information on variants, pricing rules or payment methods
- Tax and legal scores run 0-1, with no public information on VAT determination, OSS or reverse charge
- Operations scores run 0-1, with no public information on order management, stock, shipping or ERP and accounting links
- Data control and exit scores run 0-1, with no public information on export of catalogue, customer or order data
- Each confirmed fact traces to one capture of the vendor homepage
Best for
- You want to assemble a storefront yourself with a drag-and-drop editor, flexible content blocks and a bookable design service
- You plan to extend the shop through an app store and native integrations rather than custom code
- You serve international website visitors and want automatic translations built in
- You want a German GmbH as the contracting entity
Avoid if
- You need the checkout path itself evidenced — variants, payment methods, conversion flow — before you can compare platforms
- Your peak season depends on order workflow, stock, shipping and returns you can verify up front
- You sell cross-border and need VAT, OSS and B2B reverse-charge handling in evidence
- You require a documented export and migration path for catalogue, customer and order data before onboarding
The scores
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 page evidences a drag-and-drop storefront editor with flexible content blocks, an app store and native integrations — but we found no public information on variants, bundles, tiered pricing, guest checkout, promotions with rules, or the payment methods German shoppers expect, including invoice and direct debit. Nothing on the checkout path to payment itself is evidenced, and that is the part I sell on. 1
The B2B Seller
The captured pages evidence a drag-and-drop editor with content blocks, automatic translations and an app store for additional tools — storefront building, in other words. We found no public information on variants, pricing rules, the checkout path or payment methods, and nothing on net display, customer-specific price lists or payment on account for trade customers. 1
The Developer
The captured homepage sells a website builder — drag-and-drop editor, automatic translations, a personal design service — and says nothing about the commerce core; we found no public information on product variants, bundles, pricing rules, guest checkout or payment methods. There is nothing here for a buyer to evaluate conversion against, so this lands at the bottom of the scale. 1
The Operations Lead
The captured page talks about a drag-and-drop editor, flexible content blocks and automatic translations, and we found no public information on product variants, bundles, pricing rules, guest checkout, the checkout flow itself or payment methods. I cannot credit a conversion path I cannot see, and for a German shop I would want to see invoice and direct debit before trusting it. 1
The Data Protection Officer
The captured pages describe website building, automatic translations and an app store with native integrations, but we found no public information on product variants, pricing rules, bundles, guest checkout or the payment methods offered. A checkout path full of third parties that I cannot see described is exactly the silence I would want disclosed before onboarding, so I cannot evidence more than the lowest level here. 1
The Skeptic
The captured homepage sells the site-builder: a drag-and-drop editor, flexible content blocks, automatic translations and a paid design service. We found no public information on variants, bundles, pricing rules, the checkout flow or which payment methods a shop can take; an app store exists, but what commerce tools sit in it is not shown. 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
We found no public information on VAT determination by destination or customer type, OSS reporting, reverse charge for B2B, or the legal texts and price indications a German checkout must carry. Only German-language marketing for site building is captured, so a merchant would be buying tax and legal handling entirely on trust. 1
The B2B Seller
We found no public information on VAT determination by destination or customer type, VAT-ID validation, reverse charge, OSS, or the checkout elements German law requires. The closest claim is automatic translations for international customers, which addresses language, not tax or legal correctness. 1
The Developer
We found no public information on VAT determination, OSS, B2B reverse charge, e-invoicing or the mandatory German checkout elements; the only German-market signal is that the copy is in German. With nothing evidenced on tax or legal handling, I score by what absence is worth. 1
The Operations Lead
We found no public information on VAT determination, OSS, B2B reverse charge, invoicing or the legal texts a German checkout must carry. For a platform pitched at German merchants, that silence decides the score. 1
The Data Protection Officer
We found no public information on VAT determination by destination, VAT-ID validation or reverse charge, OSS reporting, or the mandatory German checkout elements like withdrawal policy and order button wording. Automatic translations for international customers are described, but nothing on how prices are taxed or invoiced per case. 1
The Skeptic
We found no public information on VAT determination, B2B or reverse-charge handling, OSS thresholds, or the checkout elements German law requires. The only cross-border feature on the page is automatic translation of the website. 1
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
An app store with installable tools, native integrations and a drag-and-drop editor are evidenced, which matches theme-level flexibility with a small extension catalog. We found no public information on a documented API, webhooks, staging environments or a headless storefront, so I cannot credit a checkout that can be changed without a rebuild. 1
The B2B Seller
An app store and native integrations are evidenced, so the shop can be extended beyond what ships with it. We found no public information on a documented API, webhooks, themes, staging environments or any headless surface, which keeps this far from a platform a developer team could own. 1
The Developer
The page shows an app store with native integrations and a drag-and-drop editor with flexible content blocks — editing within limits, but we found no public information on a template language, an API, webhooks, headless storefronts or staging environments. As the person maintaining this for five years, an editor I cannot put under version control and no local development story reads as a future migration, not a foundation, so I sit just above the floor on the strength of the app store alone. 1
The Operations Lead
An app store and some natively integrated tools are confirmed in the vendor's own words, which is a genuine start. We found no public information on a documented API, webhooks, a template language for themes or any headless surface, so the developer story stays at marketing level. 1
The Data Protection Officer
A drag-and-drop editor and an app store with native integrations correspond to theme editing within limits plus installable tools; we found no public information on a documented API, webhooks, headless storefront access, staging environments or any local development story. That places it at the level of a limited app store with no developer surface described. 1
The Skeptic
A public app store, native integrations and a drag-and-drop editor are confirmed, which is design editing within limits plus an app ecosystem. We found no public information on a documented API, webhooks, template or theme code, headless storefronts or any local development story. 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
We found no public information on order workflow, partial shipments, stock, returns, carrier label printing or interfaces to ERP and accounting systems; the app store and native integrations exist as facts but no tool is named. I judge fulfilment only on named capabilities, and there are none here. 1
The B2B Seller
We found no public information on order management, stock, shipping, returns or interfaces to ERP and accounting systems. The only adjacent items are unnamed native integrations and the app store, neither of which evidences an order workflow after checkout. 1
The Developer
We found no public information on order management, stock, returns, shipping integrations, carrier label printing or ERP and accounting links; the native integrations are presented only as marketing and visibility tools. Nothing on the back office is evidenced at all. 1
The Operations Lead
This is my yardstick and the captured page says nothing about it: no public information on order workflow, partial shipments or partial refunds, stock truth across channels, carrier integrations with label printing, returns or ERP and accounting interfaces. A shop whose December I cannot plan sits at the bottom of my scale. 1
The Data Protection Officer
We found no public information on order management, stock keeping, returns, carrier integrations or interfaces to ERP and accounting systems. Order history handling matters directly for deletion requests, and nothing about it is described on the captured pages. 1
The Skeptic
We found no public information on order management, stock keeping, shipping integrations, returns or any link to ERP or accounting. The page mentions native integrations and an app store without naming a single back-office tool. 1
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
We found no public information on export of catalogue, customers or order history, on documented deletion, on hosting choice or self-hosting, or on any migration path. An unevidenced exit is the most expensive kind, and that is what the captured pages leave me with. 1
The B2B Seller
We found no public information on export of catalogue, customer or order data, on hosting choice, or on any documented migration path. What leaving the platform costs cannot be assessed from the captured pages. 1
The Developer
We found no public information on catalogue or order-history export, deletion, self-hosting, hosting partners or a documented migration path in either direction. A free trial is an entry, not an exit; nothing here evidences that the data remains the merchant's in any operational sense. 1
The Operations Lead
We found no public information on export of catalogue, customers or order history, on deletion, on hosting choice or on any migration path. Without export evidence, leaving this platform is a bet rather than a plan, and that costs it everything here. 1
The Data Protection Officer
We found no public information on export completeness for catalogue, customers and order history, on how deletion executes, on hosting choice, or on any documented migration path in either direction. No data-return commitment appears on the vendor page, and a free trial tells me nothing about what leaving costs. 1
The Skeptic
We found no public information on export of the catalogue, customers or order history, on hosting choice or self-hosting, or on a documented migration path in either direction. A free trial is offered; what it costs to leave with your own data is not shown on the captured page. 1
European sovereignty
panel opinion
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 contracting entity is a German GmbH on a German-language site, which is the one solid fact, but hosting location is unstated and no list of subprocessors in the checkout path is published. Payments routed through unnamed processors are not something I can assess for European sovereignty. 1
The B2B Seller
The vendor is ePages GmbH with a German-language site, so the contracting entity appears European. Beyond the vendor's name we found no public information on hosting location, the subprocessor chain in the checkout path, or any certification — no sovereignty attributes are on record. 1
The Developer
The vendor presents as ePages GmbH with a German-language offering, so the contracting entity looks European, but we found no public information on hosting location or infrastructure, and the subprocessor list is simply absent. That is exactly the picture of a European-facing vendor with no published custody chain, which sits low rather than at zero only because the entity itself appears German. 1
The Operations Lead
The vendor operates as ePages GmbH, so the contracting side looks European, and the page pitches German-language services to German merchants. The captured pages give no hosting location and no subprocessor list, and no certification is published, so I can credit the entity name and little else. 1
The Data Protection Officer
The contracting entity is a German GmbH, but we found no public information on hosting location, the infrastructure used, or a subprocessor list — no word on where the CDN, analytics or payment routing sit. An absent subprocessor list in a checkout full of third parties is the specific gap I am here to find, and it caps this at the level the published information supports. 1
The Skeptic
The independently collected sovereignty attributes for this vendor are empty. The only European signal is the German legal form in the vendor name; we found no public information on where customer and order data are hosted, which subprocessors sit in the checkout path, or any certification. 1
Pricing transparency
not rated — the vendor publishes no price
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 only pricing fact captured is a free trial; we found no public prices for any tier, no billing period, no transaction or revenue-share rates, and no costs for apps, hosting or payment gateways. From these pages a merchant cannot compute even the licence portion of an annual bill, let alone the whole. 1
The B2B Seller
The only pricing fact captured is a free trial, which prices the first step but nothing after it. We found no public information on tier prices, billing period, transaction fees, order limits or VAT treatment, so the annual cost is unknowable from the pages alone. 1
The Developer
The only commercial signal on the captured page is a free trial ("Starte noch heute deine kostenlose Testphase"); we found no public information on tier prices, billing periods, transaction or revenue-share fees, order limits, hosting costs or VAT treatment. An annual cost is not computable from anything captured, so a merchant starts with a sales conversation. 1
The Operations Lead
The only price-adjacent statement on the captured page is an invitation to start a free trial, with no term or conditions attached; we found no public information on tier prices, billing period, transaction fees, order limits or hosting costs. A merchant cannot compute an annual cost from this page, and the invoice stays a sales conversation. 1
The Data Protection Officer
A free trial is offered publicly, but we found no public prices for any tier, no billing period, no transaction or revenue-share rates, and no word on what hosting or app-store extensions cost. The real annual cost of running a shop on this platform cannot be computed from the captured pages. 1
The Skeptic
The page states a free trial and, as far as cost goes, nothing else: we found no public information on tier prices, billing periods, transaction or revenue-share fees, order limits, or the price of the apps and hosting a shop actually needs. The annual invoice is not computable from public pages; every real number is a sales conversation. 1
European sovereignty — proven facts
1 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE ⚠ unverified | 3/3 pts | 2 Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. The English legal notice instead lists ePages Software Ltd. registered at Companies House in the United Kingdom, so the contracting entity differs by language region.
- Weak sourcing — Data residency, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- 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 pricing on the pages we read (epages.com, epages.com/de/impressum, epages.com/de/datenschutz, epages.com/en/legal-notice, epages.com/en/themes, epages.com/en/theme-documentation). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 8 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
- 8 subprocessors 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
- 3 support 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 hosting 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. 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 (6)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.epages.com Checked 29 Sep 2026 Details →
- 2 Imprint — found from the homepage epages.com Checked 30 Sep 2026 Details →
- 3 Privacy policy — found from the homepage epages.com Checked 30 Sep 2026 Details →
- 4 Tax & German legal correctness — found from sitemap epages.com Checked 1 Oct 2026 Details →
- 5 Extensibility & developer surface — found from sitemap epages.com Checked 1 Oct 2026 Details →
- 6 Extensibility & developer surface — found from sitemap epages.com Checked 1 Oct 2026 Details →