Shopify chargeback response letter generator: what wins

You have written this letter before. Maybe forty times. The opening changes a little each time, the order details get pasted in from a different tab and the tone swings between polite and furious depending on how the week went. Then a new dispute arrives, you stare at the box marked "uncategorized text" and think: there has to be a better way to write this.

A Shopify chargeback response letter generator is that better way, if it is built properly. It drafts the written account of the dispute from the records in your store, in a structure a bank reviewer can follow in under a minute, and leaves you with an edit instead of a blank page. This guide covers what a winning letter contains, how it changes by dispute reason, ready-to-adapt skeletons for each, what a generator must never write and how to review a draft in three minutes.

This guide is for you if:

You respond to Shopify Payments disputes and the writing is the part you dread.
You want your letters to be consistent, factual and short, without sounding like a form.
You are weighing a generator and want to know what a good draft looks like before you trust one.

Last updated: 30 October 2026. Written by the ChargeFix team. Reviewed against sources on 30 October 2026.

A note on bias: we make ChargeFix, so we gain if you use a generator and pick ours. A letter cannot rescue a case with no evidence, and we say so more than once below. The sample letters are our own illustrations, not templates approved by any bank or by Shopify, and all dollar figures are assumptions.

The 30-second answer (TL;DR)

A response letter is the written narrative that sits beside your evidence files. Shopify gives it a text field, and the reviewer reads it first.
A strong letter is short, factual and ordered: what the customer claims, what actually happened with dates, which files prove it and what you ask the bank to do.
It changes with the dispute reason. A fraud letter leans on matched data and history. A not received letter leans on the delivery scan. A credit not processed letter leans on the refund date.
A generator should write only from records it read. It should flag gaps, never fill them with invention, and never accuse the customer of anything you cannot show.
Evidence is final once submitted, so review every draft. Three minutes of checking beats a response you cannot fix.
A good letter helps a good case. It does not turn a weak case into a win.

Quick note: Think of the letter as a cover page for your evidence. The files carry the proof. The letter tells the reviewer where to look and why it matters. If a letter and the files disagree, the files win and the letter loses credibility.

At a glance

Dispute reason	What the letter must say first	What it points to	What to leave out
Fraudulent or unrecognized	The cardholder's history with you and the data that matches	Earlier orders, address and device match, delivery to the billing address	Accusations of fraud against the customer
Product not received	The product was delivered, where, and when	Carrier scan, address on label, signature or photo	Guesses about where the parcel went
Credit not processed	The refund was issued on this date for this amount, or why none was owed	Refund record, refund policy	Anger about the dispute
Not as described	The item matched the listing	Listing, photos, order notes, messages	Opinions about the customer's taste
Subscription canceled	The customer agreed to recurring billing and did not cancel in time	Signup consent, billing schedule, cancellation policy	Legal threats

What is a Shopify chargeback response letter generator?

It is software that drafts the written part of your dispute response. It reads the order, fulfillment, refund and customer records in your store, picks out the facts that matter for the dispute reason and turns them into a short, structured narrative with dates and amounts.

Most of what makes a letter good is routine. The same questions come up every time: who is the customer, what did they buy, when did it ship, when did it arrive, what did they say to you and what does your policy say. A generator answers those from data, so you spend your time on the bit only a person can do, which is judging whether the draft is true and fair.

There are two kinds of tool, and the difference matters.

Template fillers. They drop order fields into a fixed paragraph. They are fast and predictable, and they sound exactly like a form letter because they are one.

Record-driven drafters. They look at what the records say, choose the facts that fit the dispute reason, and leave out anything they cannot support. ChargeFix is built this way. The draft is shaped by the case, not by a single template.

Neither kind helps if your records are thin. A letter can describe a delivery scan beautifully only if a delivery scan exists.

Who reads your letter, and what do they want?

Picture a reviewer at the card network, issuing bank or acquirer who handles a large number of cases. We do not know the exact reading routine at any bank, and it varies, so treat the following as a sensible working assumption rather than a documented rule.

They want to answer a short list of questions.

What is the customer claiming?
Does the merchant dispute that claim?
What is the merchant's proof?
Does the proof match the transaction?

Everything in your letter should serve one of those questions. The first two lines should answer the first two. The middle should lay out the proof. The close should state what you are asking for.

Shopify's own guidance on evidence adds one practical rule: it should be readable without zooming in, in high contrast, because pages may be faxed. Plain text beats a decorated PDF. A short letter in a clean font beats a four page essay with a logo in the corner.

What does a winning response letter contain?

Across reasons, a good letter has six parts, in this order.

1. A one sentence summary. State the dispute and your position. For example: "The cardholder disputes order 4821 for $72.00 as not received. The order was delivered to the shipping address on 12 September 2026, as shown in the attached carrier record."

2. The order facts. Order number, date, amount, product, quantity, billing and shipping address match, and the email used. Keep it to the facts a reviewer would check.

3. The timeline. Dates in order: ordered, shipped, delivered, any contact from the customer, any refund. A timeline of four to eight lines is usually enough. Use real dates, not "a few days later".

4. The proof, by file. Name each attached file and say in one line what it shows. "File 1: USPS tracking record showing delivery on 12 September at 2:14 pm to the address on the order." Matching the letter to the file labels saves the reviewer from hunting.

5. The policy. If your refund, shipping or cancellation policy matters to the dispute, say where it was shown to the customer and attach it. Point to the checkout page or confirmation email, not to a policy page that may have changed since.

6. The request. Ask plainly: "We ask that the dispute be resolved in the merchant's favor." No pleading and no threats.

That is the whole structure. Most of the craft is in what you leave out.

How long should the letter be?

We have not found a published rule on length, so this is our guidance rather than a requirement: aim for one page, roughly 250 to 450 words, with the proof carried by the files.

Shorter is fine when the case is simple. A credit not processed case where you refunded on a known date can be 120 words. Longer is justified only when there is a real sequence to explain, such as a subscription with several charges and a disputed cancellation.

If a draft runs past a page, ask what the reviewer needs and cut the rest. Long letters usually mean the writer is arguing rather than showing.

What tone works best?

Neutral and factual. A letter is a record, not a rebuttal speech.

Do:

State what happened and when.
Refer to files by name.
Use the customer's order details as they appear in Shopify.
Acknowledge uncertainty plainly where it exists, such as "the carrier record shows delivery to the address on the order; we have no record of contact from the customer before the dispute".

Do not:

Accuse the customer of fraud or lying. You can say what your records show without judging motive.
Use capital letters, exclamation marks or sarcasm.
Quote law or threaten action. If a legal point matters, a lawyer should write it.
Overclaim. If a signature was not collected, do not imply one.

The phrase "we have no record of" is one of the most useful in the whole exercise. It is true, it is neutral and it makes a point without making an accusation.

Sample letter skeletons by dispute reason

These are structures to adapt. Replace the bracketed items with facts from your own records. If you cannot fill a bracket truthfully, delete the line rather than guessing.

Product not received

The cardholder disputes order [number] placed on [date] for [amount] as not received.

The order contained [product and quantity] and was shipped on [date] by [carrier] with tracking number [number] to the shipping address on the order: [address]. The carrier record (File 1) shows delivery on [date] at [time] to that address. [Signature or photo, if one exists: File 2 shows the delivery photo / signature.]

Timeline: ordered [date]; shipped [date]; delivered [date]. Before the dispute was filed, we have no record of contact from the customer reporting a problem. [If contact exists: On [date] the customer wrote that ..., and we replied on [date] with ...]

Our shipping policy (File 3) was linked at checkout and states [relevant line].

We ask that the dispute be resolved in the merchant's favor.

Fraudulent or unrecognized

The cardholder disputes order [number] placed on [date] for [amount] as fraudulent or unrecognized.

The order was delivered to [address], which matches [the billing address / an address used on earlier orders]. The email address [email] was used on [number] earlier orders placed between [dates], none of which were disputed (File 1). The IP address or device used on this order matches [the earlier orders / the cardholder's account activity] (File 2).

The product was shipped on [date] and delivered on [date] per the carrier record (File 3).

We ask that the dispute be resolved in the merchant's favor.

For fraud claims under Visa reason code 10.4, the Compelling Evidence 3.0 rule looks for two earlier undisputed transactions 120 to 365 days old, with two matching data elements, one of which must be the IP address or device ID. If your records meet that test, say so precisely and attach the matched transactions. If they do not, do not imply it.

Credit not processed

The cardholder disputes order [number] for [amount], stating a refund was not received.

A refund of [amount] was issued on [date] to the original payment method (File 1, refund record). Banks can take several business days to post a refund; the refund was issued [number] days before the dispute was filed / after the dispute was filed.

[If no refund was owed: Our refund policy (File 2) states [line], and the return window closed on [date]. The customer requested a refund on [date], which we declined on [reason] (File 3).]

We ask that the dispute be resolved in the merchant's favor.

Not as described

The cardholder disputes order [number] as not matching its description.

The product page at the time of purchase (File 1) described the item as [description]. The item shipped was [description, SKU]. [Photos of the item as shipped: File 2.]

On [date] the customer wrote [summary of complaint]. We replied on [date] offering [return / replacement / refund]. [Outcome.]

We ask that the dispute be resolved in the merchant's favor.

Subscription canceled

The cardholder disputes the charge of [amount] on [date] under order [number], stating the subscription was canceled.

The customer subscribed on [date] and accepted recurring billing of [amount] every [interval] at checkout (File 1, signup record). Our cancellation policy (File 2) states [line]. We have no record of a cancellation request before the charge on [date]. [If one exists: the customer requested cancellation on [date], after the charge.]

Prior charges of [dates] were not disputed.

We ask that the dispute be resolved in the merchant's favor.

Each skeleton is under 200 words before the details are filled in. That is deliberate.

Where does the letter go in Shopify?

Shopify's dispute evidence form has text fields and file fields. The documentation lists a refund policy disclosure, a cancellation policy disclosure, a cancellation rebuttal, a refund refusal explanation, an access activity log and an uncategorized text field, plus file fields for policies, customer communication, service documentation, shipping documentation and uncategorized files. There is also a response summary file type.

The main narrative usually belongs in the uncategorized text field or the most specific field that matches the reason. A refund refusal goes in the refund refusal explanation. A subscription dispute that centers on cancellation goes in the cancellation rebuttal. Policies go in their own fields. The documentation does not describe each field's purpose, so we are inferring from names, and you should check the form you see in the admin.

Two rules follow.

Do not repeat the letter in every field. Say it once where it belongs and keep the other fields for the material they are named for.

Keep field text short and the files labeled. If the letter says "File 1: carrier record", name the file "File 1 carrier record" so the reviewer can match them.

What must a generator never write?

This is the most important section. A generator that fails here is a liability.

Invented facts. If the record has no delivery scan, the letter must not mention one. If there is no signature, the letter must not say the parcel was signed for. A made-up claim can be checked against the carrier and issuer records, and it damages the rest of your response.

Accusations. "The customer is committing friendly fraud" is a conclusion you cannot prove. "We have no record of contact before the dispute" is a fact you can.

Legal claims. Citing statutes or implying a legal duty belongs to a lawyer. We are not lawyers, and neither is your software.

Statements about the customer's intent. You do not know what the customer meant. State what your records show.

Exaggerated certainty. "Definitively delivered" is worse than "the carrier record shows delivery". Say what the record says.

Evidence is final once submitted, which means an error in a letter stays. That is why a generator should show you the draft and wait.

How do you review a generated letter in three minutes?

Use this checklist every time. It is the same whether the draft came from a tool, a template or your own hand.

Names and numbers. Order number, amount, dates and the customer's name all match the order in Shopify.
Every claim has a file. Each factual sentence points to something attached. Cut any sentence that does not.
Missing items are missing. If a delivery photo does not exist, the draft does not mention one.
Dates in order. The timeline runs from order to dispute with no gaps and no contradictions.
Tone. No accusation, no capitals, no threats.
Length. About a page. If it is longer, cut.
Policy timing. The policy attached was the one in force on the order date.
Close. One clear request.

If the draft passes all eight, send it. If two or more fail, the case itself may have a problem the letter is exposing, and it is worth asking whether to accept instead.

Illustration: a not received letter, before and after

An order for $72 shipped by USPS on 8 September and the carrier record shows delivery on 12 September. The customer disputes it as not received. These details are made up for illustration.

A weak letter:

This customer is lying. We sent the package and it was delivered. We have been in business for years and have never had a problem. Please side with us. The tracking proves it.

It states a conclusion, accuses the customer, offers no dates, names no files and asks for sympathy. The reviewer learns nothing they can check.

A strong letter:

The cardholder disputes order 4821, placed on 8 September 2026 for $72.00, as not received. The order contained one ceramic mug and shipped on 8 September by USPS, tracking 9400 1000 0000 0000 0000 00, to the address on the order. File 1, the carrier record, shows delivery on 12 September at 2:14 pm to that address. We have no record of contact from the customer before the dispute was filed on 29 September. Our shipping policy, File 2, was linked at checkout. We ask that the dispute be resolved in the merchant's favor.

It states the claim, the facts, the file and the request in about 90 words. Nothing in it asks the reviewer to take the merchant's word.

The second letter wins more often, not because of better writing but because it points at evidence a reviewer can check. We cannot say how often, and we will not guess a win rate.

Illustration: the time a generator saves on 30 disputes a month

A store sees 30 disputes a month and values its time at $30 an hour. Assume writing the letter by hand takes 10 minutes of the 35 minute total, and that reviewing a generated draft takes 2 minutes. These are assumptions.

Item	Calculation	Result
Letter time by hand	30 x 10 min	5.0 hours
Letter review time with a generator	30 x 2 min	1.0 hour
Hours saved on letters alone	5.0 - 1.0	4.0 hours
Value of time saved	4.0 x $30	$120
Plan (Growth, 100 filings)	fits 30 filings	$49
Net value on letters alone	$120 - $49	$71

That counts only the writing. It ignores the time saved gathering evidence, which is the bigger share of the 35 minutes. It also ignores the quieter benefit, which is consistency. When the tool writes in the same structure every time, your worst-tired Friday letter reads as well as your best Monday one.

With a smaller volume the picture changes. A store with 10 disputes saves 80 minutes on letters, worth about $40, so the $19 Starter plan still clears but the margin is thin. A store with 2 disputes a month can use the Free plan, which covers 2 filings, and write them by hand if it prefers.

Illustration: an honest letter on a mixed case

A customer disputes a $140 order as not received. The carrier record shows delivery to the right address, but there is no signature and the customer wrote to you two days after delivery saying the box was empty. That message is in your inbox. You replied offering a replacement and heard nothing back.

This case is mixed. The delivery is documented. The complaint is also documented. An honest letter includes both.

The cardholder disputes order 5107 for $140.00 as not received. The order shipped on 3 October by UPS and the carrier record (File 1) shows delivery to the order address on 6 October. On 8 October the customer wrote that the box arrived empty (File 2). We replied on 8 October offering a replacement or refund (File 2) and received no further response. The shipment weight recorded at dispatch was 2.4 lb and the carrier-recorded delivery weight was 2.4 lb (File 3). We ask that the dispute be resolved in the merchant's favor.

Whether to submit depends on the evidence strength. Delivery is shown, the weight matches and the customer was offered a remedy and did not take it. That is a reasonable case. But a different set of facts, say a lighter delivery weight or a damaged box photo, would change the answer, and a letter that hid the customer's message would be both dishonest and easy to rebut.

A good generator includes the unhelpful fact, and a good reviewer lets it. If the fight is not worth it, the tool should say so rather than write a letter that pretends otherwise.

What do bad generated letters look like?

You can spot weak output quickly.

Generic openings. "We respectfully submit the following evidence in response to the claim" says nothing about this case.
Facts that appear from nowhere. Weights, times or signatures that are not in your records.
Repetition. The same sentence in the summary, the timeline and the close.
Mismatch with the reason. A fraud letter that talks about shipping, or a not received letter that talks about account history.
Over-polish. Long, flowing paragraphs where a table of dates would do.

If you see any of these, the tool is working from a template, not from your records.

Common mistakes in dispute letters

Arguing instead of showing. Adjectives do not win cases. Dates, scans and policies do.
Writing for yourself. The reviewer does not know your store, your product or your customer. Spell out what a stranger would need.
Letting the letter contradict the files. A letter that says "delivered 12 September" next to a scan dated 14 September undermines you.
Attaching today's policy. If you changed your policy since the order, say which version applied and attach that one.
Hiding bad facts. If the customer wrote to you, mention it. The bank may see it anyway.
Pasting the same letter for every reason. Each reason has its own question.
Sending without reading. Evidence is final. Read the draft once through, out loud if you can.
Treating the letter as the evidence. It is not. It is the guide to the evidence.

How does ChargeFix draft a letter?

ChargeFix drafts the letter from your Shopify records, matched to the dispute reason on the case, and shows it to you before anything is sent.

It writes from records. Dates, amounts, addresses, tracking events and refund details come from your order data. If a record is missing, the draft does not claim it.

It shapes the letter to the reason. A fraud case emphasizes history and matched data. A not received case emphasizes the delivery record. A refund case emphasizes the refund date.

It scores the evidence alongside. Each case gets an evidence strength score and a worth-fighting verdict, so the letter is one part of a decision, not the whole of it.

You approve before it goes. Manual mode is the default. Automatic mode is available on Starter and above for routine cases. We explain how to choose in our post on automatic vs manual chargeback response.

It never takes a cut of wins. Plans are flat: Free with 2 filings, Starter at $19 for 25, Growth at $49 for 100 and Scale at $99 for unlimited, with a 14-day trial on paid plans. A dispute counts as one filing the first time its evidence is saved or filed, and usage resets on the 1st of each month.

It has limits. ChargeFix works with Shopify Payments only. It does not prevent disputes or send alerts, and it is new, with no public reviews yet. Customer data is read during review and is not saved. We would like you to judge the drafts on your own cases rather than on our description.

For the wider picture of what gets assembled around the letter, read our guide to the Shopify chargeback evidence generator.

Can you improve a generated letter by editing it?

Yes, and you should. Editing takes minutes and makes the letter yours.

Add what only you know. If you spoke to the customer by phone and noted it in the order, add the date and the gist.
Remove what you cannot stand behind. If a sentence feels like a stretch, cut it.
Tighten. Shorter usually reads stronger.
Keep the structure. Resist the urge to reorder the six parts. The reviewer expects the claim first and the request last.

If you find yourself rewriting most of every draft, the issue is probably thin records, not the writing. Check what the tool could see.

Should you ever skip the letter?

Rarely, but yes. If the evidence is a single clear file, such as a refund record with a date before the dispute, a one line note can do the job. Most bank reviewers read the files anyway.

What you should not skip is the decision about whether to respond. Accepting a dispute is final. Shopify's help pages say the amount goes to the customer and the fee is not refunded, and there is no appeal. If the evidence is thin and the order is small, accepting is a fair choice. See our guide to the break-even point of a chargeback app for the arithmetic.

What we checked, and what you should check

We read Shopify's developer documentation for the dispute evidence update input and file types, Shopify's help pages on the chargeback process, chargeback.io's Visa reason code guide, Redo's guide to Compelling Evidence 3.0 and Redo's estimate of manual dispute time, all on 30 October 2026. Redo and chargeback.io sell related products, so we treat their figures as claims. We did not find a published rule on letter length or on how reviewers read responses, so the structure and length guidance is our own reasoning. The sample letters are illustrations and contain made-up details.

The order values, dispute counts, hourly values and the 10 and 2 minute letter times are our assumptions. Run your own figures in the chargeback cost calculator. Check Shopify's live help pages for your due date and fee before you rely on them.

Frequently asked questions

What is a Shopify chargeback response letter?

It is the written narrative you submit with your evidence files in response to a dispute. It states what the customer claims, the facts in date order, which attached files prove them and what you ask the bank to decide. It sits in a text field on Shopify's evidence form and is usually the first thing a reviewer reads.

How long should a chargeback response letter be?

We found no published rule, so this is our guidance: about one page, 250 to 450 words, with the proof carried by the attached files. Simple cases such as a refund issued before the dispute can be much shorter. If a letter runs past a page, it usually means the writer is arguing instead of showing.

Can an AI-written letter hurt my case?

It can if it states things your records do not support. A reviewer can compare the letter with carrier and transaction data, and a contradiction damages the rest of your response. A letter drafted only from real records and reviewed by you is safe. A letter that invents a signature or a delivery is not.

Should I accuse the customer of fraud in the letter?

No. You rarely know the customer's intent, and an accusation you cannot prove weakens the response. State what your records show, such as matched addresses, order history or the absence of contact before the dispute. Let the evidence make the point without a verdict on the person.

Can I edit a generated letter before it is submitted?

Yes, and you should review it. Evidence is final once submitted, so check names, amounts and dates, confirm every claim has a file, remove anything you cannot support and tighten the wording. In ChargeFix's default Manual mode, nothing is sent until you approve it.

Do I need a different letter for each dispute reason?

Yes. Each reason asks a different question. A fraud letter leans on history and matched data, a not received letter on the delivery scan, a credit not processed letter on the refund date and a subscription letter on consent and billing terms. A single letter for every case answers the wrong question much of the time.

What if I have no evidence to attach?

Then the letter cannot help much. Shopify submits a default response with order data on the due date if you submit nothing. For a small order with no supporting records, accepting is often the sensible choice. For future orders, save policies, tracking and customer messages so there is something to point to.

Does a better letter lower my dispute rate?

No. Writing a better response happens after the dispute is filed, and card network monitoring counts disputes whether you win or lose. Lowering the rate takes prevention, such as clear listings, fast refunds, honest delivery dates and good records. A letter helps you win back money on cases worth fighting.

What should I do first?

Take your last three disputes and rewrite each response using the six part structure: summary, order facts, timeline, proof by file, policy and request. Notice where you had no file to point to. Fix the most common gap first, then try a generator on live cases and compare the drafts with your own.

Start free trial with ChargeFix

If you want response letters drafted from your real records, shaped to each dispute reason and shown to you before anything is sent, ChargeFix starts free and moves to flat monthly plans as your volume grows. It never takes a cut of what you win. It checks your order evidence item by item, tells you honestly whether a case is worth fighting and leaves the final call with you. Nothing goes to the bank until you say so, and paid plans include a 14-day free trial.

Start free trial

Shopify chargeback response letter generator: the structure, tone and sample letters that hold up