Find where your storefront leaks revenue — in 60–90 seconds
The scan opens your homepage, a product page and the cart the way a shopper does, and scores what it finds: one CRO score from 0 to 100 with six weighted parts, the issues that cost the most, a directional revenue-at-risk range and an “Open fix” for every leak. Read-only, shareable, and the starting point for Copilot’s brief and the AI Action Plan.
- Read-only — never changes your store
- CRO score 0–100 · Target 70+
- Shareable public report
6 points below Target 70+
Six weighted parts, scored the way a shopper sees them.
from public signals
60–90 s
From URL to score
Four passes over the live storefront: connect, read, score, quantify — then Copilot writes the brief
0–100
One CRO score, target 70+
“Healthy” starts at 70; below 45 the verdict reads “Critical friction”
6
Weighted parts
Homepage clarity /15 · PDP structure /25 · Cart & checkout /20 · Trust /15 · Offer & AOV /15 · Technical /10
≈
Revenue at risk, always marked
A directional estimate from public storefront signals — never presented as measured
Illustrative figures on this page come from the product’s own demo fixtures. Your scan shows your store’s numbers, or “Awaiting data” — never an invented one.
One score. Six weighted parts. A target of 70+.
Every scan writes a CRO score from 0 to 100 and the verdict that goes with it — Healthy, Needs attention or Critical friction — plus the highest-impact root cause and the action recommended next. Scores are trended across your last six scans against a dashed Target 70 line, so you can see whether the store is moving toward the benchmark or away from it.
- A weighted breakdown you can read part by part: homepage clarity, PDP structure, cart and checkout friction, trust signals, offer and AOV system, technical basics
- Each part is scored the way a shopper sees it — the price, variant, add-to-cart and rating summary above the fold, the drawer, the delivery threshold, the trust marks
- The weakest part is ranked first and linked to the Comver module that can improve it
CRO score
Why conversion is underperforming and which root cause matters first.
Audit snapshot
Latest completed scan · beautyskin.com
64
of 100
Several conversion areas are underperforming.
6 points below Target 70+ · 6 / 6 parts backed by evidence
Score history · last 6 scans
Score breakdown · weakest first
Each part links to its moduleHighest-impact root cause
Weak above-the-fold product page structure
PDP structure scores 15 of 25 — price, variant, add-to-cart and the rating summary sit below the fold on mobile.
CRO score
64 / 100
Target 70+
Evidence coverage
6 / 6 parts
Homepage · PDP · cart · trust · offer · technical
Revenue at risk
≈ $17,200 / mo
Directional estimate from public signals
Expected recovery
≈ $12,850 / mo
Sum of itemized leak estimates
The six parts, and what each one is worth
The score is a weighted sum. Product page structure carries the most points because it is where most Shopify stores lose the add-to-cart; technical basics carry the fewest because most themes already pass them.
Homepage clarity
Is it obvious what you sell, who it is for and where to start? Hero, navigation, first offer and the path to a product.
PDP structure
Price, variant, add-to-cart and rating summary above the fold; benefits, proof and delivery answered before the shopper has to scroll for them.
Cart & checkout friction
The cart drawer, the free-delivery threshold, quantity controls, upsell logic and how many steps sit between the cart and Shopify checkout.
Trust signals
Reviews and their placement, payment marks, guarantees, returns policy — visible where the buying decision is made.
Offer & AOV system
Bundles, add-ons, thresholds and rewards: whether the store has any mechanism that raises the order value beyond the single product.
Technical basics
Shopify and theme detected, product feed reachable, pages load and render as a shopper — the foundation the other five stand on.
Where the revenue leaks — with the fix one click away
Revenue recovery turns the scan into a funnel: At risk → Recoverable → In execution → Recovered. Under it sits an itemized list of every leak with its source (Copilot or CRO score), priority, a monthly estimate or “Not estimated”, the size of the change, and an “Open fix” link that lands in the Comver module able to close it — Sticky ATC, Cart Rewards, Bundling & Upsells, Trust AI.
- The “Biggest leak” is called out first; every other row is ranked by its estimate
- Impact by revenue engine shows each module’s configured estimate (“+8–20% AOV uplift”, typical, not measured) and whether it is Active or Ready
- “Recovered” reads “Not measured yet” until measured attribution exists — it is never modelled from the estimates above it
Revenue recovery
Where your store is leaking revenue, backed by evidence — and the fastest path to recover it.
Recovery funnel
From estimated exposure to measured recovery — real data only
Estimated stages carry an ≈. “Recovered” stays “Not measured yet” until measured attribution exists — it is never modelled.
Where revenue leaks (4)
Ranked by estimate · source shown per rowNo sticky add-to-cart bar on mobile product pages
Copilotcritical priorityMobile add-to-cart rate 8.9% vs 13.4% on desktop; the buy box scrolls away on every product page.
Free-delivery threshold not shown inside the cart drawer
Copilothigh priorityShoppers leave the drawer without seeing how far they are from free delivery.
No active cart upsell or bundle logic
CRO scorehigh priorityOffer / AOV system scores 8 of 15 — no bundle offer on the product page, no add-ons under it.
Rating summary below the fold on product pages
Copilotmedium priorityTrust signals score 9 of 15; reviews exist but are not visible before the first scroll.
A report you can share, a queue you can act on, a command center that keeps score
The scan is the entry point. Its result is written to three places: a public report page you can send to anyone, the AI Action Plan queue inside Comver, and the Overview — the command center that shows the score, what is recoverable now and the button to run the next scan.
A shareable page with the score, the breakdown and the leaks
Every scan produces a public report at its own link: the CRO score ring, the six-part breakdown, top revenue leaks with their estimated lift, detected opportunities, missing conversion signals, what is already working and an estimated recoverable-revenue range — labelled as directional. Send it to a founder, an agency or a colleague; nobody needs a login.
AI Commerce Copilot Scan report
beautyskin.com
Scanned Aug 16, 2026 · homepage, catalogue, sample product page, cart
64
CRO score
Six weighted parts scored from public storefront pages. Target 70+.
Estimated recoverable revenue
$12k–$17k / mo
Score breakdown
This is a directional estimate based on public storefront signals. Full revenue recovery model requires analytics, Shopify and traffic data.
Top revenue leaks
Detected opportunities
- Add Bundling & Upsells
- Add Sticky ATC
- Improve PDP trust system
Missing conversion signals
- Free-delivery threshold
- Reviews above the fold
- Payment trust marks in cart
What’s already working
- Shopify detected · OS 2.0 theme
- Technical basics 9 / 10
- Clear homepage hero and navigation
- Product feed reachable
From URL to the first fix
Nothing to install for the public scan. Connect the Comver app when you want the score to feed Copilot, the Action Plan and Reports.
- 1beautyskin.comScan
Read-only · public pages only
Enter your storefront URL
On the homepage, in the app’s Overview (“Run AI scan”) or from Copilot (“Scan store”). The scan reads public storefront pages only — the homepage, the product feed, a sample product page and the cart.
- 2Connect to the storefrontRead the storefrontScore the funnelQuantify and report
58% · usually 60–90 seconds
Four passes, 60–90 seconds
Connect to the storefront, read it, score the funnel, quantify and report — with screenshots captured along the way. Stay on the page; the stage rail shows exactly where the scan is.
- 3Daily brief · after the scan
PDP structure scores 15 / 25 — mobile shoppers reach add-to-cart below the fold. Two low-risk fixes cover most of the gap.
CRO 643 actions in queue≈ $12,850 upsideCopilot writes the brief
The result becomes a CRO score, top issues, opportunities, missing signals and a leak range. Inside Comver, Copilot then reads the store’s connected data and writes the daily brief and up to five recommendations.
- 41Sticky add-to-cart bar on mobile$6,400 / mo est. · Low changeOpen fix
Sticky ATC module · Prepare change · reversible
Open the fix
Each leak links to the module that closes it. Prepare the change, review its evidence and measurement plan, apply it — reversibly — and watch the next scan move the score.
Directional where it must be. Blank rather than invented.
A public storefront scan can see structure, offers and trust; it cannot see your analytics. So the score is exact, and the money is a range — and the product says so on every screen.
≈
Revenue at risk
A directional estimate based on public storefront signals. A full recovery model needs analytics, Shopify and traffic data connected.
Not estimated
When there is no evidence
Leaks that come from the CRO score without a dollar basis say so, instead of carrying an invented figure
Not measured yet
Recovered revenue
The last stage of the funnel fills only when measured attribution exists — never from the estimates above it
Once the store is connected, revenue at risk uses one canonical estimator across Overview, CRO score, Revenue recovery, the Action Plan and Reports: the larger of the latest audit’s leak range and the sum of open recommendation estimates, capped by measured monthly revenue when known.
Frequently asked questions
Nothing. It is read-only: it fetches your public homepage, product catalogue, a sample product page and the cart, takes screenshots and scores what a shopper would see. Nothing is applied to your store, and no theme change or app permission is needed for the public scan.
Usually 60–90 seconds. You get a CRO score from 0 to 100 with a six-part weighted breakdown, the top conversion issues with recommended fixes, detected opportunities, missing signals and a directional monthly revenue-leak range — on a public report page you can share. Inside Comver, Copilot adds a written daily brief and a ranked action queue.
Six weighted parts: homepage clarity (0–15 points), PDP structure (0–25), cart and checkout friction (0–20), trust signals (0–15), offer and AOV system (0–15) and technical basics (0–10). Healthy starts at 70 — the dashboard shows the target as 70+ and trends your score across the last six scans against it.
From the public scan alone it is a directional range based on storefront signals, and it is labelled that way. Once the store is connected, one canonical estimator is used everywhere: the larger of the latest audit’s leak range and the sum of dollar impacts on open Copilot recommendations, capped by measured monthly revenue when known. If neither exists, the UI says “Awaiting data” rather than inventing a figure.
Not for the public scan — enter a storefront URL and you get the report. To open the fixes, see the recovery funnel, get the daily brief and let the score feed the Action Plan and Reports, install the Comver Shopify app and connect the store. Behaviour-based measurement of applied changes additionally needs the Comver storefront tracking to be live.
Yes. Every scan has its own public report page — score, breakdown, top leaks, opportunities, missing signals and what is already working. Anyone with the link can read it; no login is required.
The result is written to the CRO score page, the Revenue recovery funnel and the AI Action Plan. Copilot writes the brief, and every leak carries an “Open fix” link into the module that can close it — Sticky ATC, Cart Rewards, Bundling & Upsells, Trust AI. Prepare a change, review its evidence and measurement plan, apply it reversibly, and rescan.
On demand — “Run AI scan” on the Overview or “Scan store” in Copilot — and the score history keeps your last six completed scans. Separately, the daily brief refreshes automatically every morning at 04:30 UTC for every connected store.
See your CRO score before you change a thing
Enter your storefront URL and get the score, the six parts and the leaks in about a minute — read-only, shareable, and honest about what is estimated. Then connect the store and open the first fix.
14-day free trial · Live on Shopify in minutes · Checkout stays in Shopify