- Company sizes or stages where this product is overkill or insufficient
- Early-stage or small single-site manufacturers with simple workflows may find a full vertical ERP disproportionate compared with lighter inventory/accounting systems.
- Industries or use cases where competitors are clearly superior
- Non-corrugated discrete manufacturing where generic ERPs or other vertical ERPs may offer a better out-of-the-box fit.
- Organizations that require a large global ecosystem with many published prebuilt integrations may prefer alternative vendors with broader public integration catalogs.
- Technical requirements that this product cannot meet (unknowns to validate)
- If an organization requires documented SAML/SSO and SCIM provisioning guarantees, specific encryption and key management details, or formal certifications (SOC 2 Type II / ISO 27001) as a procurement precondition, RTS did not publish these details in the sources accessed and this may be a blocker unless the vendor provides them under NDA.
- Budget constraints that make alternatives more appropriate
- If budget is constrained and the required scope is limited, a narrower or phased solution may be more appropriate.
- Specific workflows or integrations where the product falls short
- If extensive prebuilt connectors (EDI variants, shipping carriers, BI stacks) are required, verify availability; vertical ERPs frequently require custom integration work.
- Red flags in the buying process
- Lack of transparent pricing and limited third-party reviews increase the diligence burden for procurement.
- Current limitations acknowledged by the vendor
- RTS terms of service include broad warranty disclaimers (service may not be continuous, timely, safe, or error-free; results are not guaranteed). These are standard legal protections but relevant for risk assessment.
- Features on the roadmap (not yet available)
- RTS describes ongoing development of additional web features and UX/KPI improvements for RTS Global, without firm delivery dates in the public material.
- Scale limitations
- Not explicitly documented; procurement teams should request references for multi-plant, high-volume customer deployments to validate scale capabilities.
- Security or compliance gaps
- No public SOC 2 / ISO 27001 certifications were identified in the sources accessed.
- Data residency and encryption standards were not specified publicly and should be validated during procurement.
- API limitations or integration constraints
- RTS Global references SOA/web services and OData; actual API coverage, rate limits, versioning, SDKs, and integration tooling are not publicly detailed and should be validated.