Infor CloudSuite Industrial (SyteLine) has a broad set of functionality for manufacturing and distribution, and the underlying platform is highly configurable. When properly implemented, it can handle a wide range of manufacturing, inventory, purchasing, customer order, quality, and shop-floor processes within a single system.
One of its stronger points is the flexibility of the Mongoose platform and the ability to extend the system using IDOs, events, forms, DataViews, and other configuration tools without necessarily modifying the core application. For an organization with knowledgeable technical resources, that provides a lot of options for adapting the system to specific business requirements.
The product also has a long history in manufacturing, so many of the fundamental ERP capabilities are there. The challenge, in my experience, is less about whether SyteLine is capable of doing something and more about how difficult it can be to determine the correct way to accomplish it, configure it, and support it. Review collected by and hosted on G2.com.
The biggest issue with Infor CloudSuite Industrial is that too many things are harder than they should be. The system is capable, but accomplishing relatively straightforward business requirements can require a surprising amount of technical knowledge, trial and error, customization, or vendor assistance.
Documentation is a significant weakness. It is often difficult to find clear, current, CloudSuite-specific documentation that explains not only what a feature does, but how it is actually intended to be configured and used. Troubleshooting frequently becomes an exercise in searching multiple sources, experimenting, reviewing IDOs and underlying data, and trying to determine whether the issue is configuration, customization, product behavior, or a defect.
The Cloud multi-tenant environment adds another layer of frustration. While SaaS obviously requires controls around the application and database, the restrictions can make troubleshooting, reporting, integration, and extending the system more difficult than they were in a traditional ERP environment. At the same time, many of the tools provided to work within those restrictions are complex and not particularly intuitive.
There is also a heavy reliance on specialized SyteLine knowledge. Mongoose is powerful, but becoming proficient with forms, events, IDOs, background tasks, application messages, report processing, and the various extension mechanisms has a substantial learning curve. Even relatively small changes can involve understanding several layers of the application.
We have also encountered situations where seemingly minor details such as unit-of-measure conversions, rounding precision, pricing, reporting behavior, background processing, or transaction sequencing create significant operational issues. These are the kinds of things that an ERP system should make predictable, but they can require considerable investigation to understand and correct.
Reporting and analytics have also been more difficult than expected. There are multiple reporting and analytics technologies within the ecosystem, and getting reliable operational information often requires deeper knowledge of the underlying data structures than I would expect from a modern cloud ERP.
Finally, the overall implementation and support ecosystem can make the product feel overly dependent on consultants or highly experienced internal resources. A mature manufacturing ERP should certainly support complex processes, but complexity in the business should not automatically translate into complexity in every aspect of configuring and maintaining the software.
My frustration is not that SyteLine lacks functionality. It is that accessing that functionality, understanding how it works, and maintaining it often requires far more effort than I believe should be necessary for a modern SaaS ERP platform. Review collected by and hosted on G2.com.