Main Developer at a transportation company with 11-50 employees
Real User
Top 5
Jul 7, 2026
Tulip can be improved by implementing more AI features as we are in an AI era, and many features could be implemented thanks to AI. Regarding the needed improvements for Tulip, regarding integration that you mentioned, because you have a bunch of features of third-party connections, it is not enough. Tulip is a pretty complete tool just to use at the beginning with MES implementation.
One way Tulip can be improved is that the biggest challenge is if you already know programming. Tulip is extremely hard to set up because it doesn't follow standard programming rules. It runs based off more logic rules that somebody who doesn't know programming might think. This makes it a little bit difficult for people with some programming background to use. The main problem that Tulip has right now is that they're still learning as they grow. They're growing a little bit faster than they can really maintain. Some of the individualism and customer service that they had at the beginning has been lost. I give it a six for this reason.
Student at a healthcare company with 201-500 employees
Real User
Jul 4, 2026
Some of the templates in Tulip had very few FAQ sessions or knowledge base information, especially the automation section. If there were more information on many of the templates available, it would be helpful. I could easily plug it in and understand the plugin rather than finding out how it works through trial and error. The user interface of Tulip is very good, but performance-wise, it sometimes feels laggy when I am trying to undo my activities. When I do something and want to go back to the previous state, sometimes it may take a bit of time to do that. However, it is acceptable; it is nitpicking, basically. I chose eight out of ten for Tulip because it is not perfect, but it is almost there. The only thing that would have made this an eight a ten would be the knowledge base. If it was a bit more updated or maybe a bit more detailed, it would have been an easy ten.
Tulip can be improved to have a lower entry point. Currently, it is a SaaS solution that starts with 10 interfaces minimum, and an interface is a screen where you operate Tulip applications. A lower entry model would allow small to medium enterprises to start using Tulip faster, whereas now Tulip focuses more on big enterprises. Regarding the technical part, the data model inside Tulip needs improvement. Tulip works with Tulip tables which have a database in the backend, but the user only sees the Tulip tables where they can easily create tables and add new columns. While auditing features exist inside so you can see who has done what inside the table design, one of the shortcomings is relational mapping between tables. One-to-many and many-to-many relations are still quite unclear without the use of primary keys and foreign keys.
Senior Solution Engineer at a tech services company with 51-200 employees
Real User
Top 5
Jun 15, 2026
One area Tulip can be improved is addressing the issue that arises when simultaneous data entry occurs in the same table using an auto-incremented process ID, data integrity constraints may lead to an error for one of the transactions. As a result, one record is successfully generated while the other process fails.
Tulip is an innovative platform designed to enhance manufacturing operations by integrating core functionalities that streamline process management and data collection.Tulip offers a dynamic approach to manufacturing tasks. By providing users with tools to build applications without code, Tulip optimizes production lines and enhances workforce efficiency. Users often highlight the platform's ability to aggregate real-time data for better decision-making and its ease of customization. Despite...
Tulip can be improved by implementing more AI features as we are in an AI era, and many features could be implemented thanks to AI. Regarding the needed improvements for Tulip, regarding integration that you mentioned, because you have a bunch of features of third-party connections, it is not enough. Tulip is a pretty complete tool just to use at the beginning with MES implementation.
One way Tulip can be improved is that the biggest challenge is if you already know programming. Tulip is extremely hard to set up because it doesn't follow standard programming rules. It runs based off more logic rules that somebody who doesn't know programming might think. This makes it a little bit difficult for people with some programming background to use. The main problem that Tulip has right now is that they're still learning as they grow. They're growing a little bit faster than they can really maintain. Some of the individualism and customer service that they had at the beginning has been lost. I give it a six for this reason.
Some of the templates in Tulip had very few FAQ sessions or knowledge base information, especially the automation section. If there were more information on many of the templates available, it would be helpful. I could easily plug it in and understand the plugin rather than finding out how it works through trial and error. The user interface of Tulip is very good, but performance-wise, it sometimes feels laggy when I am trying to undo my activities. When I do something and want to go back to the previous state, sometimes it may take a bit of time to do that. However, it is acceptable; it is nitpicking, basically. I chose eight out of ten for Tulip because it is not perfect, but it is almost there. The only thing that would have made this an eight a ten would be the knowledge base. If it was a bit more updated or maybe a bit more detailed, it would have been an easy ten.
Tulip can be improved to have a lower entry point. Currently, it is a SaaS solution that starts with 10 interfaces minimum, and an interface is a screen where you operate Tulip applications. A lower entry model would allow small to medium enterprises to start using Tulip faster, whereas now Tulip focuses more on big enterprises. Regarding the technical part, the data model inside Tulip needs improvement. Tulip works with Tulip tables which have a database in the backend, but the user only sees the Tulip tables where they can easily create tables and add new columns. While auditing features exist inside so you can see who has done what inside the table design, one of the shortcomings is relational mapping between tables. One-to-many and many-to-many relations are still quite unclear without the use of primary keys and foreign keys.
One area Tulip can be improved is addressing the issue that arises when simultaneous data entry occurs in the same table using an auto-incremented process ID, data integrity constraints may lead to an error for one of the transactions. As a result, one record is successfully generated while the other process fails.