Cart drawer or cart page: which converts better?

Every store has to decide what an add to cart does. It can leave the shopper exactly where they were with a small confirmation, slide a panel over the page, or navigate them away to a dedicated page. Each interrupts the browsing session by a different amount.

That is the trade. Less interruption keeps people shopping and adding, which suits catalogues where baskets are naturally multi-item. More interruption forces a review, which suits catalogues where a shopper needs to check what they have chosen before committing.

So start by looking at your own baskets. If most orders contain one item, the browsing flow you are protecting barely exists, and a page that lets the shopper confirm and move to payment costs nothing. If most orders contain four or five, every interruption on the way to the fifth is expensive.

The second input is basket value. A shopper spending a large amount wants to see the total, the delivery cost and the arrival date together before continuing, and a narrow panel is a cramped place to present all of that.

It preserves context. The shopper stays on the collection or product page, sees the item was added, and can continue without a page load or a back navigation. On a phone that saves a meaningful amount of time and effort.

It suits impulse and repeat categories: consumables, accessories, food and drink, anything where adding another item is normal and reviewing the basket every time would be tedious.

It gives a natural place for a free delivery progress message, which is one of the few basket interventions that reliably changes behaviour, because it appears at the moment the shopper can act on it.

What it does badly is complexity. A discount field, a shipping estimator, a gift message, quantity controls, a note field and two upsells will not fit in a narrow panel without becoming cramped, and cramped is where people stop reading. Keep a drawer to the essentials and let anything more move to a page.

It gives room to answer the last questions before payment. Delivery cost and estimated date, the discount field where people expect it, quantity changes with clear pricing, and a summary that adds up in a way the shopper can check.

It suits considered and higher-value purchases, mixed baskets where some items ship differently, and stores where a meaningful share of orders use a code. A discount field hidden inside a drawer or only visible at checkout sends shoppers away to search for a code, and some of them do not come back.

It also gives space for a genuine cross-sell rather than a squeezed one. A recommendation with an image, a price and a reason has a chance of being taken; the same recommendation compressed into a strip does not.

And it is a page, which means it can be measured, tested and linked to. That matters more than it sounds: a page has an address, appears in analytics as a step, and can be the target of an abandoned cart email.

Look at three numbers before choosing. Items per order, which tells you whether the browsing flow is worth protecting. The share of orders using a discount code, which tells you how important the code field is. And the mobile share of your traffic, since the constraint is tightest there.

Then measure the step rather than the whole funnel. The rate at which an add to cart becomes a started checkout is the number this decision moves, and it is much more sensitive than site-wide conversion rate.

Many stores end up with both: a drawer for the immediate confirmation with a clear route to a full cart page for anyone who wants to review. That is often the practical answer, and it removes the need to choose in the abstract.

Whatever you run, make sure express payment options are present and prominent, since a large share of shoppers will use them and skip the debate entirely. And check the whole thing on a real phone, because a drawer that covers the screen and hides its own checkout button is a common and costly implementation error.