Reports built only from connected evidence
Three report views assembled exclusively from what is connected — Shopify, behaviour, Copilot, the CRO score and the Comver modules. Every figure is a count of something Comver generated, a sum of estimates it labelled, or a number Shopify synced. The B2B twin reads the same evidence across accounts, quotes and reorders. No sample data, no benchmarks, no modelled recovered revenue: an empty chart says it is empty.
- Assembled from connected data only
- No example reports — ever
- Every figure labelled counted or estimated
Shopify · behaviour · scan → change prepared and applied → measured before / after → ≈ estimate until counted
Executive reportsB2B · planned
Assembled from Shopify, behaviour, Copilot, CRO and module data
Account briefs
51
Generated
Completed audits
6
Catalog scans
AI actions completed
4
Measured executions
Open recommendations
5
Waiting on a decision
Quote & revenue reports
Sum of every estimate · not measured revenue
Account reports
Accounts by stage
3
Report views, shipping today
Executive · Revenue · Customer — one tab each, four metrics and one chart per tab
5
Connected data families
Shopify, behaviour, Copilot, the CRO score and Comver module data — nothing else feeds a report
8 weeks
Evidence generated, plotted
Audits, daily briefs and recommendations per week — plotted even when every week is zero
0
Example reports
“No example reports are shown.” An empty tab offers to generate a brief or ask Copilot instead
These four figures describe Reports as it ships today for Shopify DTC stores. Account, quote and reorder views need the account layer that does not exist yet, and the screens on this page are illustrative.
Three views of the same evidence, none of it invented
Every tab opens with the outcome-ledger rail — Source → Execution → Evidence → Revenue impact — then four metrics and one chart. The Executive tab counts what the AI produced, the Revenue tab sums what it estimated, the Customer tab reads what Shopify synced. In the B2B twin the third tab reads accounts rather than shoppers.
What Comver produced this week
Daily briefs generated, completed audits, AI actions completed (“Measured executions”) and open recommendations (“Waiting on a decision”), with an eight-week column chart. If nothing has been recorded, the chart says so in words rather than showing a sample.
Executive reports
Assembled exclusively from connected Shopify, behaviour, Copilot, CRO and module data.
AI daily briefs
51
Generated for this store
Completed audits
6
Storefront scans finished
AI actions completed
4
Measured executions
Open recommendations
5
Waiting on a decision
Evidence generated
Eight weeks · counts only
Latest evidence
Newest first
Five connected families — and one deliberate gap
A report can only cite what is connected. Each family below is shown Connected or Unavailable in Copilot’s data-sources grid; anything Unavailable is simply absent from the report, never approximated.
Shopify
Products and orders read live from the Admin API, customers synced to Comver. Lifetime revenue, returning buyers and orders per customer come from here.
Learn moreBehaviour
Sessions, events, heatmaps, funnels and traffic sources from the Comver storefront tracking — what measures an applied change before and after.
Learn moreCopilot
Daily briefs, recommendations with confidence and monthly potential, prepared changes and completed measurements — the rows behind “AI actions completed”.
Learn moreCRO score
Completed storefront audits, the score, revenue at risk and the leak estimates from the latest scan.
Learn moreComver modules
Which revenue modules are active, their configured estimates and the orders they attributed by discount code or cart token.
Learn moreWhat is deliberately missing
No example reports, no industry benchmarks, no modelled recovered revenue — and no quote, invoice or price-list data, because Comver does not hold any of it yet.
One trace from source to revenue impact
Every report opens with the same rail because every figure follows the same path. A source produces evidence (a scan, a brief, Shopify orders); Copilot turns it into a change that is prepared, approved and applied — reversibly; measurement compares behaviour before and after (at least 24 hours and 50 sessions per window); and the result lands as an estimate while it is estimated, and as a counted figure only once it is attributed.
- The same canonical revenue-at-risk figure is printed on Overview, the CRO score, Revenue recovery, the Action Plan and Reports — they never disagree
- Estimates carry an ≈; counts carry none; “Not measured yet” is written out instead of a zero that could be mistaken for a result
- The rail is identical on all three tabs, so a founder, a sales lead and whoever owns the account book read the same chain of custody
Source
- Storefront scan · CRO score 64
- Daily brief · today 06:30
- Shopify orders + Comver sessions
Execution
- Change prepared · reversible
- Approved · applied Aug 12
- Rollback snapshot kept
Evidence
- ≥ 24 h · ≥ 50 sessions per window
- ATC rate 8.9% → 10.4%
- Measurement completed
Revenue impact
- ≈ $6,400 / mo while estimated
- Counted only when attributed
- “Recovered” · Not measured yet
No example reports are shown. An empty tab says so — “Eight weeks are plotted and every one of them is zero” — and offers Generate daily brief · Ask Copilot for recommendations · Check the store connection.
What is counted, what is estimated, what is never claimed
The honest version of a reporting page: which figures are rows in your own data, which are labelled estimates, and which the product refuses to show at all. The last two rows are the ones a B2B buyer should read first.
| Counted from your rows | Estimated, labelled ≈ | Not shown | |
|---|---|---|---|
| Daily briefs generated | |||
| Completed audits (storefront scans) | |||
| AI actions completed · measured executions | |||
| Open recommendations | |||
| Estimated impact by recommendation | |||
| Synced customers · returning · lifetime revenue | |||
| Recovered revenue | “Not measured yet” until attribution exists | ||
| Quotes, invoices and price-list activity | Not held by Comver — roadmap |
The reporting engine is honest. The account objects are missing.
Reports plot counts and sums of labelled estimates from connected sources. Account, quote and reorder reporting needs objects — companies, buyers, quotes, price lists — that Comver does not store today, and no chart can be drawn from a table that does not exist.
Today
Counts and estimate sums
Briefs, audits, completed actions, open recommendations, estimated impact ranked by recommendation, and the customers Shopify synced
Needed
Accounts, quotes, price lists
The account layer — Shopify B2B company and price-list APIs — before a quote ageing report or reorder cycle can be counted from anything real
Never
Example reports
“No example reports are shown.” Before your store generates evidence, the tab says so and offers to generate a brief — it does not show a sample cohort
Reports are read inside the Comver workspace; there is no scheduled email or file export today. The daily brief refreshes every morning, and “Generate new evidence” runs a brief or recommendations on demand.
Frequently asked questions
No. Reports ships with three tabs — Executive, Revenue, Customer — built from connected Shopify, behaviour, Copilot, CRO and module data. Account, quote and reorder reporting needs the account layer described across these B2B pages, and that is roadmap with no date announced.
Only what is connected: Shopify (products, orders, customers), Comver behaviour data (sessions, events, heatmaps, funnels, traffic sources), Copilot (briefs, recommendations, changes, measurements), the CRO score and its audits, and Comver module status and attribution. Nothing else feeds a report.
No, and there will not be. The product states it plainly: “No example reports are shown.” Before your store has generated evidence the Executive tab reads “No generated reports” and offers to generate a daily brief or run an audit; the chart footnote says every one of the eight plotted weeks is zero.
No. It is the sum of the monthly estimates attached to open recommendations and audit leaks, and it is labelled as such. Recovered revenue is a separate stage that reads “Not measured yet” until measured attribution exists — it is never derived from the estimates.
The rail at the top of every tab: Source → Execution → Evidence → Revenue impact. It shows the path every figure took — a scan, a brief or Shopify orders as the source; a prepared and applied change as execution; a before/after measurement as evidence; and an estimate or a counted, attributed figure as impact.
Each applied change ships with a measurement plan. After at least 24 hours and 50 sessions on each side, Copilot compares the primary metric before and after and records the result; the history timeline logs the change from one figure to the other. That row is what the Executive tab counts.
Not today. Reports are read inside the Comver workspace under Workspace → Reports; there is no scheduled email or file export. The daily brief refreshes automatically every morning, and evidence can be generated on demand.
Reports as it ships, on a connected Shopify store. Everything about the ledger, the counting rules and the refusal to invent a number is already there — what is missing is the account, quote and reorder dimension to read it along.
Keep exploring
Reports you can forward without a footnote
The counting rules, the ledger and the refusal to show an example report ship today. Join the B2B waitlist to hear when accounts, quotes and reorders become a dimension you can read them along.
14-day free trial · Live on Shopify in minutes · Checkout stays in Shopify