PUBLIC BETA · SHOPIFY STOREFRONT QA

Storefront QA,with proof.

StoreProof tests public Shopify buying journeys in Chromium, records the evidence behind each result, and separates confirmed defects from incomplete verification.

No Shopify app No account required No checkout or payment
STOREFRONT SCANPublic buying-journey test
Completed
BrowserChromiumDesktop1440 × 1000Mobile390 × 844Methodology2C.7
DiscoverTestCaptureAnalyze
EVIDENCE VIEWERRepresentative product journey
Chromium mobile
/products/linen-overshirt390 × 844
STOREFRONTShop   Product   Bag (1)
Brand-neutral linen overshirt used in an illustrative StoreProof product-page capture
NEW SEASON

Linen Overshirt

Natural linen · Oatmeal

XSSML
Illustrative product-page capture
OBSERVED EVIDENCEVerified
Environment
Chromium · 390 × 844
Purchase control
Visible and enabled
Cart mutation
2xx observed
Cart item count
Increased
OUTCOMECart state changed

Illustrative view of fields StoreProof currently records.

REGRESSION CHECKSame methodology
PreviousCart error observedCurrentNot observed

Fixed finding

COVERAGE & CONFIDENCE

Health Confirmed issues

Coverage What ran

Confidence Evidence strength

Chromium browserRendered journeys, not HTML alone

Public storefrontNo Shopify Admin access

Bounded commerce testIsolated cart, no checkout

Versioned methodScanner and methodology disclosed

METHODICAL BY DESIGN

Test the journey. Record the proof.

A bounded scan exercises representative public journeys, records what happened, and labels anything it could not prove.

01

Discover

Find the public homepage, collections, and representative product journeys.

02

Test

Run supported commerce, mobile, accessibility, performance, SEO, and technical checks.

03

Capture

Preserve screenshots, requests, console output, cart state, viewport, and scan context.

04

Analyze

Separate confirmed storefront failures from inconclusive or scanner-limited results.

CHROMIUM · DESKTOP + MOBILE EMULATION

Test the buying path—not just the page.

StoreProof runs Playwright-controlled Chromium sessions at defined desktop and mobile viewports. Safari, Firefox, and physical devices are outside the current beta coverage.

  • Public homepage, collection, and product discovery
  • Up to three representative product journeys on desktop
  • One representative product journey at 390 × 844
  • Isolated Add to Cart verified against cart state

EVIDENCE-BACKED FINDINGS

A finding you can reproduce.

Confirmed issues include the tested page and available rendered, network, console, or cart-state evidence. Scanner-limited results stay inconclusive.

  • Affected public URL and product context
  • Desktop and mobile screenshots
  • Console errors and failed request evidence
  • Cart mutation and quantity-state signals
COMMERCE · HIGH CONFIDENCEAdd to Cart returned a confirmed cart error
Confirmed issue
EnvironmentChromium · desktopViewport1440 × 1000MethodBrowser + cart state
PRODUCT JOURNEY
NETWORKPOST /cart/add.jsHTTP 5xxObserved in the tested browser session

Illustrative layout using fields StoreProof currently records.

1IssueDetected→2EvidenceCaptured→3FixApplied→4Verify fixTargeted where supported
BEFORE
/assets/reviews.js → 404
Confirmed issue
→
AFTER
/assets/reviews.js → 200
Verified fixed

DETECT. FIX. VERIFY.

Verify supported fixes without losing the original proof.

Eligible HTTP resource failures support a targeted retest with immutable before-and-after evidence. Other finding types honestly require a new full scan.

  • Targeted Verify Fix for eligible resource failures
  • Pending, running, fixed, failing, and blocked states
  • Original and new evidence remain intact
  • Full-scan comparisons stay methodology-compatible

THREE MEASURES · ONE HONEST REPORT

Health is not the same as certainty.

Health, audit coverage, and result confidence answer different questions. StoreProof shows all three, including checks it did not reach or intentionally excludes.

View methodology →

Health

Confirmed, scoreable findings weighted by severity and evidence confidence.

Coverage

The share of the supported public storefront journey that was exercised.

Confidence

The strength and representativeness of the evidence StoreProof collected.

FOUNDING BETA · MONITORING INTEREST

Monitor this storefront

Join the StoreProof founding beta for upcoming baseline monitoring, storefront change alerts, and Verify Fix history. Monitoring is still being built—joining helps shape what ships first.

For merchantsFounding beta target: around $19/monthFor agenciesFounding beta target: around $79/month · up to 10 stores
Set up your founding-beta accountFounding-beta pricing is being tested and may change. No payment is collected today.
FOUNDING BETA ACCESSTell us how you would use StoreProof monitoring.

Share your storefront workflow, preferred cadence, and the capabilities that would make monitoring worth paying for.

01

Methodology disclosed

Versioned scoring, coverage weights, uncertainty rules, and testing boundaries.

Read methodology
02

Privacy stated plainly

See what a scan stores, which services process it, and how long evidence may remain.

Read privacy notice
03

Built by RXR Code

Public-beta storefront QA with a conservative, evidence-first testing boundary.

Visit RXR Code ↗