Reorder feature allows you to purchase product from different stores on the website

[Kaitaka48]

Preconditions and environment

• Magento version　2.4.4-p2
• Multi Website - one store - one storeview(or multi storeview)　
• Customers can login on all websites.
  Kindly refer the screenshots.

Steps to reproduce

1. Customer login to "WebsiteA"
2. Order product A from "StoreA" (order ID: 12345)
3. Customer login to "websiteB"
4. Reorder product(order ID: 12345) on My Account page

Expected result

product A cannot be purchased at "WebsiteB"

Actual result

product A can be purchased at "WebsiteB"

Additional information

'Product A' can only be ordered on website A

• "websiteA" domain name: www.magentoA.com
• "websiteB" domain name: www.magentoB.com

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

[m2-assistant]

Hi @Kaitaka48. 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. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

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.

[m2-assistant]

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

     - 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!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

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

  - 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-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://77001b92f892260a2880ddb46d11b4de.instances-prod.magento-community.engineering
Admin access: https://77001b92f892260a2880ddb46d11b4de.instances-prod.magento-community.engineering/admin_cd0d
Login: f1af23fc
Password: d52b3fd086f4

[engcom-Bravo]

Hi @Kaitaka48,

Thank you for reporting and collaboration.

Could please provide more information regarding

1.We have to create Single website - Multiple stores(or)Single store -Multiple storeviews.(or) Multi Website - Single store.

2.Customer Account sharing options - Global (or) Per Website.

3.We have to you disable/enable reorder option for particular store/storeview.

Please provide information it is helpful for us to reproduce the issue.

Thanks.

[Kaitaka48]

Hi @engcom-Bravo,

I have answered your questions

＞1.We have to create Single website - Multiple stores(or)Single store -Multiple storeviews.(or) Multi Website - Single store.

Multiple Websites - Single Store.

＞2.Customer Account sharing options - Global (or) Per Website.

Global

＞3.We have to you disable/enable reorder option for particular store/storeview.

All store/store view reorder options are enabled

ーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーーー

There was a mistake in the steps to reproduce.Please check the correction.

I have already created a PR（#37373）, please refer to it.

Thanks

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://77001b92f892260a2880ddb46d11b4de.instances-prod.magento-community.engineering
Admin access: https://77001b92f892260a2880ddb46d11b4de.instances-prod.magento-community.engineering/admin_abbf
Login: ffe6909c
Password: f2fa3c9076af

[engcom-Bravo]

Hi @Kaitaka48,

Thanks for your update.

We have followed below steps to reproduce.

Steps to reproduce

• Customer login to "WebsiteA"
• Order product A from "StoreA" (order ID: 12345)
• Customer login to "websiteB"
• Reorder product(order ID: 12345) on My Account page

We are able to reproduce the issue in Magento 2.4 develop instance but it is an expected behaviour of Magento.When we set
Customer Account sharing options to GLOBAL It will Shares customer account information with every website and store in the installation.

Kindly refer this document https://experienceleague.adobe.com/docs/commerce-admin/customers/customer-accounts/customer-account-scope.html?lang=en and please let us know if you are still facing any issue.

Thanks.

[Kaitaka48]

@engcom-Bravo

The important aspects of this issue,"Products that are only tied to a particular website can be purchased on other websites."
Then correct reproduce procedure is:

Preconditions:
Assume 'Website A' already exists (default website)

1. add a new 'Website B'
2. add a root category (Category Name: B) and subcategory (Category Name: b) dedicated to 'Website B'
3. add a store, store view to 'Website B', Tie root categories added in 2.
4. Customer account sharing option is a global
5. the reorder option for a specific store/store view is enabled
6. create product B that is only tied to 'Website B'
   ・Enable Product: Yes
   ・Attribute Set: Default
   ・Product Name: sampleB
   ・Categories：b
   ・Product in Websites: 'Website B'
7. Create customer account
8. Purchase "Product B" from "Website B" with logged in status
9. Log in to 'Website A'(default website)
10. Access to order history
11. Do reorder(8. Product B)

The expected execution result is "Reorder cannot be completed", because Product B is a product not tied to 'Website A'
However, Magento completes reorder without any errors.

The store ID of the order object held by "current_order" is the store ID associated with the website where the product was purchased.

$order = $this->_coreRegistry->registry('current_order');
$reorderOutput = $this->reorder->execute($order->getIncrementId(), $order->getStoreId());

Wouldn't it be more natural to use the store ID of the Website you are currently ordering from?

Thanks

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @engcom-Bravo, here is your Magento Instance: https://77001b92f892260a2880ddb46d11b4de.instances-prod.magento-community.engineering
Admin access: https://77001b92f892260a2880ddb46d11b4de.instances-prod.magento-community.engineering/admin_9113
Login: 34dec8d7
Password: bd1498cc5f0c

[engcom-Bravo]

Hi @Kaitaka48,

Thanks for your update.

Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Preconditions:
Assume 'Website A' already exists (default website)

Steps to reproduce :

• add a new 'Website B'
• add a root category (Category Name: B) and subcategory (Category Name: b) dedicated to 'Website B'
• add a store, store view to 'Website B', Tie root categories added in 2.
• Customer account sharing option is a global
• the reorder option for a specific store/store view is enabled
• create product B that is only tied to 'Website B'

・Enable Product: Yes
・Attribute Set: Default
・Product Name: sampleB
・Categories：b
・Product in Websites: 'Website B'

• Create customer account
• Purchase "Product B" from "Website B" with logged in status
• Log in to 'Website A'(default website)
• Access to order history
• Do reorder(8. Product B)

Product is not assigned to default website still we are able to place the order.

Hence confirming the issue.

Thanks

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-8598 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.