ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno Busco" <bruno.bu...@gmail.com>
Subject Re: What is the best approach?
Date Sun, 18 May 2008 11:47:14 GMT
reading documentation and exploring the catalog manager application I am
actually on the path of defining same feature types and features for
"Diameter", "Height", "Width", "Speed code" and "Load code" and adding them
to my product as "Distinguishing" features.

So doing I get the features printed out in the product details in ecommerce
and a combo for each one of the feature is present in the category search in

I started defining the features as "standard" but they were not displayed in
the product details in ecommerce.

Now, for the brand, since it would be good to let the customer filter for it
also, should I use another feature or use the "Brand Name" field?


2008/5/18 Scott Gray <lektran@gmail.com>:

> Sounds like virtual/variant products could be a good fit, you've got a
> brand
> name (category?) model name (virtual product) and then the various sizes
> (17x175x45) and codes for the variants.
> Regards
> Scott
> 2008/5/18 Bruno Busco <bruno.busco@gmail.com>:
> > Hi,
> > I am considering to use ofbiz to implement an ecommerce site that sells
> > exclusively tyres.
> > Every tyre product has a specific code and some parameters as diameter,
> > width, height, load code and speed code.
> >
> > In the site there should be the possibility to filter and list all
> product
> > specifing one or more of the above parameters.
> > I would like to know what is the preferred way to implement this.
> > Every tyre type must have a specific productId toghether with its
> > parameters
> > so I do not think this is going to be a configurable product, am I right?
> >
> > At the moment I have extended the Product entity with those additional
> > fields, but I am not sure to have done the best think.
> >
> > Any help will be greatly appreciated.
> >
> > -Bruno
> >

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message