SaaS Ranking

Alternatives to Koerber

Other Warehouse management vendors we measure, sorted by how much they publish that Koerber does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 27 that differ from Koerber on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Koerber has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, 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 “publishes and Koerber does not” is the one that closes them.

VendorScorePublishes, and Koerber does notKoerber publishes, and they do not
EasyEcomeasyecom.io 52/100 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 1 security.txt (RFC 9116) Compare
Fulfil.iofulfil.io 39/100 3 Status page with history, Certifications named, HTTPS enforced with HSTS 1 Named privacy contact Compare
Infoplusinfopluscommerce.com 35/100 3 Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS 2 security.txt (RFC 9116), Named privacy contact Compare
3PL Warehouseware2go.co 22/100 3 Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS 3 Data location stated, security.txt (RFC 9116), Named privacy contact Compare
Generixgenerixgroup.com 30/100 2 Uptime SLA with a figure, HTTPS enforced with HSTS 1 security.txt (RFC 9116) Compare
Logiwalogiwa.com 30/100 2 Certifications named, HTTPS enforced with HSTS 1 security.txt (RFC 9116) Compare
AutoStoreautostoresystem.com 22/100 2 Status page with history, HTTPS enforced with HSTS 2 Data location stated, security.txt (RFC 9116) Compare
Balloon Oneballoonone.com 17/100 2 Public pricing, HTTPS enforced with HSTS 3 Data location stated, security.txt (RFC 9116), Named privacy contact Compare
Geek+geekplus.com 26/100 1 HTTPS enforced with HSTS 1 security.txt (RFC 9116) Compare
Element Logicelementlogic.net 22/100 1 HTTPS enforced with HSTS 2 security.txt (RFC 9116), Named privacy contact Compare
Dematicdematic.com 13/100 1 HTTPS enforced with HSTS 2 Data location stated, security.txt (RFC 9116) Compare
Exotecexotec.com 13/100 1 HTTPS enforced with HSTS 2 Data location stated, 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.