Well ptogel
Ive had about 4 hours sleep and to wake up and check that reply, is certainly make me work for my money
Its also like the multiple tax problem, this is something we talked about here for nearly a month whilst researching how to develop it, and just couldn't work out a way to get around it. For example if somebody lives in America, and another person lives in the UK, then the price could be different due to different tax amounts.
So what we decided to do, is export all products at both tax amounts, then at least one is right, allowing you to manually delete the other if needed. I know this is a hard job, but we couldn't think on how to export the products without adding in a tax manual amount over ride, so the admin user would add in the tax %, which it would calculate it on. But then the price would be wrong for some countries!!!!
Can you see the problems with it
Your having a similar problem that is almost impossible to correct in the system, as it doesn't matter how we built it, it wouldn't work for all shopping groups, child products, and attributes, as the combinations go into many thousands or millions of products.
We have one client with 300,000 products and many of them are clothing with different sizes and colours, so in theory with 3 sizes S,M,L and 5 colours, you would export the main product plus 5 x 3 = 15 combinations, so each product would really have 16 exports x 300K products = an XML document with 4.5 million products on it.
Also we have a guy who sells computers with many attributes to add to the product, sometimes there could be about 100 different variations or more.
And the worst one is our
Width x Height hack, that readjusts the price depending on the width and height you add.
I'm not sure i can help you with this, that is why i added the demo version for you to test, so you would be able to see if it was working or not before you bought it. I don't think even a shopping groups selector would solve this problem as it is also the child products that are causing a conflict.
if you can think of a way for me to fix this please let me know, as i think it would be great to release 4.1 with the corrections needed.
All the best
Ian