Transparency alternatives to OXID eSales
Other Ecommerce platforms vendors we measure, sorted by how much we found at them and not at OXID eSales. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from OXID eSales on at least one criterion we measured for both. Public transparency score, not a product or security rating.
OXID eSales has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at OXID eSales” is the one that closes them.
| Vendor | Score | Found there, not found at OXID eSales | Found at OXID eSales, not found there | |
|---|---|---|---|---|
| Saleorsaleor.ioSee also Transparency alternatives to Saleor | 74/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 1 security.txt (RFC 9116) | Compare |
| Lightspeedlightspeedhq.comSee also Transparency alternatives to Lightspeed | 70/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | 1 security.txt (RFC 9116) | Compare |
| Shopifyshopify.comSee also Transparency alternatives to Shopify | 70/100 | 5 Data processing agreement, Status page with history, Certifications named, +2 | nothing | Compare |
| commercetoolscommercetools.comSee also Transparency alternatives to commercetools | 52/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Gumroadgumroad.comSee also Transparency alternatives to Gumroad | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Swellswell.isSee also Transparency alternatives to Swell | 52/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Volusionvolusion.comSee also Transparency alternatives to Volusion | 35/100 | 3 Data location stated, Status page with history, Uptime SLA with a figure | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Ecwidecwid.comSee also Transparency alternatives to Ecwid | 36/100 | 2 Status page with history, Certifications named | nothing | Compare |
| BigCommercebigcommerce.comSee also Transparency alternatives to BigCommerce | 35/100 | 2 Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Shoplazzashoplazza.comSee also Transparency alternatives to Shoplazza | 35/100 | 2 Data location stated, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| ChannelEnginechannelengine.comSee also Transparency alternatives to ChannelEngine | 30/100 | 2 Status page with history, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Vendurevendure.ioSee also Transparency alternatives to Vendure | 35/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.