company field validation fails for guest checkout

[my-brain-qlicks]

Preconditions and environment

• Magento 2.4.8-p1
• guest checkout enabled
• company attribute configured as required

Steps to reproduce

• Configure company attribute as required (Stores > Configuration > Customer Configuration > Name and Address Options > Company > Required)
• Enable guest checkout (Stores > Configuration > Sales > Checkout > Checkout Options > Allow Guest Checkout = Yes)
• Add product to cart
• Proceed to checkout as guest
• Fill out all required fields including company field
• Place order

Expected result

• Order should be placed successfully since all required fields including company are filled.

Actual result

• Order placement fails with validation error: "Company" is a required value.

Additional information

Error occurs in: vendor/magento/module-quote/Model/CustomerManagement.php:180

Root cause: In the validateAddresses() method, when processing guest checkout, the code creates a customer address object from billing address data but fails to copy the company field:

// Lines 161-171 in CustomerManagement.php
$customerAddress->setFirstname($billingAddress->getFirstname());
$customerAddress->setLastname($billingAddress->getLastname());
$customerAddress->setStreet($billingAddress->getStreet());
$customerAddress->setCity($billingAddress->getCity());
$customerAddress->setPostcode($billingAddress->getPostcode());
$customerAddress->setTelephone($billingAddress->getTelephone());
$customerAddress->setCountryId($billingAddress->getCountryId());
// MISSING: $customerAddress->setCompany($billingAddress->getCompany());
$customerAddress->setCustomAttributes($billingAddress->getCustomAttributes());

The company value from the billing address is never transferred to the customer address object being validated, causing the required field validation to fail.

Workaround: Add the missing line:

$customerAddress->setCompany($billingAddress->getCompany());

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 @my-brain-qlicks. 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.

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

Hello @my-brain-qlicks ,

Thank You for your report and collaboration.

We attempted to reproduce the issue in the latest 2.4-develop instances by following the provided steps and preconditions. We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to Reproduce:

• Configure company attribute as required (Stores > Configuration > Customer Configuration > Name and Address Options > Company > Required)
• Enable guest checkout (Stores > Configuration > Sales > Checkout > Checkout Options > Allow Guest Checkout = Yes)
• Add product to cart
• Proceed to checkout as guest
• Fill out all required fields including company field
• Place order

We followed the preconditions and steps as provided and encountered the issue.

Therefore, we are marking this ticket as "Issue: Confirmed."

Thank you!

[github-jira-sync-bot]

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