New in Endora Commerce: a built-in CRM with sales opportunities See it →
Endora Commerce

Akeneo PIM integration

If you curate product data in Akeneo, your B2B shop should not keep a second version of the catalog. The Akeneo connector in Endora Commerce receives the records Akeneo sends, applies them to the catalog and leaves a record of every run.

Who this connector is for

Akeneo is a PIM system where the product team builds the catalog from families, attributes and product models, filling in values separately for each language and channel. The connector makes sense when Akeneo is already running at your company, or is being rolled out, and is meant to stay the only place where descriptions and parameters are edited. The shop then becomes a recipient of that data, not a second place to correct it.

The connector works with a self-hosted Akeneo, installed on your own infrastructure.

Direction and scope of data

Data flows one way: from Akeneo to the shop catalog. Akeneo sends the data and the shop receives it. Endora Commerce never queries Akeneo for products: every record arrives complete, already mapped to the catalog structure on the PIM side, and signed with a shared HMAC secret over HTTPS. There is no intermediate file, no CSV export and no manual import.

From AkeneoIn the Endora Commerce catalog
ProductsProducts with their name, description and parameters
AttributesProduct parameters shown on the product page
Attribute setsCatalog attribute sets
CategoriesThe category tree and product assignments
Images and filesThe product page gallery and attachments

The flow has two kinds of delivery. A full delivery carries the whole agreed scope of the catalog. The first full delivery is the starting condition: until it finishes, individual live records are refused, unless you deliberately skip it because the catalog is already aligned. After that Akeneo sends live records, that is, subsequent changes, which the shop applies without fetching anything again. A record withdrawn in the PIM is deactivated in the shop.

The shop downloads media files only from the addresses you allow in the connection settings. If the list is empty or a file cannot be downloaded, the product still reaches the catalog, and the missing file is noted in the run report.

One alignment between the two models is worth knowing. In Akeneo an attribute value can differ per language and per channel. The Endora Commerce catalog also stores attribute values per language and per sales channel, so that distinction has somewhere to go.

Stock levels and orders are not a PIM’s job. A PIM connector and an ERP connector, for example Comarch ERP Optima or Comarch ERP XL, can run side by side on one installation.

What to prepare on the Akeneo side

On the Akeneo side, a sending component maps PIM data to the catalog structure and sends the records to the shop. Mapping is set up in Akeneo: the component uses the shop’s signed lookups, that is, lists of attributes, attribute sets, categories, sales channels, languages, price lists and product link types. Before going live, prepare:

  • The receive URLs copied from the connection screen in the shop admin: for the connection probe, for full deliveries, for live records and for lookups.
  • A shared HMAC secret, the same on both sides. Akeneo signs every request with it, and the shop stores it encrypted and never shows it again.
  • The public Akeneo address and any extra HTTPS addresses, such as a CDN, from which the shop should download media.
  • The scope of the first full delivery: which families, categories and products should reach the shop.

What the shop administrator sees

The connector is a module with the id pim_akeneo, and it is switched off after installation. You switch it on in the module list in the admin panel. Once it is on, an Akeneo PIM section appears under the catalog, visible only to operators with the relevant permission. It contains:

  • the connection screen with the receive URLs, the secret, the default sales channel and the state of the first full delivery,
  • the visibility rule for new products: always inactive, always active, or following the status sent from Akeneo,
  • the delivery history, a record of what each run did.

A run is described with the shared PIM connector vocabulary, so the report reads the same whichever system it comes from:

  • delivery kind: full delivery or live records,
  • outcome: completed, completed with issues, failed or interrupted,
  • counters: records created, updated, skipped, withdrawn and failed,
  • issues with a severity level: skipped, warning or error.

Protected fields

Not every value has to come from the PIM. The platform lets you mark selected product fields as protected: the name and description in a given language, a single attribute, SEO fields, a gallery position, an attachment, a price in a specific price list and currency, or a category assignment. Later deliveries from Akeneo leave those values unchanged.

Limitations worth knowing

  • One active PIM. An attempt to switch on a second connector is refused, with a note saying which connector is active. The current one has to be switched off first.
  • The shop does not pull data from Akeneo. There is no schedule on the shop side and no on-demand sync of a single product. Changes arrive when Akeneo sends them.
  • Switching off deletes nothing. The connection, protected fields and run history stay, and come back when the module is switched on again. A disabled connection refuses deliveries.
  • Mapping lives in Akeneo. The shop admin has no attribute mapping editor. If your data model in Akeneo is unusual, raise it before implementation.

Akeneo or another PIM

The choice of connector follows from the PIM you have or are selecting, not from the shop platform. Besides Akeneo there are connectors for Pimcore, Ergonode and UnoPim. All of them use the same run vocabulary and the same protected fields, so changing PIM later does not change how the shop administrator works.

If your PIM has no ready-made connector, the platform’s partner API remains: writing products by SKU and incrementally fetching changes since a given timestamp.

Let’s find out what we can connect at your end

Book a free consultation. We will walk through your ERP, warehouse and sales processes, and show you what the integration path looks like step by step.

Michał Zabielski, founder and CEO of Endora

Michał Zabielski

Founder and CEO, Endora

We reply within one business day.