Mark Tomlinson

Glad you got this worked out.

Have not received a response in two weeks, and so assuming the issue is resolved.

Let me explain how I would do it, and we can see if you are doing it the same.

• Let’s say bed size 140 cm costs $200, 160 cm cost $250, and 180 cm costs $300.
• I would create the global attribute of Size. 140 cm would have no markup, 160 cm would have a $50 markup, and 180 cm would have a $100 markup.
• Let’s also say modification A is standard, but B is $10 more, C is $20 more, and so on.
• Create another global attribute for A, B, C, D, and E. Since A is standard, there is no markup. B has a $10 markup, C has a $20 markup, and so on.

Then I would create the product and use the Create variations from all attributes function to make all 15 variations.

Now, since there is no markup for 140 cm, and no markup for A, 140-A is the lowest priced bed at $200. This is the base price. When I use the Set regular price function, $200 is the price I would use.

Is that how you did it?

• This reply was modified 4 years ago by Mark Tomlinson.

I think I might know what the problem is, but I’m not sure how to get around it.

I counted 21 different sizes, 47 different font colors, and 5 additional customizations. This would create 4,830 different variations, which could cause multiple timeouts while creating the variations and pricing them. You might not even know it’s timing out unless you have access to your system debug.log. (I’m still testing this, but wanted to get back to you since the testing is taking so long.)

Unfortunately, Markup by Attribute requires all variations to exist in the database. This is how it was designed and works well for people with up to a few hundred variations. There are pros and cons of this approach, and, obviously, the fact that it won’t work on a few thousand variations is a ‘con’. 🙁

I can only think of two approaches to correct this problem. The first is to use a different plugin; one that updates the price at checkout and doesn’t require you to create every possible variation. I can’t recommend any because I’ve never used any others. I’m sure WooCommerce has one (for a price, of course).

The other approach, if you want to continue using Markup by Attribute, would be to break the product into multiple products. For instance, regular, glitter, and metallic fonts could be separate products. Then you would just set the base price for the metallic and glitter $1 and $2 higher, respectively, and would not include a markup on the attribute. In fact, I’d recommend making regular, metallic, and glitter fonts different global attributes if you were going to go this route. Of course, then you’d have to change every product that uses these fonts, which may also be an issue.

Sorry I couldn’t give you a simple answer.

You’re welcome.

🙂

You should be able to update directly from the Plugins page on your WordPress dashboard. If not, you can try the [Download] button on it’s WordPress Plugin page.

https://wordpress.org/plugins/markup-by-attribute-for-woocommerce/

Sorry, Markup by Attribute is made specifically for products with multiple variations.

Well, thank you.

Changing the plugin to calculate the markup in the cart would require a rewrite. The plugin was designed around the concept of changing the price of the product variations instead of doing it in the cart.

There are pros and cons of each approach. If we change the pricing in the cart, we can do what you are asking, plus we can change the markup without having to recalculate the price of the variations. But, when I wrote it, the owner of the website I wrote it for needed to (1) manage inventory by variation, and (2) retain older markups on some products, while using new markups on newer products. The approach I took lent itself well to his requirements.

Thanks again for your interest. I hope you can work something out that isn’t too difficult to manage.