Table of Contents
Magento 2 Product Builder User Guide
Related overview
For a shopper-friendly overview of features and setup, see the Magento 2 Product Builder User Guide - Complete Builder Stack on the storefront. This wiki page remains the full technical documentation.
Extension context
This is a Toweringmedia Magento 2 extension guide for the current admin extension catalog.
Product page
- Magento 2 Product Builder (SKU
Magento 2 Product Builder)
Overview
Product Builder provides a guided configuration framework for complex Magento 2 products that need more than standard option dropdowns. It supports both a grid-style ordering flow for fast quantity-based selection and a multi-step wizard flow where a customer picks a base item and then works through dependent options. Backend contracts, validation, summaries, and add-to-cart planning are shared across Luma/default and Hyvä storefronts.
What this extension does
- Guided multi-step wizard flows for products with dependent options.
- Grid-style bulk ordering flow for quantity-based selection.
- Works with configurable and bundle parent products.
- Shared backend validation, pricing summary, and add-to-cart planning across Luma/default and Hyvä.
Requirements
- Magento 2.4.x (Open Source or Adobe Commerce).
- A current Toweringmedia license and Composer credentials for
https://composer.toweringmedia.com/. toweringmedia/module-product-builderis a metapackage. It installs no code of its own — it pulls in Product Builder Core plus both flow packs (Shirt Builder and Bundle Builder).- Composer resolves
toweringmedia/module-product-builder-core,toweringmedia/module-shirt-builder,toweringmedia/module-bundle-builder,toweringmedia/module-ai-core, andtoweringmedia/module-baseautomatically.
Installation
Install and validate in a staging environment before production rollout.
cd /path/to/magento composer require toweringmedia/module-product-builder bin/magento module:enable Toweringmedia_ProductBuilderCore Toweringmedia_ShirtBuilder Toweringmedia_BundleBuilder bin/magento setup:upgrade bin/magento setup:di:compile bin/magento setup:static-content:deploy -f bin/magento cache:flush
Currently published versions at the time of writing:
toweringmedia/module-product-builder— 0.2.1 (metapackage — installs the flow packs listed above)
Toweringmedia packages are served from the licensed Composer repository https://composer.toweringmedia.com/. If Composer reports that the package could not be found, your credentials are missing or the license does not cover this package yet. Retrieve your keys from My Account on toweringmedia.com, or contact support@toweringmedia.com.
General installation notes that apply to every Toweringmedia extension are in the installation guide.
Configuration
- Stores > Configuration > Towering Media > Product Builder (config section
product_builder, provided by Product Builder Core). - Available groups:
general(enable/disable) anddisplay(layout position).
Basic usage and what to expect
- Enable the builder in Stores > Configuration > Towering Media > Product Builder, then assign a builder flow to the relevant configurable or bundle parent products.
- Shirt Builder and Bundle Builder each add their own storefront wizard flow — see the individual wiki pages for those flow packs.
Notes and limitations
- This SKU is the complete stack entitlement. If you only need one flow, the Shirt Builder and Bundle Builder SKUs are licensed separately.
- Because the metapackage installs three Magento modules, the
module:enablecommand above lists all three.
Validation checklist
bin/magento module:statusshows the module(s) as enabled.- Extension configuration saves without errors in Admin.
- The admin screens listed above are reachable and load without error.
- Expected storefront/admin behavior is present after a cache flush.
- No critical PHP/JS errors appear in
var/log/during the primary test flow.
Troubleshooting
- Composer cannot find the package: confirm the
https://composer.toweringmedia.com/repository and your credentials are present inauth.json, and that your license covers this package. - Feature not visible: verify module status, flush cache, and redeploy static content.
- Admin setting not applying: clear cache and confirm the config scope (default / website / store view).
- Unexpected behavior: retest with only the required related modules enabled.
