Support » Plugin: Markup by Attribute for WooCommerce » Ideas For Version 2.0?

  • ResolvedPlugin Author Mark Tomlinson

    (@marktomlinson)


    I am currently working on version 2.0 of Markup-by-Attribute. My goal is to remove quirks and improve usability and supportability while remaining true to the vision of a straightforward single focus plug-in.

    What features would you like to see? Is there a quirk or bug that you know of that you’d like addressed?

Viewing 12 replies - 1 through 12 (of 12 total)
  • Increasing the number of variations that can be created at once from 50 to 250 did not work for us. It seems like 250 was too much. We had to manually set it back to 50. Probably our server/settings did not meet the requirements for this.

    Maybe you can make this a setting in the plugin so other users can change the number back to 50 if 250 is too much.

    We did not have any other issues. The plugin really works great!

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Done.

    There will be a settings page that allows you to change the number. The default will be set at the WooCommerce default of 50.

    I think auto change the price will be awesome.
    What i mean.
    In variable products when we have many varitions it is difficult to calculte the right price.
    I think that the perfect is to auto adjust te price by the markup according to the attributes without changing the basic price

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    If I understand your description correctly, that is exactly what Markup by Attribute does.

    If you create an attribute called ‘color’ and indicate that ‘green’ is $2 more, then a $15 tee shirt in red or blue will cost $15 — but the green variation will automatically be priced at $17.

    Am I misunderstanding your request?

    Mark,

    First of all, thanks for this awesome plugin! I just downloaded and activated it today for a new site I am building for my brother. Being that he is the most frugal person you’d ever meet and won’t be paying me a dime for my efforts, I am absolutely thrilled that this plugin will be saving me countless hours once I get it working properly!

    With that said, I am running into a couple minor issues that are caused by either 1. trying to use it in a way that is not yet supported or 2. there is a trick that I haven’t learned yet in my short time with the plugin. I’m hoping that whatever the cause, this is something that you may be able to correct in a future build or knock some sense into me, respectively 🙂

    The first issues is this: His store will feature A LOT of products that have variations based on multiple attributes. For the purpose of this example, let’s use color and size as I’m sure they are rather common. Naturally, size will have an impact on the cost as he will be using varying amounts of material. He also offers his products in a number of standard colors (all the same cost) but also in premium colors which should have a markup. I have both of these (color and size) set up to use a percentage to handle the markup, but I can’t figure out how to make the markup for the color dependent on the size. Both markup percentages are based on the regular price (before any other markup), so while the markup for size is calculated properly, the added cost for a special color is the same regardless of whether I select small, medium, or large, etc. Is there something I am missing, or is this plugin not really set up for stacking multiple attributes yet?

    Second issue, expanding on the above example: I have a product with the following attributes and markups… Size(Large = no markup; Medium = -15%; Small = -35%), and Color(All standard colors = no markup; All premium colors = +40%). Even though I still have the issue above where the markup for premium colors is always the same regardless of size, with that aside – the calculated price for all the variations works flawlessly! However, I notice on the product page (for the same product using the variations provided above) there is a discrepancy between what is listed in the variation drop down menus and what is placed into the variation description. To be more precise, this product has a regular price of $7.99. If I select large and special color, the values listed in the variation selection menus are Large (+$3.99) and Special Color (+$1.60) while the variation description correctly lists Product price $7.99, Add $3.20 for Special Color.

    Would very much appreciate hearing your thoughts and recommendations on this! Thank you!

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Okay, the first issue, making markups dependant on each other — No, I’m afraid Markup by Attribute doesn’t do that. And, unfortunately, I think it’s a little too involved for version 2.0.

    Conceptually, I could add an ‘order’ field to the attributes and then calculate the new product price by each attribute based on the outcome of the calculations before it. Any attributes with the same ‘order’ number would be calculated together. For instance, ‘size’ has an order number of 0 so its markup is applied first. Color and collar type both have an order number of 1, so they get calculated after the size markup is applied.

    However, that would require almost a complete rewrite of a couple of the modules. It’s a great idea and I’ll put it on the future feature list. But I’m afraid I can’t get it into version 2.0. Meanwhile, may I suggest “padding’ the secondary markups a bit?

    The second issue – yes, that sounds like a bug. I’m not able to recreate it myself but will continue to try. Did you, perhaps, start with a 20% markup for special color and then change it to a 40% markup later? It may be that the metadata wasn’t updated properly in the database.

    I assure you this second issue will not exist with version 2.0. But if I can recreate the error in the next day or two, I’ll push out a patch. Meanwhile, if you have access to the WordPress database, a horribly awkward fix would be to search the wp_postmeta table for meta_key LIKE %markup%. Browse through the results until you find the offending record(s) and delete it (them). You might have to ‘Set regular prices’ again to get everything looking correct.

    Or, if you can wait, I’m looking at rolling out version 2.0 by mid next week.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    While I’m on here typing anyway, I’m going to take this opportunity to point out a bug in version 1 that is being repaired in version 2.0.

    The variation bulk edit menu has four options to increase or decrease either the regular or sale prices by a fixed amount or a percentage. If you use any of these functions the final prices will NOT match the description. Furthermore, if you do a percentage markup the options drop-down box will NOT be correct either.

    Version 2.0 fixes this by adjusting the base price first and then recalculating the markup. It rewrites the drop-down options and the variation description while recalculating the markups.

    Please do not use the Increase/Decrease regular/sale price bulk edit functions until version 2.0 is released.

    Mark,

    Many thanks for the quick reply! Yes I agree, and I understand the complications surrounding issue #1. I definitely didn’t expect it to be implemented for 2.0, but if you do find you can dedicate the time to it in the future, I know it would be extremely useful to many. In the meantime, we did pad the secondary markups to make sure he doesn’t get shortchanged on the larger items, but naturally it seems a bit greedy to be charging the same amount for the markup on a product half the size. We will come up with some kind of happy medium I am sure, meanwhile keeping our fingers crossed for a fix in the future.

    I do believe you may be correct on the second issue, and it is very likely we had it set to a different markup previously. However, I was doing some additional testing on this and interestingly enough, when I added a new product that had never existed before, the same problem appeared only with a value that didn’t match the same percentage on the example I provided. That one really had me scratching my head a bit. Anyhow, I will dig around in the database when I have a few minutes and see what I can find there. He is anxious but I think I may try to hold off until 2.0 is released before we continue importing his entire stock.

    Looking forward to taking that for a spin and benefiting from the enhancements you have made. Thanks again for the follow up and your continued work on this plugin!

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    @nextech84 and anyone else experiencing the version 1.x bug where the markup in the options drop-down does not match the markup in the description.

    Did you set a Sale Price?

    Version 1.x calculates the percentage markup in the options box based on the last price set. If you are using a fixed amount markup, this is not a problem. But for a percentage markup, it means that the markup in the options box could be based on the sale price rather than the regular price.

    To work around this issue, try resetting the regular price. Let me know if this helps.

    Since I’ve identified the issue, it will not be a problem in version 2.0.

    @marktomlinson thanks for staying on top of this! For the products I was experiencing this issue with, I did not set a sale price. Only the regular price was set on these products. I also confirmed this by creating a new product, never having prices set before, and set only the regular price. After doing this, I still saw the discrepancies between the markup in the drop-down menu and what was listed in the description.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Version 2.2 is now out.

    Let me know if it satisfies your requests.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    We are at version 2.4 now, so I am closing this.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Ideas For Version 2.0?’ is closed to new replies.