Understanding Dependent Bundle Option Product Selections

Having a firm grasp of understanding how the Bundled Mojo dependent bundle option product selections work and knowing the overall concept behind the functionality is pivotal. We will outline the functionality and key constructs in a list below.

Before we get started we would like you to take a look at the following screenshot of the bundle option product selections “Depends On” multi-select field, which you will use to add, edit, and remove bundle option product selection dependencies. The outline below is directly related to the field(s) pictured in the screenshot.

Mojo Creative & Technical Solutions

 

 

 

 

 

 

 

 

 

 

Outline of functionality and key constructs:

  • Although default out-of-the-box Magento functionality does not allow you to have different bundle option product selections on a per store view basis, Bundled Mojo will allow you to have different dependent bundle option product selections per store view. So even though your bundle option product selections will not change from store to store, Bundled Mojo will allow you to be able to have bundle option product selections that depend upon the same or different bundle option product selections per store view.
  • The dependent bundle option product selections functionality works for the most part dependently of the dependent bundle product options.
  • You can have a bundle option product selection that has dependencies upon other bundle option product selection that do not belong to the same bundle option type (checkbox, radio, select).
  • You cannot have bundle option product selections with dependencies without first assigning and saving a dependent bundle option as a dependency for that particular bundle option that the bundle option product selection belongs to.
  • Once a bundle option is associated as having a dependency upon one or more different bundle options, and the product has been saved with this associated data, only then will bundle option product selections show up in the list of selections available as a dependency within Magento admin. In short, you must save your bundle option dependencies first, before you will see any options show up within the bundle option product selection “Depends On” multi-select form field.
  • Each bundle option product selection can have multiple dependencies, and each bundle option product selection that it depends on can also have multiple dependencies; this chain can potentially be limitless.
  • When initially viewing a bundled product that contains dependent bundle options on the Magento frontend, all bundle option product selections are visible to the customer; all of its bundle option product selections will be disabled regardless of whether or not those bundle option product selections have dependencies themselves and is irrelevant because the bundle option has dependencies so it must be rendered disabled from being selectable by the customer.
  • A bundle product option selection that has dependencies will remain disabled from customer selection on the Magento frontend until its parent bundle option passes all of its criteria for dependencies and the dependent bundle option product selection passes its own set of criteria for dependencies.
  • Bundle option product selections are filtered from customer selection on the Magento frontend if they fail the criteria for its dependencies.
  • If a bundle option product selection fails its dependency criteria, it will be removed from the visible content on the Magento frontend and it will not be available for customer selection. If a customer makes a different selection and the bundle option product selection passes the dependency criteria, it will be restored and rendered visible for customer selection.
  • You can have bundle option product selections that do not depend upon another bundle option product selection alongside bundle option product selection that dependencies.
  • If a bundle option product selection does not have any dependencies but its parent bundle option has bundle option dependencies, the bundle option product selection will always be visible for customer selection on the Magento frontend, if and when its parent bundle option passes all of its dependency criteria.
  • If a dependent bundle option passes its dependency criteria and is made available to the customer for selection, and it does not have any product selections that pass their dependency criteria, there will be a notice displayed to the customer that states there are no products matching their current selections.
  • If a previously enabled bundle product option has been rendered disabled for customer selection for failing to match its dependency criteria, then all of the customer’s current selected bundle option product selections will be deselected, its relevant content will be hidden if visible, and it will be rendered disabled for customer selection. All bundle option product selections that were previously hidden/disabled from customer selection will be rendered visible and will come back into the content view, but they will be disabled for customer selection until further dependency processing renders it otherwise.