Hi Weston,

Thanks for the suggestion.
Actually a product has many compatibilities so I don't think
Spree::ProductProperty is an easy way to do that.
Also, compatibility info is hierarchical.
So once a customer selects a make, we have to provide models for that make,
and so on.


On Fri, Jun 14, 2013 at 11:28 AM, Weston Platter wrote:

Hi Sam -- I'd suggest describing part compatability in a *Spree::Property*,
which *:has_many Spree::Product* (s) through *Spree::ProductProperty*.
I'd then try to create a Solr/Elasticsearch feature to specifically target
vehicle compatibilities in the Spree::Property table when searching for
Spree::Taxon or Spree::Product.

Happy to talk more if you want.

On Thursday, June 13, 2013 11:21:30 AM UTC-6, Sam Kong wrote:


I am considering to develop an e-commerce shop for auto parts with Spree.
One special feature for an auto parts shop is that every product has
vehicle compatibilities list.

For example, auto part 'A' is compatible with
- Toyota, Camry, 2000
- Toyota, Camry, 2001
- Toyota, Camry, 2002
- Toyota, Corolla, 2000
- Toyota, Corolla, 2001
- Toyota, Corolla, 2002

Usually a product has about 100 compatibilities but sometimes it's more
than 1000.

A customer should be able to search for parts for her car.

What do you think is the best way to implement that?

Here's what I think:
Taxonomy could be used.
However, making a hierarchy for all combination is not practical.
Making 3 taxonomies for Make, Model, Year seems to be one option.
Does Spree support filtering with combined taxonomies?

Any advice would be greatly appreciated.



Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 5 | next ›
Discussion Overview
groupspree-user @
postedJun 13, '13 at 5:21p
activeJun 19, '13 at 12:45a



site design / logo © 2022 Grokbase