0–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? →
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.
Centra at a glance
- Vendor
- Centra AB
- Headquarters
- Not stated on the vendor’s pages as of 1 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Oct 2026
- Panel verdict
- The AI panel rates Centra 2.5/5, the mean of 6 judges. Centra, a fashion-brand commerce platform from Centra AB, scores highest in operations, 7–8: automated order routing and splitting, unlimited warehouses, marketplace intake with overselling protection, BOPIS, BOSS and BORIS flows, in-store returns with a gift-card fallback, and ERP functions built in with third-party synchronisation. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 1 Oct 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Centra, a fashion-brand commerce platform from Centra AB, scores highest in operations, 7–8: automated order routing and splitting, unlimited warehouses, marketplace intake with overselling protection, BOPIS, BOSS and BORIS flows, in-store returns with a gift-card fallback, and ERP functions built in with third-party synchronisation. Catalog and checkout holds at 4 — a built-in PIM for complex fashion products and unlimited markets, currencies and languages, set against a checkout that hands payment to unnamed third-party suppliers. The weakest scores are tax and legal at 0 and data control and exit at 2–3: the rationales report no public information on VAT determination, OSS, reverse charge, invoicing or German checkout requirements, and none on exporting catalogue, customers or order history — only a 'Migrate to Centra' resource aimed at moving in. Sovereignty runs 3–4: EEA data centres in ISO 27001-certified facilities and residency options are stated, while the contracting entity's jurisdiction, a published data-processing agreement and subprocessor exposure remain unknown. Scores sit in narrow bands on every criterion, and the flagged splits list none. The captured pages publish no prices.
Speaks for it
- Operations scores run 7–8, backed by automated order routing, order splitting and unlimited warehouses.
- ERP functionalities are built into the order management system, with synchronisation to a third-party ERP.
- BOPIS, BOSS and BORIS transactions are supported, with in-store returns and a gift-card fallback when the original payment cannot be refunded.
- Open APIs and a headless storefront API are documented, and extensibility scores run 5–6.
- Data centres are stated to sit in ISO 27001-certified facilities within the EEA, with data residency options offered.
Held against it
- Tax and legal scores sit at 0, with the rationales reporting no public information on VAT determination, OSS, reverse charge, invoicing or German checkout requirements.
- Data control and exit scores run 2–3, and the rationales report no public information on exporting catalogue, customers or order history, or on data return at cancellation.
- The checkout hands payment to unnamed third-party suppliers, and the rationales name no payment method such as PayPal, invoice or direct debit.
- Sovereignty scores run 3–4, with the contracting entity's jurisdiction, a published data-processing agreement and subprocessor exposure unknown.
- No prices appear on the captured pages, so an annual cost cannot be computed in advance.
Best for
- You run a fashion or lifestyle brand selling both wholesale and direct-to-consumer and need automated order routing, splitting and return management across both.
- You sell across many warehouses and channels from one virtual assortment and need overselling protection plus in-store pickup and returns.
- You want a built-in PIM for complex fashion products now, with the option to swap in a dedicated product-information system later.
- You have developers who can build storefronts and touchpoints on open APIs and a headless storefront API.
Avoid if
- You sell cross-border into the EU and need VAT determination, OSS or reverse charge settled before purchase; tax and legal scored 0.
- You need a documented exit route — export of catalogue, customers and order history, or self-hosting — before committing; data control and exit scored 2–3.
- Your German shoppers expect named payment methods such as PayPal, invoice or direct debit at checkout; the captured pages document a redirect to unnamed third-party payment suppliers.
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 2 of 5 |
| Extensibility & developer surface | 3 of 5 |
| Order operations & back office | 3.5 of 5 |
| Data ownership & exit | 1 of 5 |
| European sovereignty | 2 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 — Not a shop: no product catalogue and no checkout of its own.
3 — A product catalogue with categories and a checkout that takes payment through at least one provider.
5 — Products with variants, discounts or vouchers, guest checkout, and several payment methods including those German buyers expect (PayPal, invoice or direct debit) through named providers.
8 — Tiered and customer-group pricing, bundles or configurable products, rule-based promotions, per-channel or per-market pricing, abandoned-cart recovery, a checkout customisable without a rebuild, and 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 pages show a built-in product catalogue for complex fashion products and a checkout that redirects to an unnamed third-party payment supplier, plus claims of unlimited markets, currencies and languages and tools for prices and campaigns. But the pages name no payment provider — nothing on PayPal, invoice or direct debit, the methods my German shoppers demand — and show no vouchers, guest checkout or abandoned-cart recovery, so I sit just above the basics. 1 2 4 6
The B2B Seller
A built-in PIM for complex fashion products, a checkout that hands payment to third-party providers, and a positioning claim of serving all markets with the right prices and campaigns give a real catalogue-plus-checkout with a multi-market frame. What a trade buyer looks for — variants, discounts or vouchers, guest checkout, and named payment methods such as PayPal, invoice or direct debit — does not appear on the captured pages, so it reads above a bare shop but below a proven conversion machine. 1 2 4 6
The Developer
A built-in PIM geared to complex fashion products, unlimited markets, currencies and languages, and tools for prices and campaigns are documented, and the privacy policy confirms a checkout that redirects to third-party payment suppliers. We found no public information on variants, discounts or vouchers, guest checkout, or named payment providers such as PayPal, invoice or direct debit, so I hold this between a basic catalogue-plus-checkout and the mid merchandising level. 1 2 4 6
The Operations Lead
The built-in product information system for complex fashion and lifestyle products, price and campaign management, and unlimited markets, currencies and languages put this above a plain catalogue, and the checkout does hand visitors to third-party payment suppliers. What the pages never show is a named payment method — no PayPal, invoice or direct debit — nor guest checkout, so I hold it just under the middle. 1 2 4 6
The Data Protection Officer
The captured pages document a built-in product-information module for complex fashion products and a checkout that hands payment to third-party suppliers, with unlimited markets, currencies and languages claimed. That clears the bar of a catalogue plus a checkout that takes payment. We found no public information on variants, vouchers, guest checkout, or the names of the payment providers German buyers would expect. 1 2 4 6
The Skeptic
A built-in PIM 'geared to handle complex fashion and lifestyle products' plus 'unlimited markets, currencies, languages' give the catalogue real depth, and checkout runs by redirect to third-party payment suppliers. But we found no public information on variants, discounts or vouchers, guest checkout, or which payment providers are actually wired in — the checkout story is thinner than the catalogue story. 1 2 4 6
Tax & German legal correctness
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
VAT determination, OSS, B2B reverse charge, invoicing, and the checkout requirements German law imposes (Button-Lösung, Widerrufsrecht, Preisangabenverordnung) — judged on what the platform documents it does or ships as a maintained extension.
0 — No tax handling at all; prices carry no VAT logic and the merchant calculates tax outside the platform.
3 — VAT rates configurable per country or product, with prices shown gross or net and legal texts placed as pages in the checkout.
5 — VAT by destination country with gross and net display per customer group, B2B with VAT ID and reverse charge, and the German checkout requirements (order button wording, withdrawal policy, price indications) handled by the platform or a named official extension.
8 — VIES validation of VAT IDs, OSS thresholds tracked or OSS reporting data provided, invoices issued from orders with correct content 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 not rated — no public information
We found no public information on VAT determination, OSS, reverse charge, invoicing or the German checkout requirements (order button wording, withdrawal policy, price indications) on the pages we read, which cover the platform, privacy, security, catalogue and order management. 1 2 4 5 6
The B2B Seller not rated — no public information
We found no public information on VAT determination, OSS, B2B reverse charge, VAT-ID validation, invoicing or the German checkout requirements such as order-button wording, withdrawal policy and price indication rules. The homepage and the order-management pages speak to markets and prices but never to VAT logic, which is the first question a finance team selling cross-border will ask. 1 6
The Developer not rated — no public information
We found no public information on VAT determination, OSS, B2B reverse charge, invoicing, or the German checkout requirements around order button wording, withdrawal policy and price indications. The homepage and the catalogue and order-management pages we read say nothing about tax or legal conformity. 1 4 5 6
The Operations Lead not rated — no public information
We found no public information on VAT determination, OSS, B2B reverse charge, invoicing or the German checkout requirements on any of the captured pages, including the privacy, product and order-management pages. 1 2 4 5 6
The Data Protection Officer not rated — no public information
We found no public information on VAT determination, OSS, B2B reverse charge, invoicing, or the German checkout requirements such as order-button wording and price indications. The pages we read — the homepage, catalogue and order-management pages — describe fashion and wholesale workflows, and none of them addresses tax or legal conformity. 1 4 5 6
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 — A closed shop builder: no themes to edit, no apps or plugins and no API.
3 — Themes adjustable in an editor and a set of apps or plugins to add features.
5 — Custom themes with a template language or code access, an app or plugin ecosystem, and a documented API with webhooks for order events.
8 — A storefront API for headless builds, an extension framework with its own lifecycle, staging or development 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
Open APIs and headless API technology with "zero constraints on shop design" are documented, alongside marketplace integrations, third-party ERP synchronisation and the option to swap in a dedicated product information system — that means a storefront and checkout I can reshape without a rebuild, my first requirement. No webhooks, documented rate limits, staging environments or extension lifecycle appear on the pages we read. 6
The B2B Seller
Open APIs to integrate commerce systems and channels, plus a headless storefront API with unlimited markets, currencies and languages and zero constraints on shop design, give Centra a genuine developer surface, and the built-in PIM can be replaced by a dedicated product info system. We found no public information on an app or plugin ecosystem, webhooks for order events, staging environments, theme version control or documented rate limits, so it sits between the levels rather than at the top. 4 6
The Developer
Open APIs, headless API technology promising zero constraints on shop design, touchpoint integrations across web, app, in-store display, PoS, AR/VR and voice, and a built-in PIM that can be swapped for a dedicated system give a genuine developer surface. We found no public information on a plugin architecture, theme version control, local development, staging environments or documented rate limits — the lifecycle features that decide whether five years of customisations survive an upgrade. 4 6
The Operations Lead
Open APIs, a headless storefront API promising zero constraints on shop design, marketplace listing through the standard order flow, and the option to replace the built-in product information system with a dedicated one make this genuinely shapeable. We found no public information on an app or plugin marketplace, webhooks for order events, staging environments or documented rate limits, which keeps it below the top. 4 6
The Data Protection Officer
Open APIs and a headless storefront API are documented, and the built-in product-information module can be swapped for a dedicated system. We found no public information on an app or plugin ecosystem, webhooks, rate limits, staging environments or theme versioning, so the documented developer surface is the API itself. 6
The Skeptic
Headless API technology, open APIs for commerce systems, marketplace listing, and a built-in PIM that can be swapped for a dedicated product system show a genuinely open surface. What we found no public information on is themes or template code, an app or plugin ecosystem, webhooks, staging environments and rate limits — so the real cost of shaping this platform is not visible from these pages. 4 6
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 — No order handling in the product; orders leave as emails or exports to be processed elsewhere.
3 — An order list with statuses, stock counts per product, and shipping rates set up in the shop.
5 — Order management with status emails, stock tracking, named carrier integrations or label printing, and refunds or returns handled in the system.
8 — Partial shipments and partial refunds, multi-warehouse or multi-location stock, multi-channel or marketplace order intake, fulfilment routing, dropshipping, and maintained interfaces to named ERP and accounting systems (DATEV among them for German merchants).
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
After checkout this is substantial: automated order routing, order splitting, shipping, inventory forecasting and reordering, unlimited warehouses, marketplace intake with overselling protection, buy-online-pickup/return-in-store, in-store returns with gift-card fallback, refund and return management across direct-to-consumer and wholesale, with ERP functions built in plus third-party ERP sync. What I miss as a German-facing operator is a named ERP or accounting interface such as DATEV, and explicit partial shipments, partial refunds and dropshipping. 5 6
The B2B Seller
This is where the platform earns its keep: automated order routing, order splitting, inventory forecasting, unlimited warehouses, marketplace and in-store intake with overselling protection across channels, and returns, refunds and in-store returns worked for both wholesale and direct-to-consumer, with a gift-card fallback when the original payment cannot be refunded. The order system ships ERP functionality and can synchronise with a third-party ERP, though no named ERP or accounting system — DATEV among them — appears on the captured pages. 5 6
The Developer
The back office is the strongest part of the evidence: automated order routing and splitting, unlimited warehouses, marketplace order intake, BOPIS/BOSS/BORIS, in-store returns with gift-card fallback, return and refund management for both wholesale and direct-to-consumer, plus ERP functionality built in with synchronisation to third-party ERP systems. We found no public information on named ERP or accounting systems such as DATEV, on partial refunds, or on dropshipping, which is why I sit just under the top of this range. 5 6
The Operations Lead
This is the strongest part: automated order routing and order splitting, unlimited warehouses, marketplace and omnichannel intake with overselling protection on one virtual assortment, return and refund management for both wholesale and direct-to-consumer, in-store returns with a gift-card fallback when the original payment cannot be refunded, and ERP functionality built in with synchronisation to a third-party ERP. I hold back from the top because no ERP or accounting system is named — nothing a German merchant can check against DATEV — and we found no public information on partial refunds, label printing or named carriers. 5 6
The Data Protection Officer
Order operations are the core of the product: automated routing and splitting, multi-warehouse stock with overselling protection, marketplace order intake, in-store returns with a gift-card fallback, tracking emails, and ERP functionality built in with synchronisation to a third-party ERP. For a German merchant the last mile is open — we found no public information on maintained interfaces to named ERP or accounting systems, dropshipping, or partial refunds. 5 6
The Skeptic
Order management is the strongest evidence on offer: automated order routing, order splitting, replenishment and returns routing across stores and warehouses, unlimited warehouses, buy-online-pickup/ship/return-in-store, in-store returns with gift-card fallback, and ERP functionality built in with third-party ERP synchronisation. It stops short of the top level on specifics — we found no public information on named ERP or accounting connectors such as DATEV, dropshipping, or partial refunds. 5 6
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 — The terms state that the merchant's data cannot be exported or is not returned on cancellation.
3 — CSV export of products and customers, or of orders, from the admin.
5 — Export of catalogue, customers and orders documented (CSV, API or dump), with data deletion or return on cancellation stated in the terms or help centre.
8 — Full-fidelity export including media and order documents, a documented migration path in and out, 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
A "Migrate to Centra" resource documents moving in and open APIs exist to connect systems, but no export of catalogue, customers or orders is documented, no self-hosting or hosting choice appears, and nothing states data is returned or deleted on cancellation — the privacy policy's retention note covers personal data generally. For a merchant, the cost of leaving is simply unknown here. 2 6 7
The B2B Seller
The captured pages show a migration resource aimed at moving onto Centra, a retention policy that data is securely removed once no longer needed, and residency options within the EEA, while open APIs exist in principle. We found no public information on documented export of catalogue, customers and order history out of the platform, on self-hosting, or on contractual data return at cancellation — leaving is a matter of trust rather than documentation. 2 6 7
The Developer
The privacy policy commits to keeping data only as long as needed and then securely removing it, and open APIs plus a migrate-to-Centra resource exist — but that is migration in, not out. We found no public information on export of catalogue, customers or orders, on data return or deletion at cancellation, or on any self-hosting or hosting choice, so for a vendor-hosted platform the cost of leaving is unaddressed. 2 6 7
The Operations Lead
Open APIs give a documented route to the data, the privacy policy commits to keeping data only as long as needed or the contract requires and then securely removing it, and the vendor's site carries a migration resource — aimed at moving in. We found no public information on export of the full catalogue, customers and order history, on data return at cancellation, or on hosting choice. 2 6 7
The Data Protection Officer
The pages show a migration resource aimed at moving onto the platform and a privacy policy that removes personal data once it is no longer needed. We found no public information on exporting catalogue, customers or order history, on data return when a contract ends, or on a self-hosting option — for a shop whose value sits in its order history, that is an exit I could not price. 2 7
The Skeptic
Retention is stated as keeping data 'only as long as it is needed' with secure removal afterwards, and there is a 'Migrate to Centra' resource — but that is migration in, not out. We found no public information on export of catalogue, customers or order history, on self-hosting or hosting choice, or on what leaving with your own data costs, which is exactly where the invoice tends to hide. 2 7
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. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain (CDN, analytics, payment routing, support tooling) is unstated or partly non-EU.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessor list published with locations, 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 privacy and security pages state data centres in ISO 27001-certified facilities within the European Economic Area with data residency options and GDPR compliance — one European element proven, in fact hosting stated as standard. The contracting entity, a published data processing agreement and the subprocessor chain, including the unnamed third-party payment suppliers card data is redirected to, are not shown on the captured pages. 2 3
The B2B Seller
The vendor states its data centres sit in ISO 27001-certified facilities within the EEA, offers data residency options, frames compliance around GDPR, and never processes card data itself — checkout hands off to third-party payment suppliers. Contracting entity, ownership and the subprocessor chain are not established on the captured pages, so this is one strongly proven European element with the rest of the chain open. 2 3
The Developer
The vendor states that its data centres sit in ISO 27001-certified facilities within the European Economic Area with data residency options available, and that credit-card data never touches the platform but goes to third-party payment suppliers. We found no public information on the contracting entity's jurisdiction, on a published data-processing agreement, or on subprocessor locations, so only the hosting leg of the chain is proven. 2 3
The Operations Lead
Hosting is the one proven European element: data centres in ISO 27001-certified facilities within the European Economic Area, with data residency options offered, and card details go to third-party payment suppliers rather than being processed in-house. The contracting entity, the subprocessor list and a data processing agreement are not established by the captured pages, so one proven element is all I can credit. 2 3
The Data Protection Officer
Data centres are stated to sit in ISO 27001-certified facilities within the European Economic Area, with data-residency options offered and GDPR compliance claimed, and card data is not processed in-house but redirected at checkout. Everything my shop would need to survive a complaint is still open: we found no public information on the contracting entity's jurisdiction, a published data-processing agreement, or a subprocessor list, and the payment routing is documented only as an unnamed third party. 2 3
The Skeptic
Data centres are stated as located in ISO 27001-certified facilities within the European Economic Area, data residency options are offered, and the vendor states it does not sell personal information. The rest of the chain — the contracting entity's jurisdiction, a published DPA, and the subprocessors sitting in the payment-redirect path — is unstated in what we captured. 2 3
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 public "from" price or one priced tier.
5 — Prices for the main tiers public with the billing period stated and the main inclusions per tier listed.
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 not rated — no public information
We found no public pricing on any page we read — no tiers, no transaction or revenue-share rates, no billing period or minimum term. I judge price against contribution, and here the annual cost cannot even begin to be computed from what is published. 1 2 3 4 5 6 7
The B2B Seller not rated — no public information
We found no public information on licence tiers, transaction or revenue-share fees, order limits, hosting cost, minimum term or VAT treatment on the pages captured; the homepage and the migration comparison page name no figures. For an enterprise platform, that makes the annual cost a sales conversation a merchant cannot compute in advance. 1 7
The Developer not rated — no public information
We found no public information on licence prices, tiers, billing periods, transaction or revenue-share rates, or the cost of extensions. The homepage and the feature and comparison pages we read give no price figures, so a merchant cannot compute an annual cost from public pages. 1 6 7
The Operations Lead not rated — no public information
We found no public information on pricing — no licence tiers, billing period, transaction fees, order limits or hosting costs appear on the homepage or any of the product, order-management and migration pages captured, so no annual cost can be computed from this material. 1 5 6 7
The Data Protection Officer not rated — no public information
We found no public information on licence prices, tiers, billing terms, order limits or transaction fees on any of the captured pages, so a merchant cannot begin to compute an annual cost from what is public. 1 4 5 6 7
The Skeptic not rated — no public information
We found no public information on prices anywhere in the captured pages — no tier pricing, billing period, transaction or revenue-share rates, order limits or extension costs appear on the homepage, product pages or the migration comparison, so a merchant cannot compute an annual cost from this. 1 6 7
European sovereignty — proven facts
0 of 6 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 |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Centra
Is Centra European?
Not determined: the vendor’s pages as captured do not say where Centra is based.
Where does Centra store data?
Not stated on the vendor’s pages as of 1 Oct 2026.
Does Centra have a free plan?
Not stated on the vendor’s pages as of 1 Oct 2026.
What are the best alternatives to Centra?
As of 18 Nov 2026, the panel rates JTL-Shop (3.5/5), Saleor (3/5) and Shopware (3/5) highest among the other 28 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, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Centra alternatives.
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 processing agreement, Hosting location, Hosting options. 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
- 3 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 (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 →