A full view of claims, returns,
and every order in between.
Real-time dashboards give your team the numbers that matter: protected orders, claim rates, resolution trends and revenue recovered, all in one place.
Because every Guide module writes to the same record of the customer, the analytics show claims, returns, exchanges and delivery performance as one picture rather than four exports that have to be reconciled. The useful part is the reason data underneath: which products come back, which carriers generate claims, and which cohorts do both.
Numbers that reconcile,
because they come
from one source.
When protection, claims, returns and tracking share a database, reporting stops being an exercise in matching four exports that disagree. Ask a question, get an answer, drill to the individual order.
- Live KPIs across protection, returns and tracking
- Compare protected vs. total order performance
- Drill into every claim and customer in seconds
From event to answer.
Nothing here is a nightly batch. The dashboard is reading the same records the claims team is working from.
Every module writes to one record
A protected order, a scan, a claim and an exchange are all events against the same customer. That's what makes the reporting agree with itself.
Dashboards update in near real time
You're not waiting for a sync. What the console shows is what the operations team can see.
Ask in plain English
Which lanes are failing this month. Which SKU drives the most damage claims. Which cohort exchanges rather than refunds. No report builder, no dashboard to configure first.
Reconcile at month end
Order-level CSV that ties line by line to Shopify, so finance can check the Shopify usage charge line by line, where you qualify for revenue share, rather than taking it on trust.
Built for the person who has to explain it.
Plain-English questions
Ask which lanes are failing or which SKU drives the most damage claims, and get the answer without building a report first.
Exports finance trusts
Order-level CSV that ties back to Shopify, so protection revenue and claim cost can be reconciled line by line rather than argued about.
Alerts, not dashboards
Guide tells your ops lead when a metric moves outside its normal range, rather than waiting for somebody to remember to check.
Who sees what,
and where it goes.
The console isn't the only destination. Most teams want this data somewhere else too, and it's yours to move.
What a team actually does with this.
Dashboards are only worth building if somebody changes something because of them. These are the three loops the console is designed to close.
Weekly: failing lanes
Which carrier and destination combinations are producing claims. Enough signal in a fortnight to change a shipping rule, and it is usually one lane doing most of the damage.
Monthly: policy fit
The mix between replaced, refunded, exchanged and declined. If it drifts from what you intended, the thresholds are wrong rather than the customers.
Quarterly: SKU truth
Contribution after returns, freight and processing. This is where a product that looks like a bestseller turns out to be funding its own returns.
It does not stop at this module.
Every part of Guide writes to the same record, so what happens here changes how the next thing is handled.
See your own numbers in the console.
Connect a sandbox store during the demo and we'll populate the dashboards with real structure.
Thirty minutes, on your own catalogue · Free to install, and our team does the build