Chargebacks Dispute: The Physical Goods Merchant Playbook for Mixed-Signal Cases

When the signals contradict each other, the default response loses

A chargeback lands in Shopify Admin under Orders > Disputes. The tracking shows delivered. The AVS result is a partial match. The shipping address is a freight forwarder. The cardholder says they never received the item. You have three pieces of evidence pointing in three different directions.

Most merchants in this position do one of two things: submit everything and hope the issuer figures it out, or concede because the case looks too messy to win. Both are wrong. Mixed-signal disputes are winnable — but only if you diagnose the contradiction before you build the response.

This playbook is for physical goods disputes where the evidence stack is internally inconsistent. Not clean wins. Not obvious fraud. The cases where something is true and something else is also true and they don't line up.

Step 1: Name the contradiction before you touch the evidence

Pull the dispute from Shopify Admin and write down — literally, in an internal note — what the contradiction is. Not what the evidence shows. What the contradiction is.

Common contradiction types in physical goods disputes:

• Delivery confirmation vs. address mismatch: Carrier confirms delivery, but the address on file doesn't match the billing address and the cardholder says they didn't order it.
• AVS partial match vs. fulfilled order: AVS returned Y on street but N on ZIP. You fulfilled anyway. Now the cardholder claims unauthorized.
• Reshipper address vs. legitimate customer: The shipping address resolves to a known freight forwarder. The order behavior looks like a real customer. The dispute reason is "not received."
• Delivery photo vs. wrong location: Carrier uploaded a delivery photo, but the photo shows a door that doesn't match the address on the order.

If you can't name the contradiction in one sentence, you're not ready to build a response. The issuer will find it. You need to find it first.

Step 2: Map the reason code to what the contradiction actually affects

The reason code tells you what the cardholder is asserting. The contradiction tells you where your evidence breaks down. These are not the same question.

A Visa 13.1 (Merchandise Not Received) dispute with a reshipper address is not primarily a delivery problem — it's an authorization-intent problem. The issuer isn't asking whether the carrier delivered. They're asking whether the person who placed the order was the cardholder. Your delivery confirmation doesn't answer that question.

A Visa 10.4 (Other Fraud — Card Absent) dispute with full AVS match and a delivery photo is not primarily a fraud problem — it's a possession problem. The issuer is asking whether the cardholder received the goods. Your AVS result doesn't answer that either.

Match the contradiction to the reason code. Then identify which piece of evidence actually answers the issuer's question — and which pieces are noise.

Submitting noise alongside signal doesn't strengthen the case. It dilutes it. Issuers reading a 12-attachment response with three irrelevant screenshots are less likely to find the one attachment that matters.

Step 3: Check the fulfillment record in Shopify Admin for timeline gaps

Go to Orders > [Order] > Timeline in Shopify Admin. Look at the gap between payment capture and fulfillment. Look at the gap between fulfillment and the dispute date.

Two things to flag:

1. Long fulfillment delay: If the order was captured and sat unfulfilled for more than a few days before shipping, the issuer may treat that as a fulfillment failure regardless of eventual delivery. This is especially damaging in "not received" disputes where the cardholder may have legitimately contacted you during the delay.
2. Dispute filed before estimated delivery: If the dispute date precedes the carrier's estimated delivery window, the cardholder may have filed prematurely — or the order was never going to arrive. Either way, your response narrative needs to address the timeline explicitly, not just attach the tracking number.

A merchant shipped a $215 home goods order with standard carrier tracking. Delivery was confirmed 11 days after order. The dispute was filed on day 9. The merchant submitted tracking confirmation showing delivery and lost — because the issuer saw a dispute filed before delivery and a merchant who never addressed the timeline discrepancy. The tracking was real. The response was incomplete.

Decision point: Fight on delivery or fight on authorization

This is the most consequential choice in a mixed-signal physical goods dispute, and most merchants don't realize they're making it.

Path A: Fight on delivery. You assert the goods were delivered as described. Your evidence centers on carrier confirmation, delivery photo, tracking history, and address match. This path works when the contradiction is addressable — when you can explain the reshipper address, the partial AVS, or the delivery photo discrepancy in a way that holds up. It fails when the contradiction is the core of the dispute and you can't resolve it.

Path B: Fight on authorization. You assert the transaction was authorized by the cardholder, regardless of what happened to the goods after delivery. Your evidence centers on AVS result, IP geolocation, device fingerprint, order history, and behavioral signals. This path works when the cardholder's claim is implausible given the authorization signals — when the order behavior, billing address, and account history all point to a legitimate cardholder who is now disputing a purchase they made. It fails when the authorization signals are weak or contradictory.

Trying to fight both simultaneously is the most common mistake. A response that says "the goods were delivered AND the transaction was authorized" without a coherent narrative connecting them reads as defensive noise. Pick the stronger path. Build the narrative around it. Reference the other signals only as supporting context, not as co-equal arguments.

Step 4: Build the narrative before you attach anything

Write the response narrative in plain text before you open a single file. The narrative is not a list of what you're attaching. It's a one-to-three paragraph explanation of what happened, why the evidence supports your position, and — critically — how you're accounting for the contradiction.

If you can't write the narrative without mentioning the contradiction, you're not ready to submit. If you can write it and it sounds defensive, rewrite it until it sounds factual.

Sample narrative line for a reshipper address dispute where you're fighting on authorization:

"The order was placed using a billing address that matches the cardholder's card-on-file address (AVS full match). The shipping address is a freight forwarding service, which is consistent with international customers who use forwarding addresses for domestic US purchases. The account used to place this order has a 14-month purchase history with no prior disputes. The cardholder's assertion of unauthorized use is inconsistent with the authorization signals and account history on record."

That narrative does three things: it acknowledges the reshipper address directly, it contextualizes it without dismissing it, and it redirects the issuer's attention to the authorization signals. It doesn't pretend the contradiction doesn't exist.

Sample internal note before closing the workflow:

"Mixed-signal case: reshipper address + full AVS match. Fighting on authorization. Attached: AVS result, order history (14 months, 0 disputes), IP geolocation matching billing ZIP. Did not attach delivery confirmation — it's irrelevant to the authorization argument and the address mismatch would undercut it."

Step 5: Sequence the evidence in issuer-readable order

Issuers are not reading your evidence the way you assembled it. They're scanning. The first attachment they open gets the most weight. The last attachment rarely gets read at all.

Sequence rule for mixed-signal cases: lead with the evidence that directly answers the issuer's question, not the evidence that's easiest to find.

If you're fighting on authorization: lead with the AVS/CVV result, then account history, then behavioral signals. Do not lead with tracking confirmation — it answers a different question and primes the issuer to evaluate delivery, not authorization.

If you're fighting on delivery: lead with the carrier confirmation and delivery photo, then the order confirmation with shipping address, then any customer communication acknowledging the order. Do not lead with the AVS result — it answers a different question and creates noise before you've made your delivery argument.

Keep the total attachment count under six. If you have more than six attachments, you have not finished diagnosing the case.

The $340 outdoor gear dispute that was winnable and wasn't

A merchant sold a $340 camping kit. The shipping address was a suite number at a UPS Store — a known mail forwarding location. AVS returned a full match on billing. Delivery was confirmed with signature. The dispute reason was Visa 10.4 (unauthorized).

The merchant submitted: order confirmation, tracking with signature, AVS result, a screenshot of the product page, and a copy of their return policy. Five attachments. The issuer ruled for the cardholder.

The problem: the merchant never addressed the UPS Store address. The issuer saw a delivery to a mail forwarding location, a cardholder claiming unauthorized use, and a merchant response that didn't acknowledge the address at all. The signature confirmation was at a UPS Store counter — not at the cardholder's residence. The AVS match was real, but the merchant's response didn't connect it to an authorization argument. The product page screenshot and return policy were irrelevant.

The winnable version of that response: a two-paragraph narrative acknowledging the forwarding address, explaining that AVS full match on billing indicates cardholder-initiated authorization, noting that forwarding addresses are common for gift purchases and international buyers, and attaching only the AVS result, the order confirmation showing billing address match, and the signature confirmation. Three attachments. One coherent argument. The contradiction addressed directly.

The merchant lost because they submitted evidence without a narrative. The issuer filled in the narrative gap with the cardholder's version.

When to concede instead of fight

Not every mixed-signal case is winnable. Concede when:

• The contradiction is the core of the dispute and you cannot resolve it with available evidence. A partial AVS match on a high-value order with a reshipping address and no account history is not a winnable authorization argument.
• The fulfillment timeline shows a gap that the cardholder could legitimately have complained about. If the order sat unfulfilled for eight days and the cardholder filed a dispute on day seven, the dispute may be operationally valid regardless of eventual delivery.
• The delivery photo doesn't match the address. Carrier confirmation with a photo of the wrong door is worse than no photo — it confirms delivery to the wrong location.

Conceding early recovers the dispute fee in some processor setups — confirm with your processor whether early concession affects fee assessment. It also avoids a chargeback ratio hit from a lost fight. A lost dispute counts the same as a conceded one on your ratio, but a conceded dispute doesn't consume response time on a case you were going to lose anyway.

DisputeDesk surfaces the contradiction signals — mismatched addresses, AVS partial results, timeline gaps — during case intake so merchants aren't discovering them at submission. Automation improves consistency in flagging these cases; the decision to fight or concede still requires merchant judgment on the specific contradiction.