TaintlessTaintless
TaintlessTaintless

Storefront QA Checklist

Test the storefront like a first-time customer before launch, campaigns, and major catalog changes.

Use this checklist when the store is close to launch or when a published store has changed in a meaningful way.

The goal is not to click every pixel. The goal is to catch anything that would make a real buyer hesitate, get lost, or fail to reach checkout.

Media placeholder

QA pass recording

Recommended asset: a short screen recording of a complete desktop and mobile QA pass.

Before You Start

Prepare:

  1. A fresh browser session.
  2. A mobile viewport.
  3. A known product.
  4. A product with a discount, if one exists.
  5. A product that requires Tebex authentication, if one exists.
  6. A support link or Discord invite.
  7. The intended live domain.

Do not test only while signed in as the merchant. A customer sees the store with less context than you do.

First Impression

Open the home page and answer these questions without using internal knowledge:

QuestionPass condition
What is sold here?The hero and first visible section make it clear
Where should I click next?Primary CTA is obvious
Can I trust this store?Support, Discord, policies, or proof signals are visible
Does it feel finished?No placeholder copy, broken images, or empty sections
Does it work on mobile?Header, hero, grid, and CTA fit without awkward clipping

Click:

  1. Logo
  2. Home
  3. Products
  4. Each visible category link
  5. Subscriptions, if shown
  6. Support, if shown
  7. Cart

Expected result: every visible header item opens a useful page. If a page is not ready, remove it from the header or hide it in Pages.

Catalog

On Products:

  1. Search for a known product.
  2. Search for a term that should return no results.
  3. Change category.
  4. Change sort.
  5. Open a product card.
  6. Return to the catalog.
  7. Check spacing on mobile.

The catalog should feel useful even when search returns nothing. Empty states should explain what happened without blaming the customer.

Product Detail

For key products, check:

AreaPass condition
TitleClear and customer-facing
ImageLoads quickly and represents the product
PriceEasy to read
CTAVisible without hunting
DescriptionExplains what is included
RequirementsVisible before purchase
Tags and badgesHelpful, not decorative
Support pathCustomer knows where to ask questions

Long product names and missing images are worth testing. They often reveal layout problems before customers do.

Cart

Test:

  1. Add one product.
  2. Add the same product again.
  3. Change quantity.
  4. Remove the product.
  5. Add a different product.
  6. Apply a coupon, if available.
  7. Remove the coupon.
  8. Continue to checkout.

The checkout button should be easy to find on desktop and mobile. The customer should never wonder whether the cart updated.

Authentication

If the store sells products that require Tebex login:

  1. Open the product while signed out.
  2. Try to add it.
  3. Follow the sign-in path.
  4. Return to the store.
  5. Add the product again.
  6. Continue to checkout.

If Discord verification is required, test that path separately. Discord issues are more damaging when they appear after the customer has already decided to buy.

Checkout Handoff

Proceed to checkout and confirm:

  1. Tebex checkout opens.
  2. Basket items are correct.
  3. Final currency and total make sense.
  4. Discounts or gift cards appear as expected.
  5. Cancel or return path brings the customer back to a useful page.

Do not judge final payment totals from the storefront alone. Tebex checkout is the final source of truth.

Support and After Purchase

Check:

  1. Support page opens.
  2. Discord invite works.
  3. Email or ticket links work.
  4. Footer support links work.
  5. Thank You page explains the next step.
  6. Refund or policy links point to the correct place.

Support is part of conversion. Customers buy more confidently when help is easy to find.

Domain and Publish State

Before sharing the store:

  1. Open the default taintless.store subdomain.
  2. Open the custom domain, if connected.
  3. Confirm the store is published.
  4. Confirm the URL does not include preview parameters.
  5. Open the store in a private browser window.
  6. Check that the correct store loads.

Mobile Pass

On mobile:

  1. Open the menu.
  2. Close the menu.
  3. Visit Products.
  4. Open filters or category controls.
  5. Open a product.
  6. Add to cart.
  7. Review cart.
  8. Continue to checkout.

Mobile is often the real storefront. Treat it as the primary pass, not a smaller version of desktop QA.

Red Flags

Fix these before launch:

  • Header link opens an unfinished page
  • Product card has no image and no useful fallback
  • Price is hard to read
  • Add-to-cart feedback is unclear
  • Cart button is below the fold on mobile
  • Support link is broken
  • Checkout opens with the wrong item
  • Store title or social preview is still generic
  • Custom domain opens the wrong store

Final Pass

The store is ready when a new customer can:

  1. Understand the offer.
  2. Find a product.
  3. Trust the store.
  4. Add to cart.
  5. Reach Tebex checkout.
  6. Find support if something goes wrong.

That is the standard. Everything else is polish.

NextIntroduction