Product & Child Variants - YOUR Help, Ideas, Suggestions Needed

[ArtcoInc]

@burt

We sell high temperature gloves. Within each temperature range, there are three lengths. Each has a unique part number and price. For example ...

1000 degree (description of the 1000 degree gloves)
... 14 inch (#1000-14, $14)
... 18 inch (#1000-18, $18)
... 23 inch (#1000-23, $23)

1500 degree (description of the 1500 degree gloves)
... 14 inch (#1500-14, $114)
... 18 inch (#1500-18, $118)
... 23 inch (#1500-23, $123)

2000 degree (description of the 2000 degree gloves)
... 14 inch (#2000-14, $214)
... 18 inch (#2000-18, $218)
... 23 inch (#2000-23, $223)

I never tried to use the attribute system as it didn't allow me inventory control over each individual length and temperature glove. Your proposed system seems to address that. Thank you.

Yes, I'm willing to test this.

(even if it means updating to the new version of Phoenix)

Malcolm

[burt]

TY for posting! Yes, I believe this new system would cover your way of working

Glove - is the Parent
Child is 14"
Child is 18"
etc

---

For now it's all about using this thread to learn how shopowners run their shops, what the demographic of their customers looks like and so on - to try to get an understanding of the needed direction of travel for this new system...

[Omar_one]

Where am I, in the Admin Side


parchi-admin.png


Parent
-> Child
-> Child
-> Child
Normal
Normal

maybe show only Parent Products in the product list (admin/catalog.php) to improve loading speeds and readability for larger shops.

[burt]

maybe show only Parent Products in the product list (admin/catalog.php) to improve loading speeds and readability for larger shops.

I'm thinking that might make it difficult for the average shopowner to edit the Child Product?

[BatteryTrader]

Do not really have anything constructive to add to this discussion at the moment, but we use attributes quite a lot, not as part of the same range, more as a upgrade to the original product.

The biggest issue for us is price changes.

We might have product A, which is £10, and you could upgrade to product b that is £11, so the attribute would add £1

But say Product A has stayed at the same price, while Product B, made by a different manufacturer, has increased to £12; the only way to deal with this is to increase the attribute, which is very time-consuming and not that easy to see or use.

That said, I am guessing there are many other things to think of. If product B is an upgrade, using the proposed method, it can have its own picture. Does it then also have a small description? I will assume it would, just as attribute does, as well as price etc, so in effect another product. I have many thousands of upgrades / attributes, some thought would have to be put into how they are described.

As a shopowner, I think another way, or maybe a complementary way in certain circumstances, of providing attributes/upgrades to the product is interesting.

I am following.

[PiLLaO]

Only write to say that I'm here looking, I only use a few attribs, and I think that I can't apport nothing (at least at the moment)

[bonbec]

I'm thinking that might make it difficult for the average shopowner to edit the Child Product?

And what about adding an acronym to the right of the parent's name in the listing to indicate that there are children?

[Omar_one]

I'm thinking that might make it difficult for the average shopowner to edit the Child Product?

Each parent row has a small + icon to show the "Child Product"

[burt]

Great feedback, tnx guys - you have given me some more ideas to think about.

I think this system might be interesting.
Not ideal for all, but certainly another tool that will do a job.

[azpro]

@burt Just reading the topic (I am tied up with all sorts of things IRL - not having time to work on Phoenix)... Think it is a good start!

Just an idea I have for admin - create from Main product a pop-up/off canvas for adjusting prices. So you don not need to update every slave.

Furthemore I think a simple way to copy slaves would be great.

Thanks!