Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Actually I’ve answered my own question. This looks like the default behavior for case 1 and case 2 assuming variations are defined as you’ve indicated.

    I’m also guessing the variations are handled in typical RDBMS fashion in the actual tables.

    Now my question is how to create variations programmatically from some preexisting databases I have… 🙂

    @pablostevens71, it looks like you’ve got this sorted out already on your page, good job.

    @bigmoxy, I’m interested in a similar problem, but would like all options available for selection in any order.

    Example
    case 1

    1. user chooses color A
    2. cherry wood is available for selection or selected automatically

    case 2 – in your description above

    1. user chooses cherry wood
    2. color A, B , C are available for selection

    I’m also curious if there is a better way to define variations. I’m totally new to WooCommerce but the variation definition seems like it should be completed with a one to many relationship in the product database instead. Is this an option in WooCommerce?

    Currently I’m evaluating if Woocommerce is a good tool for me. I’d like to have a store for electronics. Products may have 10s – 100s of attribute which are searchable by a user (think data sheet specifications) but I’m not sure how to handle this with WooCommerce. I see an advantage with the payments, cart and seo benefits of an established tool but the product database is confusing to me at this point.

Viewing 2 replies - 1 through 2 (of 2 total)