A place to discuss existing Tulip features, how they can be improved, and share your product suggestions.
Before submitting your ideas and suggestions, please make sure no one else has done so already by browsing this channel.
If someone else already made a similar suggestion, you can show your support by voting for the idea and jumping in the conversation.
Every suggestion gets reviewed by our team and influences our roadmap, but not everything will be built. We’ll be as transparent about timelines as possible and will do our best to explain our thinking when ideas don’t get prioritized.
I work with Tulip daily in production and wanted to share a workflow observation that may help improve efficiency for operators.
Currently, when switching between apps, the system requires the production order to be scanned again to access the work. When this occurs multiple times during a task, it interrupts workflow and adds repeated scanning steps even though the operator is still working on the same production order.
For instance, when switching from sterile ops to “issue material” and then “router” , I scan the production order each time. I feel like it would be more efficient to have the order remain active and just switch apps until completed.
From the operator perspective, it might be helpful if the system could maintain the active production order as a session across apps so the order does not need to be rescanned unless the job actually changes.
This would reduce repeated scanning, improve workflow continuity, and likely save time during production tasks.
I realize that certain industries require traceability and data security, but thought it might be useful to share feedback from the production floor as to the time involved in achieving these goals under the current format.