Welcome to the beginning of the Malcom setup! Here is where you will configure Malcom and tailor it to your unique Akeneo platform settings.
On this page, Malcom will ask you for the information required to link your Akeneo account to the app. Open the Akeneo app in a separate tab or window and head to “Connect / Connection settings” to quickly access the necessary information below.
Required Fields:
- Base URL: Copy the http link from your Akeneo Connection and paste it here.
- Client ID: Insert your Akeneo Client ID here.
- Secret: Insert your Akeneo Secret here.
- Username: Insert your Akeneo Username here.
- Password: Insert your Akeneo Password here.
- Installation Type: Select the correct Akeneo Version that you are using, Community (CE) or Enterprise (EE)
-
Ignore Top Level Product Model: Products in Akeneo often follow a product structure in which they can have multiple levels to store and group product data. For example, we may determine that a product has 3 levels: the common level using SKU (grandparent), the style fit/fashion colour level (parent), and the size level (child). For each level, we have defined attributes and a specific axis of variation on the parent and child levels. Let's say that the axis of variation for the parent is style fit/color, and the axis of variation at the child level is size.
If we ignore the top-level product model, products will be grouped starting from the Parent Level. Products will have variants that are based on variations of style fit/color, with variations of different sizes for the variants.
If we DO NOT ignore the top level product model, products will be grouped by the common level based on the SKU. All products with the same master SKU will be grouped under one product, and we will have different variations of style fits/colours and sizes together.
For example, if we ignore the top-level product model, we get 4 products with 3 variants in each:
Product A - Master SKU 0001 - Style: Knitted Sweater - Color: White
- Variant A - Size M
- Variant B - Size L
- Variant C - Size XL
Product B - Master SKU 0001 - Style: Knitted Sweater - Color: Pink
- Variant A - Size M
- Variant B - Size L
- Variant C - Size XL
Product C - Master SKU 0002 - Style: Wool Jacket - Color: Black
- Variant A - Size M
- Variant B - Size L
- Variant C - Size XL
Product D - Master SKU 0002 - Style: Wool Jacket - Color: Pink
- Variant A - Size M
- Variant B - Size L
- Variant C - Size XL
If we do not ignore the top-level product model, we get 2 products with 6 variants each:
Product A - Master SKU 0001
- Variant A - Style Knitted Sweater - Color: White - Size M
- Variant B - Style Knitted Sweater - Color: White - Size L
- Variant C - Style Knitted Sweater - Color: White - Size XL
- Variant D - Style Knitted Sweater - Color: Pink- Size M
- Variant E - Style Knitted Sweater - Color: Pink - Size L
- Variant F - Style Knitted Sweater - Color: Pink - Size XL
Product B - Master SKU 0002
- Variant A - Style: Wool Jacket - Color: Black - Size M
- Variant B - Style: Wool Jacket - Color: Black - Size L
- Variant C - Style: Wool Jacket - Color: Black - Size XL
- Variant D - Style: Wool Jacket - Color: Pink- Size M
- Variant E - Style: Wool Jacket - Color: Pink - Size L
- Variant F - Style: Wool Jacket - Color: Pink - Size XL
By default, Malcom uses the top-level product model (Common) to create configurable products in Shopify with the variants mapped from Akeneo products. Note that changing this configuration later will create duplicate products in Shopify.
Review the information entered and Click on “Save Changes and Close” to proceed to the next step.