The average ecommerce checkout form asks for 14–15 fields. Cutting that to 8 fields or fewer can noticeably improve checkout completion rates. Every field you add is a question you are asking your customer — and every question is a reason to leave.
Why Checkout Field Length Kills Conversions
The Baymard Institute found that 17% of US online shoppers have abandoned a checkout specifically because “the checkout process was too long or complicated.” That is not the largest reason for cart abandonment (unexpected shipping costs leads at 49%), but it is entirely within your control.
The cognitive cost of form completion is not just about time. Each field is a micro-decision: should I give this? Is it required? What happens with this data? At 6 fields, that cognitive load is low. At 14 fields, it is high enough that a meaningful percentage of customers rethink the purchase.
The goal is to ask for exactly what you need to fulfill the order — nothing more.
The Fields You Actually Need
For a standard physical product shipped to a domestic customer:
Required:
- First name
- Last name
- Email address (for order confirmation)
- Address line 1
- City
- State/Province
- ZIP/Postal code
- Country
- Payment details (card number, expiry, CVV — handled by your payment processor)
Optional/Situational:
- Phone number (only if you genuinely call customers about delivery — most stores do not)
- Address line 2 (apartment/suite — keep it, some customers need it)
- Company name (only if you sell B2B)
That is 9 fields maximum for a standard physical goods checkout. Most WooCommerce stores show more than this because they include all optional fields by default.
The Phone Number Decision
Phone number is the field most frequently included unnecessarily. Ask yourself: does your fulfillment process require calling customers? Do your shipping carriers require it? Most small ecommerce stores answer no to both.
When phone is required for shipping carriers (international orders, FedEx, DHL), ask for it in the shipping section with a clear explanation: “Required by carrier for international delivery.” That context makes customers far more likely to provide it.
When phone is optional — label it as optional or remove it. Every required field that customers cannot understand the reason for is an abandonment risk.
What WooCommerce Shows by Default
WooCommerce’s default checkout includes: first name, last name, company name, country, address line 1, address line 2, city, state, ZIP, phone, email. That is 11 fields before payment, and company name and phone are rarely necessary.
WooCommerce’s own settings let you hide the company, address line 2 and phone fields or make them optional or required: in the Checkout block’s settings in the site editor, or under Appearance → Customize → WooCommerce → Checkout on the classic shortcode checkout. Other field changes need a plugin or custom code. The WooCommerce Checkout Field Editor plugin handles most of those through the admin. Alternatively, a developer can modify checkout fields in the WooCommerce template files.
Removing the company field from a non-B2B store is a 5-minute change that immediately reduces field count. Making phone optional costs nothing and removes a source of friction for customers who do not want to provide it.
Address Autocomplete: The Form Length Workaround
Address autocomplete allows customers to type a few characters of their street address and select from a dropdown of matching addresses. WooCommerce does not support this natively — it requires the Google Places API or a similar integration.
The benefit: a customer types “142 Oak” and selects their full address from a dropdown. City, state, and ZIP are auto-populated. What was 5 required fields becomes effectively 1 field plus a selection.
Autocomplete reduces form abandonment on the address section in most implementations. The API cost is usually small at typical checkout volumes. Google bills Autocomplete per request, with a free monthly allowance, so check Google Maps Platform’s current pricing against your checkout volume.
There are WooCommerce plugins that implement autocomplete (the official WooCommerce Shipping plugin includes it, or third-party plugins like Kali Forms). Custom implementation through the Google Places API requires a developer but gives you more control over the UX.
Order Summary Visibility at Checkout
This is not a field optimization, but it directly affects checkout completion: customers who can see their order summary (items, quantities, prices, total) while filling out checkout forms abandon less.
WooCommerce desktop checkout shows the order summary in a sidebar column. On mobile — where over 60% of ecommerce traffic now originates — the order summary is often collapsed or hidden until payment. That means customers are entering payment details without a visible reminder of what they are buying.
Make the order summary visible above the checkout form on mobile. This is a CSS/template change that requires a developer on a custom build or a checkout customization plugin on a standard WooCommerce setup.
Inline Field Validation
Error messages that appear after form submission are significantly worse for conversion than inline validation that catches errors as the customer types. When a customer fills 12 fields, submits, and gets a “phone number is invalid” error, they have to find the field, fix it, and submit again. The friction is compounded.
Inline validation shows a green checkmark or red X next to each field as it is completed. The email field validates format immediately. The ZIP field validates against your shipping zone. Credit card numbers validate the Luhn algorithm before submission.
WooCommerce does some inline validation by default, but it is inconsistent. Payment processors handle their own card field validation. For the shipping fields, custom validation logic requires code or a plugin.
The business case: in a usability study by Luke Wroblewski and Etre, inline validation raised form success rates by 22% and cut errors by 22% (A List Apart).
Single-Page vs Multi-Step Checkout
WooCommerce’s default checkout is single-page: all fields on one form. Some stores implement multi-step checkout (contact → shipping → payment across separate steps) on the theory that breaking the form into smaller chunks reduces cognitive load.
The research here is mixed. For simple checkouts under 10 fields, single-page outperforms multi-step — there is no benefit to adding navigation steps when the form is short. For complex checkouts (multiple shipping options, gift messaging, multiple delivery dates), multi-step can help by grouping related decisions.
For most small ecommerce stores, single-page checkout with a short, clean form is the correct choice. Multi-step checkout is worth testing when your checkout form exceeds 12 fields — and if it exceeds 12 fields, the first fix is removing unnecessary fields, not adding steps.
Our custom WooCommerce development builds checkout flows designed around the specific purchase journey for your product type — not the WooCommerce default template applied to every store. That includes field configuration, validation logic, address autocomplete, and mobile layout, all handled at build time.
Testing Checkout Changes
Checkout is not a place to make gut-feel changes without measurement. Use Google Analytics 4’s funnel exploration report to see where in your checkout process customers are abandoning. The funnel stages: cart → checkout started → contact info complete → shipping method selected → payment → purchase.
If you see 40% abandonment on the “contact info” step, that points to field friction. If you see 55% abandonment on “payment,” that points to trust signals or payment method availability.
Make one change at a time, measure until you have enough orders for a significant result (at least 2–3 weeks, to cover weekly cycles), then evaluate. Changing five things at once makes it impossible to know which change had which effect.
Need a full read on your checkout before making changes? Run a store audit at honest.designodin.com — it covers field configuration, form behavior, and mobile checkout alongside other ecommerce health signals. Or talk to us if you are building fresh.
FAQ
How many fields should a WooCommerce checkout have? For standard domestic physical goods: 8–9 fields before payment. For international orders: add phone (required by most carriers). For digital goods: just email and payment — no shipping address needed. Every additional field beyond what is required to fulfill the order is a conversion risk.
How do I remove the company name field from WooCommerce checkout?
Set the company field to hidden in WooCommerce’s checkout settings: the Checkout block’s settings in the site editor, or Appearance → Customize → WooCommerce → Checkout on the classic shortcode checkout. The WooCommerce Checkout Field Editor plugin also works, or, in your functions.php file, use the woocommerce_checkout_fields filter to unset the billing_company field. If your store serves any B2B customers who need to provide a company name for invoicing, make it optional rather than removing it.
Does address autocomplete really improve checkout conversion? Yes. Autocomplete reduces typing on the address section — the most error-prone part of checkout — and prevents address format errors that cause shipping failures. Most implementations see less abandonment at the address step.
Should I use single-page or multi-step checkout in WooCommerce? Single-page checkout works better for most small stores with short forms. Multi-step checkout can help when the form is complex (more than 12 fields) or when different checkout stages require very different information. Start with single-page, reduce field count, and only consider multi-step if the form cannot be shortened further.
What is inline validation in checkout forms? Inline validation shows the customer whether a field is correctly filled in real time — as they type, not after they submit. A green checkmark on email when the format is valid, a red indicator when the credit card number fails format check. In a usability study by Luke Wroblewski and Etre, inline validation raised form success rates by 22% and cut errors by 22%.