I have many products that have a general SKU, and variations of that SKU for each customer choice. In BVC 2004.7, this was controlled int the admin inventory page for a product. After migrating these products, the tool removed the custom SKUs and created its own based on the general SKU (product ID) by appending a single letter.


e.g., in BVC 2004.7, a product with the ID of CD-612X, has a SKU of CD-612C for the cherry finish customer choice and CD-612W for the walnut finish customer choice, etc. After the migration, these all got lost and the tool created all new choice SKU entries for product CD-612X. The BVC5 catalog entries are now CD-612XD for the cherry and CD-612XB for the dark oak. My drop ship vendors will reject these invalid SKUs. This has to be fixed because I cannot redo these manually for my entire catalog. Basically, BVC5 is useless to me without this fix along with the other migration problems I recently reported that have not yet been addressed. Are any of these even being looked at?



frank