Skip to main content

Test your shop before sending customers or running ads

Check product choices, order totals, stock, payments, delivery, and recovery from errors. Record what worked before opening the shop to customers.

Written and edited by
DokanNao Editorial Team
Reading time
2 minutes
Published: Updated:

Key takeaways

  • Test the whole customer-to-merchant record, not only visible pages.
  • Include mobile, keyboard, invalid, pending, duplicate, failure, recovery, and provider states.
  • Keep sandbox, local, production, provider, and real-order evidence as separate checks before going live.
In this guide
  1. Make a list of what to test
  2. Check how customers find and view products
  3. Check the cart, checkout, and saved order
  4. Check payment and delivery updates
  5. Check accessibility, search, and analytics
  6. Write down the results before going live

A good-looking homepage doesn’t prove the order process works. Check that customer choices, totals, payments, stock, and dashboard records all agree.

Make a list of what to test

Create test products and accounts allowed by your environment. List browser, viewport, language, product, variant, stock, coupon, delivery area, payment option, expected result, and cleanup owner. Never use a real customer or charge without authorization.

Check how customers find and view products

From home, search, category, product, campaign, and direct URL, verify title, price, images, variant, stock, policy, canonical address, and missing-page behavior. Check long Bangla text and narrow screens.

Check the cart, checkout, and saved order

Test add, update, remove, invalid quantity, unavailable variant, coupon success and failure, delivery charge, address validation, double submit, back navigation, server error, confirmation, notification, order line, totals, and stock movement. Cancel and verify restoration rules.

Check payment and delivery updates

For every payment method, distinguish initialized, pending, failed, confirmed, refunded, and duplicated callback. Provider or server evidence must control paid state. Test courier request, reference, status, return, COD collection, and checking payment and order records only in authorized environments.

Check accessibility, search, and analytics

Use keyboard, visible focus, labels, announcements, zoom, reduced motion, slow network, missing image, overflow, and contrast checks. Verify indexable HTML, one H1, metadata, canonical, hreflang, schema, sitemap, robots, 404, and consent-gated analytics with no raw form data.

Write down the results before going live

Record URL, timestamp, environment, input, expected result, actual result, logs or screenshots without secrets, and owner. Local and sandbox passes do not prove production approval or live provider behavior. Go live only when the required checks have passed and someone is responsible for restoring the previous setup if needed.