# The Checkout Field Count Audit: Fields You Can Cut and the Ones You Cannot

Source: https://edgecommercejournal.com/blog/2026-11-17-checkout-field-count-audit.html

November 17, 2026 - Edge Commerce Journal


November 17, 2026

*Last quarter we counted the fields on a client's checkout and stopped at 23 form elements before the payment step. The store had not added most of them on purpose. Apps, address validation, and a marketing team's newsletter checkbox had accreted over two years, one harmless field at a time.*

## Count elements, not fields, and count on mobile first

Baymard Institute's checkout research puts the average flow at roughly 23 form elements when you count labels, inputs, checkboxes, and selectors the way a shopper meets them. That number is the audit unit. A single address block is not one field; it is seven or eight elements, each one a chance to hesitate, mistype on a phone keyboard, or hit a validation error that clears the whole form.

Run the count on a phone, in portrait, with autofill off. Desktop hides the cost because a full keyboard and a saved address forgive a long form. On mobile every extra element is a scroll, a keyboard switch between letters and numbers, or a dropdown that opens over the continue button. The stores that cut fields and saw nothing change usually cut them on desktop-tested flows their traffic never used.

## What usually goes, and what it is worth

The repeat offenders are a separate company field nobody reads, a second address line presented as required, a phone field demanded before shipping is even calculated, and an account creation step placed before purchase instead of after it. Baymard's usability work keeps finding the same pattern: shoppers do not object to giving information, they object to giving it before they understand why the store needs it at that exact moment.

Our order is blunt. Optional fields get marked optional or get deleted, and deletion wins ties. The newsletter checkbox moves to the confirmation page, where it converts worse per impression and costs nothing in completed orders. The phone field stays only where the carrier genuinely needs it for delivery, and then it sits next to the delivery options, labelled with that reason, not in the contact block three steps earlier.

## The fields you cannot cut, so stop trying

Tax, fraud screening, and regulated goods all pin fields in place. A store selling into multiple states needs a full address before it can quote tax correctly, and a high-fraud category needs the billing details its payment provider scores. Cutting those fields does not lift conversion; it lifts chargebacks and failed payments, which show up in a different report owned by a different person, usually a month later.

So the audit ends with two lists, not one. Fields removed, with the completion rate before and after on the same traffic mix. And fields kept on purpose, with the reason written next to each one, so next year's app install does not quietly re-add the ones you removed and nobody has to redo the argument from scratch.

Related reading on this site: [Why Commerce Infrastructure Is Moving to the Edge](why-commerce-moves-to-edge.md), [Full-Page Edge Caching for Dynamic Storefronts: The Hard Part Is Not the Caching](full-page-edge-caching-dynamic.md), [Your Product Page LCP Is One Image. Find It Before You Optimize Anything](2026-11-16-product-page-lcp-element-audit.md).

Open your checkout on a phone tonight and count every element out loud. If you reach 20 before payment, you have found tomorrow's work, and it is not a redesign.

## Frequently asked questions

### How many form elements should a checkout have?

There is no magic number, but Baymard Institute's research puts the average near 23 elements, and most stores can cut several without losing information they actually use. Count elements as the shopper meets them, including labels, checkboxes, and selectors, and audit on mobile first.

### Which checkout field should I remove first?

Start with fields nobody reads: a company field on a consumer store, a second address line marked as required, and any marketing checkbox sitting before payment. Each one costs completions and returns nothing the business acts on.

### Why does my checkout need a phone number at all?

Some carriers and delivery services require a contact number for the delivery itself. If yours does, place the field beside the delivery options and say that is what it is for. A phone field demanded early, with no reason given, reads as marketing capture and gets abandoned or filled with a fake number.

### Should account creation come before or after purchase?

After. Forcing registration before payment adds fields at the moment of highest intent and lowest patience. Guest checkout with an optional account offer on the confirmation page keeps the order and still captures the accounts worth having.
