Step 1: Check if your product exist on Amazon
You can search Amazon catalog by EAN / UPC / SKU / ASIN / GTIN / ISBN / JAN / MINSAN.
By using this search, you know the Product Type and other information that are helpful for later steps, if the product exists on Amazon. Navigate to PrestaShop Sync > Search Amazon Catalog, paste in the identifier and click Search.
If the identifier exists on Amazon, the result contains 2 sections
- Brief information table: Image, name, all the identifiers, relationship, brand, product type.
- Full information as raw JSON.
Step 2: Create listing template
Listing template maps the product data in PrestaShop, into Amazon defined structure.
Amazon classifies the products by Product Type (category / universe). Each product type contains a different set of fields. They are divided into 3 groups:
- Variation theme: Only available on product types that have variation. Decide which attribute(s) is used to define the variation. E.g. A drinking cup may have the variation base on color, or age + material, etc.
- Recommended fields: Including, but not limited to fields should have data when send to Amazon.
Navigate to PrestaShop Sync > Amazon Listing Templates, click Add New Listing or edit an existed one.
If your product exists on Amazon, choose the Product Type you found in Step 1. Otherwise, browse Amazon catalog to find the best match.
Each time you change the Product Type, the module loads all its fields.
Configure the listing template
Except the variation theme field, all other fields have a same list of possible options to choose from.
If there is no option that fits, you can choose the Default Value. Default Value is helpful on some fields that Amazon offers a set of choices. E.g. there is only 2 choices for the field Is exempt from a declared supplier external identifier (supplier_declared_has_product_identifier_exemption)
- Brand: Use PrestaShop manufacturer
- Bullet_point: Use PrestaShop product description
- Country_of_origin: Choose France default value
- Product_description: Use PrestaShop product description
- Supplier_declared_dg_hz_regulation: Choose Non-applicable default value
A listing template is intended to use for many products. Don’t configure a field with a specific value that is bound to a particular product. For such case, you can specify it in Step 4.2.
Step 3: Associate listing template to products or categories
Navigate to PrestaShop Sync > Filters, choose the listing template you would like to associate to a particular product.
You don’t need to change the red X on the column on the left of Amazon Listing Template column. That column is for automatically updating only, not for creation.
You can also associate s listing template to a whole category.
The listing template on product has higher priority than the one on category. That say:
- If product A is belonged to category C
- Product A has the listing template T1
- Category has the listing template T2
→ The template T1 will be used when creating product A.
Step 4: Create simple product
Navigate to PrestaShop Sync > PrestaShop Sync, click on dropdown action and choose Create. Products that don’t have listing template are unable to be created:
It leads you to the creating wizard:
For product with variations, you need to choose the one you are going to create, parent or child:
The creating wizard is basically the same as the chosen listing template, with field data of the product itself. Continue reading to find out details about each section of the creating wizard.
Step 4.1: Product identifiers (ASIN / EAN)
Use ASIN / EAN to effectively tell Amazon to match this product to the existed one, keep as much as possible the Amazon data.
ASIN / EAN can be taken from Step 1.
Step 4.2: Override the listing template if needed
As said earlier, all the fields of the listing template are show.
Each field has the data of the product itself, or the default value you chose on the listing template.You can set a different value for any field by click to Override this, below each field.
Step 4.3: (Optional) View the data before send to Amazon
Scroll to the bottom, click on Build data only, it shows the payload that will be sent if created:
Step 4.4: Send to Amazon
Click on Send to Amazon, to fix the error if any.
Step 4.5: Check the result
After a success send, Amazon will take some time to evaluate and list your product. You can check the result by either way:
- Click on Get SKU info from Amazon. If you see the data and no error, the creation is a success.
- View actual result on Seller Central.
Example of a success creation request
Step 5: Create product with variations
Similar to Step 4 above (Create simple product), with some minor differences.
You have to create the parent product first, with minimal information. The parent product is a virtual product that will hold all the variations later on.
Step 5.1: Create parent product
Parent product does not have EAN, don’t need to fill it. Send the product to Amazon as normal:
The parent product will appear as incomplete in Seller Central:
Don’t worry, we are going to add children / variations to it.
Step 5.2: Create variation
Go to the creation wizard of the variation, click to send it to Amazon.
If the sending is success, Amazon takes 10 minutes ~ 2 hours to reflect the changes. You can check for the result by either way:
- Get SKU info from Amazon: If no error appears, Amazon accepts the listing
- View the result directly in Seller Central
The parent product becomes the holder for the first variation.
Continue to add the remain variations. They will be grouped inside the parent product.
The variation is incomplete because it does not have price nor stock. Adding this information in the step below.
Step 6: Complete the creation by adding price + stock
Back to PrestaShop Sync list, choose the product you just created, select to sync the stock + price (tax including or not), and click Update
This updating process is also executed automatically if you enable the PrestaShop Sync option in Filters page
You don’t need to fill all the fields in the listing template, there are too many of them. However, Amazon usually requires data more than the fields in Recommended section. To quickly find out which fields are mandatory, just send an initial request. Then, correct the returned errors one by one.