Transparency alternatives to Ehrhardt Partner
Other Warehouse management vendors we measure, sorted by how much we found at them and not at Ehrhardt Partner. This is a comparison of disclosure, not of features or fitness.
12 shown of 45 that differ from Ehrhardt Partner on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Ehrhardt Partner has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Ehrhardt Partner” is the one that closes them.
| Vendor | Score | Found there, not found at Ehrhardt Partner | Found at Ehrhardt Partner, not found there | |
|---|---|---|---|---|
| EasyEcomeasyecom.ioSee also Transparency alternatives to EasyEcom | 52/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 1 security.txt (RFC 9116) | Compare |
| Balloon Oneballoonone.comSee also Transparency alternatives to Balloon One | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Datapel WMSdatapel.comSee also Transparency alternatives to Datapel WMS | 30/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Fulfil.iofulfil.ioSee also Transparency alternatives to Fulfil.io | 30/100 | 3 Data location stated, Status page with history, Certifications named | 1 Named privacy contact | Compare |
| Generixgenerixgroup.comSee also Transparency alternatives to Generix | 30/100 | 3 Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Logiwalogiwa.comSee also Transparency alternatives to Logiwa | 30/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Flowspaceflow.spaceSee also Transparency alternatives to Flowspace | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Locus Roboticslocusrobotics.comSee also Transparency alternatives to Locus Robotics | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Infoplusinfopluscommerce.comSee also Transparency alternatives to Infoplus | 22/100 | 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Canary7canary7.comSee also Transparency alternatives to Canary7 | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| CognitOpscognitops.comSee also Transparency alternatives to CognitOps | 26/100 | 2 Data location stated, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Geek+geekplus.comSee also Transparency alternatives to Geek+ | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 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.