E-commerce QA audit.
We find the bugs that cost you orders before your customers do. Every issue comes with a video, reproduction steps and a priority.
An e-commerce QA audit is a one-off deep check of an online store against a 150+ point checklist, from the catalog to payment and the mobile version. It suits owners who are launching a site, losing orders or accepting work from a contractor. It starts from UAH 6,000 (up to roughly UAH 15,000) and takes 3–5 days.
When testing pays off fastest
150+ checks from the checklist
We go through the store the way a customer does: from a phone, on slow internet, with a typo in the card number. Then the way Google does.
Three formats, from quick to deep
- 10–15 key issues
- Mobile version and checkout
- Homepage and product page speed
- 2–3 page PDF
- 150+ point checklist
- Bug reports with video
- Prioritization by impact
- 30-minute walkthrough call
- Everything in the QA audit
- Playwright checkout scenarios
- Runs in CI before deploy
- Re-check after fixes
This is what the report you receive looks like
We write the report for two readers: the owner sees what hurts and what it costs, and the developer sees how to reproduce and what to fix. No "the site works incorrectly".
From request to report in 5 days
- day 0BriefLinks, goals, key scenarios. We fix the price and timeline.
- days 1–3TestingWe go through the checklist on real devices and record video.
- day 4ReportBug reports with priorities, PDF and export to your tracker.
- day 5WalkthroughA 30-minute call: what to fix first and how long it will take.
What we check in an e-commerce audit
We build online store testing around the customer journey, because that is where money is lost. We go through the site the way a customer does: from a phone, on slow internet, with a typo in the card number. Then we check it the way Google does.
The checklist is split into six blocks:
- the customer journey: catalog, filters, search, product page, cart, promo codes, guest checkout;
- payment and delivery: LiqPay, WayForPay, Monobank, Apple Pay, Nova Poshta, Ukrposhta, pickup, and emails and SMS after an order;
- the mobile version: real iPhones and Android phones, keyboard, autofill, button size;
- speed: Core Web Vitals (LCP, INP, CLS), image and script weight, behavior on slow 3G;
- technical SEO: title, description, canonical, hreflang, sitemap, robots, redirects, Product markup;
- forms and security: validation, HTTPS, mixed content, a basic XSS and access check.
We described the typical errors that show up at checkout in the article why orders get lost at checkout.
What you get after the audit
The result of the audit is not general impressions but a working document. Every finding is a separate bug report with a video or screenshot, reproduction steps and a priority based on impact on revenue.
The handover package:
- a PDF report that both the owner and the developer can understand;
- a bug export to Jira, Linear or Trello;
- a 30-minute review call: what to fix first and how long it will take;
- a re-check after the fixes, if needed.
An example of what a bug report and a test case look like is in the article how we test: a bug report and a test case.
How much does an e-commerce QA audit cost and what affects the price
An e-commerce QA audit starts from UAH 6,000, and for large catalogs with several integrations the price can rise to UAH 15,000. We fix the final amount before we start, and it does not depend on the number of bugs found.
| Factor | How it affects the price |
|---|---|
| Catalog size and complexity | Many product variants and filters need more scenarios |
| Number of payment systems and delivery methods | Each integration is checked separately |
| Mobile version and devices | A wider device matrix adds hours |
| Languages and currencies | A second language adds separate checks |
| Access to staging or a test account | Allows a deeper check of orders and payment |
The approximate formats are: a free express check in 48 hours, a QA audit from UAH 6,000 and an "audit + automated tests" package from UAH 18,000. All prices are collected on the pricing page.
How the audit works
The work takes roughly five days. On day zero we get the link, goals and key scenarios, and we fix the price. Over the next three days we go through the checklist on real devices and record videos. On day four we hand over the report with priorities, and on day five we hold the review.
For a basic audit the public site is enough. To check orders and payments we ask for a test account or staging, and access is provided under an NDA. If few problems are found, you still get confirmation that the store is ready and a list of future risks. We usually start within one to two business days after payment.
When a QA audit is not what you need
A store audit is not the answer to every question. In some situations another format is better:
- You need a check before every release, not just once. Then choose website testing: it works with every update and starts from $20 per hour.
- Critical scenarios repeat every week. Test automation on Playwright suits those.
- The problem seems to be in the code: slow queries, an outdated framework, security holes. Then you need a code audit.
- You only want to see whether everything is fine on the surface. Start with the free express check.
What makes our audit different
We do not rely on emulators: the store is opened on real iPhones and Android phones. Every bug has a video and a priority based on impact on revenue, not just technical severity. We use the 150+ point checklist every time, so results can be compared between audits.
If you want to check it yourself, take our 60-point e-commerce testing checklist. And if you want us to do it, send a link to your site through the brief.
How is an audit different from testing it ourselves?
You know how the site should work, so you unconsciously avoid the problem spots. We go through it as a new customer would: on different devices, with typing errors and slow internet, using a checklist of 150+ points.
Do you need access to the admin panel or code?
Not for a basic audit: the public site is enough. To check orders and payments we ask for a test account or staging. Access is covered by an NDA.
Will you fix the bugs you find?
We can. After the audit we offer a fix package at $20–35/h. Or you hand the report to your own developer: it is written so that it can be picked up without us.
What if you find almost no bugs?
It rarely happens, but then you get confirmation that the site is ready, plus a list of future risks. The audit price is fixed before we start and does not depend on the number of bugs.
Do you test Shopify, Horoshop and WooCommerce sites?
Yes. The audit is platform-independent: we check what the customer sees. For Laravel and Nuxt we can also review the code.
How soon can you start?
Usually within 1–2 business days after payment. The express check starts the day you submit the request.
How much does an e-commerce QA audit cost?
An e-commerce QA audit starts from UAH 6,000, and for large catalogs with many payment systems and delivery methods it goes up to roughly UAH 15,000. We fix the price before we start, and it does not depend on the number of bugs found. The express check of 10–15 key problems is free.
How long does an e-commerce audit take?
A full QA audit takes 3–5 days: first the brief and a fixed price, then testing on real devices, then a prioritized report and a 30-minute review call. We prepare the free express check in 48 hours, and the audit usually starts within 1–2 business days after payment.
Send us a link to your website.
We reply within 2 business hours. The express check is free and takes 48 hours.