Wrong price is synced in data exporter for bundle products
@sydor-dev is already working on this.
Since Sep 2, 2026.
- Dominant language
- PHP
- Stars
- 12.2k
- Forks
- 9.4k
- PR merge metrics
- No merged PRs in 30d
Description
### Preconditions and environment
- Magento version 2.4.7-p4
- Bundle product is created with variation price set on both default and website level. Prices on default and website level must differ.
### Steps to reproduce
1. Run a catalog_data_exporter_products reindex.
2. Debug a query composed in \Magento\BundleProductDataExporter\Model\Query\BundleProductOptionValuesQuery::getQuery
### Expected result
1. price_value for the variation of the bundle product in the result is taken from the website level if set, not default level. This means it is taken from catalog_product_bundle_selection_price table. The price set only on default level is taken from the default level (= from catalog_product_bundle_selection table).
### Actual result
1. price_value for the variation of the bundle product in the result is always taken from the default level, not website level - even if set on website level. This means it is always taken from catalog_product_bundle_selection table, never from catalog_product_bundle_selection_price table.
### Additional information
Patch fixes this problem (patch assumes the installation is done in 'vendor' folder).
[bundle.patch.zip](https://github.com/user-attachments/files/19226954/bundle.patch.zip)
### Release note
_No response_
### Triage and priority
- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [x] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.