- Company sizes or stages where this product is overkill or insufficient
- The product may be over-provisioned for micro-retailers needing only basic checkout, simple inventory, and basic reporting.
- Industries or use cases where competitors are clearly superior
- Restaurant/hospitality operations often benefit from restaurant-specific POS platforms.
- Direct-to-consumer-first brands may prefer a commerce-first stack such as Shopify.
- Technical requirements that this product may not meet
- Organizations requiring fully SaaS-native APIs and no legacy components should validate the Web API architecture (noting the 32-bit service detail in public documentation) and confirm fit with IT requirements.
- Budget constraints that make alternatives more appropriate
- Organizations with tight budgets and simpler requirements may prefer Square, Shopify POS, Lightspeed, or other lower-entry-cost options.
- Specific workflows or integrations where the product falls short
- If a procurement requires support for a specific payments/POS ecosystem (for example, certain integrations cited as unavailable by some reviewers), that can be a deciding factor.
- Procurement cautions
- If pricing and scope are not documented in writing (modules, support, hosting, upgrades), request a detailed SOW and TCO model as part of procurement.
- Current limitations acknowledged by the vendor
- Vendor documentation indicates partial modernization (for example, improved display scaling in some areas) while other interface assets remain legacy, suggesting an incremental UI modernization approach.
- Features on the roadmap (not yet available)
- No public, dated roadmap was located in the reviewed sources.
- Scale limitations (at what volume/size does it break down?)
- No public benchmark data or explicit scale limits were found.
- Security or compliance gaps
- Lack of clearly published security attestations (SOC 2/ISO) is a procurement gap for security-sensitive buyers.
- Technical debt or architectural limitations mentioned in reviews
- Review excerpts note complex database structure and migration difficulty as sources of vendor lock-in concerns.
- API limitations or integration constraints
- Web API documentation indicates a service-based architecture; procurement should validate authentication model, rate limits, versioning policy, and entity coverage relative to integration needs.