Volume Weight Calculation : Component Based Products

[NVL]

Got a nice one for you here with V8.

I am using zone tables and maximum weight, volume is set to divide by one and I have the actual volumetric weight based upon the 6000 rule in each volumetric weight field - no problems there with working this and I understand how that works...

What's wierd is that only on component based products only the volumetric weight is being doubled, not the actual and the first thing I checked was the "divide by" which has a value of numerical one as above... but then it dawned on me that such an error would also affect the non-component based products. This happens with the rules set to use the associated product shipping and also with the variable un-ticked, there's no workaround by setting the conversion to half (0.5) because that would affect the non-component based products also... in this example the volume weight is the greater value for the product, it is the same value in both product and associated product...

Am I missing something obvious?

[leehack]

5 times i've read and i still haven't got the slightest incline what on earth you are on about. Until i read that, i fancied myself as a bit of a shipping guru, now i feel like nothing more than a stowaway rat.

[NVL]

Aye right Lee...

Ok it's simple and perhaps I gave too much detail too early on.

Shipping is working, it's based upon Maximum Weight and I am using the Zone / Class Tables method. The volume weights are set for each product and this has been done by the L x B x H / 6000 calculation as is common in shipping, the "divide by' setting in my class tables have the value "1" so that the volume weight I have calculated is assumed to be correct.

The problem lies within products which are component based and / or have an attribute with a choice, then an associated product. For no apparent reason the volume weight is being doubled only upon these products, standard products are not affected.

Clear as mud ratty?

[NVL]

...by the way, if I fix my attribute / permutations pricing issue this thread will need addressed again too. More holes than a seive this software...

[Mike Hughes]

The problem lies within products which are component based and / or have an attribute with a choice, then an associated product. For no apparent reason the volume weight is being doubled only upon these products, standard products are not affected.

This wouldn't be because Actinic is assuming the main product AND the associated product each have a volume/weight would it?

Mike

[NVL]

It shouldn't as the setting "no orderline for main product" is ticked.

[Mike Hughes]

It shouldn't as the setting "no orderline for main product" is ticked.

I know that controls whether the items is listed on the invoice, but not sure how it affects weights.

If you have 'no orderline..' ticked then presumably you could set the weight of that item to zero to see if this is the problem?

Mike