> ## 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. # Akeneo
Akeneo
The Akeneo connector syncs your PIM's product catalog and category tree into Frontic. Akeneo's product models become parent products, individual products become variants, and the connector pre-resolves attribute values, currencies, and locales — so your Data Sync receives a normalized payload instead of raw PIM structures.
Auth
Token
Update methods
Trigger · Polling
Resources
Products, Categories
## What you get Akeneo product models as parent records, individual products as variants — with attributes, families, and prices pre-resolved. Power category pages, attach category context to other records, drive navigation. The Akeneo connector follows the standard integration model — see [how integrations work](/connectors/overview) for Connection, Channels, and Data Feeds. This page covers the Akeneo-specific configuration and data shape. ## Connection settings Your Akeneo instance URL, e.g. `https://my-pim.cloud.akeneo.com`. In your Akeneo interface, navigate to **Connect → Connection Settings** and use the **Create** button to add a new API connection. Set up the connection like this (especially choosing **Data destination** as the **Flow type**): Akeneo Connection basic setup information Copy the Connection credentials on the page, you will need them to setup the Frontic integration. Akeneo Connection Credentials Afterwards, make sure to configure the Akeneo Integration with the role of **API Destination**. Akeneo Connection Permissions Use this to connect your Akeneo instance via a Connection configuration in Akeneo. Use this if you don't (or can't) install the Frontic Akeneo App. The Akeneo Connection's Client ID given in the Akeneo configuration. The Akeneo Connection's Client Secret given in the Akeneo configuration. The Akeneo Connection's username given in the Akeneo configuration. The Akeneo Connection's password given in the Akeneo configuration. The Akeneo App for Frontic is not yet available Use this to use your Akeneo instance's installation of the Frontic Akeneo App. An Akeneo API connection token. Given after installing the Frontic Akeneo App from the Akeneo App Marketplace — Frontic uses this to authenticate against the Akeneo REST API. **Akeneo Enterprise app permissions and locale alignment.** On Akeneo Enterprise instances, the connection's app permissions limit which locales it's allowed to read. The locale dropdown in Frontic shows *all* of Akeneo's enabled locales — not the subset your connection is authorised for. If you pick a locale the connection can't read, the API rejects the request at sync time and the feed errors mid-run. Before saving the channel, open **Connect → Connection settings → Permissions** in Akeneo and confirm the connection has at least the same locales selected as the channel will pull. The two lists should match 1:1 — match what's in Frontic to what the connection is allowed to read, not the other way around. 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. A label for the channel in Frontic. Akeneo locale codes the connector pulls per record. The translation used when a value is missing in another locale. Currencies (from Akeneo's enabled set) the connector pulls. Product prices are pre-filtered to these. 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: | Feed | What it pulls | | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | **Products** | Akeneo product models (as parents) and individual products (as variants), with their families, attributes, prices, and translations resolved. | | **Categories** | The full category tree, parent links preserved. | The standard **Settings → Updates → Schema** setup wizard applies — see [Data Feeds in the overview](/connectors/overview#data-feeds). For Akeneo specifically: * **Updates step** — Polling is supported. The Ingest API and Triggers are not used. * **Manual refresh** — every Akeneo feed exposes a Refresh action that re-runs the feed against the source. ### Product Feed For a product feed, you can optionally set an attribute to be used for your products' prices. The attribute which contains the product sale price ## 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](/connectors/shopware#variants) and the [Custom integration](/connectors/custom#product-variants). ### Currency-resolved prices Product prices are pre-filtered to the currencies declared on the channel. Map prices into the [Price composite](/reference/storage-field-types#composites) 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](/reference/storage-field-types#composites) 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 How Akeneo's product models and variants compose at the API layer. commercetools' connector — same `$options` / `$properties` split.