Technology
Symfony, Vue.js
PHP, ExtJS, MySQL, MariaDB,
Symfony
PHP, ExtJS, MySQL, MariaDB,
Symfony
PHP, MySQL, MariaDB,
Symfony
Many types of product attributes
YES
YES
YES
YES
Types of attributes
Price, date, gallery, image, unit, dropdown list, numeric, file, text field, checkbox, product relationships, text.
Date, file, identifier, image, unit, multiselect, number, price, select relation, multiselect relation, checkbox, text, text field, logical attribute.
Reference unit + multiselect
(https://help.akeneo.com/v3-your-first-steps-with-akeneo/v3-what-is-a-reference-entity) – additional vs Akeneo Open Source
Text, text field, WYSIWYG editor, date and time, time, product relationships, image, image outside of Pimcore Database, image gallery, video, checkbox, select, multiselect, link, calculated value based on PHP.
Product variants
A wider range of product creation with multiple attributes, e.g., color, size, material
Ability to create a product with a maximum of 2 variants, e.g., color and size.
Ability to create a product with a maximum of 2 variants, e.g., color and size.
Ability to create a product with multiple variants – no quantity limit on variants (limited by system performance).
Product sets (bundle, grouping, configurable).
YES
YES
YES
YES
Simple product.
YES
YES
YES
YES
Product with variants.
YES
YES
YES
YES
Group product.
YES
YES
YES
YES
Virtual product.
NO (this can be bypassed with e-commerce integration).
NO (this can be bypassed with e-commerce integration).
NO (this can be bypassed with e-commerce integration).
YES
Entities that are not products.
NO
YES
YES
YES
Multiple product relationships (e.g., cross-sell, up-sell, etc.).
YES
YES
YES
YES
Spreadsheet mode (editing in text).
YES, however, if multiple product templates need to be created, it becomes cumbersome.
NO, however, this should not be considered a downside – it is graphically simpler, but the result is the same.
NO
NO
Custom units of measurement.
YES
YES
YES
YES
Configurable search filters.
YES
YES
YES
YES – the widest range
Kanban view (for product view).
YES
NO, but there is the possibility of filtering products.
NO
Natively NO, but it can be overridden.
Gallery view (for product view).
TAK
TAK
TAK
TAK
Multiple category trees.
TAK
NO – one category tree with an unlimited number of levels (categories, subcategories, sub-subcategories).
TAK
YES – the ability to expand with a document/resource tree per channel.
Bulk product editing.
TAK
TAK
TAK
TAK
Category management.
TAK
TAK
TAK
TAK
Automatic translations.
TAK
NO, but there is an extension.
TAK
NO, but there is a free extension.
Automatic content generation based on attributes.
YES
YES
YES
YES
Category attribute management.
YES, it is a new functionality, very useful for managing a large range of categories.
NO
YES
YES
Identifier generator.
NO
NO
YES – the ability to automate the creation of product identifiers in line with business requirements.
YES
Ability to create tags
NO
It is not native, but there is the possibility of using a plugin.
Not natively, but there is the possibility of using a plugin.
YES
Attribute sets for product types/families.
YES
YES
YES
YES
Attributes per specific channel and language.
Language – YES, channel – NO.
YES
YES
Not natively, but there is the possibility of customization.
Template names.
Product Templates – without defining a template, the product cannot be created.
Families – product families, the product automatically inherits attributes from a given family, example: attribute sets from Magento.
Families – there is the possibility to automate the creation of product names according to business requirements
Classes – products with similar attributes, which are comparable to families.
Ability to copy families and change a few attributes.
NO – no possibility of copying, products must be manually created from scratch.
NO, but there is the possibility to quickly create separate attribute sets.
YES – there is the possibility to automate the creation of products from other sections, according to business requirements.
NO
Inheritance within variants.
YES, but only during the initial creation of the variant.
YES
YES
YES
Possibility to create products without a product template.
No possibility to create a product without a product template.
Possibility to create a product without Families.
YES – the possibility to automate the creation of products according to business requirements.
NO
Graphic layout.
Possibility of graphical arrangement of the product.
No possibility, but a simple and user-friendly interface with extensive filtering options
YES – the possibility to automate the creation and arrangement of products according to business requirements
NO
Sales Channels
“NO – no sales channels (they are expected to be available soon).
YES – sales channels and attribute visibility.
YES – the possibility to automate the creation of product sales according to business requirements.
YES
Import of products that are assigned to a specific sales channel.
Possibility to create a rule in the segment.
Possibility to select a sales channel for a given product and preview with editing
Possibility to select a sales channel for a given product and preview with editing.
Sales channels are used both in PIM and CMS, but it is not possible to create different content depending on the sales channel.
PDF catalogs
NO
Adding an extension, there is the possibility of native export, but it does not meet the requirements.
Adding an extension, there is the possibility of native export, but it does not meet the requirements.
There is a built-in .pdf generator that needs to be configured – it requires developer work for configuring twig [print_page] [print_container]. However, once configured, Pimcore provides the greatest capabilities for exporting entire catalogs to .pdf.
Quick export to .pdf
NO
YES, but graphically limited – the possibility to install an extension.
YES, but graphically limited – the possibility to install an extension.
YES – however, it needs to be configured manually
Brand management
NO
NO
NO
YES
Content management
NO
Not natively, but there is the possibility of using a plugin.
Not natively, but there is the possibility of using a plugin.
YES – integrated content management system (CMS).
Category trees
Multiple, taxonomy similar to Akeneo.
Multiple, taxonomy similar to Ergonode.
Multiple
One
Product relationships
Bidirectional relationships, different way of association with quantity.
Bidirectional relationships, at this stage, association with quantity can be done.
Bidirectional relationships, at this stage, association with quantity can be created.
YES, through object references.
Identifier
SKU
UUID – product identifier in the database, visible in the URL.
UUID – product identifier in the database, visible in the URL.
UUID
Editing SKU
None – SKU is the identifier.
YES – there is the possibility, as it is not an identifier.
YES – the possibility to automate the creation of SKUs for products according to business requirements.
YES, because it is not an identifier.
Possibility to create a custom field.
NO
NO
YES
YES
Filtering by missing attributes.
NO
YES
YES
NO
Grouping by attributes within a given product.
YES
YES
YES
NO
Possibility to hide fields based on permissions.
YES
NO
YES
YES
Visibility when 2 users are working on the product.
NO – if a situation occurs where multiple users are working on the same element simultaneously, the data will be overwritten by the last ‘save changes’ after saving.
NO
YES
NO
Versioning and publishing
None – visible change history without the possibility of restoring.
None – visible change history without the possibility of restoring.
YES – restoring products to the previous version and maintaining multiple product versions.
YES
Scope of restricting permissions
Per attribute group (highest package)
Per attribute group
Possibility per specific attribute, or even product.
Per attribute group. In Pimcore, there are two levels of user permissions: 1) permissions for system components, 2) permissions for data elements (Assets, Data Objects, and Documents).
Product list
3 view types, including Kanban.
2 view types, without Kanban.
2 view types, without Kanban.
2 view types, without Kanban.
Workflow
Shows in which phase (defined in the workflow) a given product is.
None (work on the product can be resolved by working on categories).
A ‘Validation workflow’ appears, allowing for reviewing and approving changes to ensure high-quality product information, depending on the user’s role.
Possibility to define your own workflow, or even different workflows.
Intelligent rules for automatic completion of product information.
YES – based on AI.
NO
YES
NO
Pulling fields for variants.
Pulls from the base (during the first creation).
Pulls from the base.
Pulls from the base.
Pulls the name from the base.
Rules for validating attributes.
NO
NO
YES
YES
Possibility to schedule publication.
NO
NO
NO
YES
Rules engine
NO
NO
YES – automatic data enrichment while reducing errors and manual effort.
YES
Asset Manager
NO
NO
YES – the possibility to organize, enrich, combine, and transform multimedia assets for specific channels.
YES – Pimcore is an MDM platform.
Connectors
GraphQL API
REST i EVENTS API
REST i EVENTS API
GraphQL API, REST API
Team collaboration assistant
NO (there is the possibility to set notifications within the application for the user assigned to a specific status).
no
YES – the user/team can easily see which products and attributes they are responsible for.
YES – however, this functionality needs to be configured on the backend.
Possibility of simultaneous work.
NO
NO
YES – we can see who is editing the product, every change is saved in real-time; this prevents data overwriting
NO
Possibility to create reference objects.
NO
NO
Possibility to create reference objects.
YES
Insight into data quality
Limited
Limited
YES – the ability to measure the quality and consistency of product data and receive suggestions for improvements.
YES
Insight into product time-to-market.
NO, but it is possible to configure a view that shows when the product was added.
NO
YES
YES – it needs to be configured on the backend.
Dedicated product export
NO
NO
YES, creating custom exports according to the requirements of the seller or distributor.
YES
Dedicated import
YES, the possibility of mapping during import.
NO
YES, the possibility of uploading product data files with any structure and mapping them to the structure in Akeneo PIM.
YES
Dedicated Onboarder and Shared Catalogs
NO
NO
The ability to collaborate with all product stakeholders, whether they are suppliers, distributors, retailers, or internal teams.
NO, but there is the possibility to configure access for suppliers to add products to the PIM.
Automatic updates
YES
NO
YES
YES – it needs to be configured on the backend.
Dedicated mobile panel
NO
NO natively – possibility to download the app.
NO natively – possibility to download the app.
NO
Automatic image correction
NO
NO
NO
YES
Platform type
PIM without DAM (with the ability to catalog multimedia assets)
PIM with the possibility of extending to DAM through a module (of rather poor quality)
PIM with DAM functionalities
PIM, MDM, DAM, DXP/CMS
Implementation model
SaaS
On-Premises
On Premises/SaaS/PaaS
On Premises/SaaS