Shipping Address email field is being replaced with the billing address email

[rahimimo]

Preconditions (*)

1. Reproducable on Magento CE 2.4.3-p1
2. Using REST API of magento

Steps to reproduce (*)

When creating an order out of guest cart is being done, the shipping email is being replaced by the billing email.

1. Create a guest Cart using a POST request to this endpoint https://magento.test/rest/default/V1/guest-carts
2. Add an item to creared the guest cart using this endpoint
   https://magento.test/rest/default/V1/guest-carts/{created-guest-cart-step-1}/items? example body { "cartItem":{ "sku": "sample-sku", "qty": "1" } }
3. Add shipping info using this endpoint a POST request to:
   https://magento.test/rest/default/V1/guest-carts/{created-guest-cart-step-1}/shipping-information
   example body

{
  "addressInformation": {
    "billingAddress": {
      "country_id": "FI",
      "street": [ "Testikatu 1 C 44" ],
      "company": "",
      "telephone": "0",
      "postcode": "02230",
      "city": "Espoo",
      "firstname": "Siamak Rahimi Motem",
      "lastname": "Siamak Rahimi Motem",
      "email":"billing@address.co"
  },
  "shippingAddress": {
    "country_id": "FI",
    "street": [ "Testikat" ],
    "company": "",
    "telephone": "0",
    "postcode": "15877",
    "city": "gisha",
    "firstname": "Mona",
    "lastname": "Pourdeljoo",
    "email": "shipping@adress.co",
    "same_as_billing": 0
  },
  "shipping_method_code": "flatrate",
  "shipping_carrier_code": "flatrate",
  "extension_attributes": {}
}}

Up to this point if you use GET Cart endpoint you can see this shipping@adress.co email. BUT, if you create an order, that email is no longer can be retrieved.
4. Make a PUT request to create order endooint
https://magento.test/rest/default/V1/guest-carts/{created-guest-cart-step-1}/order
5. Get Order using a GET request to
https://magento.test/rest/default/V1/orders/{created-order-number-step5}

Expected result (*)

It is expected that the billing address does not leak to the shipping address.

1. [Screenshots, logs or description]

Actual result (*)

1. 

You see on fetching the order instead of shipping email, the billing email is being replicated.
2. Before creating the order that email can be seen from get guest cart end point

---

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 @rahimimo. 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

[Usik2203]

@magento give me 2.4-develop instance

[magento-deployment-service]

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

[magento-deployment-service]

Hi @Usik2203, here is your Magento Instance: https://6e5c89f8c1545f2c78eb82a91f656dfc-2-4-develop.instances.magento-community.engineering
Admin access: https://6e5c89f8c1545f2c78eb82a91f656dfc-2-4-develop.instances.magento-community.engineering/admin_bcdc
Login: 0177cb03
Password: 212d2595a428

[m2-assistant]

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

[m2-assistant]

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

Hello @rahimimo,

Thanks for posting this issue!

We have tried to reproduce this issue in the Magento 2.4-develop branch, and it is reproducible for us with the given steps. We have also tried to check the root cause of the issue and found that the data in table sales_order_address has the billing@address.co value for the row. Please have a look at the below screenshot for reference:

Hence confirming the issue.

Thanks