control, work, clerk, form, business, on a white background, white background, clerk, form, form, form, form, form
Photo by jarmoluk on Pixabay

Checkout Usability

Part of Checkout conversion and usability

Finding unnecessary fields in a checkout form

Audit checkout inputs by order journey, find fields with no necessary purpose and make conditional requests easier to understand.

This is an editorial pen name used by the publication, not a claim of an independently verified personal identity. Original editorial credit: Desk Checkout Strategy.

undefined

List every input a buyer sees, then ask what the store cannot complete correctly without its value for that order. Remove fields with no necessary checkout purpose. Show a field only on the journeys that need it when the checkout supports that rule. Keep genuinely required details and explain less obvious requests.

Start with the fields stores add by habit. A business name field is unnecessary where the store does not sell to businesses, and a tax identifier field is unnecessary where it does not sell to businesses in the European Union or the United Kingdom (help.shopify.com).

Key findings from Australian checkout form research

  • Average number of form fields in checkout
  • Required phone number with email on Shopify
  • Secondary address line setting in Shopify

Inventory the form by journey

Record fields as they appear to a new guest buyer, if guest checkout is offered. Repeat for returning buyers and materially different order types. Delivery, click and collect and digital fulfilment can require different information. Include visible choices as well as text boxes: an optional company name or open billing-address section still asks for attention.

For each field, note its label, required or optional status, when it appears and which process uses its value. Include fields supplied by apps or payment components in the visual inventory. Not all checkout form fields can be edited: in Shopify, some fields cannot be changed (help.shopify.com). Check any proposed change to those components against the actual platform and provider integration.

Question for each fieldDecision it informs
What order task uses this value?Keep it if that task cannot work correctly without it.
Does every journey need it?Show it only for relevant products or fulfilment choices where possible.
Has the buyer already supplied it?Reuse it where accurate and appropriate.
Is it optional but prominent?Mark it optional and consider a less intrusive presentation.
What happens when it is blank or wrong?Explain the error and offer a way to correct it.

Audit checklist for unnecessary checkout fields

  • What order task uses this value?
  • Does every journey need it?
  • Has the buyer already supplied it?
  • Is it optional but prominent?
  • What happens when it is blank or wrong?

Challenge the field, not the customer

A delivery address has an obvious role when goods are shipped. A collection order calls for a separate check of what information pickup actually needs. A phone number may support a particular delivery or contact process; if it is required, explain why. Do not keep a field mandatory merely because the current form requires it.

Shopify offers no option to require both an email address and a phone number as the contact method, so a required phone number adds nothing to a form that already requires email (help.shopify.com). A required shipping address phone number is enforced only when checkout includes a shipping address step (help.shopify.com).

Check whether the form asks for the same address twice without a reason or splits a value into inputs buyers struggle to use. A billing address cannot simply be discarded when a payment or business process requires it. The aim is an accurate rule for each journey, not the smallest field count.

When to keep vs. remove common checkout fields

  • Company name field
  • Tax identifier (e.g., ABN/GST)
  • Phone number (with email already required)
  • Billing address

Make the remaining fields easier to complete

Give controls clear, persistent labels. A label should describe the purpose of its control and stay associated with the control in the code, so screen reader and speech input users can identify the field (w3.org). Mark both required and optional fields so buyers need not infer which they can skip.

Place brief instructions beside unusual requests. When validation finds an error, list the errors at the top of the form, before the fields, and reference the label of the field concerned with a link to the control (w3.org). Explain each error in text and preserve other correct entries where safe.

For Australian orders, test an address with a unit or apartment number. In Shopify, the secondary address line can be required, optional or removed, and requiring or removing it can stop some customers completing their purchase depending on their type of residence (help.shopify.com). If the store takes overseas orders, review those address formats separately.

Pros and cons of making fields optional

  • Pros
  • Cons

Decide what to change

Assign each field an outcome: keep, make conditional, make optional, combine or remove. Record the reason and the process that uses it. Under APP 5, a store must tell buyers why it collects personal information, who it may be disclosed to, and how they can access and correct it (wilco.au).

Check affected order types through fulfilment and payment before release so removing an input does not break a later task. After release, review validation errors and customer contacts alongside completion; a shorter form can shift work to support.

Steps to simplify a checkout form

  1. Inventory all fields by user journey
  2. Evaluate necessity per field
  3. Remove or make conditional fields
  4. Test changes across fulfilment and payment flows
  5. Review support data post-release

Further reading: E-Commerce Checkouts Need to Mark Both Required Fields and Optional Fields Explicitly (Only 14% Do So) self.__wrap_n!=1&&self.__wrap_b("R_14b7bkqim",1) (baymard.com).

More from Checkout Usability