Shopify Inquiry vs Chargeback: How Misclassification Costs You the Dispute

They land in the same queue — and that's the problem

Both inquiries and chargebacks surface inside Shopify Admin under Orders, and both carry the word "dispute" in the interface. That's where the similarity ends. An inquiry is the issuer asking a clarifying question on behalf of the cardholder — no funds have moved, no chargeback fee has posted, and the merchant's account balance is untouched. A chargeback is a reversal: the funds are already gone, a fee has typically posted, and a hard response deadline is running. Treating an inquiry like a chargeback wastes the one thing inquiries actually give you — a low-stakes window to resolve the cardholder's question before it becomes a financial claim. Treating a chargeback like an inquiry is worse: you miss the deadline and forfeit automatically, before the issuer evaluates a single piece of evidence.

Inside Shopify Admin, check Orders > Disputes for the dispute type and status before doing anything else. The reason code and dispute type shown there determine which response path applies. Visa and Mastercard run different inquiry and chargeback processes; confirm the exact response windows and fee structures with your processor, because what Shopify surfaces may not reflect the acquirer's internal clock.

What each dispute type actually requires from you

Inquiries ask for clarification — a transaction description, a confirmation that the cardholder authorized the charge, a copy of the receipt. The goal is to answer the cardholder's question clearly enough that the issuer closes the inquiry without escalating. Submitting a full evidence package — tracking numbers, delivery confirmation, AVS match data — is not just unnecessary; it signals to the issuer that you've misread the dispute type, and it does nothing to address the cardholder's actual question.

Chargebacks require evidence that directly rebuts the dispute reason code. A fraud dispute needs proof of authorization. A "not received" dispute needs proof of delivery to the cardholder's address, not just a carrier scan. A "not as described" dispute needs documentation of what was sold and what was delivered. The evidence has to match the reason code — a delivery confirmation doesn't save a fraud dispute, and an authorization record doesn't save a "not received" claim. Chargeback evidence is also time-sensitive in a way inquiry responses are not: miss the deadline and the reversal stands regardless of how strong your evidence is. Inquiry timelines are more flexible, but ignoring an inquiry is not a safe default — unaddressed inquiries escalate to chargebacks, at which point the merchant loses the clarification window and inherits a hard deadline instead.

Chargebacks immediately affect merchant accounts: funds reversed, fee posted, dispute ratio incremented. Inquiries carry none of that direct financial impact — they're a communication channel, not a reversal mechanism. That distinction matters for financial reconciliation too. Resolved inquiries and resolved chargebacks need to be documented separately; conflating them skews your dispute records and makes win-rate analysis unreliable.

How a $75 inquiry became a $75 chargeback — and why it didn't have to

An apparel merchant with a $75 average order value received an inquiry on May 5th. A customer was questioning a $75 charge for a shirt — not disputing it as fraud, not claiming non-delivery, just asking for clarification on the charge. The inquiry notification arrived in Shopify Admin on May 6th. The merchant, monitoring primarily for chargebacks, read the alert quickly and assumed it was a chargeback filing.

On May 8th, the merchant submitted a response package: delivery tracking number, order confirmation email, and a customer service communication log. That's a reasonable chargeback evidence set for a "not received" dispute. For an inquiry about a charge the cardholder didn't recognize, it answered the wrong question entirely. The cardholder's question — what is this charge for? — went unanswered. The issuer received a delivery confirmation instead of a transaction explanation.

On May 15th, the inquiry escalated to a chargeback. The $75 reversed. A chargeback fee posted. The merchant now had a hard deadline and a dispute on record — both of which were avoidable. The evidence the merchant had submitted ten days earlier was still available, but it was still the wrong evidence for the wrong dispute type. A clarification response on May 6th — transaction description, itemized receipt, confirmation of authorization — would likely have closed the inquiry before it escalated.

The merchant had the right documentation. The failure was classification, not evidence. That's the pattern: merchants who monitor primarily for chargebacks miss inquiries until they've already escalated, then fight the chargeback with evidence that was never the point.

Decision lesson: This case was fightable at the inquiry stage with a one-paragraph clarification. It became a chargeback because the merchant applied a chargeback response to a pre-dispute question. The rule: classify before you respond. If the dispute type is inquiry, answer the cardholder's question. If it's a chargeback, match your evidence to the reason code and meet the deadline.

What to check in Shopify Admin before you submit anything

Work through this before touching the response form. First, open Shopify Admin > Orders > Disputes and confirm the dispute type — inquiry or chargeback — and the reason code. Do not assume based on the notification email alone; check the detail screen. Second, if the merchant account uses Shopify Payments, check whether Shopify Protect has flagged the order as PROTECTED — this affects whether Shopify covers the reversal, but it does not change your response obligation or deadline. Third, confirm the response deadline with your processor directly; Shopify may display a deadline that doesn't match the acquirer's internal window, and the acquirer's clock controls. Fourth, match your planned response to the dispute type: clarification content for inquiries, reason-code-specific evidence for chargebacks. Fifth, verify that any delivery proof you're including actually demonstrates cardholder receipt at the correct address — a carrier scan to a zip code is not the same as confirmed delivery to the billing address. Sixth, decide whether to fight or accept. On a $75 dispute with weak delivery proof, the math on fighting a chargeback may not hold; on an inquiry with a clear transaction record, a two-minute clarification response is almost always worth sending. DisputeDesk automation can identify dispute type and surface relevant evidence fields, but the classification call and the response strategy are yours to confirm before submission.