Storefront reliability for commerce teams
The broken request. The slow page. The step where shoppers stop. Dozenfold measures what each one costs in purchases—against comparable shoppers who didn’t hit it—then hands your team the evidence and follows the result after the fix.
For commerce teams and their developers · Estimate your price
EXPLORE WHAT DOZENFOLD DOES TODAY
Start with the question on your mind.
Move between the shopper experience, technical detail and the result.
182 const rate = rates.find(matchRate)183 setPending(true)184 await updateCart(rate.handle)185 setPending(false)186 refreshCart()/cart/updateRequest failedMapped from an uploaded source map · selected occurrence
Illustrative product views. Take the full product tour ↗
What sets Dozenfold apart
Measured −1.5 pts · 95% interval −2.1 to −0.9
Not affected sessions × conversion rate × order value. Dozenfold compares shoppers who hit the issue with shoppers at the same step, device and environment who didn’t, and shows the gap with a 95% interval.
Inspect an example calculation →Turn on error-session replay and only sessions with an error upload a recording: the minute before it and the rest of that session. Inputs are always masked. Every other session stays event-based.
Our privacy approach →What costs us the most?
list_problems · get_problem
Cart update fails after a delivery change. Theme code, cart.ts:184.
Connect Claude Code, Cursor or another MCP client with a read-only key. Your assistant reads the same issues, sessions and releases you see, next to your code.
Connect your AI tools →Context before code
Each issue shows where its occurrences came from, so your developer starts with the right question. When most of an error comes from browser-extension code, a social app’s in-app browser or shoppers who lost their connection, the issue page says so instead of handing you noise.
Overview also compares conversion by country, connection type and device memory, and names the segment that converts worst only when the gap is clear.
See issue breakdowns →TypeError in reviews-widget.jsMostly the shopper’s environment. Check before anyone starts debugging.
SEGMENT THAT CONVERTS WORSTShoppers on 3G convert 60% less
FROM THE SHOPPER TO THE SOURCE
A drop-off tells you where to look. A slow script or a failed request gives you something to investigate. The shopper’s journey puts it in context.
Keep that context as you choose the next fix, bring in your developer and check what changed after shipping.
Follow the connected workflowOriginal source appears when source maps are uploaded. Revenue estimates show their basis and remain distinct from proven loss.
One connected investigation, with the underlying evidence in reach.
CONNECT YOUR STOREFRONT
Connect through our Shopify integration, or work with our team on a custom storefront setup.
PLATFORM INTEGRATION
Install the app, enable the theme embed and connect commerce events through the Shopify Pixel.
Explore the Shopify integration ↗WORK WITH OUR TEAM
Your frontend, checkout and consent setup shape the integration. Work with us to scope the signals and access your team needs.
Discuss your setup ↗Where your team already works
Each channel picks what it receives: checkout errors, cart failures, new issues, regressions, spikes or slower Core Web Vitals.
New checkout issue · Cart update fails after a delivery change
The Developer brief opens as a prefilled issue in your tracker, under your own sign-in. Dozenfold stores no tracker credentials.
Developer brief →Mark each deploy and upload its private source maps from CI, so the next release is followed from its first session.
npx dozenfold releases create Release setup → Available now · AI tools (MCP)
Connect Claude Code, Cursor or another MCP client to Dozenfold with a read-only key. Ask which problem costs the most, open its full context, follow a shopper’s session or compare releases, with your code in the same window.
Next on our roadmap: an AI reliability engineer that works on the fix and checks the result. See the direction →
Which storefront problem is costing us the most? Who can fix it?
list_problems7 open problems, ranked by estimated revenue impactget_problemCart update fails after a delivery change · stack mapped to cart.ts:184get_session_timelineProduct viewed → delivery changed → cart request failedThe cart update in your theme code fails when the delivery option changes. rate is undefined at cart.ts:184. 68% of affected sessions are on Mobile Safari. The impact estimate is directional, not booked loss.
Read-only access, scoped to one store by its key.
Built for a live storefront
No fingerprinting · No input values · Replay only if you turn it on. Diagnostic context without a shopper’s identity.
Our privacy approach →Every amount shows its comparison and 95% interval. Measured and directional estimates stay distinct; missing inputs keep the issue visible.
Inspect a revenue estimate →A lightweight collector with no shopper-facing UI. Your developer or agency stays in control of changes.
Explore the product →Common questions
Not by default. Dozenfold reconstructs privacy-safe journeys from page, action, request, funnel, error and performance events, without DOM snapshots, screens, mouse movement or input values. Stores can turn on error-session replay: a masked recording of the minute before an error and the rest of that session, only in sessions where an error happens. Heatmaps are planned as an opt-in module.
An estimate of missed purchases and their value for the selected period. Dozenfold compares sessions that hit the issue with clean sessions at the same journey stage, device and environment, and reports the gap with a 95% interval: a measured loss when the whole interval is above zero, a directional signal when it is positive but uncertain. It does not present the estimate as booked loss, project a short window into a monthly loss, or add overlapping issues into a store total. See how the estimate works →
Dozenfold uses a lightweight storefront collector. Integration and consent requirements are reviewed with your team. We confirm activation with you, do not inject shopper-facing UI, and can disable collection if storefront safety is in question.
Anonymous error, performance, page-group, bounded diagnostic and funnel evidence, plus coarse context: country, connection type, device class and whether a page ran in a social app’s browser. We do not ask for customer identities or order payloads, and we do not record input values or cross-session shopper identities. Screen replay stays off unless a store turns on error-session replay.
No. Some come from browser extensions, from shoppers who lost their connection, or from social apps’ built-in browsers. Each issue shows those shares, so you can tell a store bug from an environment problem before anyone starts debugging. How issues are grouped →
Overview compares conversion by country, connection type and device memory. A segment is named only when it and the rest each have at least 200 sessions and the gap is large and statistically clear; until then the card says it is still collecting.
Yes, in Slack. Add one or more channels and choose what each one receives: checkout errors, cart API failures, new issues, regressions, spikes or Core Web Vital degradation. Each alert links to the issue and, when ready, shows its estimated revenue impact and likely owner: your theme, Shopify, a third-party script or a browser extension. Set up alerts →
Yes. Create a read-only key under Settings → AI agents and add it to Claude Code, Cursor or another MCP client. Your assistant can list the costliest problems, open one problem’s full context, follow a session and compare releases. MCP access is included in every plan. Connect your AI tools →
Commerce teams that regularly change their storefront and work with a developer or agency. Dozenfold connects the shopper problem with the technical context your team needs to act.
Choose a session volume to estimate your price, then contact us to discuss your storefront and setup. We agree scope and commercial terms with you. Booking a demo does not start a trial or subscription. Estimate your price and contact us.
Put Dozenfold to work
Explore your storefront from every angle: shopper journeys, performance, technical issues and what changes after a release.
Journey drop-offs, slow pages and recurring failures.
The request, browser, release and source context in one place.
Release comparisons, buying flows and issue recurrence.