It can be customised to handle virtually any business logic and comes with a wide range of features and functions that you can use out of the box or extend as needed. This includes workflows, role-based permissions, completeness rules, and automation for mundane tasks, and more recently an added framework for AI and AI refinement. Pimcore used to offer a very low TCO for companies, and although they moved to a licensing model in later versions, the cost still isn’t huge. The new Studio UI provides a much better user experience along with improved performance. The Data Hub is essential as well, since Pimcore is where you want to maintain a single source of truth for all consuming systems, and you typically need both input and output integrations with support for whatever formats those systems require. You need to set up and understand the company data model and channels, once you have that mapped out, most of the work is detailing how you and your different departments are to work with the software. One key change for us was coming from a flat structure to a hierarchy structure with use of inheritance. We had a great partner help us. Review collected by and hosted on G2.com.
The only thing I dislike about Pimcore is the redefinition of bundles that used to be part of the community offering but were later moved to the Enterprise subscription. This means that companies already building on top of bundles like Web2Print not only have to pay for a Professional edition, but may end up having to jump from the zero-cost Community edition straight to the Enterprise edition. That’s a much bigger cost to swallow than being able to move gradually from Community 2024.4 to Professional 2025.1. If they used Web2Print features in 2024.4, then they will need the Enterprise edition to upgrade to 2025.1 or beyond. Review collected by and hosted on G2.com.
Hi Magnus,
Thank you for the detailed review and for sharing how Pimcore is working for your team.
We also appreciate the honest feedback on the redefinition of bundles. We understand that shifting a bundle from Community to Enterprise, especially for teams already relying on it, might be a meaningful cost jump rather than a gradual step. We're always weighing this kind of feedback as we shape future licensing and edition changes, so thank you for raising it clearly.
