An online store is ready when customers can place an order and your team can fulfil, support and refund it reliably. An attractive product grid is only the beginning. Before launch, walk through the full journey using realistic orders and clearly separated test data.
Make product information dependable
Check names, variants, prices, stock behaviour, images and delivery information. Explain what is included and what is not. A customer should not have to guess whether a photograph shows an optional accessory or the actual product they are buying.
Assign responsibility for inventory updates. Decide what happens when two people order the last item, a variant is unavailable, or a supplier changes lead times. Do not promise delivery dates that your fulfilment process cannot support.
Test more than a successful checkout
Use your payment provider’s approved test environment first. Test a successful payment, a declined payment, an interrupted checkout and a customer returning after abandoning the payment screen. An unpaid order must not look paid simply because the browser reached a thank-you page.
- Confirm the server records the provider’s payment result appropriately.
- Check duplicate notifications do not create duplicate orders or fulfilment actions.
- Confirm stock and totals remain correct after retries.
- Check customers receive clear messages without internal technical details.
Outsourcing payment processing does not remove every merchant responsibility. PCI SSC explains that merchants still need to ensure third-party account-data protection. Confirm your obligations with your provider and acquiring bank for your specific checkout arrangement; avoid collecting card details in ordinary website forms.
Prepare delivery, returns and support
Show shipping charges and relevant restrictions before the final commitment. Check taxes and consumer terms with the appropriate local advisers. Your store settings need to match the regions and products you actually serve.
Run a fulfilment rehearsal with the people who will handle orders. Can they find the order, confirm stock, prepare delivery, communicate a delay and process a return? Test refund reporting as well as the customer-facing message. Keep test orders out of operational and financial reporting.
Verify messages and ownership
| Journey | Evidence to collect |
|---|---|
| Order confirmation | The right recipient receives the correct items and totals |
| Payment failure | No paid-order status or shipment is created |
| Refund | Provider result, order status and customer communication agree |
| Support enquiry | A responsible team member can see and answer it |
Use a real controlled mailbox for delivery checks. A green form message does not prove an email arrived. Agree on a process for failed notifications, and ensure order records remain available even when email delivery fails.
Keep the launch reversible
Confirm backups and practise restoring a safe copy before accepting real orders. Limit account permissions, protect administration access and document who can change payment or fulfilment settings. Schedule a small launch window when someone can monitor problems and pause sales if necessary.
Check mobile checkout, keyboard navigation, visible form labels and error messages. Compress product imagery without hiding useful product detail. Review the actual shopping journey instead of relying on a homepage performance score.
Keep a short go/no-go checklist with named owners and recorded results. Our websites and ecommerce service can help with the build and launch planning; share your store requirements to discuss the scope.
Primary reference
PCI SSC: responsibilities when payment processing is outsourced. The remaining checklist is practical project guidance and should be adapted to your store.
