Skip to main content

​
Introduction

The Akeneo-Spryker Template facilitates seamless product data retrieval from Akeneo and transfers it to Spryker to make products sellable on the Spryker platform. The Template focuses on using Akeneo and Spryker as target applications, with Alumio serving as the middleware to ensure structured data transfer and precise data mapping.
Image

​
The Template Scope

Data mapping includes the following structure (greyed-out fields are excluded from scope):
Image
Out of scope: Akeneo: Data mapping of Family, Family Variant (see Table 1). The data model of Spryker doesn’t include Family and Family Variant, to which data could be mapped. The Template uses Family Variant (axes) as a part of the Family Variant to create Super Attributes. Spryker: Measurement and packaging Units, Tier Pricing, Bundles, Related Products, Binary Assets.

​
API Documentation

Akeneo v1: https://api.akeneo.com/concepts/products.html Alumio v3.82-RC1: https://apidocs.alumio.com/ Spryker v202404.0: https://docs.spryker.com/docs/pbc/all/data-exchange/202404.0/sending-requests-with-data-exchange-api.html

​
Business Rules and Assumptions

Users can import and export the Akeneo-Spryker Template via the Alumio UI. Additionally, the template can be imported into other Alumio Spaces. For Spryker configuration, the B2B business model is used, with the following data mapping settings:
  • Stock: static number (configurable, but static);
  • Language: German, English.
The Akeneo-Spryker Template is designed for a one-time import and doesn’t support repeated imports.