Fix-ready storefront evidence pack
This sample shows the structure of a Storefront QA Sprint deliverable: captured routes, reproducible evidence, severity, and the next repair action—not a generic automated score.
Example storefront
Northstar Outfitters
Public mobile QA
Routes captured
6
Example findings
3
Repair format
Developer-ready
Fixed fee
£895
Delivery
48 hours
Full crawl
Up to 250 pages
Delivered pack
12 findings + 30-day watch
Coverage appendix
What was actually checked
| Route | HTTP | Page type / result |
|---|---|---|
| / | 200 | Home |
| /collections/summer-edit | 200 | Collection |
| /products/linen-set | 200 | Product |
| /products/linen-set-blue | 404 | Broken destination |
| /pages/shipping | 200 | Policy |
| /policies/refund-policy | 200 | Policy |
Prioritized repair queue
Evidence your developer can reproduce
/collections/summer-editFeatured product destination returns HTTP 404 on mobile
Captured evidence
The collection card links to /products/linen-set-blue. The destination returned HTTP 404 during the captured public mobile check.
Fix-ready recommendation
Redirect the retired handle to the live product and update the collection-card destination so the journey does not depend on the redirect.
Exact reproduction steps
- Open the Summer Edit collection at a mobile viewport.
- Select the featured blue linen-set card.
- Observe the 404 response at /products/linen-set-blue.
/products/linen-setSale message conflicts with the price shown later in the journey
Captured evidence
The product page example advertises £69 while the captured cart state displays £79 for the same selected variant.
Fix-ready recommendation
Use one variant-aware price source for the promotional message, product price and cart line item; remove cached sale copy when the promotion ends.
Exact reproduction steps
- Open the linen-set product route and select the blue / medium variant.
- Confirm the promotional message shows £69.
- Add the variant and compare the £79 cart line price.
/pages/shippingDelivery window disagrees with the storefront announcement
Captured evidence
The shipping page example says 3–5 working days while the announcement bar promises dispatch and delivery within 48 hours.
Fix-ready recommendation
Separate dispatch time from delivery time and reuse the same market-specific wording in the announcement, policy and product template.
Exact reproduction steps
- Read the delivery promise in the storefront announcement bar.
- Open /pages/shipping in the same market and session.
- Compare the 48-hour promise with the 3–5 working-day window.
Repair and watch outputs
The pack continues beyond the finding cards
Redirect CSV row
from,to,reason /products/linen-set-blue,/products/linen-set,broken collection card
Copy-ready correction
“Dispatches within 48 hours. Estimated delivery: 3–5 working days.” One market-specific promise for the announcement and policy.
Regression-watch baseline
Daily public checks on up to 10 agreed routes for 30 days, with an operator alert when the observed status or content fingerprint changes.
Your pack contains only captured, reproducible evidence.
Automated signals are reviewed before delivery. Unverified hypotheses and conversion-uplift promises are excluded.
The paid £895 pack expands this structure to up to 250 public pages, 12 selected findings, downloadable CSV/JSON evidence and daily observation of 10 agreed routes for 30 days. Read the service terms.