What is happening?
Maropost Commerce Cloud are migrating our Amazon AU and Amazon US integrations to the new Amazon SP-API, which replaces the deprecated MWS API.
Part of the integration, including Order download, Order Status/Tracking upload, and Listing Status download, already runs on the SP-API. The last section to be migrated is the Listing Upload section, which involves the Product data being synced from Maropost to Amazon. This includes “offer” related data such as quantity and pricing, and “product” related data such as images, title, and description.
When is it happening?
Maropost Commerce Cloud engineers will perform a staggered rollout to different segments of our merchant base between 16-18 November. The exact date for your store will be communicated to you via email and Control Panel in-app message.
Why do I need to know this is happening?
Because with the new SP-API comes a new set of Amazon Product Types and Product Attributes, meaning the change-over will require some mapping reconfiguration. The affected configuration in the Control Panel is found in:
- The Amazon “Category Mapping” page
- The Amazon “Product Field Mapping” page
The Amazon Category, Product Type, and Product/Offer Attribute Data (which we refer to as the “Amazon Taxonomy”) has changed to an extent where it is not possible to completely automatically migrate your current mapping configuration to match that of the new data. You will therefore need to manually reconfigure some of the mapping to ensure your product data can continue to successfully sync to Amazon.
What should I expect to happen?
Category Mapping page
The category mapping configuration will be migrated to the new Amazon categories and product types. Please double check this page after the migration.
Product Field Mapping page
Common fields:
The non-category specific field mapping at the top of the page will be migrated to the new Amazon attributes. Please double check this page after the migration. Note that some new attributes may be available here that you may want to map or need to map if “required”.
Expect Amazon field names to have changed, for example “Shipping Template” is now called “Merchant Shipping Group”.
Category-Specific fields:
Due to the extent and intricacy of the API changes in that section, we will not be able to migrate your Category-Specific field mapping configuration programmatically; You will need to reconfigure manually.
To assist you with this process, we can provide with a backup of your existing mapping configuration in a CSV file. Please contact your relevant Maropost Commerce Cloud Support team to request the file (before or after the migration).
See step by step guide for a suggested workflow to complete the reconfiguration.
What should I do (step by step)
- Navigate to the AMAZON AUSTRALIA > Category Mapping page. Click on each of your Maropost category visible on the page and check that:
- They are mapped to an Amazon Australia category
- A Product Type is selected under “Amazon Australia Product Type”
- ⚠️Ensure you have completed Step 1 before you navigate to the AMAZON AUSTRALIA > Product Field Mapping page and check that:
- In the section under “Product Fields”, all Required fields are mapped.
- Any other non-required field that you wish to map is mapped. We can provide with a backup of your existing mapping configuration should you wish to check it as a guide post-migration.
- Similarly, check each expandable section under “Category specific product fields” and ensure each Required field is mapped as well as any other field that you wish to map (e.g “Variation Theme” and corresponding variant-related fields such as “Color”, “Size”, etc.)
- Navigate to AMAZON AUSTRALIA > Dashboard and check for errors. Add product data as required by Amazon and complete field mapping accordingly. Note that when the Field Mapping page will pre-populate field mapping when a Product Specific or Custom Product Field is found that matches the Amazon attribute name. You may find this helpful to complete the Category-Specific Field Mapping after adding new product data.
Once the Maropost Commerce Cloud developers have migrated your site they will continue to monitor the Maropost Amazon integration.
Is there anything I should look out for?
Using ASIN as an identifier
Previously, the Amazon ASIN could be used as a product identifier instead of a product’s barcode (UPC or EAN). Now, Amazon requires that a barcode is provided (UPC, EAN or GTIN) and the ASIN can be specified in a new field called “Merchant Suggested ASIN”. We have amended the logic of the “Automatic” barcode detection so that if an ASIN is present in any of the UPC/EAN fields in Maropost, it will be sent as “Merchant Suggested ASIN” along with the barcode. You will however need to ensure that no product only holds an ASIN in Maropost without a barcode.
If you have opted for “Manual” barcode detection in the Amazon integrations Settings, you will see the new “Merchant Suggested ASIN” field in the Amazon Field Mapping page, and you will need to ensure that your mapping configuration and product data is still valid to accommodate for this new requirement.
New attribute requirements
In some categories, the new Amazon API will require more product details than the previous API. The attributes requirement is dynamic, so you may not know in advance all the attributes that you need to provide. For example:
If a shirt size is provided, you may need to then specify the “size system” and “size class”.
Amazon may require that you specify the “Power Plug Type” and “Accepted Voltage Frequency” on a football, but the “Accepted Voltage Frequency” will no longer be required if “Power Plug Type” is set to “None”.
Attributes that do not vary per product (i.e. the same value applies to all items listed on Amazon) can be added as a "static value" in the Field Mapping page using the "Type in a value" option:
For attributes where the value will vary per product, we recommend adding these attributes on the products as "Product Specifics" rather than Custom Product Fields, as the number of Custom Product Fields available is limited.
On variation listings, required attributes that are common to all the children can be added to the Parent only and the Children will inherit the parent's mapping if the option to "Inherit missing variation product data from parent product" is selected in the Settings page.
We recommend focusing on one or two products at a time initially before bulk importing the remaining products. This will allow you to work though the process and observe any errors that may not present until the current one is corrected. Once you're comfortable, you can then plan your bulk import to reduce the need to repeat the often time consuming import task, especially when a large number of products are included.
Watch this video to learn how to bulk import Product Specifics: https://galaxy.maropost.com/s/article/video-import-product-specifics
Valid Values
It is possible that for some attributes, the list of available values has changed. Values that may have been accepted by Amazon may no longer be accepted, or have changed (spelling, casing…).
Click on the ℹ️ icon to check if a field only accepts a limited list of values, and see what those values are.
“Color” attribute
The Amazon “Color” attribute is now found in the common section at the top of the Field Mapping page. As it used to be Category-specific, the mapping of this attribute will not be migrated.
"Offering Condition Type" attribute
The “Offering Condition Type” (condition_type) attribute is now found near the top of the Field Mapping page, in the common "Product Fields" section as part of the "Offer" group.
As the "Offering Condition Type" used to be Category-specific, the mapping of this attribute could not be migrated. This attribute is required in a large number of categories, so the error "condition_type' is required but not supplied" is likely to affect most listings until resolved.
Merchant Shipping Group
The “Shipping Template” attribute is now called “Merchant Shipping Group” and no longer accept the name of the Shipping Template configured in Amazon Seller Central. This attribute is optional and your Default Amazon Shipping Template will be used if the field is not mapped in Maropost. See further instructions on where to find the Merchant Shipping Group ID in Amazon Seller Central.
CONTINUED BELOW (See Best Answer)
