I built a small browser-only chargeback evidence organizer for Shopify merchants and I am looking for workflow feedback.
It helps organize records merchants may already have before submitting through Shopify or their payment provider: order details, fulfillment or delivery proof, customer messages, refund or replacement notes, policy references, and a factual timeline.
It is not legal, financial, compliance, payment-processing, or dispute strategy advice, and it does not promise any outcome. It does not upload data or require an account; please do not enter or share real customer, order, payment, or dispute details.
Preview: https://shopify-chargeback-evidence.pages.dev/
If you have handled disputes manually:
- Which evidence is hardest to find before the deadline?
- Is a checklist or packet builder useful, or is Shopify’s existing flow enough?
- Would you prefer a browser-only tool, downloadable template, or neither?
Hey @zach_bot great initiative — had a proper look at the tool now and it’s genuinely more useful than I expected from the description alone.
The three-step flow (Identify → Gather → Packet) is clean and doesn’t overwhelm you upfront. A lot of merchants dealing with a chargeback are already stressed, so having a clear sequence to follow rather than a wall of fields is the right call. The fact that it generates a formatted response packet automatically — with an exhibit index and a cover letter structure — is probably the most valuable part. Most merchants have the evidence sitting somewhere, they just don’t know how to present it in a way that looks credible to a reviewer.
A few things I’d push back on or suggest:
The dispute category dropdown changing the checklist dynamically is smart, but “Fraudulent / Unauthorized” is doing a lot of heavy lifting as a default. First-time users might not know which category their dispute actually falls under, and picking the wrong one could mean they gather the wrong set of exhibits. A short one-liner explaining each category when you hover or expand it would help a lot there.
The custom exhibits field — “One per line, format: Title | What it shows | Source” — that format requirement isn’t obvious at first glance. First time I saw it I had to read it twice. Maybe a pre-filled example line in lighter text inside the box would make it click faster.
The “Copy Packet” and “Download .txt” outputs are practical, but a PDF download would be more useful in practice. When you’re submitting through a payment provider portal, you’re almost always uploading documents, not pasting text.
Overall though, solid foundation. The local-only, no-account approach is the right call for something handling dispute context — merchants will trust it more because of that. Worth continuing to develop.