What Checkout Fields Are Actually Necessary for Conversion?
The Four Fields You Genuinely Need
You need exactly four things to complete an ecommerce order: a way to contact the buyer, a place to send the parcel, a delivery method, and a payment instrument.
That is the whole list. It is worth writing it down because most checkouts have drifted well beyond it, usually one well-intentioned addition at a time. A field gets added for a campaign, the campaign ends, and the field stays forever because nobody remembers why it is there.
- Email: For the order confirmation and shipping updates. This is the only contact field that is genuinely required.
- Delivery address: Name, street, city, region, postcode, country. All of it needed to ship.
- Shipping method: Only if you offer more than one. If you have a single rate, do not make the shopper choose it.
- Payment details: Handled by your payment provider, not by your form.
Everything beyond those four is a business preference dressed up as a requirement. That does not automatically make it wrong, but it does mean it should have to justify itself against the conversion it costs. For merchants on OpoShop, auditing this list is usually the fastest checkout improvement available.
The Fields That Quietly Cost You Orders
Some fields cost far more than merchants expect, mostly because their cost is invisible. Nobody emails to say they left because of a phone number box.
- Phone number: Often collected "for delivery issues" and rarely used. If your carrier genuinely requires it, mark it required and explain why in one short line. Otherwise drop it.
- Company name: Useless for the vast majority of consumer stores. It is one more box in the shopper's path.
- Account password: The single most damaging optional field. It converts a purchase into a signup.
- Address line 2: Harmless if optional, but it should never be required.
- Marketing consent checkbox: Fine as an unticked option, damaging as a gate.
- Survey questions: "How did you hear about us" belongs on the thank-you page, not before payment.
The account password deserves a paragraph on its own, because it is the field that costs OpoShop merchants the most orders. A shopper who wants a t-shirt is being asked to create and remember a credential. That is a different kind of commitment, and it arrives at the moment they are most likely to reconsider. Guest checkout is not a compromise, it is the default that works.
If you want accounts, offer one after the order is confirmed, when the shopper has a reason to want it. At that point you already have their email and their address, so creating the account is a single click rather than a form.
Why Every Extra Field Compounds
Every field you add costs more than the seconds it takes to fill, because each one is a small decision and decisions accumulate.
A shopper filling in a checkout on an OpoShop store is not just typing. They are evaluating. Each field prompts a tiny internal question. Do I have to give this? Why do they want it? What will they do with it? Most of those questions resolve in a fraction of a second, but they are not free.
There is also a physical cost on mobile. Each field is a tap, a keyboard change, and possibly a scroll. Eight fields on a phone is a genuinely different experience from eight fields on a desktop with a saved address book.
The compounding shows up in the numbers. If each unnecessary field costs you a small fraction of shoppers, four of them stacked together stops being small. A store on OpoShop that trims a checkout from twelve fields to seven has not made a cosmetic change.
How To Audit Your Own Checkout
The best audit is to go through your checkout field by field and force each one to justify itself.
1. List every field
Open your checkout and write down every input a shopper has to interact with, including checkboxes and dropdowns. Most merchants are surprised by the length of the list.
Do this on a phone rather than a desktop. A field that reads as one line on a wide screen can be a full scroll on a narrow one, and the list you produce should reflect the device most of your buyers actually use.
2. Ask what breaks without it
For each field, ask a specific question: if this were empty, could I still charge the card and ship the parcel? If the answer is yes, the field is optional by definition.
3. Ask when you last used the data
Phone numbers are the classic example. Many stores have collected phone numbers for years and never once called a customer. Data you do not use is friction you are paying for.
4. Move what survives to after the order
Anything you genuinely want but do not strictly need can be asked for on the confirmation page or in the follow-up email. The order is already placed, so a question there costs you nothing.
What About Address Autocomplete
Address autocomplete is the rare addition that reduces effort rather than adding it, which is why it is worth having.
A standard address is five or six separate fields. Autocomplete collapses that into typing a few characters and picking a suggestion. On mobile that is the difference between a minute of thumb-typing and about four seconds.
It also improves your data quality, which matters more than most OpoShop merchants expect. Addresses entered by hand contain typos, missing unit numbers, and mismatched postcodes. Addresses picked from a validated list mostly do not. Fewer bad addresses means fewer failed deliveries, fewer support emails, and fewer reshipping costs.
For OpoShop merchants selling physical products, the delivery-failure saving alone often justifies it, before you count the conversion benefit.
The one caveat is to always leave the fields editable. Autocomplete should be a shortcut, not a cage. Some addresses are unusual and the shopper needs to be able to override the suggestion.
It is also worth checking how the suggestions behave for the countries you actually ship to. Address formats vary more than most merchants realise, and a lookup tuned for one country can produce confident nonsense in another. If you sell internationally, try a few real addresses from your biggest non-domestic market before you trust it.
If you keep an optional field, label it as optional rather than leaving the shopper to guess.
This sounds pedantic and it changes behaviour. An unlabelled field reads as required by default, so a shopper who has no company name, or who does not want to give a phone number, stops and wonders whether they can proceed. Some of them try leaving it blank and hitting continue, some of them invent something, and some of them close the tab.
The convention that works is to mark optional fields explicitly and leave required ones unmarked, since required is the assumption anyway. It is a small piece of clarity that costs one word per field and removes a genuine moment of hesitation.
Order and Grouping Matter As Much As Count
How you arrange the remaining fields matters nearly as much as how many there are.
That ordering is not arbitrary. It moves from lowest commitment to highest, which means a shopper who is going to abandon does it early, before they have invested effort. It also means you captured their email first, which gives you a way to follow up.
Comparing Common Checkout Approaches
Different field strategies suit different businesses, and the trade-offs are worth being explicit about.
| Approach | Fields required | Conversion effect | Best for |
|---|---|---|---|
| Guest checkout, minimal fields | 4 groups | Highest completion | Almost every consumer store |
| Guest checkout plus optional extras | 4 required, some optional | Slightly lower, more data | Stores that genuinely use the data |
| Forced account creation | 5 groups including password | Lowest completion | Subscription or wholesale, where an account is the product |
The middle row is where most stores should sit, provided the optional fields are genuinely optional and clearly marked. The bottom row is only defensible when an account is intrinsic to what you sell.
Best answer: A checkout needs an email, a delivery address, a shipping choice, and payment. Everything else should be optional, moved to after the order, or removed. If a field would not stop you charging the card or shipping the parcel, it does not belong before the pay button.
What To Do With The Data You Stopped Collecting
Removing fields does not mean losing the information. It means asking for it at a better moment.
The confirmation page is prime real estate that most stores waste. The shopper has just paid, they are pleased, and they are not going anywhere. That is the ideal place for "how did you hear about us", a newsletter opt-in, or an invitation to create an account with one click.
Your post-purchase email is the second-best place. It arrives when the shopper is thinking about the order anyway, and a single question in a friendly email gets better response rates than a required field in a checkout.
The difference is that neither of those costs you the sale. A survey question before payment risks the order. The same question after payment risks nothing at all. For an OpoShop store, that reframing usually means you end up with more data, not less, because you are asking people who already converted.
FAQs
Is a phone number required at checkout?
Only if your carrier genuinely requires it for delivery. Most consumer stores collect phone numbers and never use them, which makes it pure friction.
Should I offer guest checkout?
Yes, for almost every consumer store. Forcing account creation before payment is one of the most reliable ways to lose an order that was otherwise won.
Does address autocomplete really help?
Yes, on two fronts. It cuts the typing dramatically on mobile, and it reduces bad addresses, which means fewer failed deliveries and less support work.
How many fields is too many?
There is no magic number, but if a shopper on a phone has to scroll through more than about eight inputs before reaching payment, it is worth auditing what each one is for.
Where should I put optional fields?
After the order, ideally. The confirmation page and the follow-up email are both good places to ask questions that would have cost you conversion in the checkout itself.
Can I change my checkout fields without a developer?
On OpoShop most checkout behaviour can be adjusted through an app rather than by editing theme files, so this is usually a configuration task.
The shortest checkout that still lets you charge the card and ship the parcel is almost always the one that makes the most money.
