- PIM
- Product information management: the system that holds the product model, attributes, media and enrichment workflow and feeds one or more sales channels. Akeneo and Pimcore are the two PIMs the agencies on this site publish work for.
- Akeneo Connector for Adobe Commerce/Magento
- The vendor-published module that imports catalog data and structure from Akeneo PIM into Adobe Commerce over API. Its README credits Agence Dn'D with building it. Also called the community connector, after its repository name, akeneo/magento2-connector-community.
- Connector line
- One of the three version series of that connector: 103.x for Magento 2.3.7 up to but not including 2.4.4, 104.x for 2.4.4 up to but not including 2.4.7, and 105.x for 2.4.7 and above, according to the README compatibility table.
- Product model and family variant
- Akeneo's terms for a parent product and the rule that says which attributes vary across its children. The connector imports both, alongside products, families, attributes, options and categories.
- Channel
- In Akeneo, a sales context such as eCommerce or print with its own locales and completeness rules. The connector's Website Mapping setting matches each Adobe Commerce website to one Akeneo channel.
- Store view
- Magento's unit of localized presentation under a website. A multi-store-view build is one where the PIM feeds several languages or markets; scandiweb's BK-Group case lists four.
- Scopable and localizable attributes
- Akeneo attributes whose values differ by channel or by locale. Their count, multiplied by locales and channels, drives the attribute volume that the connector's Storage Engine setting warns about.
- Storage Engine setting
- A field in the connector's system.xml for the temporary tables built during import. Its comment states MyISAM allows high scalability with many attributes and that InnoDB is recommended but may cause errors during import for a large catalog.
- akeneo_connector_entities
- The table defined in the connector's db_schema.xml that maps an import type and an Akeneo code to an Adobe Commerce entity ID under a unique constraint. Duplicate products after a re-run usually trace to rows in it.
- Field ownership map
- A one-page statement of which system owns price, stock, media, categories and attribute options. On the community connector, price and stock are not imported, so the ERP owns them.
- One-way sync
- An integration in which data travels from the PIM to the storefront and nothing is written back. The community connector, StrikeTru's connector and Pimcore's partner-built connector are all described that way.
- Middleware
- A layer between systems that transforms and routes data. In scandiweb's BK-Group case, Pimcore acts as middleware between Magento and the ERP.
- Akeneo Community, Growth and Enterprise
- Akeneo's editions. Its Community Edition page describes a free open-source PIM; Growth and Enterprise add cloud hosting, services and support. Akeneo publishes no prices.
- Pimcore Open Core License (POCL)
- The licence Pimcore's Community Edition moved to at platform version 2025.1, replacing GPLv3. Free use is limited to non-production use, academic and non-profit institutions, and companies under EUR/USD 5 million in annual revenue.
- Regular and extended support
- Adobe's two support phases for a Commerce version. 2.4.6 left regular support on 11 August 2026 and stays in extended support until 31 August 2027; 2.4.4 and 2.4.5 have left both.
- Partner tier
- A level a vendor assigns to an agency, shown as a badge on the vendor's directory. This site scores a tier at full weight only when the badge is on the vendor's own page, and at half when it appears only on the agency's site.
- Verified, stated by the agency, removed
- The three statuses in the evidence ledger: read on a third-party page on the ledger date; sourced only from the agency's own material; or deleted after it could not be confirmed on re-check.
- Adobe Commerce and Magento Open Source
- The paid and free editions of the platform this site calls Magento (Adobe Commerce). The connector README uses both names, and its compatibility table applies to both.