Price not depends from website scope when base price updating via REST api

[monteshot]

Preconditions (*)

1. Magento 2.4.2-p1
2. Get Admin token before using base price endpoint

Steps to reproduce (*)

1. Set REST endpoint using code for example https://aquapolis-migua.dev.perspective.net.ua.local/rest/ru/V1/products/base-prices where '/ru/' - code
   2.Put Data in body for example
   { "prices": [ { "price": 14, "store_id": 2, "sku": "99999", "extension_attributes": {} } ] }

Expected result (*)

1. Base price should use settings from website scope

Actual result (*)

price_bug.mp4

2. Base price setting gets data from storeview

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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”.

[m2-assistant]

Hi @monteshot. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-Echo. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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-Echo]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @engcom-Echo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @engcom-Echo, here is your Magento Instance: https://59bc0ea21b4e16b5a5606f16ab7079ce-2-4-develop.instances.magento-community.engineering
Admin access: https://59bc0ea21b4e16b5a5606f16ab7079ce-2-4-develop.instances.magento-community.engineering/admin_f917
Login: a8a25cd4
Password: 1a999d20920d

[engcom-Echo]

Hi @monteshot
Thanks for reporting this issue.
I tried to reproduce this issue, using the video you have attached, unfortunately it was a little confusing for me. Could you please help me out with the Steps that you are performing to reproduce the issue & explain to me little more about the issue.
I could also share with you the steps I did,

1. On a clean instance of magento 2.4-develop branch , created a multi store view set up(say Russian storeview & Netherland store view)
2. Got the Admin token & Hit the API to add/update product prices rest/V1/products/base-prices with the payload
   { "prices": [ { "price": 122, "store_id": 3, "sku": "24-MB01" } ] }
   here store Id 3 corresponds to the Netherlandian Store View & after hitting the API , the Base Price on the corresponding store view got updated.
   So please provide more details or additional/missing steps regarding the same.

Thank you.

[monteshot]

Hi @monteshot
Thanks for reporting this issue.
I tried to reproduce this issue, using the video you have attached, unfortunately it was a little confusing for me. Could you please help me out with the Steps that you are performing to reproduce the issue & explain to me little more about the issue.
I could also share with you the steps I did,

1. On a clean instance of magento 2.4-develop branch , created a multi store view set up(say Russian storeview & Netherland store view)
2. Got the Admin token & Hit the API to add/update product prices rest/V1/products/base-prices with the payload
   { "prices": [ { "price": 122, "store_id": 3, "sku": "24-MB01" } ] }
   here store Id 3 corresponds to the Netherlandian Store View & after hitting the API , the Base Price on the corresponding store view got updated.
   So please provide more details or additional/missing steps regarding the same.

Thank you.

@engcom-Echo

Hello.
Let me clarify steps.
You hit the Netherlands StoreView with code (for example) "ne" and in payload you has put
{ "prices": [ { "price": 122, "store_id": 3, "sku": "24-MB01" } ] }
Then please try to hit API with with code "ne" and the with Russian store_id (for ex: "2") in payload
{ "prices": [ { "price": 123, "store_id": 2, "sku": "24-MB01" } ] }

The price will change. Moreover the price on RU and NE StoreView will be different on product page and the same on the catalogsearch

Thank you.

[engcom-Echo]

Hi @monteshot
I tried to hit API with with code "nl" ( for Netherland storeview) and the with Russian store_id (for ex: "2") in payload
{ "prices": [ { "price": 123, "store_id": 2, "sku": "24-MB01" } ] }
I got the Russian store view price updated. It seems the store code passed via the url is ignored & the one passed via the payload is taken into consideration. Do you concur with this scenario?