E-Commerce Platforms & Shop Systems
SCAYLE
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by SCAYLE Commerce GmbH · scayle.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.
SCAYLE at a glance
- Vendor
- SCAYLE Commerce GmbH
- 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 SCAYLE 2/5, the mean of 6 judges. SCAYLE Commerce GmbH earns its best marks on operations: distributed order management across channels, locations and fulfilment centres, basket splitting with routing by location, merchant priority and stock, virtual stock updated in real time across shops and warehouses, auto-failover, and refunds handled in-system. 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
SCAYLE Commerce GmbH earns its best marks on operations: distributed order management across channels, locations and fulfilment centres, basket splitting with routing by location, merchant priority and stock, virtual stock updated in real time across shops and warehouses, auto-failover, and refunds handled in-system. Extensibility scores 6 for a headless backend with fast APIs and extensive SDKs; catalog and checkout spans 4-6 on any-PSP payment freedom and currency and language localisation, with no public information on variants, tiered pricing or named payment methods. The weak side is uniform: tax and legal scores 1-2, with no public information on VAT determination, OSS or German checkout requirements; data control and exit sits at 1, its only migration figures describing moves in — 91% live within 12 months, 100% under 15 months, 0% of projects fail; sovereignty scores 0-1, with AWS named as host and no region, jurisdiction or subprocessor list stated. The flagged splits report none; score ranges span at most two points: a strong back office documented over thin legal, exit and sovereignty evidence. No prices appear on the captured pages.
Speaks for it
- Distributed order management spans channels, locations and fulfilment centres, with basket splitting and dynamic routing by location, merchant priority and stock availability
- Virtual stock is updated in real time across shops and warehouses, with auto-failover for reliable fulfilment
- Any payment service provider integrates into the checkout, or the vendor's own payment solution covers authorisation, capture and refunds in one lifecycle
- A headless backend with fast APIs and extensive SDKs supports independent frontend development per device, market and audience
- Refunds and returns run in-system, with automated rules in the admin panel, manual in-store refunds and a traffic-light flag for repeat returners
Held against it
- We found no public information on VAT determination, OSS, reverse-charge handling or the checkout texts German law requires
- We found no public information on export of catalogue, customers or order history; the published migration figures (91% live within 12 months, 100% under 15 months, 0% fail) describe moving in, not out
- The captured pages name AWS as host with no region stated, and jurisdiction of the legal entity, ownership, data residency and subprocessors are all marked unknown
- We found no public information on variant handling, tiered or customer-group pricing, guest checkout, or named payment methods such as invoice and direct debit
- We found no public information on named carrier integrations with label printing, dropshipping flows, or maintained interfaces to ERP and accounting systems
Best for
- You run orders across multiple channels, locations and fulfilment centres and need real-time stock and dynamic routing — operations scored 7-8, the high point of the verdict
- Your team plans to build and own its storefronts — the headless backend with fast APIs and extensive SDKs scored 6 on extensibility
- You want payment-provider freedom at checkout, with any PSP integrating and the vendor's own payment solution as an alternative
- You are migrating onto a new platform and value published timelines — 91% of customers go live within 12 months and 100% of migrations complete under 15 months
Avoid if
- You sell B2B across the EU and need VAT determination, reverse-charge and net-price display by customer group evidenced before signing — tax and legal scored 1-2
- You must be able to price your exit — data control and exit scored 1, and the judges found no public information on export of catalogue, customers or order history
- Your compliance review requires confirmed data residency and a subprocessor list — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Catalogue & checkout | 3 of 5 |
| Tax & German legal correctness | 0.5 of 5 |
| Extensibility & developer surface | 3 of 5 |
| Order operations & back office | 3.5 of 5 |
| Data ownership & exit | 0.5 of 5 |
| European sovereignty | 0.5 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 checkout comes as a module with any-PSP flexibility built in, a rule engine that can switch payment methods by basket value, and currency and language localisation, all on a decoupled front end I could reshape without a rebuild — that is the part I care about most. But I found no public information on the variant matrix, tiered or customer-group pricing, guest checkout, or the methods a German shopper expects like invoice and direct debit, and promotions appear only as a module name with no rule detail shown. Strong plumbing, unproven merchandising depth. 5 6 7 9
The B2B Seller
The money side of checkout is well evidenced: any payment service provider integrates into the checkout alongside the vendor's own payment solution, a rule engine deactivates payment methods by basket amount, and currency and language localise across the frontend with a click. On the trade side, however, we found no public information on variants, tiered or customer-group price lists, guest checkout, or named payment methods such as invoice and direct debit — and a shop that cannot show a trade customer a net price has not met the trade customer. 5 6 7 9
The Developer
The payments story is genuinely open: any payment service provider integrates into the checkout, an in-house payment option covers the authorise-capture-refund lifecycle, and a rule engine can switch payment methods by basket value. Promotions, vouchers, gift cards, subscriptions and currency and language localisation are all named on the captured pages, alongside bundle and buybox frontend modules. The product-data half is a blank — I found no public information on variant matrices, tiered or customer-group pricing, guest checkout or conversion features like abandoned-cart recovery — so I can only credit the half I can see. 5 6 9
The Operations Lead
Promotions, vouchers and gift cards are named modules, currency and language localise per frontend, and any payment service provider can be integrated into the checkout, which is real checkout flexibility. But no payment method is ever named, and we found no public information on a variant matrix, tiered or customer-group pricing, guest checkout or abandoned-cart recovery, so I cannot place it higher. 5 6 9
The Data Protection Officer
Payment flexibility is the strongest documented asset: any payment service provider can be wired into the checkout, or the vendor's own payment solution covers authorisation, capture and refunds in one lifecycle, with currency and language localisation and promotions governed by a rule engine that can even switch payment methods by basket amount. We found no public information on variant matrices, tiered or customer-group pricing, guest checkout, or German staples such as invoice and direct debit; bundles appear only as a storefront module. 5 6 9
The Skeptic
Checkout, promotions, vouchers, one-click currency and language localisation and any-PSP integration are all evidenced, and a bundles module ships. But we found no public information on variant handling, tiered or customer-group pricing, guest checkout, or named payment methods such as invoice and direct debit — the conversion-critical basics go unaddressed on the captured pages, and I would want that risk priced before signing. 5 6 9
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
The only German-legal item the captured pages show is the double opt-in procedure for newsletters. I found no public information on VAT determination, OSS, reverse charge, VAT-ID validation, gross and net display per customer group, or the legal texts the checkout must carry. For a platform pitching a launch across 200 countries, that silence is expensive for me. 3
The B2B Seller
We found no public information on VAT determination, VAT-ID validation, reverse charge, OSS, gross and net display per customer group, or the checkout legal texts German law requires; the only adjacent facts are automated invoice creation and double opt-in for newsletters. For a B2B programme across the EU this is the criterion that decides the deal, and the captured pages are silent on all of it. 3 9
The Developer
I found no public information on VAT determination, per-country rates, VAT-ID validation or reverse charge, OSS reporting, or e-invoicing formats. The only legal-adjacent items the pages evidence are automated invoice creation and a correctly implemented double opt-in for newsletters. Judged on what the platform itself does rather than what a partner could add, that is hygiene, not tax correctness. 3 9
The Operations Lead
Automated invoice creation is mentioned alongside order communication, and the privacy policy describes the double opt-in procedure for newsletters, but that is the whole of the legal story on the captured pages. We found no public information on VAT determination, OSS reporting, VAT-ID validation with reverse charge, gross and net display per customer group, or the checkout elements German law requires. 3 9
The Data Protection Officer
The only German-legal machinery in evidence is a double opt-in for newsletter consent and automated invoice creation; on VAT determination by destination and customer type, VAT-ID validation with reverse charge, OSS and the mandatory checkout elements we found no public information. Invoicing is presented as an automation convenience, with nothing on which invoice cases are covered or which e-invoicing formats are supported. 3 9
The Skeptic
We found no public information on VAT determination by destination or customer type, OSS, reverse-charge handling, XRechnung or ZUGFeRD, or the mandatory German checkout elements such as order-button wording and withdrawal policy. The only compliance signals are a double opt-in for newsletters and automated invoice generation, neither of which is tax or checkout-legality correctness. 3 9
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
Headless is the pitch and the pages back it: fast APIs, extensive SDKs, integrated third-party services, and front ends I can build independently for any device, market and audience. But I found no public information on an app or plugin ecosystem, webhooks, staging environments, version control, documented rate limits, or a local development story. I can build the shop I want; I cannot see what it costs to keep a team owning it. 6 7 9
The B2B Seller
The headless backend with fast APIs, extensive SDKs and decoupled frontend development for any device, market or audience is a real developer surface, and order events from confirmation through returns to delivery and payment synchronise by API in real time. But we found no public information on an app or extension ecosystem, staging environments, theme version control or documented rate limits, and the pages state that security and performance controls are handled in the vendor backend. 6 7 9
The Developer
The headless story is real and stated twice: a decoupled backend with fast APIs, extensive SDKs, and frontend development unconstrained by device, market or audience — that is a surface a team can build a storefront on. But everything I need to run a shop for five years goes unmentioned: I found no public information on a local development environment, version control for themes, an extension framework with its own lifecycle or dependency model, documented rate limits, or how upgrades treat custom frontends. The backend is also described as keeping security and performance controls on the vendor's side, so I stop scoring at the API layer. 6 7
The Operations Lead
A decoupled headless backend with fast APIs, extensive SDKs and realtime order, return, delivery and payment synchronisation is exactly the surface I want feeding fulfilment. We found no public information on an app or extension ecosystem, staging environments, documented rate limits or a local development story, so it falls short of a platform a team can fully own. 6 7 9
The Data Protection Officer
Headless is the pitch: fast APIs, extensive SDKs and a decoupled architecture that lets frontends be built independently per device, market and audience, with order, return, delivery and payment status synced in real time. We found no public information on an extension lifecycle, staging environments, version control, documented rate limits or a local development story, so the cost of shaping the shop to the business stays unquantified. 6 7 9
The Skeptic
Headless is real and well evidenced: fast APIs, extensive SDKs, decoupled frontends per touchpoint, ready-made modules, and order and payment status synchronised in real time. But everything that determines the cost of owning the build is unevidenced — we found no public information on an app or plugin ecosystem, webhooks, staging environments, documented rate limits, a local development story, or source availability. 6 7 9
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
This is the strong suit: distributed order management across channels, locations and fulfilment centres, dynamic routing on location, merchant priority and stock, auto-failover, real-time virtual stock across all shops and warehouses, automated invoicing and customer communication, and refunds and returns worked into the system with conditions set in the admin panel. What I found no public information on is supplier and dropshipping flows and maintained interfaces to named ERP or accounting systems. The back office is clearly real; the ERP seam is invisible. 5 8 9
The B2B Seller
The order side is genuinely enterprise: distributed order management across channels, locations and fulfilment centres, basket splitting with routing by location, merchant priority and stock availability, virtual stock updated in real time across shops and warehouses, automated refunds configured in the admin panel, and a service suite where agents place and edit orders. We found no public information on named carrier integrations with label printing or maintained interfaces to named ERP and accounting systems, which is what I would need before wiring this into a client's books. 5 8 9
The Developer
This is the strongest part of the record: distributed order management across channels, locations and fulfilment centres, virtual stock updated in real time across shops and warehouses, basket splitting with routing by location, merchant priority and availability, auto-failover, and a returns flow covering automated refunds, in-store refunds and a traffic-light flag for serial returners. The service suite can place and edit orders directly and every step from confirmation to return syncs by API with real-time status updates. I found no public information on named carrier integrations with label printing, supplier or dropshipping flows, or maintained interfaces to named ERP and accounting systems, which is what holds this below the top band. 5 8 9
The Operations Lead
This is where the words go: distributed order management across channels, locations and fulfilment centres, a virtual stock per shop updated in realtime, basket splitting with dynamic routing by location, merchant priority and availability, auto-failover, and refunds worked through a payment lifecycle with automatic rules, manual in-store processing and a traffic-light flag for serial returners. What the pages do not show is the layer I need before trusting a shop with December: no carrier is named, label printing is never mentioned, and we found no public information on interfaces to ERP or accounting systems, dropshipping flows, or partial refunds as distinct from refund processes in general. 5 8 9
The Data Protection Officer
Life after checkout is genuinely worked: distributed order management across channels, locations and fulfilment centres, dynamic routing by location, merchant priority and stock availability, virtual real-time stock per shop with warehouse coordination, auto-failover, and returns and refunds in the system including automated refund rules and returns for vouchers and gift cards. We found no public information on maintained interfaces to named ERP or accounting systems, on supplier and dropshipping flows, or on partial refunds. 5 8 9
The Skeptic
The back office is the strongest part of the record: multi-channel order intake, distributed order management, basket splitting with routing by location, merchant priority and stock, real-time virtual stock across shops and warehouses, automated and in-store refunds, and a traffic-light system for repeat returners. What we found no public information on is named carrier integrations with label printing, dropshipping or supplier flows, and maintained interfaces to specific ERP and accounting systems. 5 8 9
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
The only migration evidence points inward — statistics about coming to the platform, not leaving it. I found no public information on export of catalogue, customers or order history, documented deletion, self-hosting, or any data-return commitment, and the platform runs on the vendor's AWS hosting. An exit I cannot price is an exit I would be negotiating blind. 6 10
The B2B Seller
The only migration facts published describe moving merchants in — 91% go live within 12 months, 100% of migrations complete under 15 months, 0% of projects fail — while we found no public information on leaving: on export of catalogue, customers or order history, on deletion, or on any outbound migration path. Hosting sits with the vendor on AWS, and no alternative was evidenced. 6 10
The Developer
The only migration evidence in the captured pages points inwards: 91% of customers go live within twelve months and every migration finishes under fifteen months. For leaving, I found no public information on export completeness for catalogue, customers or order history, no self-hosting option — hosting is AWS with security and performance controls kept in the vendor's backend — and no documented path in either direction. An operator planning five years out should note that exit is neither priced nor described on anything captured. 6 10
The Operations Lead
The only migration evidence is inbound — 91% of customers go live within 12 months — and nothing on the captured pages describes exporting catalogue, customers or order history, deletion, or a documented path out. We found no public information on export completeness, self-hosting or contractual data return. 10
The Data Protection Officer
The shop runs on the vendor's AWS hosting, and the only exit-adjacent figures describe moving merchants in — ninety-one percent live within twelve months, all migrations under fifteen months — with nothing on leaving. We found no public information on export completeness for catalogue, customers and order history, on documented deletion, or on any data-return commitment, so the catalogue and order history remain the vendor's to keep. 6 10
The Skeptic
The only migration facts on record describe bringing merchants onto the platform — the under-15-months and zero-failure figures are an entry pitch, not an exit path. We found no public information on export of catalogue, customers or order history, and hosting is the vendor's AWS operation with backend controls handled on the vendor side, so the cost of leaving is a negotiation rather than a published term. 6 10
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 captured pages name AWS as the host without stating where data resides, the contracting entity's jurisdiction is not confirmed on the vendor's own captured pages, and I found no public information on subprocessors. A double opt-in in the privacy policy is the only European signal I can see. What a German merchant's compliance officer needs to review, I could not find. 2 6
The B2B Seller
The sovereignty picture is unconfirmed end to end: the captured pages leave the contracting entity's jurisdiction, ownership and data residency unknown, AWS is named as host without a region, and we found no public information on subprocessors in or near the checkout path. A privacy policy with double opt-in is a courtesy, not an answer to where customer and order data sit and who processes them. 3 6
The Developer
The sovereignty record is empty: the contracting entity's jurisdiction is not confirmed on the vendor's own captured pages, and ownership, data residency and the subprocessor list are all unstated. The only hosting statement is AWS chosen for scalability, with no region named, so nothing published lets me place customer or order data in Europe or name who sits in the checkout chain. 2 6
The Operations Lead
Every sovereignty attribute is marked unknown: the captured pages give no confirmed contracting-entity jurisdiction, no data residency beyond the host name AWS with no region stated, and no subprocessor list. With nothing on the pages evidencing EU processing of customer and order data, this sits at the bottom of the band. 2 6
The Data Protection Officer
The compliance file stays empty: jurisdiction of the contracting entity, ownership, data residency and subprocessor exposure are all unconfirmed on the captured pages, and hosting is AWS with no region stated. We found no public information on subprocessors, or on where the CDN, analytics or payment routing sit — the first question I would ask for a checkout this full of third parties. 3 6
The Skeptic
Everything a buyer would need to verify here goes unstated on the captured pages: the legal entity's jurisdiction is not confirmed, hosting is described only as AWS with no region named, and no subprocessor list is published. The GmbH in the vendor's name suggests Germany, but suggestion is not evidence, and nothing states where customer and order data actually live. 2 6
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
I found no public information on licence cost, tiers, transaction or revenue-share fees, order or GMV limits, hosting or extension pricing — not a single figure on any captured page. With no figures public, the price is a sales conversation by necessity, and I cannot weigh contribution against cost at all. Zero, with confidence. 1 9
The B2B Seller
We found no public prices at all on the captured pages — no public information on tiers, transaction or revenue-share fees, order limits, implementation or hosting costs, so the annual invoice is unknowable without a sales conversation. The only figures published are migration statistics, and every one of them is a timeline rather than a price. 1 9 10
The Developer
No price appears in the captured pages — no licence tiers, no transaction or revenue-share rates, no implementation or hosting costs, no VAT treatment or minimum term. What is published reads as enterprise-sales material with migration statistics rather than numbers, so the annual cost is a conversation, not a computation a merchant can do from the pages alone. 1 10
The Operations Lead
No price appears anywhere: no licence tiers, no transaction or revenue-share rates, no hosting or module costs, and no VAT treatment or minimum term. For an enterprise order-management platform presented this way, the annual cost is only available through a sales conversation, which matches the lowest band exactly. 1 9
The Data Protection Officer
We found no public prices at all — no licence tiers, transaction or revenue-share rates, implementation or hosting costs; the pages sell enterprise migrations with timeline statistics rather than figures. No annual cost can be computed from them, and every number appears to come from a sales conversation. 1 10
The Skeptic
No price of any kind appears on the captured pages — no licence tier, no transaction or revenue-share rate, no hosting line item, nothing on what the modules, the platform or the vendor's own payment solution cost. From public information alone the annual invoice is unknowable, which is exactly the situation the buyer should fear. 1 4 5 6 9
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 ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about SCAYLE
Is SCAYLE European?
Not determined: the vendor’s pages as captured do not say where SCAYLE is based.
Where does SCAYLE store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does SCAYLE have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to SCAYLE?
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: SCAYLE 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.
- Weak sourcing — Legal entity. 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 could not confirm any pricing 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
- 44 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
- 9 compliance 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
- 6 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 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 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
- 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 (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page scayle.com Checked 13 Oct 2026 Details →
- 2 Imprint — found from the homepage www.scayle.com Checked 13 Oct 2026 Details →
- 3 Privacy policy — found from the homepage www.scayle.com Checked 13 Oct 2026 Details →
- 4 Catalogue & checkout — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →
- 5 Catalogue & checkout — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →
- 6 Extensibility & developer surface — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →
- 7 Extensibility & developer surface — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →
- 8 Order operations & back office — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →
- 9 Order operations & back office — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →
- 10 Data ownership & exit — found from sitemap www.scayle.com Checked 13 Oct 2026 Details →