Transparency alternatives to Kewill
Other Trade compliance vendors we measure, sorted by how much we found at them and not at Kewill. This is a comparison of disclosure, not of features or fitness.
12 shown of 26 that differ from Kewill on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kewill has 9 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, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Kewill” is the one that closes them.
| Vendor | Score | Found there, not found at Kewill | Found at Kewill, not found there | |
|---|---|---|---|---|
| Zonoszonos.comSee also Transparency alternatives to Zonos | 43/100 | 4 Data location stated, Status page with history, Certifications named, +1 | 1 No third-party tracking before consent | Compare |
| AEBaeb.comSee also Transparency alternatives to AEB | 39/100 | 3 Data processing agreement, Status page with history, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Scoperiege.comSee also Transparency alternatives to Scope | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| MIC Customsmic-cust.comSee also Transparency alternatives to MIC Customs | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Customs4tradecustoms4trade.comSee also Transparency alternatives to Customs4trade | 26/100 | 3 Status page with history, Certifications named, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| ImportGeniusimportgenius.comSee also Transparency alternatives to ImportGenius | 22/100 | 2 Public pricing, Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Cargowisewisetechglobal.comSee also Transparency alternatives to Cargowise | 22/100 | 1 Notice before subprocessors change | 1 No third-party tracking before consent | Compare |
| e2opene2open.comSee also Transparency alternatives to e2open | 17/100 | 1 Named privacy contact | 1 No third-party tracking before consent | Compare |
| OCR Servicesocr-inc.comSee also Transparency alternatives to OCR Services | 13/100 | 1 Named privacy contact | 2 No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Nexus Tradenexustrade.ioSee also Transparency alternatives to Nexus Trade | 9/100 | 1 Public pricing | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| Trademotrademo.comSee also Transparency alternatives to Trademo | 4/100 | 1 Named privacy contact | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | Compare |
| BDP Smartbdpsmart.comSee also Transparency alternatives to BDP Smart | 17/100 | nothing we found there and not here | 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.