Akeneo develops technology designed to help organizations manage and improve the quality, consistency, and accessibility of their product information. Through its Product Information Management (PIM) and Product Cloud capabilities, Akeneo supports teams in centralizing product data, enriching product content, and distributing accurate information across multiple channels. Its solutions help businesses address challenges related to maintaining reliable product data, accelerating time-to-market, and delivering coherent product experiences across digital and physical touchpoints. Akeneo works with companies of various sizes and industries, including brands, manufacturers, distributors, and retailers, to support their omnichannel and product experience management initiatives.
Do You Manage Peer Insights at Akeneo?
Access Vendor Portal to update and manage your profile.
Support team that understands our business: From the selection process through implementation and daily operations, Akeneo's support and customer success teams have been responsive and knowledgeable. Their technical expertise and understanding of furniture retail challenges helped us navigate complex requirements effectively. This quality of partnership was one of our key vendor selection criteria. Validation capabilities that improved data quality: Error-prone free-text fields decreased from over 50 to fewer than 10 through proper validation rules. Mandatory attributes expanded from 7 to more than 30 per product family. This provides reliable, consistent product information across our channels. Team independence through import/export tools: These capabilities give our merchandising team operational autonomy, eliminating roughly X yearly in developer time previously spent on manual database work. We successfully coordinated a complete five-locale catalog review using freelancers with minimal training requirements. Reference entities as our content engine: We manage most product page content, including translations, directly in the PIM through this feature. Creating channel-specific experiences is handled through attribute adjustments rather than rebuilding page templates. Operational cost reductions enabling scale: Attribute management costs decreased 80%, media operations dropped 90%. This reduction allowed us to build richer product experiences without proportional cost increases
I appreciate how the product view is structured and the quick export functionality within the product grid is valuable. Additionally, having tracking enabled for all jobs is extremely helpful.
Two things genuinely stand out after 5 years of use. First, the data modeling flexibility. Akeneo handles the complexity of our catalog well, including thousands of SKUs across multiple product families with varying attributes, without requiring heavy workarounds to make it fit. Second is the pace of product development. Workflow and automation capabilities have matured significantly since we started, and the platform now supports things like AI-assisted content enrichment that simply weren't psosible when we first implemented.
Licensing Model Evolution: During our implementation, we built our product data architecture and operational processes around the original licensing model (limits on users and channels, unlimited products). The subsequent shift to a product-based limit model has created challenges, as our catalog structure and workflows were optimized for the previous framework. Adapting our existing setup to align with the new model is complex and resource-intensive, making this transition frustrating from both technical and business planning perspectives. Ecosystem Instability Due to Expanding Product Scope: As Akeneo extends its solution coverage into areas previously handled by partners (DAM, syndication, translation), we've experienced disruption when partner integrations are discontinued or deprioritized. The partner ecosystem and native connectors were initially key selection criteria for us, yet we've been forced to rebuild certain integrations internally when partners abandoned their native connectors. This lack of ecosystem stability creates additional development overhead and undermines the value proposition of a well-integrated partner network. Learning Curve for Advanced Features: While the interface is user-friendly, maximizing the platform's more sophisticated capabilities (like reference entities and complex workflows) requires significant initial training and adjustment time for teams transitioning from simpler systems.
1) There is currently no mass upload option for translating Reference Entity Record Attribute values (both Main Values & Multi Values). Managing translations manually across 30 locales is extremely time consuming, as each attribute must be updated individually for every locale and value type. 2) Tailored exports should be the most flexible in terms of adjusting the needed structure, however, they are have some limitations like in Product Selection we can't select product model structures (Root product model, Parent). Also conditions like in list or is empty would be very helpful. 3) Quick export doesn't contain the 'Categories' attribute as a possible column. 4) Products don't keep a complete history of changes. While this cam be overwhelming, it is often essential for understanding what occurred at a detailed granular level. 5) In the Process Tracker, the job logs do not provide an option to export only the lines that failed along with their associated error feedback.
A few areas where there's room for improvement. First, workflow triggering logic can be too blunt. When you're running AI-assisted content enrichment at scale, you need fine-grained control over what triggers a workflow and when. Right now, that granularity isn't quite there, and it creates workarounds that add friction to what should be a smooth process. Second, table attribute migration is more painful than it should be. Moving complex attribute structures between environments requires more manual effort than you'd expect from a platform at this maturity level. Third, the learning curve for administrators is steep. Akeneo is powerful, but that power comes with complexity. Getting new team members up to speed on catalog structure, rules, and enrichment logic takes real time and investment. Fourth, pricing transparency at the higher tiers can be frustrating. As you scale into Serenity, costs can grow in ways that aren't always easy to anticipate, and the enterprise pricing model isn't the most straightforward to navigate. These aren't dealbreakers by any stretch, and most of them reflect the natural tradeoffs of a platform built for scale. But they're real friction points worth knowing going in.