REVENUE IMPACT & PRIORITIZATION

A bug list is a backlog.
Know what deserves a fix.

Connect technical failures to affected shoppers and purchase evidence. Give your team a clear reason to choose one investigation over another.

A priority you can open up.

The amount is the start of the review. Inspect the sessions, purchase comparison and order value behind the example.

northstar / revenue impactLast 30 days

DF-1876 · CART UPDATE FAILURE

Choose the next fix with its evidence in view.

Estimated revenue impact$614/dayMeasured loss · 30-day evidence

PURCHASES WITHIN 30 MINUTES

With this issue10%48 of 480 compared sessions
Clean sessions34%Same stage, device and environment mix

Gap 24.0 points · 95% interval 21.2–26.8.
Open the amount to inspect all inputs.

486 affected sessionsOne issue · USD · Equal purchase follow-upExplore the issue ↗
Illustrative product data Explore freely. No store connection required.

KEEP THE INVESTIGATION MOVING

From the number to the work.

Read the product guide ↗
01

Put one issue in business context.

Review affected sessions, observed purchase outcomes and the revenue estimate together. Each amount belongs to one issue and reads per day the issue was seen, like $614/day, so a new issue is not diluted by the days before it existed. Every window, even the last 24 hours, compares at least seven days of shoppers.

Explore the issue behind the amount
02

Look through the number.

Affected sessions are compared with clean sessions at the same journey stage, device and environment, with the same 30-minute purchase window. See both purchase rates, the pooled gap with its 95% interval and the clean order value behind the amount. The selected window stays attached to the estimate.

Understand the shopping path
03

Rank by evidence, not by the biggest number.

Measured losses lead, ordered by missed orders per day at the cautious end of the interval; directional signals follow, ordered by affected sessions. When purchases are too few to compare, Dozenfold measures whether shoppers still reach the next step (≈ 15 fewer continue/day) and never puts money on it.

Prepare the developer handoff

A LITTLE MORE DETAIL

Good questions.
Useful answers.

Does the amount mean that revenue was definitely lost?

It is an estimate based on an observed comparison. It is not booked loss or proof that the issue caused every missed purchase. The evidence and selected period remain visible so your team can judge the priority.

What if my store has few purchases?

Each issue also compares whether shoppers reached the next journey stage (product to cart, cart to checkout) within the same 30 minutes. That happens far more often than a purchase, so it reaches a clear answer sooner. It reads as shoppers lost per day and never carries money. Without order values, a purchase gap reads as missed orders per day.

Why per day?

Amounts are averaged over the days the issue actually occurred within the evidence window, which is the selected window or seven days, whichever is longer. That keeps a short window comparable with a long one and a new issue comparable with an old one. It is not a forecast.

Can I add all issue estimates into one store total?

Issue populations can overlap, so their amounts should not be summed into a store total. Use them to inspect and prioritize the individual issues, then review the relevant follow-up after a change.

CONNECTED PRODUCT WORKFLOWS

Follow the next connection.

An issue, a journey, a page or a release. Each view gives you a way into the next.

SEE IT ON YOUR STORE

See it on your own store.

Install Dozenfold from the Shopify App Store and switch on the theme embed; the first sessions arrive within minutes. Custom storefront or prefer to talk first? Book a demo.

Install on Shopify Book a demo · See pricing

DF-1876 / REVENUE EVIDENCE

A priority you can look into.

Cart update fails after a delivery change

Measured loss$614/dayOne issue · 30-day evidence window · USD

Illustrative calculation.
No live store connected.

486Affected sessions
480Compared with clean sessions
9,720Clean sessions

What happened after the failure?

Affected sessions hit the failure within 30 minutes of entering a journey stage. Clean sessions reached the same stage on the same device and environment without this issue. Purchases count in the same 30-minute window for both.

With this issue10%48 / 480 purchased
Clean sessions34%Same stage, device and environment mix
The interval decides the label.

The pooled gap is 24.0 percentage points with a 95% interval of 21.2–26.8 points. The whole interval is above zero, so the loss is measured. Strata where affected shoppers converted better pull the gap down instead of being ignored.

See the inputs and calculation

480 compared sessions × 24.0% conversion gap = 115.2 missed purchases × $159.90 clean average order value ≈ $18,420 over the evidence window. The issue occurred on all 30 days, so it reads $614 per day.

The order value uses complete clean-session orders in USD. This example has uniform, full capture. The 6 affected sessions without a comparable clean group are not priced.

This estimates a difference associated with the issue. It does not identify confirmed lost orders or establish cause. The per-day amount averages the days the issue was seen; it is not a monthly projection. Every window, even the last 24 hours, compares at least seven days of sessions.

Read the complete methodology ↗

DF-1876 / DEVELOPER HANDOFF

Take the evidence with you.

A technical brief for your developer or coding assistant. Review it here, then copy or download it into your own workflow.

Illustrative issue · No shopper identity or revenue figures
# Dozenfold — example developer brief

Illustrative product-tour data. This is a fictional issue, not a customer incident.
Use it to see the kind of evidence you can take from Dozenfold into your team's workflow.

## Issue

DF-1876 — Cart update fails after a delivery change

- Error: TypeError: Cannot read properties of undefined
- Observed environment: production, Mobile Safari
- Release: storefront@2.18.4
- Affected surface: storefront cart delivery selector

## Observed journey

1. 12:41:58 — Viewed /products/ridge-jacket
2. 12:42:11 — Added a variant to the cart
3. 12:42:46 — Changed the cart delivery option
4. 12:42:47 — POST /cart/update failed; TypeError captured

These are captured events, not a screen recording or a guaranteed reproduction.
No shopper identity, typed value, request body or response body is included.

## Original source context

Available in this example because a usable source map was uploaded.

```ts
// cart.ts:184 — illustrative source
const rate = rates.find(matchRate);
setPending(true);
rate.handle; // captured failing line
await updateCart(rate);
```

## Investigation starting point

Inspect how the delivery selector handles a missing matching rate. Check the captured browser
and release context against your implementation. The evidence locates an observed failure;
it does not establish its root cause or prescribe an automatic fix.

## Product guides

- Developer evidence: https://docs.dozenfold.com/docs/developer-evidence
- Source maps: https://docs.dozenfold.com/docs/source-maps
- Sessions and journeys: https://docs.dozenfold.com/docs/sessions-and-journeys

The live product's brief is scoped to the selected issue and occurrence. This public example
contains no live investigation link and no financial estimate.

DF-1876 / CLIENT REVIEW

A decision you can explain.

Client review: cart delivery update

Northstar Outdoor · DF-1876 · Last 30 days

Illustrative working example prepared for a client conversation. This is not a customer result or an automatically generated client report.

The decision

Prioritize investigation of the cart delivery selector with the team responsible for the storefront. Shoppers changing a delivery option encounter a recurring failure, concentrated on Mobile Safari in storefront@2.18.4.

Why this issue

  • 486 affected sessions in the selected period.
  • $614 per day measured revenue loss, associated with this issue in USD ($18,420 over the 30 days it occurred).
  • 480 affected sessions were compared with clean sessions at the same journey stage, device and environment. Within the same 30-minute window, 10% of affected sessions purchased against 34% of clean sessions.
  • The pooled gap is 24.0 points with a 95% interval of 21.2–26.8 points, entirely above zero. About 115 missed purchases are valued at the $159.90 clean average order value. The 6 affected sessions without a comparable clean group are not priced. This is not confirmed lost revenue or a store-wide total.

Inspect the example calculation

The proposed next step

The storefront developer investigates the delivery selector using the observed journey and uploaded source map at cart.ts:184. Check how a missing matching delivery rate is handled; the evidence does not yet establish the root cause.

The technical brief carries the stack, environment and source context. It deliberately excludes financial estimates so it can be shared in the developer’s own workflow.

Open the technical investigation

What we will review after a fix

Record the actual deployment and look for this issue on the new release, including relevant traffic and browser coverage. If it recurs, reopen the investigation. An absence of errors without observed activity is not evidence of a successful fix.

Current status: investigation proposed. No fix, recovered revenue or post-fix outcome is claimed in this review.

DOZENFOLD / PRIVACY

Make yourself at home.