Most checkout redesigns start with trust badges, payment icons and a progress bar. Those help, but they treat the symptom. The bigger lever sits underneath all of it: how many fields a buyer has to fill in before they can pay you. Baymard Institute's long-running checkout research keeps finding the same gap, an average checkout still asks for around 14 form fields when 6 to 8 would capture everything a normal order actually needs. Here is a field-by-field way to close that gap, and what to put in its place.
The average checkout displays about 14 form fields when 6 to 8 are enough for most orders, per Baymard Institute research. Cutting duplicate name, address and confirmation fields, merging shipping and billing, and replacing manual entry with autofill and digital wallets typically removes 20 to 60 percent of visible form elements without losing required data.
How many fields does a checkout actually need?
Baymard's checkout usability research, built from hundreds of hours of user testing across large ecommerce sites, has repeatedly found the average US checkout displays close to 14 form fields, roughly twice what a well-built flow requires. The same research shows most checkouts can cut the number of form elements shown to users by 20 to 60% without removing any data the order actually needs. The excess is rarely one obvious offender. It is usually five or six small ones stacked together: a separate billing address form that duplicates shipping, a company name field on a consumer store, a fax field nobody has used since 2004, and a confirm-email box that exists out of habit rather than necessity.
Why extra fields cost you real orders, not just goodwill
This is not a minor UX nitpick. Nearly one in five shoppers has abandoned a cart specifically because the checkout process felt too long or too complicated, according to Baymard's research. Separately, testing compiled on landing page and form conversion in 2026 found that reducing form length delivers the single highest average lift of any tested change, with one case shortening a form from eleven fields to four and gaining a 120% increase in completions. Checkout fields are not neutral real estate. Every one you keep has to earn its place against a buyer who is already halfway to abandoning.
| Field | What to do | Why |
|---|---|---|
| Separate first name / last name | Combine into one full name field | Splitting rarely improves data quality and adds a field for nothing |
| Billing address (when it usually matches shipping) | Default to "same as shipping" with a toggle | Most orders ship and bill to the same address |
| Company name | Cut on consumer stores, keep for B2B | Irrelevant to most individual buyers |
| Confirm email / confirm password | Cut, use a single field with inline validation instead | Duplicate entry adds friction without meaningfully reducing errors |
| Phone number | Keep, but mark clearly as optional unless needed for delivery | Useful for shipping issues, but not always required to complete a sale |
| Fax number | Cut entirely | Legacy field with effectively no modern use case |
| Account creation fields | Move after purchase, offer guest checkout by default | Forcing account creation before payment is a well-documented abandonment driver |
| Address line 2 | Keep, but collapse into address line 1 with autocomplete | Address lookup autocomplete handles most cases in one field |
What replaces the fields you cut
Cutting a field only works if the information still reaches you accurately. Address-lookup autocomplete fills most of the address block from a few typed characters. Browser and card autofill, especially on mobile, can complete a payment field in one tap once a buyer has purchased anywhere else recently. Digital wallets remove the payment and shipping fields almost entirely by pulling verified data straight from the buyer's device, a shift we cover in more depth in our piece on digital wallet checkout adoption. None of these require you to collect less data. They just stop asking the buyer to type it.
Audit your checkout with a stopwatch, not a checklist. Time how long it takes a new team member, unfamiliar with the form, to complete a test order on mobile. If it takes more than 90 seconds excluding payment processing, you almost certainly have fields to cut, merge or default before you touch anything else on the page.
Don't just cut fields, rewrite the ones you keep
Field count is half the problem. The other half is how the remaining fields are labeled. Recent landing page testing found pages written at a fifth to seventh grade reading level convert at roughly 11.1%, nearly double the 5.3% rate for dense, professional-register copy, and the same clarity gap shows up in checkout microcopy. "Apt/Suite/Unit" beats "Address Line 2." "We'll only use this to text you delivery updates" beats a bare, unexplained phone number field. A short, specific error message beats a generic "invalid input" that leaves the buyer guessing what actually went wrong.
A simple test plan for this quarter
- Audit the live checkout field by field against the cut list above and flag anything you cannot justify keeping.
- Cut or merge one to two fields at a time and A/B test against the current flow, watching completion rate and error rate together.
- Add or improve autofill and address-lookup support before removing fields that depend on accurate manual entry.
- Rewrite labels, help text and error messages for the fields that remain, aiming for plain, specific language over generic prompts.
- Re-test on mobile specifically, since a field that is a minor nuisance on desktop can be the difference between finishing and abandoning on a small screen.
This kind of incremental, measured testing is exactly what our conversion optimization team runs for clients who want checkout improvements they can actually attribute, not a redesign they have to take on faith.
Frequently asked questions
How many form fields should a checkout have?
Baymard Institute's checkout research has long found the average checkout displays around 14 form fields, while 6 to 8 are enough to capture what most orders actually need. Most checkouts can cut their visible form elements by 20 to 60 percent without losing required data.
Do extra checkout fields really reduce conversion?
Yes. Baymard's research finds nearly one in five shoppers have abandoned a cart specifically because the checkout process felt too long or too complicated. Separate testing on form length reduction has shown lifts as high as 120 percent when a signup or checkout form dropped from eleven fields to four.
Which checkout fields are safe to cut first?
Start with a separate billing address field when it usually matches shipping, a company name field for consumer checkouts, a fax or landline field, and any confirm-email or confirm-password duplicate field. Combine first and last name into one field and shipping and billing into a single toggle instead of two forms.
What should replace fields you remove from checkout?
Digital wallets like Apple Pay and Google Pay, browser and card autofill, and address-lookup autocomplete replace most of the manual typing a long checkout form used to require. A guest checkout option removes the account-creation fields entirely for buyers who do not want to create a password.
Does simplifying checkout copy help as much as cutting fields?
It helps more than most teams expect. Pages and forms written at a fifth to seventh grade reading level convert at roughly 11.1 percent versus 5.3 percent for dense, professional-register copy in recent landing page testing, and the same clarity gap shows up in field labels, error messages and checkout help text.
How do I test checkout form changes without breaking the order flow?
Cut or merge one to two fields at a time and run it as a proper A/B test against your current checkout, watching completion rate and error rate together, not completion rate alone. A field that looks safe to remove can quietly increase failed orders if it was catching bad addresses or invalid phone numbers before submission.
The takeaway
The checkout field audit is one of the few conversion fixes that is genuinely low risk and consistently high reward. You are not redesigning the page or testing a new value proposition, you are removing friction that was never earning its place. Start with the fields on the cut list above, replace what you remove with autofill and wallets rather than nothing, and rewrite the labels on what stays. Then test it properly instead of assuming the win.