The dispute landed on a Tuesday in May, eleven weeks before the product existed. The maker had been honest about everything. The product page said "Ships late July." The confirmation email said it again. The customer had paid in March anyway, happily, the way people do when they want to be first. Now a bank was asking him to prove he had delivered something he had never promised to deliver yet. For a strange moment he felt accused of a crime he was still in the middle of not committing.

Here is what nobody tells you about pre-order chargebacks: the customer is almost never disputing the product. They are disputing the silence between the charge and the box. Once you understand that, the dispute stops being an insult and becomes something you can prevent, and when you can't prevent it, something you can win.

The dispute that arrives before the box

Pre-orders and backorders share an awkward structure. The money moves on day one. The product moves on day ninety. Stripe, like every card processor, charges the card when you create the payment, and a plain authorization hold only lasts about a week on most cards, so you cannot simply "reserve" the funds until you ship. The charge is real and immediate. The fulfillment is a promise.

From the customer's side, the promise fades faster than the charge. In March they were excited. By May the excitement has worn off, the statement arrives, and there is a line item with your name on it and nothing on the porch. They don't remember the ship date. They may not remember agreeing to one. They call the bank and choose the option that fits: product not received.

From the reviewer's side, it looks worse than it is. A bank analyst sees a charge date, no tracking number, and a cardholder who says nothing came. On paper, that is the exact silhouette of a merchant who took the money and vanished. Your job in a pre-order dispute is to replace that silhouette with a timeline.

Why waiting hurts more than it should

In 1985, the Harvard Business School professor David Maister published an essay called "The Psychology of Waiting Lines," and it has aged uncomfortably well. Three of his observations describe a pre-order customer almost perfectly. Uncertain waits feel longer than known, finite waits. Unexplained waits feel longer than explained waits. And anxious waits feel longer than calm ones.

A pre-order with no updates hits all three at once. The customer has no visible progress, no explanation for the gap, and a growing low-grade anxiety that they have been taken. Layer loss aversion on top. The money is a loss that has already happened, sitting right there on the statement. The product is a gain that might happen, someday. Every week of silence shifts that balance a little further toward the loss.

So the dispute is rarely fraud in the way merchants imagine it. It is an exit from an uncomfortable emotional state. The customer isn't trying to get a free product. They are trying to stop feeling exposed. This matters because the fix for exposure is not a sterner refund policy. It is information, delivered before they go looking for it.

The rule that's quietly on your side

Card network dispute rules were written with this exact scenario in mind, and they lean toward you more than you might expect. For a "merchandise not received" dispute, both Visa and Mastercard generally require the cardholder to have waited until the agreed delivery date has passed before filing. A dispute raised before a clearly disclosed ship date is premature under those rules, and reviewers accept that argument when the date is documented and obvious.

The key word is disclosed. You cannot invent the date after the fact. It has to have been in front of the customer before they paid, in language a hurried person would notice.

There is a second rule, and it cuts both ways. In the United States, the Federal Trade Commission's Mail, Internet, or Telephone Order Merchandise Rule says you must have a reasonable basis for any ship date you advertise. If you don't state one, the rule assumes thirty days. If you cannot meet the date, you must notify the customer, give them a revised date, and offer the option to cancel for a full refund. A stated, honest date protects you. A missed date with no notice exposes you, and no amount of rebuttal writing will fix it.

Which leads to the honest part. If your disclosed ship date has passed, you haven't shipped, and you never told the customer, do not fight the chargeback. Refund it, apologize, and fix the process. A dispute you deserve to lose is not worth the fee or the hit to your dispute rate. Fight the early ones. Own the late ones.

What the reviewer needs to see

A bank analyst spends minutes on your case, not hours. Your evidence should make the timeline impossible to miss. Lead with a short narrative, two or three sentences, that states the three dates: when the customer bought, when you told them it would ship, and when they disputed. For example: "The customer purchased a pre-order on March 3 with a disclosed estimated ship date of late July. The dispute was filed on May 12, before the disclosed date. The order remains on schedule." That paragraph does more work than any attachment.

Then back it up with records that prove each date existed before the money moved:

  • A screenshot of the product page as it looked at the time of purchase, with the ship date visible near the buy button. If you didn't capture one, your site's version history or the Internet Archive's Wayback Machine may have a snapshot.
  • The order confirmation email, showing the ship date repeated in the body and ideally the subject line.
  • Every update email you sent since, with send timestamps, showing the wait was explained.
  • The order's current status: the production batch it belongs to, the expected ship window, or tracking if it has shipped since the dispute opened.

Resist the urge to attach your whole terms page. A reviewer who has to hunt for the ship date inside two thousand words of policy will stop hunting. Highlight the one line that matters, and let everything else support it.

Your next moves

  • Put your ship date in three places today: on the product page directly above the buy button, as a line in checkout, and in the subject line of the confirmation email. "Pre-order: ships late July 2026" is enough.
  • Take a dated screenshot of the product page with the ship date visible and file it with the date in the filename. Repeat every time the date changes. Future disputes are won with this file.
  • Schedule a status email to every open pre-order customer every three to four weeks, even when nothing has changed. "Still on track for late July" is the whole message. Maister's research says an explained wait feels shorter, and a customer who hears from you doesn't go looking for the dispute button.
  • If the date slips, send the notice the FTC rule describes: the new date, plus a one-click way to cancel for a full refund. Keep a copy of what you sent and when. That email is your defense in any dispute filed afterward.
  • Open your Stripe disputes list, find every open case tied to a pre-order, and sort it by one question: has the disclosed ship date passed? Fight the ones filed early. Refund the ones where you are late and never said so.

When the clock is shorter than your production run

The cruel detail of a pre-order dispute is that you have months to build the product and about a week to defend the charge. Stripe gives you a seven-day window to respond, and it tends to open while you're buried in the exact work the customer is waiting for. That is where Argeback fits. It pulls in the dispute, assembles the timeline from your order data and the records you've been keeping, drafts the evidence-backed response, and files it before the deadline, from your phone, between whatever else the week throws at you. Keep making the thing. Let the dispute get answered anyway. You can see how it works at argeback.lumenlabs.works.