Tiered/Group Pricing + Media

[dguedry]

Working on a Magento import plugin (https://github.com/dguedry/reaction-magento-import). Are there any plans to implement tiered/group pricing? We use this in our Magento stores for retail vs wholesale.

I'd like to go ahead and start developing a "Group Price" plugin if it's not already slated.

Thanks!

Donnie

[aaronjudd]

In Reaction, variants, options, etc are all product documents, and all your images can be associated at any level, (so at the product) and as many as you want. The association is in the image meta data, and right now the default view is just the first image is determined by the priority value in the meta data. If you do associate to both products and variants, you'll need the ancestor array from the variants so that can retrieve all associated images from the Media collection. ( by default, we'll cascade down this ancestry when presenting a product, so we don't have products with no images when a variant does have images).

[aaronjudd]

Regarding pricing, this can be done via the "Discounts" collection (which is likely to be renamed "Pricing" in the future, because that's the true intent). We'll be adding conditionals soon, but what I think you are looking for is to return a price/rate as a conditional audience result, and that's what we're implementing there..

[dguedry]

The product grid picks the correct image if the image's metadata only contains productId (and variantId == null); however, the productImageGallery.js helper for media selects by variantId only. So, if the product's variantId is not set, all images that have a variantId of null are returned to the product page (even though they don't have the correct productdId).

[kieckhafer]

I'm working through an issue (#1303) right now that seems to have a tie-in to this discussion. On the product grid, we seem to only subscribe to and / or only publish top-level products (type: simple), no variants (type: variant), meaning we can't use our getVariants method, or any other we already have for that matter, as this needs the variants subscribed to in order to check match them to their ancestors.

I'm currently working to add the Variants info into the grid page data, so ancestor info will be available, by subscribing to all the data in the products collection, not just top-level products.

Not only will this help with what we are trying to achieve in #1303 and #1715, but it will also set us up for the future when we want to display Product Variants and Options together with the top-level product on the grid page.

Update: PR #1738 updates the product publication to publish type: variant data as well as the type: simple product data.

[aaronjudd]

Feature request that requires more definition to meet our current issue guidelines.