Bulk Upload Suggestions

[PetBazaar]

Two suggestions here for the price of one. Bargain.

During the bulk upload process, would it be possible to have a log generated for the Stage 2 portion of the upload. Nothing is more annoying when removing a selection of out of stock items than seeing 10 items were closed, 2 items were not closed. Then you have to go through the whole process manually to find the two still open items. A log file with a list of items closed or otherwise would be exceptionally usefull.

When doing a bulk upload, is there any chance that the "overwrite" option could also have the facility to use the SKU as its comparison field. Again, it's a similar situation as above. You correct a typo in your master database, or change the title to something more informative and you've got suddenly got an addition rather than an overwrite. Then with no stage 2 log you have to manually figure out which one has gone wrong.

[gazza]

Problem with using SKU is many sellers have duplicate SKUs, the field isn't used correctly by some. We would have to intriduce a strict unique running SKU rule first for this to work.

[PetBazaar]

Could you get around that issue if the upload file had an extra column that said "UseSKUComparison" with a Y or (N or blank) - every record having the same value. With N or blank the current routines are followed. However, only if there was a Y in this field then, during the Stage 1 import, a quick select, group by SKU where the count is greater than 1 would do the trick to catch duplicates. Just dump the whole upload if it fails.

Those who don't use SKUs are unaffected, those who use them incorrectly are encouraged to sort out their data, and those who use them properly get an extra feature.

Just a thought.