Product Versions are incorrect in live order

Posted By TheCalicoTree Wed 16 May 2012
Add to Favorites0
Author Message
TheCalicoTree
 Posted Wed 16 May 2012
Supreme Being

Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)Supreme Being - (70,800 reputation)

Group: Forum Members
Last Active: Thu 18 Jun 2015
Posts: 98, Visits: 1,382
Hi,

We have just received an order where the customer selected 4 of the same product (Bath Towel), each with different options. The SKU for the base version is BS4.

The product option are colours.

The products have come through on the order as follows:

600g Bath Towel - Chocolate

(BTCHO600)

Colour:Chocolate

600g Bath Towel - Chocolate

(BTCHO600)

Colour:Sky

600g Bath Towel - Chocolate

(BTCHO600)

Colour:White

So the colour is correct, but the product name and SKU are incorrect. What is even stranger is that this SKU does not exist in the database. Is it generated at checkout?

This is potentially a massive problem for us and seeing as no changes have been made I am confused as to what has suddenly gone wrong.

Thanks

Helen
Paul
 Posted Wed 16 May 2012
große Käse

große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)große Käse - (509,334 reputation)

Group: Administrators
Last Active: Tue 10 Sep 2024
Posts: 807, Visits: 2,748
This suggests you have this product set to have individual combinations.

There are two ways of having options:

1. Options

In this case, there is a base version (holds the SKU) and then the options hang off this, and provide modification of it

2. Option Combinations

Same interface from a user perspective as above, but an extra step is performed in the back end to 'create combinations'. This creates a version record for each permutation of the options set for the product. So if you have colour (2 choices) and size (2 choices), 4 combination versions will be created, plus the base version (used for the front end). Each of the 4 combination records must have its own unique SKU (the back end auto-fills them into a form, but they can be manually changed in the form fields before you commit them), and each can have its own stock level.

The reason for doing (2) is largely if you need individual SKUs, or if you need to stock track the individual permutations of options (e.g. you need to know how many small black and large white items you have in stock, and which if any you've run out of).

What you describe sounds like you've done the extra steps in (2), which you don't need to since you only want a single SKU regardless of the options.


--
If my post solves your issue, can you 'Mark as Answer' so it's easier for other users to find in future.

If you would like to be informed of new features, new releases, developments and occasional special bonuses, please sign up to our mailing list: http://bit.ly/19sKMZb

Similar Topics

Expand / Collapse

Reading This Topic

Expand / Collapse

Back To Top