Reviewed October 25, 2026

Shopify Checkout Settings: The Configuration Pass Most Stores Skip

Checkout settings decide what you ask, what you require, and what customers can fix later. Marketing consent, address options, order status, and the fields worth requiring.

The settings page nobody revisits

Checkout is configured once at setup, usually in a hurry to launch, and then treated as fixed while everything around it evolves. Meanwhile the settings page holds decisions with daily consequences: whether email or phone is the primary contact, which address fields are optional, whether customers can check out as guests, and what the order status page offers after the sale. Stores spend heavily to win the click and then let a default settings page run the transaction.

A deliberate configuration pass takes under an hour and pays out on every order afterward. Work through it with two questions in hand for each setting: what does this cost the customer in effort, and what does it earn the business in data, accuracy, or recovery options. Any setting that costs effort and earns nothing is a launch default you are still paying for.

Contact and account choices

Decide whether checkout identifies customers by email or phone number, based on how you actually communicate afterward. Email suits most stores: receipts, tracking, and marketing all flow through it. Phone first checkout serves markets where messaging apps carry commerce, but it raises the cost of every typo. Whichever you choose, enable the order status and account conveniences that come with it, so customers can find their orders without a support ticket.

Guest checkout should stay on for almost every store. Forcing account creation before purchase is a conversion tax paid to a database preference. Offer the account after the sale, on the thank you page and in the order emails, when the customer has a reason to want one: tracking, reordering, and managing subscriptions. Accounts earned that way are real. Accounts extorted at checkout are abandoned carts.

Address, fields, and error proofing

Set company and address line two to optional unless your shipping genuinely needs them, and align required fields with what your carriers and tax setup require, no more. Every required field is a small toll. Some are worth collecting. Most stores inherit tolls they never chose, like mandatory phone numbers that exist because a shipping app once wanted them.

Turn on the address validation and autocomplete features your plan offers. A meaningful share of failed deliveries are checkout typos that a suggestion list would have caught, and the cost of a reship dwarfs the cost of the feature. Review the checkout language and error text while you are in there, since the default strings were written for every store and therefore for none of them.

Consent, tips, and the post purchase page

Marketing consent wording and its default state are regulated differently across markets, so configure them per market where the platform allows, and keep the unchecked default where the law wants an active opt in. This is a compliance setting wearing a growth setting costume, and getting it backwards is expensive in the wrong direction.

If your business model fits tipping, such as local delivery or services, enable it deliberately with sensible preset amounts rather than discovering the feature during a redesign. Finally, treat the order status page as a configured asset: add the tracking visibility, the help information, and the one next step you want a buyer to take. It is the most visited post purchase page you own, and most stores leave it saying almost nothing.

Related reading

If this topic is useful, these earlier guides go deeper on connected questions: Shopify Staff Accounts and Permissions: A Setup Guide That Prevents Lockouts, Shopify Payments Setup: Steps to Complete Before Your First Sale, and Shopify Tax Setup: A Plain Checklist for New Stores.

Frequently asked questions

Should I require a phone number at checkout?

Only if a carrier or delivery workflow genuinely needs it for the orders you ship. Required phone fields cost conversions and collect typos. If you need it for delivery coordination in specific markets, require it there rather than globally, and say why on the form.

Is guest checkout really better than required accounts?

For conversion, consistently yes. Account creation is friction placed at the moment of maximum hesitation. Offer accounts after purchase and through order tracking, where the value to the customer is obvious, and your account numbers will grow without taxing the checkout that feeds them.

What checkout setting causes the most failed deliveries?

Missing or wrong address data, which is why autocomplete and validation settings punch above their weight. The second is an apartment or unit number squeezed into an optional field customers skip. Making the second address line clearly labeled for units, while keeping it optional, recovers many of those packages.

How often should checkout settings be reviewed?

Whenever you change markets, carriers, fulfillment, or product mix, and at least twice a year otherwise. Checkout settings interact with everything operational. A change in your warehouse or your returns policy usually has a checkout setting that should have changed with it.