EasyPopulate 4.0 Support Thread

[Crunch]

@Crunch,

What are the separators for attributes and additional images?
With regards to attributes, how is a grouping of option names expected to be considered/separated?
Ie. If a product has an option name of size and an option name of color, are they looking for all potential sizes and all potential colors or only the combinations that are expected to exist, both, etc...

Unfortunately I was provided no specifics. I was cold added into an email thread between the store owner and an Amazon rep discussing migration to a Amazon store.

This is all they asked for:

"Send me a data file or spreadsheet (as a product export from your eCommerce platform) containing the following product information for the initial items you’d like to list:

• Product Name
• Brand/Manufacturer
• UPC Code
• Price
• Quantity
• Description
• Image URL

There are many other optional fields that can be included, such as your own SKU#, search keywords, additional images, size or color variations available, weight if you want to charge weight-based shipping rates, etc. But those are optional—the fields above are the basic ones needed."

They refer to attributes as variations.

I think at this point I will send them two data files - the "Complete Products (with Metatags)" and "Basic Products Attributes (basic single-line)" and see if that works for their integration team. If I receive any other info, I will let you know.

[mc12345678]

Unfortunately I was provided no specifics. I was cold added into an email thread between the store owner and an Amazon rep discussing migration to a Amazon store.

This is all they asked for:

"Send me a data file or spreadsheet (as a product export from your eCommerce platform) containing the following product information for the initial items you’d like to list:

• Product Name
• Brand/Manufacturer
• UPC Code
• Price
• Quantity
• Description
• Image URL

There are many other optional fields that can be included, such as your own SKU#, search keywords, additional images, size or color variations available, weight if you want to charge weight-based shipping rates, etc. But those are optional—the fields above are the basic ones needed."

They refer to attributes as variations.

I think at this point I will send them two data files - the "Complete Products (with Metatags)" and "Basic Products Attributes (basic single-line)" and see if that works for their integration team. If I receive any other info, I will let you know.

Well, I began creating a sort of EP4 plugin to try to accomodate. Figured why not. Seeing that the "combined" list of attributes is expected to fill in a single block I thought I would try to find out. :)

Didn't see anything about language though, like identifying the content to a language (as you may have come to know, EP4 does support populating multiple languages) so was going to try to adapt to that as well... perhaps though in the conversations you can find out some more information.