E-Commerce Platforms & Shop Systems
Centra
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Centra AB · centra.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 public record this bench could judge is thin: a single captured vendor page positioning Centra as a fashion brand commerce platform for serving all markets with the right products, prices and campaigns. Catalog and checkout tops out at 1 — minimal credit for the multi-market claim, with no public information on variants, bundles, guest checkout or payment methods. Tax and legal runs 0 to 1, and extensibility, operations and data control and exit sit at 0, with no public information on VAT determination and reverse charge, developer surface, order workflows, or export and exit terms. Sovereignty shows the widest spread, 0 to 2: the higher scores credit the vendor's Swedish corporate form, Centra AB, as a European contracting entity, while the lower ones find nothing beyond a company name to verify — no sovereignty attributes are on record, and hosting location and subprocessors are unstated. No price of any kind appears, so an annual cost remains a sales conversation.
Speaks for it
- Positions as a fashion brand commerce platform with built-in tools for products, prices and campaigns across markets.
- Vendor appears as Centra AB, a Swedish corporate form that the top sovereignty scores read as a European contracting entity.
- Catalog and checkout reaches 1, minimal credit for the multi-market positioning claim.
- Sovereignty tops the table at 2, the highest mark any criterion received.
Held against it
- Tax and legal scores run 0 to 1, with no public information on VAT determination, OSS, reverse charge or German checkout texts.
- Extensibility, operations and data control and exit score 0, with no public information on APIs and webhooks, order management and stock, or export and migration paths.
- No sovereignty attributes are on record, leaving hosting location and checkout-path subprocessors unstated.
- No price of any kind appears on the captured page, so an annual cost is not computable from public information.
Best for
- You run a fashion brand selling across many markets, the case the vendor's positioning addresses directly.
- You want a European contracting entity at signature — the vendor appears as Centra AB, a Swedish corporate form.
- You are prepared to obtain catalogue, tax, operations and exit specifics in direct talks with the vendor rather than from public pages.
Avoid if
- You sell outside fashion — the vendor's public positioning targets fashion brands specifically.
- Your shortlisting depends on published evidence of tax handling, developer surface or back-office operations — those criteria scored 0 to 1 here.
- You need export and migration terms in writing before committing — the developer judge reads an exit story available only through sales conversations as itself a lock-in cost.
- Your data protection review requires stated hosting location and subprocessors in the checkout path, on which the judges found no public information.
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 only thing on the captured pages is the marketing sentence about serving all markets with the right products, prices and campaigns — a claim, not a checkout. I found no public information on variants, guest checkout, the payment methods a German shop needs such as invoice and direct debit, or promotions with rules, so I cannot judge whether this thing converts at all. 1
The B2B Seller
The single captured page is a positioning statement promising built-in tools for products, prices and campaigns across markets — claim-level marketing, not a demonstration. We found no public information on variants, bundles, checkout flow, payment methods, guest checkout, or the customer-specific net price lists a trade buyer needs. 1
The Developer
The single captured page is a positioning line about serving all markets with the right products, prices and campaigns, naming no variant model, checkout flow or payment methods. We found no public information on the product catalogue or the path to payment, so there is nothing on the page to evidence capability above the bottom. 1
The Operations Lead
All that is public is a positioning line about serving all markets with the right products, prices and campaigns; we found no public information on variants, bundles, guest checkout or which payment methods the checkout takes. The campaign talk hints at pricing rules, but a marketing sentence is not a checkout I can judge. 1
The Data Protection Officer
The only captured material is the vendor's positioning that fashion brands can serve all markets with the right products, prices and campaigns — a marketing claim rather than an evidenced checkout. We found no public information on variants, bundles, pricing rules, guest checkout or payment methods, so only a minimal credit is possible for the multi-market claim. 1
The Skeptic
The only captured material is the vendor's own positioning that it offers built-in tools for products, prices and campaigns across markets — a marketing line, not an evidenced catalogue. I found no public information on variants, bundles, tiered pricing, the checkout flow or which payment methods are supported. 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 by market or customer type, OSS handling, reverse charge for B2B, or the checkout texts German law demands. For a shop selling into Germany that silence decides the score by itself. 1
The B2B Seller
Nothing in the captured material addresses VAT determination, VAT-ID validation, reverse charge, OSS, or the checkout requirements German law imposes. The phrase about serving all markets is marketing rather than evidence of tax handling; we found no public information on invoicing cases, e-invoicing, or net-price display for B2B customers. 1
The Developer
We found no public information on VAT determination, OSS, reverse charge, B2B handling or German checkout requirements. The captured material contains only a marketing sentence and stops well short of anything a merchant could run tax-correct sales on. 1
The Operations Lead
We found no public information on VAT determination, OSS, reverse charge, VAT-ID validation or the checkout texts German law requires. The all-markets promise does not evidence a single tax mechanic, so I score this at the bottom. 1
The Data Protection Officer
We found no public information on VAT determination, VAT-ID validation with reverse charge, OSS, gross and net display per customer group, or the checkout legal texts German law requires. Nothing captured evidences any of the mandatory elements, which places this at the bottom of the scale. 1
The Skeptic
I found no public information on VAT determination, OSS, B2B reverse charge, VAT-ID validation or the checkout texts German law requires. The vendor's slogan about serving all markets with the right prices says nothing about tax or legal correctness. 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
No public information on themes, an app or plugin ecosystem, APIs, webhooks or headless builds. I cannot tell what a checkout change would cost here, or whether it would mean a rebuild. 1
The B2B Seller
The captured page says nothing about themes, an app or plugin ecosystem, APIs, webhooks, or a headless storefront. We found no public information on any developer surface or extension model, so there is nothing here to judge above the lowest level. 1
The Developer
We found no public information on themes, a template language, apps or plugins, APIs, webhooks, staging or a local development story. As the one who has to keep a shop alive for five years, that silence is the loudest signal here: I cannot even see whether custom work would survive an upgrade. 1
The Operations Lead
We found no public information on themes, an app or plugin ecosystem, a documented API, webhooks or a headless storefront. Nothing on the captured page speaks to developers at all. 1
The Data Protection Officer
We found no public information on themes, an app or plugin ecosystem, APIs, webhooks or headless support — no developer surface appears in the captured pages. 1
The Skeptic
I found no public information on themes, an app or plugin ecosystem, APIs, webhooks, staging or headless builds. Nothing a developer could size or cost is visible in the captured material. 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
I found no public information on order management, stock, shipping integrations, returns or ERP and accounting links — nothing after the buy button is evidenced on the captured pages. 1
The B2B Seller
We found no public information on order management, stock, returns, carrier integrations, or interfaces to ERP and accounting systems. The captured page is a single marketing statement about serving markets, with nothing on what happens after checkout. 1
The Developer
We found no public information on order management, stock, returns, shipping integrations or ERP and accounting links. The positioning statement ends at the storefront and says nothing about what happens after checkout. 1
The Operations Lead
This is what I buy a platform for, and we found no public information on order workflow, stock across channels, partial shipments, carrier integrations with label printing, returns with partial refunds, or ERP interfaces. The positioning is all front-of-house, and the back office goes entirely without evidence. 1
The Data Protection Officer
Nothing captured addresses order management, stock across channels, returns, carrier integrations or interfaces to ERP and accounting systems; we found no public information on any back-office capability. 1
The Skeptic
I found no public information on order management, stock, returns, shipping integrations or links to ERP and accounting systems. What happens after checkout is entirely undocumented in what was captured. 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
No public information on export completeness, self-hosting or hosting choice, or any documented migration path. Whether my catalogue, customers and order history stay mine is entirely unstated. 1
The B2B Seller
We found no public information on export completeness, hosting choice, deletion, or a documented migration path in either direction. Nothing on record lets a merchant judge whether catalogue, customers and order history remain theirs, or what leaving would cost. 1
The Developer
We found no public information on export completeness, hosting choice, self-hosting, deletion or a documented migration path. An exit story that has to be requested in a sales conversation rather than read on a page is, from my seat, itself a lock-in cost. 1
The Operations Lead
We found no public information on export of catalogue, customers or order history, on documented deletion, hosting choice or any migration path. What leaving would cost is unknowable from the public pages. 1
The Data Protection Officer
For a shop holding customers, addresses and buying histories, the captured pages are silent on export completeness, documented deletion, hosting choice and any migration path; we found no public information on data ownership or on what leaving would actually cost. 1
The Skeptic
Nothing captured addresses export completeness, hosting choice, migration paths or what it costs to leave with your own catalogue, customers and order history. I found no public information on data ownership or exit terms — the exit price is invisible, which is exactly the part I read for. 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 vendor name Centra AB reads as a Swedish company form, which suggests an EU contracting entity, and that is the only signal I have. Hosting location, the infrastructure behind it and any subprocessor sitting in the checkout path are not shown on the captured pages. 1
The B2B Seller
The vendor is Centra AB, a Swedish and therefore European contracting entity, which is a genuine structural positive. Beyond that we found no public information on hosting location, named infrastructure, subprocessors in the checkout path, or certifications; no sovereignty attributes are on record. 1
The Developer
We found no public information on where customer and order data is hosted, on the contracting entity's jurisdiction, or on any subprocessor in the checkout path — the captured page is silent on all three. Nothing on the vendor page lets a European buyer place a single link in that chain. 1
The Operations Lead
No sovereignty attributes are on record: we found no public information on hosting location, the contracting entity beyond a Swedish-style corporate name, or any subprocessor list. With hosting unstated and the checkout chain unnamed, there is nothing European or otherwise to verify. 1
The Data Protection Officer
No sovereignty attributes are on record: we found no public information on hosting location, the contracting entity beyond a European-sounding company form, or any subprocessor list. 1
The Skeptic
The vendor appears as Centra AB, a Swedish corporate form pointing to an EU entity, but no sovereignty attributes are on record. I found no public information on where customer and order data are hosted, on the contracting entity in detail, or on any subprocessor list. 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
No prices appear on the captured pages — no tiers, no transaction fees, no term, nothing. As far as public information goes, the annual cost is a sales conversation, not a figure a merchant can sit down and compute. 1
The B2B Seller
The captured page publishes no prices of any kind — no tiers, billing periods, transaction fees, order limits, or VAT treatment. We found no public information from which a merchant could compute an annual cost, so every commercial question is a sales conversation. 1
The Developer
The captured page carries one marketing sentence and no prices of any kind. We found no public information on tiers, billing periods, transaction fees, app costs or terms, so a merchant cannot compute an annual cost from public pages alone. 1
The Operations Lead
We found no public prices at all — no tiers, no transaction fees, no billing period, no minimum term. Every cost here is a sales conversation, the worst case for a merchant budgeting a year. 1
The Data Protection Officer
We found no public information on licence tiers, billing periods, transaction or revenue-share fees, order limits or hosting costs; no headline price appears in the captured pages, so an annual cost is not even approximately computable. 1
The Skeptic
The captured page carries no price of any kind — no licence tier, no transaction fee, no hosting cost, no order limits. I found no public information on pricing, so the real annual invoice is uncomputable from what is public. 1
European sovereignty — proven facts
0 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 | Not determined | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 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 — Data residency. 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 (centra.com, centra.com/privacy, centra.com/security, centra.com/product-information-management-for-fashion-products, centra.com/order-management-system, centra.com/distributed-order-management and 1 more). 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
- 37 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
- 3 integrations 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 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 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
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is 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 (7)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page centra.com Checked 22 Sep 2026 Details →
- 2 Privacy policy — found from the homepage centra.com Checked 30 Sep 2026 Details →
- 3 Security / trust page — found from the homepage centra.com Checked 30 Sep 2026 Details →
- 4 Catalogue & checkout — found from sitemap centra.com Checked 1 Oct 2026 Details →
- 5 Order operations & back office — found from sitemap centra.com Checked 1 Oct 2026 Details →
- 6 Order operations & back office — found from sitemap centra.com Checked 1 Oct 2026 Details →
- 7 Data ownership & exit — found from sitemap centra.com Checked 1 Oct 2026 Details →