Currently the user must authorize the marketplace and then create unique listings for that marketplace. Over the next week or so, Shekhar will be working on the following:
1) Tweaking a generic Libereco Create Listing method that routes the posted data to the appropriate marketplaces.
2) Designing #1 such that the "routing" is authorization-aware. In other words, if the user has authorized Etsy, then the listing ends up on Etsy. If the user has authrozied Etsy, Amazon, and eBay, then the listing appears on all three.
According to the above logic, the marketplace fields exposed to the customer will vary from authorization to authorization. If I am just authorized for eBay, and eBay has fields A, B, C, then I see fields A, B, C when creating a listing. If I am also authorized for Etsy, and Etsy has fields A,B,D and F, then I see fields A,B,C,D and F when creating a listing (eliminating duplicates of A,B and C). The presentation layer will vary dramatically depending on the user's authorization profile.
Currently the user must authorize the marketplace and then create unique listings for that marketplace. Over the next week or so, Shekhar will be working on the following: 1) Tweaking a generic Libereco Create Listing method that routes the posted data to the appropriate marketplaces. 2) Designing #1 such that the "routing" is authorization-aware. In other words, if the user has authorized Etsy, then the listing ends up on Etsy. If the user has authrozied Etsy, Amazon, and eBay, then the listing appears on all three. According to the above logic, the marketplace fields exposed to the customer will vary from authorization to authorization. If I am just authorized for eBay, and eBay has fields A, B, C, then I see fields A, B, C when creating a listing. If I am also authorized for Etsy, and Etsy has fields A,B,D and F, then I see fields A,B,C,D and F when creating a listing (eliminating duplicates of A,B and C). The presentation layer will vary dramatically depending on the user's authorization profile.