- If you require formal, publicly documented security certifications
- If your procurement process mandates SOC 2 Type II / ISO 27001 documentation up front, SelMatic may not meet expectations based on publicly available materials.
- If you are seeking a cloud-native SaaS ERP with minimal infrastructure involvement
- SelMatic’s technical requirements indicate an on-prem/server-oriented system with a specific database (Firebird) and OS guidance.
- If you need global, multi-country compliance out of the box
- SelMatic appears optimized for Bulgaria and nearby markets; multinational compliance breadth is unclear.
- If you rely heavily on public peer-review platforms
- Lack of strong public review presence on G2/TrustRadius/Gartner Peer Insights makes it harder to benchmark sentiment and common pain points.
- If you want standardized implementation with low customization
- SelMatic’s main differentiation is customization; if the goal is to adopt standardized processes, a more standardized ERP may reduce long-term maintenance burden.
- Public roadmap and feature timelines
- No public roadmap with dates found.
- Scale limitations
- Not explicitly defined in public materials.
- Technical requirements suggest performance sensitivity to virtualization and server resource allocation.
- Security/compliance gaps
- Certifications and enterprise IAM features are not clearly documented publicly.
- API limitations
- API is mentioned, but public developer documentation, rate limits, authentication standards, and integration patterns are not clearly presented in accessible sources.