Markups not applying

Issue was using BULK > Set Regular Prices (I added manually to each one before)

(Please check my combo question!)

Glad you got this worked out.

I hit same problem and can’t figure it out:

https://test.rumatech.com/belts/product/genuine-leather-buckless-belt/

I did not use bulk edit to set prices.

I am importing product from CSV file.
Here is a link to the CSV file: https://test.rumatech.com/belts/testdata.csv
Perhaps it is something in the data I am loading?

Thanks,
Rudolf

Markup by Attribute relies on the Set regular prices and Set sales prices functions. It may seem unnecessary to use the Set regular prices function when you’ve already imported the base price on the CSV, but that is where Markup by Attribute hooks into WooCommerce.

I’m working on improving the description and directions because this is easily my most asked question.

Hi Mark,

I just tried to set regular prices and effect is same — price is not updating.
I did it by selecting “Set Regular Price” option in product editing. I saw another post talking about same problem and using bulk editing.

Do I have to do it manually for each combination instead?

Rudolf

Okay, I think I see what the problem is.

I imported the belt from the CSV file you linked to, and it created 19 variations (one for each variation row in the CSV file), when you actually have 132 (6 colours, 11 sizes, and 2 gift pouch options). All variations had “Any gift pouch” set, instead of alternating between “No gift pouch” and “Add gift pouch”.

Since Markup by Attribute reprices the variations based on their attributes, there must be variations in the database that include those attributes. This is why I recommend using the Create variations from all attributes function. But, restructuring your CSV file to use the “Attribute 1″, “Attribute 2″, and “Attribute 3″ columns would also work. The important thing is that there are no “Any gift pouch” variations in the database.

But, before you try that, I have a tip. If the gift pouch is the only attribute with a markup, then you may only need two variations. Set the colour to “Any colour” and the size to “Any size”. (With only two variations, this plugin is probably unnecessary). If you intend, perhaps, to add a markup for larger sizes, then you’ll need 22 variations (11 sizes and two gift pouch options). The only reasons you’d need all 132 are, 1) all attributes have an option with a markup, or, 2) you use the inventory management features of WooCommerce and want to know when you’re out of a size and colour, or 3) you really don’t feel like trying to figure out what you need or don’t need. ??

(Tip: If you use the Create variations from all attributes function, you may want to set the Variation Max on the Markup by Attribute settings page to something like 250, since WooCommerce defaults to 50.)

Hope this solves it.

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

Thanks,

I am actually converting a web store from old osCommerce engine.
I am working on a script that transfers existing products across. Or rather, script exports them into a CSV file, then I use WooCommerce import function.

There are quite a few products, so I do not really want to go and modify each product manually.
There are two attribues that affect size — “gift pouch” and “waist size”.

Let me try your suggestions on CSV file and I will let you know.

Rudolf

OK,

Thinking about what you said and trying to create products manually, I think I understand what you mean. Each possible permutation of attributes must be explicitly defined.

I created new CSV file (https://test.rumatech.com/belts/testdata_new.csv) and imported it (I cut down on attribute values to test).
This set up all possible combinations, but plugin did not work at all — price would not be re-calculated.
I then went into product and did “Set Regular Price”. This fixed the problem. So, looks like one can not just import products and expect it to work.
I do have a plugin that allows bulk editing of products,tried to change price with it and it did not work. I guess, they are modifying database values directly. So, the only option is to visit individual products.

I wonder how plugin works if it is installed on a site with existing products. You would have same problem, right? I mean, if there is no call to “Set Regular Price” on existing product.

As a suggestion, I think it is worth adding an option to “re-scan” the site and apply the markup as necessary. Should not be too difficult — just go through each product and check its attributes/prices, right?

Otherwise, plugin is great and does exactly what I need. Some manual work will be involved in my case, but I can live with that.

Rudolf

Thanks.

I thought about a re-scan type of feature, but was dissuaded because it will have to run in background and would have to spawn subtasks to keep it from timing out. All doable, of course. But I’m a retired guy who wrote this plugin for a friend’s website, I’m not sure I want to improve it beyond what I can reasonably support. It’s already moved from being a hobby to being my ‘unpaid profession’.

If another developer wants to fork the code and add features like that, I’d be more than willing to help them with it.