• Resolved SundayDriverxXx

    (@sundaydriverxxx)


    Hi Mark,

    Great idea for a plugin! I hope we can get it working for us!

    I want to make a variable subscription product.

    Pick 2 flavors: Mint, Berry(+1), Vanilla(+2), etc…

    I have a single variation made for Mint flavor at $5. But if I choose Berry it is not $6, it stays $5 per month.

    I am not sure if I am supposed to make a variation for each possible combination? For 3 flavors that would be 9 variations? for my 33 flavors… impossible?

    Is it the fact that I am trying to do this with subscriptions or did I set it up wrong?

    Any help would be greatly appreciated!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter SundayDriverxXx

    (@sundaydriverxxx)

    Ok I see in the instructions that I need to make a variation for every possible combination. What is the point of the plugin if I have to do that? Wouldn’t I just adjust the price for each variation anyways?

    What am I missing?

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Thanks for your interest. The point of the plugin is that if you have many products and many variations, calculating and updating the prices is tedious and error-prone.

    It was originally written for a client who has 42 products of different prices and over 50 variations with markups for each product. It gets more complicated for stores that have multiple attributes with markups; imagine trying to figure a 10% off sale price on all product variations that might add $5 for one attribute and subtract 2% for another.

    Markup by Attribute also puts the markup in the options drop-down for you and adds the detail of the pricing to the variation description. You can see examples of that in the screenshots on the main plugin page.

    So if you’ve only got nine variations, you probably are not interested in the plugin. It was really intended for people with many variations or multiple attributes.

    Thread Starter SundayDriverxXx

    (@sundaydriverxxx)

    Thanks for your reply Mark. I am still confused, can you help?

    I want to make a pick 5 flavors combo pack, scenario is below.

    Step 1 – Customer picks their nicotine level for the combo box. (0mg, 1.5mg, 3mg, 6mg, 12mg, 18mg)

    Step 2- They pick their 5 flavors using drop downdowns like so: https://www.kindjuice.com/vape-juice/nectar-5-pack-combo-15ml/

    But in the example above, all the flavors are the same price. so in the backend, there is only 1 variation of Any nicotine level and Any Flavor Name for 1 price.

    I want to charge +$1 or +$2 if they pick different flavors. Example:

    Attribute – Flavor 1 Options: 5 O’Clock Somewhere | Alpine Frost (+$1) | Custard’s Last stand | Dawn of the Living Grapefruit (+$2)| Geisha Moon Song | Granny “Tart” Smith.

    Attribute – Flavor 2 Options: 5 O’Clock Somewhere | Alpine Frost (+$1) | Custard’s Last stand | Dawn of the Living Grapefruit (+$2)| Geisha Moon Song | Granny “Tart” Smith.

    Attribute – Flavor 3 Options: 5 O’Clock Somewhere | Alpine Frost (+$1) | Custard’s Last stand | Dawn of the Living Grapefruit (+$2)| Geisha Moon Song | Granny “Tart” Smith.

    Attribute – Flavor 4 Options: 5 O’Clock Somewhere | Alpine Frost (+$1) | Custard’s Last stand | Dawn of the Living Grapefruit (+$2)| Geisha Moon Song | Granny “Tart” Smith.

    Attribute – Flavor 5 Options: 5 O’Clock Somewhere | Alpine Frost (+$1) | Custard’s Last stand | Dawn of the Living Grapefruit (+$2)| Geisha Moon Song (+1)| Granny “Tart” Smith.

    Can I do this with the current setup of this extension? Are you available for hire to make it work if not?

    Thank you very much!

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Yours is an interesting situation because you use the same attribute several times. I see up to six when I looked around the site.

    So the first question is how would you do that in WooCommerce? The answer, I supposed, is that you create 6 flavor attributes; Flavor 1, Flavor 2, Flavor 3, Flavor 4, Flavor 5, and Flavor 6. All would have the same terms and markups. (A three-pack would use the first three attributes only.) Your list would look like this;

    • Nicotine Level
    • 0 mg
    • 1.5 mg
    • 6 mg
    • 6 mg
    • 12 mg
    • 18 mg
    • Flavor 1
    • 5 O’Clock Somewhere
    • Alpine Frost (+$1)
    • Custard’s Last stand
    • Dawn of the Living Grapefruit (+$2)
    • Geisha Moon Song
    • Granny “Tart” Smith
    • Flavor 2
    • 5 O’Clock Somewhere
    • Alpine Frost (+$1)
    • Custard’s Last stand
    • Dawn of the Living Grapefruit (+$2)
    • Geisha Moon Song
    • Granny “Tart” Smith
    • etc…

    Big, big, big problem with that! The Tobacco Ridge combo pack will have 60,466,176 variations. 120,932,352 if your subscription offering is yet another attribute. There’s no way WooCommerce can handle that many variations and Markup by Attribute requires variations to price them.

    So, yeah, you need to find a different approach. I’m sorry to say Markup by Attribute won’t work. I believe WooCommerce’s Product Bundles might work.

    Sorry I couldn’t be more help.

    Thread Starter SundayDriverxXx

    (@sundaydriverxxx)

    Hi Mark,

    Your assumption is correct. It is quite a dilemma.

    Are you available for custom development? We are a business and have a budget for this project.

    I think what we would need is some custom code that checks the flavors that are picked before adding to cart. Using IF/THEN statements, we could check for the flavors that need to be markedup and add a custom price to the cart. In theory, this could be done via JavaScript or PHP. Maybe both are needed.

    I think I could write the JS to change the price on the front-end, but I am not familiar enough with the woocommerce database to actually make it work in the backend.

    Is this something you would be interested in doing?

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    I see I never got back to this thread.

    Sorry, but I am a retired guy who does this for fun. I think I’d enjoy the custom development work. But I’ve gotten to a point in my life where my goal is to be as irresponsible as I can get away with. Supporting this plugin is about the limit for me. I don’t think that’s an attribute that people look for in their developers.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Not working for subscriptions’ is closed to new replies.