Connect a PIM: Akeneo, Pimcore, Salsify and Plytix
Bring product attributes from your PIM into passports: the settings for each supported PIM and how to map attributes to passport fields.
DPP Shield editorial team · Updated:
Start a mapping from your PIM's template in Integration hub, connect it to the PIM's API or channel feed, map each attribute to a product field or a passport data path, then preview, apply and schedule it. The PIM stays the source of the attributes, and each passport field records the run that wrote it.
Why connect the PIM
A PIM usually holds the passport's descriptive content - materials, composition, care, dimensions, certifications - that the ERP does not. Mapping those attributes to passport data paths keeps passports in step with the catalogue your teams already maintain, without retyping.
Akeneo
Template: Akeneo products (REST API). Feed URL https://<your-pim>/api/rest/v1/products?limit=100, records path _embedded.items, key identifier, with values.name.data, values.ean.data and values.description.data.
Create a connection in Akeneo (Connect, Connection settings) to get a client ID, secret, username and password, and choose OAuth 2.0 with the password grant; the token endpoint is /api/oauth/v1/token. Attribute codes such as name, ean and description are your catalogue's own, and values.<code>.data reads the first locale and channel value. One feed request reads one page of at most 100 products, so post larger exports to the mapping's push endpoint.
Pimcore Datahub
Template: Pimcore Datahub (GraphQL). The feed posts the query { getProductListing { edges { node { sku name ean } } } } to https://<your-pimcore>/pimcore-graphql-webservices/<endpoint> with the Datahub API key in the X-API-Key header; records path data.getProductListing.edges, key node.sku.
Class and field names follow your data model: change the query and the source fields together, and test the feed before saving.
Salsify
Template: Salsify product export (JSON), key salsify:id, with Product Name and GTIN. Property names are your organization's, and salsify:id is Salsify's own identifier - use your SKU property as the key if that is what your products carry. Upload the export or post it to the push endpoint.
Plytix
Template: Plytix product feed (CSV). Use the channel's feed URL, which needs no authentication; key sku, with label and gtin. Custom attributes arrive as further columns: map each one to a passport data path.
Map attributes to passport fields
Passport fields are data paths - data.materials.0.name, data.textile.care_instructions and so on; the field help in the passport editor shows each one. Map one attribute per rule, and use a value map where vocabularies differ, for example 100% Cotton=cotton or Li-ion=lithium-ion.
Use transforms for numbers written with a decimal comma or in another unit (a scale of 0.001 turns grams into kilograms), for yes/no attributes and for country names that must become two-letter codes. A mapping writes one value per field; translations of passport text are reviewed in Localization.
Set it up
- Open Integration hub, choose New mapping and start from your PIM's template.
- Enter the feed URL and credentials, then use Test feed to see the first records.
- Add a rule for every attribute that belongs in the passport.
- Run a preview, check a few products field by field, then apply.
- Schedule the feed hourly or daily, or have the PIM push its exports.