berrypath / magento2-berrypath-flow
BerryPath guided selling flows and product finders for Magento 2.
BerryPath Guided Selling Flows for Magento 2

Help shoppers choose the right product with guided selling flows on Magento category pages, product pages, and CMS content.
New to BerryPath? A free plan is available with 1 guided selling flow and up to 2,500 products. Existing customers keep using their current plan.
Guide shoppers where decisions happen
- Category pages: narrow a large collection before filters and product grids become overwhelming.
- Product pages: confirm whether the current product fits and guide shoppers to stronger alternatives.
- CMS content: turn homepages, buying guides, landing pages, and campaigns into interactive product advice.
- Popup, sidebar, or inline: choose the experience that best fits the page and storefront theme.
Built for Magento teams
- Configure global market, locale, placement, and product identifier defaults per Magento scope.
- Assign a different BerryPath Flow UUID to individual products and categories.
- Place flows in CMS content with the Magento
BerryPath Flowwidget. - Match the current product by Magento product ID, SKU, or another product attribute.
- Measure assisted order value from the Magento checkout success page.
- Connect Magento product data with the included BerryPath Product Feed module.
- Add Hyva storefront support with the optional compatibility package.
How it works
- Build and publish a guided selling flow in BerryPath.
- Copy its BerryPath Flow UUID or published widget URL.
- Add it to a Magento category, product, or CMS widget.
- Test the shopper journey and use BerryPath analytics to improve it.
A BerryPath account is required to build and publish guided selling flows.
Installation
composer require berrypath/magento2-berrypath-flow
bin/magento module:enable BerryPath_Flow
bin/magento setup:upgrade
bin/magento cache:flush
For local app/code development, place the module at:
app/code/BerryPath/Flow
The Composer package installs berrypath/magento2-berrypath-product-feed as a dependency.
Configuration
Store defaults:
Stores > Configuration > BerryPath > Flow
Configure the global enable switch, market code, locale, category and product placements, product ID source, and assisted conversion measurement here. Settings support Magento default, website, and store-view scope.
Place a flow:
Category: Catalog > Categories > BerryPath Flow
Product: Catalog > Products > BerryPath Flow
CMS: Content > Widgets > Add Widget > BerryPath Flow
Paste the public token, share URL, or embed URL from a published BerryPath flow. If no BerryPath Flow UUID is configured for the current placement, the module renders nothing.
The locale setting is sent as data-berrypath-locale. Leave it empty to derive the primary language from the Magento store locale—for example, de_DE becomes de.
Product feed
Manage product feeds from:
Catalog > BerryPath > Product Feeds
Create separate feeds for store views and channels, select the product attributes BerryPath needs for matching, and generate XML, CSV, or JSON output manually or through Magento cron.
See the berrypath/magento2-berrypath-product-feed package for detailed feed configuration.
Hyva compatibility
For Hyva storefronts, install the separate compatibility module:
composer require berrypath/magento2-berrypath-flow-hyva-compat
bin/magento module:enable BerryPath_FlowHyvaCompat
bin/magento setup:upgrade
bin/magento cache:flush
The package replaces the standard frontend templates through hyva-themes/magento2-compat-module-fallback while keeping the same placements and configuration.
External service and privacy
The module loads the BerryPath embed script only when a guided selling flow or assisted conversion event is used. BerryPath receives the configured flow token, locale, market code, and product identifier required to display and match the selected flow.
When assisted conversion measurement is enabled, the Magento checkout success page sends the order total and configured product identifiers to BerryPath. Customer names, email addresses, postal addresses, and payment details are not included. Measurement can be disabled in the module settings.
- Service provider: BerryPath
- Terms and conditions
- Privacy statement
Screenshots
Ask relevant, easy-to-answer questions:

Turn shopper answers into focused product recommendations:

Place guided selling in Magento CMS content, category pages, and product pages:



License
MIT. See LICENSE.
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
| Version | Stability | QA Status | Compatibility | Released |
|---|---|---|---|---|
| 1.0.5 | stable | Fail | Magento 2.4.7-2.4.9 Details | 2026-07-21 16:40:06 |
| 1.0.4 | stable | Not tested | Not yet tested Details | 2026-06-30 11:26:18 |
| 1.0.3 | stable | Not tested | Not yet tested Details | 2026-06-25 14:24:32 |
| 1.0.2 | stable | Not tested | Not yet tested Details | 2026-06-20 11:02:34 |
| 1.0.1 | stable | Not tested | Not yet tested Details | 2026-06-16 08:05:53 |
| 1.0.0 | stable | Not tested | Not yet tested Details | 2026-06-14 08:24:02 |
Requires 2
| Package | Constraint |
|---|---|
| berrypath/magento2-berrypath-product-feed | ^1.0 |
| php | >=8.1 |
Suggests 1
| Package | Reason |
|---|---|
| berrypath/magento2-berrypath-flow-hyva-compat | Hyva compatibility for BerryPath Flow. |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from berrypath
View vendorTurn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.