Transparency alternatives to ChannelEngine
Other Ecommerce platforms vendors we measure, sorted by how much they publish that ChannelEngine does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 42 that differ from ChannelEngine on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ChannelEngine has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and ChannelEngine does not” is the one that closes them.
| Vendor | Score | Publishes, and ChannelEngine does not | ChannelEngine publishes, and they do not | |
|---|---|---|---|---|
| Saleorsaleor.io | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Status page with history, Certifications named | Compare |
| Shopifyshopify.com | 70/100 | 5 Data processing agreement, No third-party tracking before consent, security.txt (RFC 9116), +2 | nothing | Compare |
| Lightspeedlightspeedhq.com | 70/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | nothing | Compare |
| commercetoolscommercetools.com | 52/100 | 4 Data processing agreement, Subprocessor list, Notice before subprocessors change, +1 | 2 Status page with history, Public pricing | Compare |
| Gumroadgumroad.com | 52/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 2 Status page with history, Certifications named | Compare |
| Swellswell.is | 52/100 | 2 Data processing agreement, Notice before subprocessors change | 1 Certifications named | Compare |
| Volusionvolusion.com | 35/100 | 2 Data location stated, Uptime SLA with a figure | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Payhippayhip.com | 27/100 | 2 Data location stated, Named privacy contact | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | Compare |
| OXID eSalesoxid-esales.com | 26/100 | 2 security.txt (RFC 9116), Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Shopwareshopware.com | 26/100 | 2 Data processing agreement, security.txt (RFC 9116) | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | Compare |
| Fabricfabric.inc | 9/100 | 2 Uptime SLA with a figure, Named privacy contact | 4 Status page with history, Public pricing, Certifications named, +1 | Compare |
| Shoplazzashoplazza.com | 38/100 | 1 Data location stated | 1 Status page with history | 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.