- Company sizes or stages where this product is overkill or insufficient
- Very small shippers with infrequent ocean shipments may find onboarding and process change overhead outweigh benefits unless compelled by a specific regulatory requirement or trading corridor.
- Industries or use cases where competitors may be a closer fit
- Organizations that require tightly integrated, multi-bank trade finance portals may prefer vendors with deeper trade finance modules.
- Teams that require a broad logistics execution and visibility suite in a single vendor may find other vendors more suitable.
- Technical requirements that this product may not meet
- Strict data residency requirements in a single jurisdiction may be difficult to reconcile with an architecture that uses public blockchain anchoring and distributed storage unless the vendor provides specific architectural and contractual controls.
- Budget constraints that make alternatives more appropriate
- High-volume senders may prefer flat enterprise licensing from alternatives if per-document fees would be material.
- Specific workflows or integrations where the product falls short
- If an organization's trading ecosystem is committed to a different eBL network with limited interoperability in production, adopting this product may add dual-network complexity.
- Red flags in the buying process
- If the vendor cannot provide requested security documentation (SOC/ISO, pen test summaries, DPA, subprocessors) within the buyer’s security review timeline, consider this a procurement red flag.
- Current limitations acknowledged by the vendor
- Not all documents have the same blockchain support
- The vendor differentiates between documents that are recorded on-chain with transfer-of-ownership semantics, documents recorded only for authenticity, and documents processed off-chain with a digital trail. Buyers must map document types to required legal and operational properties.
- Hard-copy needs remain for some workflows
- The vendor notes that printing for customs, banks, or insurers may still be required in practice.
- Features on the roadmap (not publicly dated)
- No explicit public roadmap with release dates was located in the reviewed sources.
- Scale limitations (at what volume/size does it break down?)
- No explicit public limits on document size, transaction throughput, or API rate limits were surfaced. Given the dependence on blockchain transactions at transfer time, procurement teams should test performance and cost at expected peak volumes.
- Security or compliance gaps
- Absence of clearly published SOC 2 / ISO certification statements in publicly accessible material may be a blocker for some regulated enterprises.
- API limitations or integration constraints
- Developer documentation indicates specific webhook action types for eBL; procurement and integration teams should validate that the available API and eventing model meet their end-to-end automation requirements.