Discussions

Attributes + Sku + Multiple products instance

Hello,

I have about 100 products, those are flowers, so they have weight, tall, blooming time... For those fields I think its ok, they will go in the "data" field from "products" table in my "Flower" product type, if I'm not totally idiot.
But for the next, I'm totally lost. I need for each flowers, an "age" attribute which give 1 different sku and price for each option. The number of options depend on flowers.

=>Flowers are the same but they have each many entries with few differences:
- age 3,5,7 (but it can be only 3 or 5 or 3 and 5 or...)
- sku (one for each age)
- price (one for each age and different for each flowers)
Other fields are equivalent.

    Example:
  • flowers 1 => 3 years - sku 100 - 50€
  • flowers 1 => 5 years - sku 30 - 70€
  • flowers 2 => 3 years - sku 200 - 30€
  • flowers 2 => 5 years - sku -60 - 110€
  • flowers 2 => 7 years - sku 1000 - 110€
  • ...
  • flowers 100 => ...
    Other needs:
  • When the customers choose a flower, he will see each option for this one, like a select box with 3 and 5 for flowers 1 and 3,5,7 for flowers 2. So sku and price must be load from this select box (Like the demo I think).
  • And when my client (the website administer) want to change a flower description, it must change the description for each sub-flower.
  • I have 4 class, which is just a word, they didn't have any difference with other class, I just a ordering. I will make it after with 1 field.

My question is, it is possible to do this (i believe yes, this module is pretty broad minded), and if it yes, any help to do this will be appreciate?

First I'm french, so be cool for my english. And i'm on training for my third year CAT, so i'm not comfortable with drupal and not really with sql... but I want to achieve this. If you didn't have understand my goal, please tell me I will explain it better if I can ^^ .

Tags: 
attributes
sku
multiple products instances
lberbey
Posted: Jun 7, 2012

Comments

lberbey on June 8, 2012

Hum, it seems that I can use "commerce_products_type" for each flowers, but, I don't think it's a good idea, even this is the best way to do that.

Any idea? thank for answering if you have any idea...

joecanti on July 28, 2012

Hi,
I'm not sure exactly...It's quite a specific use case, and I'm only really getting started with Commerce myself. But it's a good idea to try the inline entity form module - it really ties it all together with the products/product displays.

you'll need a new product type for each product that needs a different set of fields - so from your example it appears like you need only the one product type.

It may only be possible to create an ending on the SKU to make it unique - EG sku100-0001 - but it's not ideal.

Possible you need a way to attach an sku to your product display - a sort of master SKU - that's what I'm searching for as well.

Good Luck! Joe

audster on September 20, 2012

Okay, I think I'm banging my head on this too.

I am setting up a store where each product can be purchased with fixed options, HOWEVER those options are not the same for every product sold, in fact each product has unique attributes, so there is no standard set of attributes I can set up for these products..AND each of these options changes the price...

They go like this

ITEM A $300.00
with unique option just for this product A - $350.00
with unique option just for this product B - 400.00
with unique option just for this product C - 425.00
etc

ITEM B - $7000.00
with unique option just for this product A - $7500.00
with unique option just for this product B - $7800.00
with unique option just for this product C - $8000.00
with unique option just for this product D - $9275.00

So just to be clear, the options and therefor prices available for each product/SKU are different for each SKU!

To top it off, since I want the orders to also be sent to the drop-shipper, each one of those configurations has a mfr part number that is different.. and must be used when forwarding the order to the drop-shipper!
ie
ITEM A with option A has mfr # 1234
ITEM A with option B has mfr # 4567

I'm struggling with the best way to do this, in fact I haven't' even been able to see the solution well enough to begin. Actually, I think I do see the solution, I just don't like it...

It seems like I'm going to have to create a product type for each ITEM and attribute field for each items attributes (options A, B, C, D) and correlate with their pricing. I was thinking I could make the attribute field hold the different mfr numbers and prices.. but I'm not happy with the idea that for each of the hundreds of products I will have to create a new product type with attributes specific to only that type...

I can't see how this is a "fault" of DC, but this clearly isn't a unique problem either as evidenced here.. I guess I'm just looking for a solution that isn't so laborious...

Any ideas?

PS, I speak fluent french... my written french is horrible, but I will try if you need language arts help!

torq on September 20, 2012

I'm not 100% sure if I'm following along correctly, but, I'll toss in a couple cents.

A did a project for a client that sells helmets (Bell Racing). So, here's an example.

The GP2 Helmet ( http://bellracing.com/helmets/pro-series/gp-2 ) has 2 unique properties, size and color. A small white GP2 helmet sitting on the shelf is different then a medium white GP2, and is different compared to a small black GP2. Because each one is different, they have unique SKUs. Which makes sense, because they're physical items that are already made. There isn't a warehouse full of generic helmets, and when ordered they aren't turned into the model, color, and size requested.

So I have a helmet product type that has fields for color, size, and an image (along with the sku & price):

Products:
Sku: 2021982 | Size: 6 3/8 | Color: White | Price $599.99 | theImage
Sku: 2021983 | Size: 6 1/2 | Color: White | Price $599.99 | theImage
Sku: 2021984 | Size: 6 5/8 | Color: White | Price $599.99 | theImage

Then on my helmet product display, I have all the rest of the stuff you see on that page. Specifications, description, etc.

Product Display:
Title: GP.2 | Body: (a bunch of copy) | Specifications: (a bunch of copy) | Product Reference: 2021982, 2021983, 2021984

I have multiple product types that are dependent on their options. I have generic accessories that only need the default sku & price. The rest of the information is entered into the generic product display. I also have accessories like Shields, that only have a color option along with the default sku & price. So that unique option of color is on the product type, which the stuff that is unique to that model is on the product display.

Fields on Product - unique that individual item (The Small White GP.2 Helmet)
Fields on Product Display - unique to that model (The GP.2 Helmet)

Hope that answers some questions.

mikeaja on November 11, 2013

@torg not sure if you still are following discussions here, but your site does highlight an issue here (nor sure if that is an issue with DC or with your setup)

Select a size and a color ( the update can be a little slow ), and then change the size again. You lose the colour (which is not so bad, but surprising given this is not a common issue on some much older e-commerce systems).