Catch the checkout bug before the refund

Shoppers who hit a broken step rarely email you — they leave. A one-click report on the page turns a lost sale into a bug you can fix today.

On a storefront, a broken interaction is not a support ticket. It is an abandoned cart, and it is invisible in your analytics beyond a slightly worse conversion number that could be anything.

A feedback tab gives the small fraction of shoppers who are willing to tell you a way to do it in seconds, from the page where it broke.

Install without touching your theme logic

One script tag before the closing body tag in theme.liquid, or through your platform's script injection. No app install, no checkout extension, no theme fork.

Ask for the order number

A single optional text field for an order or cart reference is usually the difference between a report you can investigate and one you cannot.

Keep the storefront fast

A few kilobytes, deferred, one request. The widget does not block rendering and does not participate in your Core Web Vitals beyond its own tiny footprint.

Frequently asked

Does it collect anything about shoppers automatically?
No. There is no passive tracking of any kind — nothing is collected unless a shopper writes something and sends it. The one thing that can leave the browser before send is a screenshot, and only if they press the button for it and confirm the preview they are shown.
Can we hide it on checkout pages?
Yes — include the script tag conditionally in your template so it never loads on the pages you exclude.