Akeneo

Documentation Index

Fetch the complete documentation index at: https://docs.frontic.com/llms.txt

Use this file to discover all available pages before exploring further.

​

What you get

The Akeneo connector follows the standard integration model — see how integrations work for Connection, Channels, and Data Feeds. This page covers the Akeneo-specific configuration and data shape.

​

Connection settings

The connection populates the channel’s currency dropdown from Akeneo’s enabled currencies (with their enabled flag respected).

​

Channels

An Akeneo channel in Frontic carries the locales (Akeneo “locale codes”) and currencies the connector pulls per record. The Refresh button re-fetches Akeneo’s enabled currencies and locales — use it after enabling new ones in Akeneo.

​

Data Feeds

The Akeneo connector exposes two feed types: The standard Settings → Updates → Schema setup wizard applies — see Data Feeds in the overview. For Akeneo specifically:

• Updates step — Trigger and Polling are supported. The Ingest API isn’t used.
• Manual refresh — every Akeneo feed exposes a Refresh action that re-runs the feed against the source.

​

What the data looks like

​

Identifiers

Akeneo’s identifier field is what Frontic uses as the record key on both sides of the parent/variant divide — for product models, it’s the model code; for individual products, it’s the product identifier (typically the SKU). Treat the SKU as the stable lookup key when configuring blocks, listings, and slugs that point at variant records.

​

Variants

Akeneo’s product models become parent records; the individual products underneath become variants linked via parentId. Standalone products (no model) are emitted twice on purpose — once as a parent and once as a self-referencing variant — so a product with no variants still has a record on each side of the parent/variant divide. Same convention as Shopware and the Custom integration.

​

Currency-resolved prices

Product prices are pre-filtered to the currencies declared on the channel. Map prices into the Price composite without per-region picking logic.

​

Attributes split into options and properties

Akeneo attributes don’t all play the same role: some define variants (size, colour, material — the things customers pick from), others describe the product (ingredients, dimensions, care instructions). The connector’s attribute extractor splits them apart and stamps each list onto the feed record under the reserved $-prefix namespace:

• $options — variant-defining attributes, normalized into a single list per record
• $properties — descriptive attributes that don’t drive variant selection

Map either list straight into your storage’s Option and property fields in the Value Composer, instead of re-deriving them from Akeneo’s raw values structures.

​

Family and attribute caching

Akeneo families and attributes are cached on the integration’s Instance to avoid refetching them per record — speeds up large catalog syncs.

​

Good to know

• Read-only. The Akeneo connector pulls from Akeneo; it doesn’t push back. Catalog edits happen in Akeneo.
• Reserved $-prefix keys. The connector emits $options and $properties on every product record. Don’t use $-prefixed keys for your own custom attributes — Frontic reserves that namespace for connector-side normalization.

​

Related