Akeneo PIM

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.

- AI writing tool is a big one, at least for us. Being able to go in and write a prompt for an attribute that is then filled in across an entire product model is a massive way to save time and energy. - Activation portal. Specifically, the prebuilt connections within the activation portal which are easily accessible and save a ton of time. The fact that you can open up the portal, find your desired amazon connection, and instantly plug in and get real time data feedback from (in our case) one of our larger ecommerce platforms will be extremely valuable once we have that up and running. - Generally the ease of use. Specifically the import and export process and the amount of variability you can put in. We aren't even fully off the ground yet with PIM and we are finding use cases for data exports that we are directly tailoring to specific requests, and the fluidity behind it makes it that much quicker for us so we don't have extensive data gaps for our retailers.

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.

Not sure if I can directly think of 3, but I can try: - As mentioned before, the category codes being unilaterally grouped into one category header makes category exports painful to try and sift through, especially when you have 2500 categories. A more tiered or hierarchical approach to category call outs would be easier to read on a category export and would allow for easier integration across other platforms or services. As an example, instead of calling my Bolts folder the same thing as my Zinc Coarse Thread Grade 2 Hex Bolts folder, call my Bolts folder the great grandparent and my subfolder the great grandchild. - There isn't directly an ability to link Akeneo platforms to my knowledge. This would be a great feature to add for customers who may have customers of their own that also use Akeneo. In our case, we have a fairly large customer of ours currently implementing Akeneo, and it would be extremely streamlined for both parties if we had some connection capability which fed their system with our product data directly. - I guess maybe the inconsistency in the auto generation of labels/codes? Certain label fields will automatically create codes for you, while others require a manual input. This leads to inconsistent code formatting across the PIM, which isn't necessarily a bad thing but does look a little clunky on an export.