Over-complication, Made Simple

Part of my current job is to apply an online store’s tool set to conform to the kind of selling an owner wants for their store. Sadly, this often can create a severe case of unnecessary over-complication, because teaching a computer program that a mix-and-match sale item with four different SKUs can have a series of product-specific quantity discounts applied to the end total isn’t an easy task.

Whoever tried to explain how to do this to the store owner the first time may have figured out how to make it work, but creating a series of product discounts for each flavor prevents the individual flavors from being mixed and matched unless you create a series of conditions for each and every possibility… up to twenty-four! For example, you get a discount if you buy three items in any flavor, which means if you buy three strawberry-flavored items or buy three chocolate-flavored items that you get a discount. Unfortunately, the store program doesn’t understand that two strawberry and one chocolate is ALSO three items because it’s a product promotion and not a store-wide promotion.

The fix sounds complicated, but is actually very simple: don’t over-complicate it to begin with. If there is only one product with a choice of four flavors, you can use attribute editing to give each flavor a separate SKU, then create a series of product promotions for three, four, or full-case discounts. It’s simpler, it easier to set up, and you could add more flavors later without rebuilding the product from the ground up.

Is it smarter to think up an easier way to do something to get out of doing it the hard way? Nah. After all, laziness IS the “mother of invention.”

Orignal From: Over-complication, Made Simple