Changing customer email changes that customer's orders with CUSTOM emails.

[bgorski]

When you create an order for a registered customer, the email field comes pre-filled with that customer's email. Usually you won't change it when creating the order. Then, if it turns out that the customer calls the customer service and wants to change their email (maybe there was a typo when they registered, maybe they use a different email now etc.), it can be done on the customer edit page. It will affect the orders that customer placed - the email value will change on them as well.

So far so good.

However, when creating an order for a registered customer, you can change the email on the order. They may just want to use a different one for this particular order while not changing the email associated with their account (for example they may be buying a gift for their lover and don't want the spouse to find out while jealously browsing their email inbox). Those custom email addresses associated with orders should NOT change when you change the main email address on the account edit page in the admin panel. But it does, and it's a bug.

Then, you have no way of reverting just one order to the custom email address value. No workaround is possible for customer service, a code change is required by vendor's implementation team to change this behavior.

Preconditions (*)

Steps to reproduce (*)

1. Register a customer
2. Create an order for that customer with an email address unchanged
3. Create an order for that customer with a custom email address - change the default one on the order creation page
4. Notice that the main customer email address remains remained unchanged by this
5. Change the main customer email address on the customer edit page in the admin panel

Expected result (*)

1. Email address on the first order (one created with an unchanged email) is now changed
2. Email address on the 2nd order remains custom

Actual result (*)

1. Both orders have their email address changed to the new value

---

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 @bgorski. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

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.

🎥 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 @krishprakash. 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.

[krishprakash]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @krishprakash. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @krishprakash, here is your Magento Instance: https://38de4a3b9f5e9d5c35f5a5387cc4c8ab-2-4-develop.instances.magento-community.engineering
Admin access: https://38de4a3b9f5e9d5c35f5a5387cc4c8ab-2-4-develop.instances.magento-community.engineering/admin_cf8b
Login: 7495df4d
Password: aaa68b05898c