ConFlowIO
Enquire

Product information (PIM)

Akeneo PIM

Reading works per channel and locale, in full or only the products changed since the last run, and only complete ones if you wish. The products come out as Commerce Bundle products — with images, properties such as colour and size, associations and the assignment of variants to their product model — and from there go into every shop.

In the other direction, Akeneo takes master data from the ERP or from a supplier catalogue. Akeneo is connected in the cloud as well as in your own data centre.

Demo on your own data

An image that has not changed is not stored a second time when uploading.

  1. Akeneo PIMProduct information (PIM)
  2. ConFlowIOintegration platformRun active
  3. Shopware 6
  4. Shopify
  5. Adobe Commerce
  • 7ready-made building blocks
  • 21data models in the Commerce Bundle, one mapping for every target

Building blocks

Seven building blocks for Akeneo PIM

  • Read productsRead

    Reads products per channel and locale as Commerce Bundle products, in full, changes only or complete ones only. A mapping table sets which attribute fills which product field; weights and dimensions are converted.

  • Read categoriesRead

    Reads the categories from Akeneo as Commerce Bundle categories.

  • Read structures and product modelsRead

    Reads the catalogue structure and the product models the variants belong to.

  • Write productsWrite

    Creates or changes products in Akeneo from the ERP or a supplier catalogue. Only the mapped fields are changed.

  • Write categoriesWrite

    Creates or changes categories in Akeneo.

  • Upload mediaWrite

    Uploads images into Akeneo without storing unchanged ones twice.

  • Free request

    For everything there is no ready-made building block for: a request to the API, with the stored credentials.

In practice

Two workflows with Akeneo PIM

  1. Product data from the PIM

    Akeneo maintains, the shop displays — with no export file in between.

    1. Triggerschedule
    2. Readproducts from Akeneo, per channel and locale, changes only
    3. Maponto the Commerce Bundle
    4. WriteShopware 6, Shopify or another shop

    Variants stay assigned to their product model. A second shop is one more target building block; the mapping stays the same.

  2. Master data into Akeneo

    New articles are created in the ERP or arrive in a supplier's catalogue — they are maintained in Akeneo.

    1. Triggerschedule
    2. Readarticles from the ERP or a supplier catalogue
    3. Writeproducts and categories into Akeneo, only the mapped fields
    4. Upload mediathe images, unchanged ones not a second time

    Fields without a mapping stay in Akeneo as they are; what is maintained there by hand is not overwritten by the workflow.

Good to know

What to know about Akeneo PIM

  • PrerequisitesWhat has to be set up on your side.
    • A connection created in Akeneo
    • A PIM reachable over HTTPS — in the cloud or in your own data centre
  • Not coveredWhat the integration deliberately leaves alone.
    • Fields without a mapping are not changed when writing
    • Unchanged images are not stored again
  • DurabilityApplies to this integration as to every workflow in ConFlowIO.
    • Failed steps retry themselves
    • Large reads are processed page by page, each page a step of its own
    • A failed run is continued rather than started over
    • Live logs per step, with credentials removed

Works well with

What works with Akeneo PIM

Frequent partners

Products out, master data in.

Contact

See Akeneo PIM on your own data

We are glad to show ConFlowIO on your own data. Bring a real slice of your catalogue.

The difference shows at real volumes — not at five sample records.

Would you like to read our whitepaper? Just say so in your enquiry and we will send it to you.

Rather write directly?info@conflowio.com