Ecommerce Checkout Process: 6 Steps, Examples and Best Practices

An e-commerce checkout process is the sequence of steps that turns a shopper’s cart into a completed order. It usually covers cart review, customer information, shipping, payment, order review, and confirmation.

Simple enough from the customer’s perspective. Under the hood, checkout does considerably more work.

A modern checkout can coordinate product and cart data, prices and discounts, inventory, taxes, shipping methods, customer details, payment providers, and finally order creation. That is why checkout shouldn't be treated as merely “the page where customers enter their card.” Payment is one part of checkout. Checkout is the orchestration layer that gets a valid order from intent to completion.

That distinction matters because checkout is also where a large amount of purchase intent disappears. Baymard’s 2026 data puts the average documented cart abandonment rate at 70.22%. Some abandonment is unavoidable—people compare products or simply are not ready to buy—but a meaningful portion comes from problems merchants can actually fix.

The ecommerce checkout process starts when a customer decides to purchase the products in their cart, typically by selecting Checkout, Proceed to checkout, or Buy now. It ends when the transaction has been accepted and the customer receives confirmation that the order exists.

A typical ecommerce checkout follows six stages:

These stages do not have to appear on six separate pages. A one-page checkout may present several at once, while an accelerated checkout can prefill or bypass some for a returning customer. What matters is that the system still has to resolve the underlying information before it can create an order.

1. Cart Review

The cart gives customers one last opportunity to verify what they are buying before committing to checkout.

They should be able to see products, variants, quantities, prices, discounts, and an understandable order subtotal. Depending on the business, this may also include subscription terms, configuration choices, booking dates, or other product-specific information.

Customers should also be able to change quantities or remove products without restarting the process.

The important principle here is predictability. If a discount disappears or a meaningful cost suddenly appears three screens later, the checkout itself has created friction.

2. Customer Information

The store collects the minimum customer data required to process and communicate about the order. Usually, that means an email address and, depending on the order, a name and phone number.

This is also where many stores create unnecessary friction by treating account creation as part of the purchase.

For first-time customers, guest checkout should normally be the easiest path. You can still offer an account, but buying a product shouldn't depend on creating a password unless the business model genuinely requires authentication.

For returning customers, saved profiles and autofill can make this step almost disappear.

3. Shipping Details

For physical products, the checkout needs a delivery address and a shipping or fulfillment method.

Customers should see their available options together with useful information such as expected delivery date and price. Asking someone to choose between “standard” and “express” without showing what those labels mean in practice creates another decision the shopper has to resolve.

This stage changes significantly by commerce model. A digital product may not need shipping at all. Click-and-collect needs pickup locations. B2B orders may use negotiated logistics rules. Bookable products may need time slots rather than delivery dates.

The checkout flow should adapt to the product being sold rather than forcing every transaction through the same generic form.

4. Payment Information

The customer chooses a payment method and authorizes the transaction.

That may involve cards, digital wallets, local payment methods, buy-now-pay-later providers, invoices, or business-specific payment arrangements. A payment gateway then handles authorization with the relevant payment infrastructure.

This is one reason checkout and payment should not be treated as synonyms. Stripe, Adyen, Klarna, PayPal, Vipps, or any other payment gateway provider may handle payment, while the commerce system remains responsible for the cart and order surrounding that transaction.

Crystallize, for example, is payment-agnostic. You can choose payment providers based on market, customer preference, or business requirements rather than making the commerce backend dictate the gateway.

5. Order Review

Before the final commitment, customers should be able to verify exactly what they are about to buy and what it will cost.

A useful order review shows products, quantities, delivery details, discounts, taxes, shipping costs, payment method, and the final total. Important information should also be editable without forcing the shopper to restart checkout.

This stage is especially valuable for larger, configurable, subscription, and B2B orders where the consequences of an incorrect order are higher.

The rule is simple: nothing important should become visible for the first time after the customer clicks the final purchase button.

6. Order Confirmation

A successful payment isn't the end of the customer experience.

The store should clearly confirm that the order was created and provide an order number or other reference, a purchase summary, and information about what happens next. The same information is commonly sent by email.

Behind the interface, checkout also hands responsibility to downstream processes such as fulfillment, inventory, shipping, invoicing, and customer communication.

A failure here can be particularly ugly: the customer gets charged but sees an error page, or the interface reports success while no valid order reaches the backend. Test checkout as an end-to-end transaction, not just a collection of functioning forms.

There is no universally correct number of checkout pages.

One-page checkout works well when the purchase is simple, and the required information is limited. A typical DTC order with one shipping address, a few fulfillment choices, and a familiar payment method is a natural candidate.

Multi-step checkout can work better when the transaction involves more decisions: B2B purchasing, complex delivery, multiple addresses, configurable products, subscriptions, or other situations where dumping every option onto one page makes the experience harder, not easier.

This is where an interesting checkout misconception appears: reducing pages is not the same as reducing friction.

Baymard’s checkout research found that the average checkout contains around five steps, but its usability testing also shows that the number of form fields customers must consider has more impact on perceived effort than the number of steps itself.

The better question is therefore not “Can we turn our four-step checkout into one page?” It is “What work are we unnecessarily asking the customer to do?”

People abandon carts for plenty of reasons that checkout design cannot solve. Someone may be comparison shopping, saving a product for later, or simply not ready to purchase.

But the avoidable reasons are much more interesting.

Baymard’s 2026 research found that, excluding shoppers who were simply browsing, 40% cited high additional costs such as shipping, taxes, and fees. Another 18% abandoned because a site wanted them to create an account, while 17% said the checkout was too long or complicated.

That puts a useful dent in one common optimization habit. If your checkout is losing customers, changing the color of the purchase button probably belongs fairly far down the debugging list.

Start with unexpected costs, forced registration, unnecessary form fields, unclear delivery options, payment limitations, and technical failures.

Offer Guest Checkout

Do not turn customer acquisition into an obstacle to the transaction.

Let shoppers complete their purchase without creating an account, then give them the option to create one afterward. You already have much of the information required, and the customer has now actually completed the action you care about.

Accounts make sense when they provide genuine value. Mandatory accounts created solely because your system prefers authenticated users mostly add friction.

Ask for Fewer Form Fields

Every field creates work, and some create questions: Why do you need my phone number? Is company name required? Why am I entering a billing address when it matches shipping?

Only ask for information required to complete the transaction or satisfy a clear business requirement. Use address autocomplete and sensible defaults where possible, reuse existing information, and hide conditional fields until they are relevant.

Do not optimize for the fewest screens. Optimize for the least unnecessary effort.

Show the Total Cost Early

Unexpected cost remains one of the strongest abandonment triggers.

Show shipping charges, taxes, fees, discounts, and other predictable costs as early as you reasonably can. If the exact number depends on the customer’s location or shipping choice, make that dependency clear instead of presenting an artificially low subtotal that jumps at the final step.

A transparent checkout may occasionally show a higher number sooner. That is still better than surprising customers when their wallet is already out.

Consider a straightforward DTC order. A shopper adds sneakers to the cart, checks the size and quantity, enters an email and address, chooses standard delivery, pays with Apple Pay, reviews the total, and receives an order number. That entire sequence could comfortably live in a single-page checkout.

Now consider a B2B purchase. Pricing may depend on the customer account. The order could require a PO number, company information, negotiated shipping, payment by invoice, and approval before fulfillment. Trying to make that transaction behave exactly like the sneaker checkout would not make it simpler—it would hide necessary complexity.

The best checkout is therefore not necessarily the shortest checkout. It is the one that asks for the minimum information required for that specific transaction, in an order the customer understands.

Our SUPERFAST SHOP Crystallize demo examples also show industry store examples with completed checkout processes. This means you can see subsription, product, booking, etc. examples for each industry's needs.

In headless and composable commerce, you don't have to deliver the checkout interface and commerce backend as one tightly coupled application.

With Crystallize, for example, you can retrieve product information through the Discovery API, while the Shop API handles cart and checkout operations. A typical implementation fetches products, adds them to a cart, maintains the required cart context, places the cart, and turns that placed cart into an order.

For the implementation details, see Building a Modern Checkout Flow with Crystallize APIs and the Shop API Checkout Flow Tutorial.

This separation gives developers more control over the storefront and checkout experience, but it also makes testing important. A checkout touches several systems, and each one can appear healthy while the complete transaction still fails.

Our End-to-End Testing Checkout Flow guide walks through testing the full journey—from adding an item to the basket through payment, order confirmation, API verification, and cleanup.

The architecture may be composable. The customer journey cannot feel that way.

The customer should experience checkout as a simple path from “I want this” to “order confirmed.”

The architecture behind that path can be anything but simple. Pricing, promotions, inventory, customer data, shipping, tax, payments, and order creation all need to agree on what is being purchased and what should happen next.

That is why good checkout design is not just a CRO exercise. It combines UX and commerce architecture.

Remove unnecessary work for the customer. Surface costs before they become surprises. Let the underlying systems handle the complexity—and test the complete flow so they actually do.

What is an ecommerce checkout process?

An ecommerce checkout process is the sequence of actions required to turn a shopping cart into a completed order. It normally includes cart review, customer details, shipping, payment, final order review, and confirmation.

How many steps should an ecommerce checkout have?

There is no ideal number for every store. A simple purchase may work well as a one-page checkout, while complex B2B, configurable, or subscription transactions may benefit from several steps. Reducing unnecessary fields and decisions generally matters more than minimizing the raw number of pages.

What causes customers to abandon checkout?

Common avoidable causes include unexpected shipping or other costs, forced account creation, an unnecessarily complicated checkout, limited payment or delivery options, lack of trust, and technical errors. Improving checkout means removing these points of uncertainty and effort, not just shortening the flow visually.