You can use it to bulk update products also. The import program will lookup products by sku, if the product currently exists in the database it will update the existing product. If the product sku does not exist it will insert a new record.

-Scott

---

Scott Kelly
Project Manager

In the BuyNow module settings "Product Listing Setup" section there is a checkbox titled "Force Unique Sku". If you check that box the cart will require unique skus be saved at the product level. Currently, the cart doesnt have a similar setting to force unique skus at the variant level. I do see your point about forcing unique skus, however there are some cases where businesses would want to allow duplicate skus in the database. For example, if they clone a product and deactivate the old product to test drive a new pricing structure or maybe they just have deactivated a product and want to keep it in the database and have created a new product wih the same information. Another example would be if you are running multiple buynow modules on different pages secured by different dnn roles for different customer types may drive the requirement to have duplicate skus in the database. If the cart enforced this rule if would be less flexible and our goals is to make the product as flexible as possible to support as many different business requirements as possible. The stored procedure above used in the product import program that searches on productid, variantgroupid and variant name is the best way that I can see to determine if an existing variant exists in the database before executing an insert or update. Let me know if you see a better way.

---

Scott Kelly
Project Manager