Most conversion rate audits start with the homepage or the product page. Few start where the actual money is lost: the checkout form. Every field you ask for is a small tax on someone's willingness to finish buying — and most checkout forms are still collecting fields nobody on the team can explain a current reason for.

Why Checkout Forms Quietly Bleed Revenue

Checkout abandonment rarely has one dramatic cause. It's usually a series of small frictions that compound: a field that feels invasive, a label that's unclear, a required field that shouldn't be required. Each one only costs a percentage point or two — but on a form every customer has to complete, those percentage points are pure, direct revenue.

Cart Started 100% Checkout Reached 68% Form Completed 51% Purchase Confirmed 47%
Where checkout friction typically costs the most

The fields worth auditing first are the ones that were added for a reason that no longer applies — a shipping provider that's been replaced, a sales process that's changed, a "just in case we need it later" field that's outlived whatever it was for.

The Five Fields Worth Auditing First

These are the fields we most often find still sitting in a checkout flow long after the reason for asking has disappeared:

  • Phone number (marked optional). Optional fields still add visual weight and a moment of "do I need to fill this in?" hesitation. If it's genuinely optional, consider whether it needs to be visible at all during checkout versus collected post-purchase.
  • Fax number. Still present in a surprising number of legacy checkout templates. Almost no consumer checkout flow needs this in 2026.
  • Company name. Relevant for B2B invoicing, unnecessary friction for a consumer storefront. If only a subset of customers need it, show it conditionally rather than by default.
  • Secondary address line. Useful for apartment or suite numbers, but defaulting it to a separate required-looking field (rather than an optional inline addition to line one) adds a field most single-family-home customers stare at and skip.
  • Birthdate. Sometimes a genuine requirement (age-restricted products), often a leftover from a marketing segmentation request that was never actually used. Worth confirming who, if anyone, uses this data before keeping it in the required path.
The pattern to look for
It's rarely that a field is "bad" in isolation — it's that nobody has re-justified its presence since it was added. A quarterly checkout field audit catches this before it becomes a permanent tax on conversion.
Before AfterPhone (optional)Fax numberCompany nameSecondary address lineBirthdateRemoved or deferredRemovedConditional toggle onlyCombined into one fieldRemoved unless required
Auditing checkout fields against their actual use

How to Test Field Removal Safely

Removing a field isn't risk-free if that data feeds fulfillment, fraud checks, or downstream systems. Before removing anything, we map every field to what actually consumes it: shipping, billing, customer service, analytics, or nothing at all. Fields with a real downstream consumer get moved to post-purchase collection or made conditional, rather than deleted outright.

From there, we typically A/B test the streamlined form against the original for at least one full sales cycle, watching both conversion rate and downstream error rates (failed deliveries, support tickets citing missing information) before rolling out fully.

What to Do Instead of Just Deleting Fields

  • Move genuinely optional data collection to a post-purchase or account-creation step, away from the critical checkout path.
  • Use conditional logic to show fields like company name only when relevant (e.g., a "business order?" toggle).
  • Combine address line one and two into a single expandable field rather than two stacked required-looking inputs.
  • Default to the minimum legally and operationally necessary fields, and treat every addition as something that needs to earn its place back.

Measuring the Impact

The clearest signal is checkout completion rate — the percentage of people who start checkout and finish it — tracked before and after the change, ideally isolated from other simultaneous changes. Session recordings and form-analytics tools that show field-level abandonment are useful for confirming which specific field a customer stalled on before leaving.