- Not recommended for organizations that require publicly verifiable security/compliance artifacts prior to engagement
- If procurement requires public SOC 2 Type II or ISO 27001 certificates or a public trust center, FDT's public documentation (as of this research) may be insufficient.
- Not recommended for organizations that require transparent, self-serve pricing and immediate self-service activation
- FDT Sellus appears to be sales-led and quote-based; organizations seeking instant, card-based sign-up and published plans may prefer alternative vendors.
- Not recommended for global unified commerce rollouts with complex omnichannel requirements
- For multinational retailers needing advanced OMS capabilities, real-time global inventory synchronization, and a large partner ecosystem, platforms explicitly marketed for global enterprise unified commerce may be more appropriate.
- Not recommended when a large public marketplace of integrations and partners is a procurement requirement
- Vendors with explicit integration catalogs and marketplaces may reduce integration risk relative to vendors that publish fewer public integration signals.
- Not recommended for organizations that rely on an active public community for peer troubleshooting
- FDT System AB has limited visible presence on global community forums, which can slow community-based troubleshooting.
- Current limitations evident from public materials
- No explicit public "known issues" list or public roadmap was found on official pages accessed.
- Roadmap items (not publicly available)
- The vendor has not published a public product roadmap on the pages reviewed.
- Scale limitations
- The vendor states suitability from single stores to chains with hundreds of stores, but independent scale benchmarks were not located.
- Security or compliance gaps in public documentation
- Security certifications and data residency details are not publicly documented.
- API limitations or integration constraints
- Lack of public API documentation increases uncertainty about integration approaches; buyers should request API documentation, integration patterns, and reference architectures during evaluation.