SomewhereWarm

My feedback

  1. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SomewhereWarm commented  · 

    Done!

  2. 170 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    43 comments  ·  WooCommerce » Category - Extension Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm commented  · 

    Hey all,

    If you are looking into different options for offering personalized product recommendations on the order-received page, check out the official WooCommerce Product Recommendations extension: https://woocommerce.com/products/product-recommendations/

    The extension does not provide any sort of "one-click" functionality that bypasses checkout for product recommendations selected on the order-received page, but this is an excellent idea that could be rolled into the extension in the future.

    Cheers,
    Manos
    SomewhereWarm

  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SomewhereWarm commented  · 

    Hey all,

    Have you checked out WooCommerce Product Recommendations?

    The extension allows you to create rule-based engines that make taxonomy-based recommendations like this a breeze to create, deploy and manage. Here's an example: https://docs.woocommerce.com/document/product-recommendations/recommendation-strategies/offer-complete-the-look-recommendations/

    On top of that, it brings in-depth recommendation analytics right into your dashboard.

    You can read more about it at https://woocommerce.com/products/product-recommendations/

    Cheers,
    Manos
    SomewhereWarm

  4. 84 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  WooCommerce » Category - Extension Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm commented  · 

    Hey all,

    Have you checked out WooCommerce Product Recommendations?

    The extension allows you to create rule-based engines that make such category-based recommendations a breeze to create, deploy and manage.

    On top of that, it brings in-depth recommendation analytics right into your dashboard.

    You can read more about the extension at https://woocommerce.com/products/product-recommendations/

    Cheers,
    Manos
    SomewhereWarm

  5. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  WooCommerce » Category - Extension Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm commented  · 

    Hey Kevin,

    Have you checked out WooCommerce Product Recommendations?

    The extension allows you to create recommendation engines to accomplish what you describe, for example have a look at this "Complete the Look" example: https://docs.woocommerce.com/document/product-recommendations/recommendation-strategies/offer-complete-the-look-recommendations/

    You can read more about it at https://woocommerce.com/products/product-recommendations/

    Cheers,
    Manos
    SomewhereWarm

  6. 98 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SomewhereWarm commented  · 

    Hey all,

    this feature is now available with the free Composite Products: Conditional Images mini-extension. Read more at https://somewherewarm.gr/composite-products-conditional-images-mini-extension/

    Important:

    1. Composite Products 4.1+ is required.
    2. The mini-extension only works with themes that declare support for the 'wc-product-gallery-slider' feature.

    Cheers,
    Manos

  7. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  WooCommerce.com Ideas » Vendor Dashboard  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm supported this idea  · 
  8. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  WooCommerce.com Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm shared this idea  · 
  9. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  WooCommerce.com Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm supported this idea  · 
  10. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SomewhereWarm commented  · 

    Hey Guillaume,

    Thanks for chiming in here! As mentioned in the extension docs, when you enter a base/static price the container/parent line item gets its own totals + taxes, which are calculated from the entered static/base price.

    There are many uses cases of bundling based on the need to sell a "base item" along with a set of required items or add-ons, which may need to be priced individually. In these cases, the static/base price component cannot be (and should not be) transferred from the parent to the children. Furthermore, even if this was possible, your assumption that the "static" cost should be shared among all items according to the ratio of their standalone prices is very limiting and limited in scope, even if this functionality was implemented as a "feature plugin".

    If you need to maintain the tax rates of the individual items contained in a bundle, you should use the "Priced Individually" option and define a Discount for each item to bring down the total price -- instead of defining a "base" bundle price. If you don't want to display the individual (line) item prices/totals, you can even use the provided Price Visibility options to hide them in all templates.

    I understand that this has an overhead for the store owner, in the sense that you need to calculate the individual Discount amounts in a way that brings the total bundle price where you want it to be, but doing these sort of calculations is a routine operation for all businesses selling taxed goods.

    In short -- if you want to calculate tax rates / totals at bundled item level, you'll need to check the Priced Individually option and work from there.

    Cheers,
    Manos

  11. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    SomewhereWarm commented  · 

    This is already built into Bundles and will work correctly as soon as Subs 2.0 is out. In addition to this, we are working together with Prospress to develop a plugin that will make it possible to "subscribe" to a configured Bundle/Composite. With this, you'll be able to configure a Bundle / Composite / Mix and Match Product and then subscribe to its contents.

  12. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  WooCommerce » Category - Extension Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm commented  · 

    v3.0 is now live and includes this feature.

    Component options are now pulled using a WP_Query wrapper, so developers can build custom queries to fetch component options.

    SomewhereWarm commented  · 

    Thanks for the feedback, guys. This has already been logged, but it will require some more improvements, such as the ability to load / filter component options dynamically by sending queries via ajax.

    If a component includes 100s of products from a category, the extension should be able to scale in order to handle that and display / load all options in pages.

    Noted.

  13. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  WooCommerce » Category - Extension Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm commented  · 

    Hey Andy,

    Are the properties "Size" and "Wood Type" attributes used in Bed, Mattress and Companion Furniture variations?

    Component dependencies (Scenarios) cannot be based on Attributes, but perhaps I have misunderstood what you mean by "Scenario Masking"?

    Scenarios are the most general (and most powerful and complex) solution in order to:

    1. Allow multi-component dependencies (ie selecting Option A from Component 1 and Option B from Component 2 allows you to purchase Option X from Component 3), and
    2. Allow starting from any Component, without necessarily forcing a progressive selection process.

    The downside is that it can be quite time-consuming to create complex dependencies, but the feature covers a massive set of possible applications and use cases.

  14. 12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  WooCommerce » Category - Extension Ideas  ·  Flag idea as inappropriate…  ·  Admin →
    SomewhereWarm commented  · 

    Regarding Component-specific scenarios:

    Dependencies could be implemented simply using a sequential logic describing the allowed alternatives when following a progressive selection path, or by using a combinational logic to describe the allowed solutions without caring about the progression.

    The first could be implemented using simple sets of rules that relate the allowed options of a Component to the options made in the previous Components. *However*, to be practical this approach would only allow selecting options progressively, ie starting with the 1st Component, then moving to the 2nd, and so on.

    Scenarios follows the second approach which doesn't have any "memory" - this means that you can create any sort of dependency you like, including multi-component dependencies, without having to force a progressive selection route. In the docs example, you can start by selecting a Lens that you like without knowing or caring which Cameras it is compatible with.

    Some applications assume dependencies which have an inherent progression (ie *this* Camera is not compatible with *that* Lens), but there are cases where this is not desirable or possible, because all components are of equal importance to the whole.

    The downside is that Scenarios are more complex. If the configuration of your Composite needs to have a simple progression and your restrictions are based on this progression, you will need a slightly analytical approach to break down the problem into Scenarios.

    In short, Scenarios forces you to think about which items can co-exist in a possible configuration - put simply, you need to define all possible outcomes.

    Reagrding Conditional components:

    This can be done using Scenarios. If you just define a Component as optional, you can make the None option available in certain Scenarios. In those Scenarios, it won't be possible to select anything for the specific Component, which is the same as saying that the Component itself is conditional.

    Conditional default options is really overkill - such a niche feature would never justify its development and maintenance cost.

Feedback and Knowledge Base