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