Support » Plugin: Markup by Attribute for WooCommerce » Still Charging Base Price

  • Resolved speedofpain

    (@speedofpain)


    On the product page the items change fine. However during checkout noting has changed with the price. I looked through support and saw this statement….

    What Markup-by-Attribute does is actually change the product variation price on the database, not at the checkout

    Im not sure what the point is of the plugin if it doesn’t seem to work on the front end at all. How do i charge the customers what im showing them they should be getting charged?

    Amazing idea for a plugin, my product has over 500 variations. If i can just charge for those now haha.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Mark Tomlinson

    (@marktomlinson)

    Wow, more than 500 variations is a lot! It’s entirely possible that the server is timing out during the “Set regular price” bulk edit function. If so, that would be entirely out of the plugin’s control.

    Im not sure what the point is of the plugin if it doesn’t seem to work on the front end at all.

    Markup-by-Attribute changes the regular and sale prices of each variation of a variable product. It does this during the Set regular price and Set sale price bulk edit functions while you are creating the products, rather than modifying the prices while the customer is purchasing them. This approach does not work for everyone.

    The most common resolution I’ve found is to ensure the variations were created and priced in the right order.

    1. Create global attributes and set the markups.
    2. Create a variable product and add the attributes.
    3. You could create all variations by hand, but the bulk function Create variations from all attributes is way easier.
    4. You must use the Set regular price bulk edit function for Markup-by-Attribute to work.
    5. If you are going to set a sale price, you have to use the Set sale price function after the regular price is set.

    I hope this clarified things and helped. Regardless of whether you choose to use the plugin or not, I appreciate your feedback and would like to know what I can do to make it more useful.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Not hearing anything else, I’m closing the issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.