Magento 2.3.3 Customer shipping address firstname trouble. "firstname" is required

Magento 2.3.3 Customer shipping address firstname trouble. "firstname" is required

August 14, 2026 · Illustrated author avatarBy Stefan Bogdanescu
Magento 2.3.3 Customer shipping address firstname trouble. "firstname" is required

Solving Magento 2.3.3 Customer Shipping Address “Firstname” Required Issue

Are you facing the notorious “Firstname is required.” error when trying to place an order in your Magento 2.3.3 store? This issue often crops up after migrating data from older versions or performing customer registration/logins. Let’s dive into the root cause and provide a step-by-step solution.

Understanding the Problem

The core issue lies within the eav_attribute table, specifically with the is_required flag for the firstname attribute of the customer_address_entity entity type. Even if you’ve migrated data successfully from Magento 1 using the Data Migration Tool, this flag might remain set to yes.

The Root Cause: Incorrect Attribute Configuration

The is_required flag is responsible for enforcing field validation during form submission. When it’s enabled, Magento expects a non-empty value for that attribute regardless of whether you’ve configured the field as required in your theme files or not. This discrepancy leads to the frustrating “Firstname is required.” error.

Step-by-Step Solution

1. Identify the Culprit Attribute

First, log into your MySQL database using a client like phpMyAdmin or Navicat. Locate and open the eav_attribute table. Search for the attribute ID or code associated with the firstname field in the customer shipping address.

In most installations, you’ll find an entry something like this:

entity_type_id…entity_type_code…
4…customer_address…

2. Update the Attribute Configuration

To resolve the issue, we need to update two columns in the eav_attribute table:

  1. is_required: Set this flag to 0 (false). This disables the strict validation for the firstname field.
  2. is_visible: Ensure it’s set to 1 (true). This ensures the firstname field is visible on the frontend.

You can update these values either by manually editing the database entry or running a SQL query like this:

UPDATE eav_attribute SET is_required = 0, is_visible = 1 WHERE entity_type_id = 4 AND attribute_code = 'firstname';

3. Clear Cache

After updating the attribute configuration, clear your Magento cache to ensure the changes take effect immediately.

In a typical setup, you can do this by navigating to System > Cache Management in the admin panel and clicking on “Flush Magento Cache.” If you’re using Varnish or other caching mechanisms, make sure to flush those as well.

Verifying the Fix

Once you’ve implemented these changes, log out of the backend, and test the customer checkout process again. The firstname field should now be visible in both the frontend shipping address form and the customer profile page, with no validation errors appearing when submitting an order.

Conclusion

The “Firstname is required.” issue in Magento 2.3.3 is a classic example of how subtle database configuration discrepancies can disrupt the user experience. By directly updating the eav_attribute table and clearing cache, we’ve addressed the root cause and restored smooth checkout functionality for your customers.

Remember, when dealing with attribute configurations in Magento, it’s crucial to ensure consistency between the database schema and your theme’s frontend rendering logic. Regularly auditing these settings can help prevent similar issues from cropping up in the future.

If you found this solution helpful, be sure to explore our other Magento troubleshooting guides and tutorials at LaravelCompany.com. We’re constantly updating our resources to keep you informed about the latest developments in the e-commerce landscape.

Magento 2 Magento 1 Database Themes

Our network