Low conversion rate ecommerce: check the total

A shopper compares what they will pay with what they expected from the product page, and the store has to match both numbers. Shipping that appears only at checkout, a tax line that jumps once an address is entered, a handling fee, and a delivery date that moves can each add enough to make a shopper stop. The shopper does not argue with the price in the abstract. They react to the surprise. Trust works the same way: a missing returns policy, no contact address and an unfamiliar payment option make a stranger hesitate at the exact moment they are asked for a card.

• Shipping cost: is it visible on the product page or the cart, before the address form appears?
• Tax line: does the total change after an address is entered, and is the change explained?
• Returns and contact: are they one click from the cart, with a real address or phone number?
• Payment options: do the ones shoppers expect appear before the final step, not after it?
• Account wall: can a shopper buy as a guest, or does checkout stop at a sign-up screen?

Write down the amount a shopper sees at the product page, at the cart, after the address, after the shipping choice and at the payment step. Stores often show a different number at each one, and the shopper has to notice every change. The wrong check is to compare the price on the product page with the price in the catalog, which usually match. The right check is to compare the first number with the last one, for the same item and the same address. Any gap that the shopper did not see coming is a reason to leave, and it usually sits at the address step, where the store finally asks where the parcel goes.

Stores often spend their effort on a clean homepage and leave the trust questions to the last step. A stranger at the card field wants to know three things quickly: whether the store can be contacted, what happens if the item is wrong, and whether the payment options are ones they recognize. A returns link buried in the footer answers none of them at the right moment. Put the returns policy and a contact address in the cart, and show the payment options before the card form. Decorative badges rarely answer any of the three, so do not count them as a replacement.

A checkout with a required account, a long address form, a delivery date picker and a newsletter opt-in in the middle asks a shopper to work for a lamp. The wrong version treats each field as harmless. The right version asks only for what delivery needs, lets the shopper continue as a guest, and moves the account offer to the confirmation page, after the order exists. Count the fields between the cart and the payment step, and cut any field that the order does not need to ship. Each one you keep should have an obvious reason a stranger can see.

Pick one product and walk it from the search result to the payment step, on a phone and on a laptop, with a delivery address that is not your own. Write down every number and every question that comes up. This is slow, but it shows the same thing a simulated shopper shows: the step where the total changed and the step where trust ran out. A simulated shopper takes the same walk when you start a run and reports each stop with a screenshot, so you can compare what your own walk found with what the run found.

Shipping rules, tax settings and carrier choices change more often than the product page does. A new free shipping threshold or a changed duty line can move the surprise from the product page to the address step, without any visible edit. Run the same purchase path after each change to shipping, tax or payment settings, and compare the first total with the last one.