Skip to content

Price issues with configurable products linked to the same simple product, same online shop - Magento 2 #39839

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 of 5 tasks
FCarriere-37 opened this issue Apr 18, 2025 · 3 comments
Assignees
Labels
Issue: needs update Additional information is require, waiting for response

Comments

@FCarriere-37
Copy link

Preconditions and environment

Dear,

We are currently migrating from Magento 1 to Magento 2.

On Magento 1, we were able to create two configurable products with different prices, both linked to the same simple product.

It seems this is no longer possible in Magento 2, as it automatically applies the same price from the shared simple product to all related configurable products.

Can you confirm if this is native behavior in Magento 2?

If so, could you suggest any proven solutions or workarounds to display configurable products with different prices while still linking them to the same simple product?

Thank you in advance.
Best regards,

Steps to reproduce

  1. create a simple product, with given prices
  2. Create 2 configurable products
  3. Link those 2 products to the same simple product
  4. Apply a specific price on each of the configurable product

Expected result

2 configurable products, linked to the same storage management.
But with distinct prices each.

Actual result

Only the price of the simple product is displayed.

Additional information

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • 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”.
Copy link

m2-assistant bot commented Apr 18, 2025

Hi @FCarriere-37. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

Copy link

m2-assistant bot commented Apr 21, 2025

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-November
Copy link
Contributor

Hello @FCarriere-37 ,

Thank you for your report and collaboration.

We have reviewed your issue and would like to clarify the following point:

"A configurable product does not have its own price in the catalog. The configurable product price is derived from its In Stock child products."

Image

For further reference, please review the attached document. https://experienceleague.adobe.com/en/docs/commerce-admin/catalog/products/types/product-create-configurable

Thank you for reaching out to us. If you have any additional queries, please let us know.

Hence marking this issue as "Needs Update"

Thank You!

@engcom-November engcom-November added the Issue: needs update Additional information is require, waiting for response label Apr 25, 2025
@ct-prd-projects-boards-automation ct-prd-projects-boards-automation bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response
Projects
Development

No branches or pull requests

2 participants