Matt, I've got 8 choices (actually, I use modifiers) on this and other products:

http://www.missionfurnis...ne-Cabinet__MAS742R.aspx

Try switching to modifiers if you don't need to edit the URL... I don't need to fiddle around with the URL, swapping images, etc. Perhaps choice editing is topping out and that's where you're hitting the limit.

Hey Matt,

Do you still need to increase this limit? There is a setting in the database you can modify to increase the number of product choices. Like you mentioned though, a huge number of choices on a product can make the product pages really slow (Think of the product choices like individual products - if you load a product that has 1000 choices, well your essentially loading 1001 products). If you still want to increase this limit, just say so.

Thanks,

It's hard to imagine that I will not be able to assign sku's numbers to a product with different choices.


I have over 3,000 skus at UnoClean.com, a large warehouse. If I can not assign different skus to different colors, sizes of the same sku how is the warehouse personnel going to locate the product. We run a warehouse by location/bins/sku



I will have modifiers on most products, i.e. we sell by the single item, by the case. Floor pads just by itself has 5 different sizes and 8 different colors. I could go on with most of our products.



By raising the web app settings to accomodate my existing BV4 site - what performance hit will I take.

I enter a product. I click "Product Variations". I add let's say 2 choices to the product (Size & Color, 4 options each)

That's 16 SKU #s. When I hit 100 variants, the website says no more are allowed.

I have been told that the application is capping it at 100 variants due to performance reasons. So let's look at the fact that I have a store that has roughly 75% of it's catalog needing unique SKUs (solved with variants). Let's say that the site is going to need 6000 unique SKUs (a.k.a variants), some of the products are at a 16-28 SKU range, some are at a 40-75 SKU range, handful well over 75 SKUs (think exhaust systems as a real product example).

I up the app settings to 6000.

What's that going to do to the:

1. Server
2. Website
3. Other websites that may be on the server assuming it's a dedicated
4. Other websites that are on the server because it's a shared enviroment

I keep hearing this "performance hit" statement and that's what is getting me in a tizzy right now...LOL...because I'm not seeing cold hard facts.



what's it going to do? Has this been tested in-house at BV?



If this "performance hit" isn't much, than say the word!! I'm waiting for guidance from BV Software on this as I can't afford to sacrifice performance just so I can get unique SKUs. We're already getting them in BV2004.

LOL...You can lead me to the water and I will most certainly drink it!

Attached is a visual.



Top Graphic - This product has 3 Product Choices (two options for each choice)



Middle Graphic - This is how we setup the choices. Red font explains the W's of each choice.



Bottom Graphic - I add a 4th choice and two options. I get that error that is underlined.



Currently the MaxVariantCombinations is set to the default 100.

---

Does the fact that I'm adding so many null items affect the variant limit? From a top level observation, I click "Edit Product Variations" and I don't see the null items, so I assume that this doesn't affect the limit.



I will modify the choices to not have the null items to test this, but by changing the current display (i.e 1: [Table Top Color]), I'm making a sacrifice in regards to usability and Jakob Nielsen would have a field day with me and I then have to further modify the product templates to allocate the necessary space required to display the Choices (which completely ruins aesthetics and usability) as not matter what, we need to have a null item in each choice to eliminate possible errors of selecting the wrong combination of choices.



By having a null item (i.e Table Top Color), the customer has to choose an option. By not having a null item, a customer may leave the first option at the wrong color thus creating a wrong order!



Make sense?

For this product, we're looking at 4 Choices with 2 selections per choice.

A: 1,2
B: 1,2
C: 1,2
D: 1,2

I never did well in math class (you know us creative types...always thinking about landscapes and pretty colors...LOL) so I'm thinking that's 128 possible combinations? I'm probably wrong but it's gotta be over 100...Which is why we're getting the Max out error. So the maxvariant level is tied to an individual product or the amount of variants allowed on the entire store?

So like I said, you're leading me to the water....

As long as you guys (BV) feel that raising the MaxVariantCombinations to maybe 200 or 300 isn't going to affect the overall site performance and other sites on the box, I'll tap Resposio and I'm off to the races!

Thanks for walking through this with me, sometimes us designers need it crystal clear...LOL

Sounds good on the variant limit change. Resposio has some mean machines!


If it's 16 (which I just confirmed by looking at it...who would've thought it was that easy...LOL) that's why I'm wondering why it's capping out?