Support for configurable products

[skwp]

I would like to understand what's involved with taking a configurable product (e.g. tshirts with multiple sizes) and sending them to Reverb as individual entries. The assumption is that each will have a unique SKU (is this always true?)

[dunagan5887]

Yes, each simple product which is part of a configurable product will have a unique SKU. I would estimate about 3-4 hours for this update

[dunagan5887]

@skwp If the configurable product has images which are not on the child products, those configurable-only images will not be communicated to Reverb. Additionally only data related to the simple products will be sent to Reverb (only simple products are sent). Is this acceptable?

[skwp]

The idea here is that every configurable variation should be like the parent. So the images should appear on all children. Not sure what you mean by simple products being sent?

The way I see it is you hav ea Tshirt with S/M/L variants. This should result in 3 different products on Reverb, one for each variation, each with the images of the parent if the children don't have images.

[dunagan5887]

Simple product means child product. Am I supposed to be sending child and parent products to Reverb? Sending parent products wouldn't make much sense given that they don't have inventory.

So if the child product doesn't have images, then the parent's images should be sent? What if the child product does have images attached?

[skwp]

understood. yes I would say send the child's images if you have them, if not use the parent's images for each child

[dunagan5887]

Right, my concern here is that there's a chance that people could have the same images on the parent as on the child, which would cause in the same image being sent to Reverb multiple times

[skwp]

Yeah we should not combine images. either the child has images and we use only those or we use the ones from the parent if the child is empty.

[dunagan5887]

Scenario:

• Admin creates configurable product
• Admin adds image(s) to the configurable product
• Admin uses the Quick Create feature in the Associated Products tab to create child products for the parent
• Admin Saves the configurable product
• All image(s) added to the configurable parent will be sent to Reverb for all child products
• Admin adds an image for a child product
• The child product will now have the parent's image and it's own image on Reverb

I have confirmed this happening. At the moment I don't have a quick fix for how to go about this. I'm not sure a clean solution exists. The best would be to unlist the parent images once the image has been attached to the child

[skwp]

I'm ok with this. Sellers can clean up their own images by hand for this scenario

Sent from my iPhone

On Feb 4, 2016, at 3:14 PM, Sean Dunagan notifications@github.com wrote:

Scenario:

Admin creates configurable product Admin adds image(s) to the configurable product Admin uses the Quick Create feature in the Associated Products tab to create child products for the parent Admin Saves the configurable product All image(s) added to the configurable parent will be sent to Reverb for all child products Admin adds an image for a child product The child product will now have the parent's image and it's own image on Reverb I have confirmed this happening. At the moment I don't have a quick fix for how to go about this. I'm not sure a clean solution exists. The best would be to unlist the parent images once the image has been attached to the child

— Reply to this email directly or view it on GitHub.