Review products, checkout, payment outcomes, delivery and order handling before launch. A practical ecommerce checklist for accepting your new store.
An online store is ready to launch when a customer can choose a product, understand the final terms and place an order that your team can fulfil correctly. Your review also needs to cover a declined payment, an unfinished purchase and a repeat attempt.
Prepare acceptance scenarios with expected results. “Payments connected” leaves too much undefined. “The customer pays, the manager sees a confirmed payment and can begin picking the order” describes something the team can demonstrate.
Prepare products people can confidently choose
Start with the information customers need to make a decision. A product page needs a clear name, photographs, a price with its currency and current availability. For variants, check the relationship between the selected size or colour, its price and its stock.
Consider a hypothetical ceramics store. Its mugs come in different capacities and colours. A shopper needs to see the exact variant added to the basket, and the manager needs the same variant in the order. A collection photograph cannot explain that selection by itself.
Before filling the entire catalogue, review a few representative products:
- a standard item that is in stock;
- an item with multiple variants;
- an unavailable item;
- a product with a long name or an extra specification.
This exposes data structure problems before your team enters every product. Agree on who updates prices, stock and images after launch. Ask that person to make a real content change during the handover.
Follow the journey from category to basket
Check that category names match how customers look for products. Filters should support selection and make their results understandable. When a combination returns no products, the shopper should be able to change it easily.
In the basket, change quantities, remove an item, return to the catalogue and add a different variant. Check the total after each action. If a promotion is included, document which products qualify and when the discount is applied.
Complete the whole journey on a phone. A good product photograph on a desktop screen tells you little about selecting a variant or correcting a delivery address on mobile.
Explain the purchase terms before confirmation
Before the final confirmation, shoppers need to understand the items, currency, available payment methods and how delivery is priced. If a manager confirms the exact delivery cost later, explain that before the order is placed.
Try different addresses and fulfilment options. Collection and home delivery may require different fields. Changing a destination or delivery method should update the summary and any affected charges.
Prepare seller contact details, return information and the policies your store needs as part of the content scope. They should describe how your business will actually handle the order.
Review every payment outcome
A payment can need further authentication or remain in processing. Stripe, for example, distinguishes successful, incomplete and pending payments. Returning to a confirmation page alone is insufficient evidence for dispatching goods. Stripe’s payment status documentation.
Ask your team to demonstrate these scenarios for your chosen payment provider:
- Successful payment. The amount and currency match the order, and the customer receives the correct confirmation.
- Declined payment. The website explains the next step and leaves the order in an appropriate unpaid state.
- Abandoned payment. The shopper closes the payment screen, and the manager can identify the unfinished purchase correctly.
- Pending confirmation. The interface shows the current state and explains how to check the outcome.
- Another payment attempt. Retrying does not create extra paid orders or duplicate fulfilment work.
- A double click or page refresh. Repeating an interface action does not cause another charge.
Make these checks part of acceptance. Agree which scenarios will be demonstrated in the provider’s test environment and which need a controlled review once the live account is connected.
Check the stock rule alongside payment. For the last available item, define what happens while a shopper is paying and after the attempt expires. The right reservation policy depends on the products and payment methods you use, so it needs an explicit decision.
Hand the order to the person fulfilling it
Take one order through the complete operational process. A manager should be able to find its items, variants, customer details, delivery method and current payment status.
Check who receives notifications and what happens if a message is not delivered. The order should remain available in your management system. An email is useful as a notification; the dispatch decision needs reliable order and payment information.
Work through cancellation, stock changes and your agreed returns process too. Identify which actions a manager can perform independently and which require help from the development team or payment provider.
Review public pages and purchase reporting
Customers should be able to reach categories and products through ordinary links. Check page titles, descriptions, mobile layouts and language switching if the store is bilingual.
Product structured data should reflect the prices and availability customers can see. Google uses this information for product search experiences, although a particular display is not guaranteed. Google’s Product structured data guidance.
Compare analytics with an actual order. Agree when reporting records an order and when it records a successful payment. Refreshing the confirmation page should not add another purchase to your reports.
Frequently asked questions
Can we launch with a small catalogue?
Yes. A limited initial range can support a complete buying journey. Your checks still need to include every product and variant type that you intend to sell.
Is one test purchase enough?
One successful purchase covers one route. Add declined, pending and retry scenarios, along with different delivery options and the behaviour of the last available unit.
What should we provide before requesting an estimate?
Share a sample catalogue, product types, selling countries, currencies, payment methods, delivery options and the way your team handles orders. These define the required features and integrations.
Plan your store launch
UAVA designs and builds online stores from catalogue to checkout. Show us your product range and explain how your team will process purchases. We can define the required journeys and prepare an estimate. Discuss your online store.