Shopify Inquiry vs. Chargeback: Two Different Clocks, Two Different Playbooks

Same queue. Different clock. Different stakes.

When a dispute appears in Shopify Admin under Orders → Disputes, the label doesn't always tell you what you're actually dealing with. An inquiry and a chargeback can sit in the same list view, carry similar language, and still require completely different responses — on different timelines, with different reversibility, and with different consequences for getting it wrong.

Most merchant teams treat them identically. That's the operational failure. An inquiry handled like a chargeback wastes response time and often escalates a situation that could have been resolved with a single customer email. A chargeback handled like an inquiry — with the relaxed urgency of a clarification request — expires before evidence is submitted.

Here's how to tell them apart immediately, and what to do differently for each.

Step 1: Identify what you're actually looking at

In Shopify Payments, disputes surface under Orders → Disputes. The dispute type field — visible when you open the dispute detail — will show either Inquiry or Chargeback. Do not skip this field. It determines everything that follows.

If you're on a third-party gateway (Stripe, Braintree, PayPal, etc.), the same distinction exists but may be labeled differently — "retrieval request," "pre-dispute," or "inquiry" depending on the processor. Confirm the terminology with your gateway. The operational logic below applies regardless of label.

Inquiry: The issuer is asking for documentation before deciding whether to file a formal dispute. Funds have not moved. No chargeback has been initiated. The issuer wants clarification — a receipt, a shipping confirmation, a policy screenshot — and is giving you a window to provide it.

Chargeback: The issuer has already moved funds back to the cardholder. The dispute is formal. You are now in a representment process with a network-enforced deadline. Evidence must be submitted or the case defaults against you automatically.

The practical difference: with an inquiry, you can still prevent the chargeback from ever happening. With a chargeback, you're already fighting to recover funds that have left your account.

Step 2: Lock the deadline — and understand why inquiry windows are more dangerous

Chargeback response windows are widely discussed. Inquiry windows are not — and they're shorter than most merchants expect.

Typical inquiry response windows run 20–30 days from issuance, but some issuers push tighter internal cutoffs. Visa's pre-dispute (Visa Resolve Online / VROL) window is often 20 days. Mastercard's pre-arbitration inquiry windows vary. Confirm the exact deadline with your processor — do not assume the window matches your chargeback window.

The dangerous part: if you miss an inquiry deadline without responding, the issuer typically auto-converts it to a formal chargeback. You've now lost the low-stakes window and entered the high-stakes one — with less time remaining and funds already reversed.

Set your internal cutoff two business days before the network deadline for both dispute types. For inquiries, treat that internal cutoff as the hard submission date — not a buffer.

Internal note template:
"Inquiry received [date]. Network deadline: [date]. Internal cutoff: [date minus 2 business days]. Assigned to: [name]. Risk of auto-conversion if missed."

Step 3: Read what the issuer is actually asking — the response logic is different

A chargeback response is built around a reason code. The reason code tells you what the issuer's theory of the case is — fraud, item not received, not as described — and your evidence has to address that specific theory. The response is adversarial by design.

An inquiry is not adversarial yet. The issuer is asking a question. The cardholder may be confused about a charge, may not recognize the billing descriptor, or may be asking the bank to verify a transaction before deciding whether to dispute it. Your job is to answer the question clearly — not to build a litigation packet.

Over-responding to an inquiry is a real failure mode. A merchant who submits a 12-page evidence packet to an inquiry asking for a receipt confirmation has wasted internal resources, potentially confused the issuer's review, and still hasn't resolved the underlying customer confusion that triggered the inquiry in the first place.

Read the inquiry reason carefully. If it's a recognition issue (cardholder doesn't recognize the charge), your response is: billing descriptor explanation, order confirmation, and a short narrative. If it's a delivery question, your response is: tracking confirmation and delivery timestamp. Match the response to the question — not to your worst-case chargeback scenario.

Decision point: Respond with documentation, or resolve directly with the customer?

This is the most operationally significant fork in the inquiry workflow, and most merchants skip it entirely.

Path A — Respond through the dispute channel with documentation. You submit evidence to the issuer. The issuer reviews it and either closes the inquiry or escalates to a chargeback. You retain the sale if the issuer is satisfied. Risk: if the cardholder is genuinely dissatisfied (not just confused), the inquiry closes but a chargeback follows days later anyway — now with a shorter response window.

Path B — Contact the customer directly and resolve before the inquiry closes. If the inquiry signals a dissatisfied customer rather than a confused one, proactive outreach can close the loop without the issuer ever escalating. A refund or replacement offered directly — before the chargeback — costs you the transaction but saves the dispute fee, the chargeback ratio hit, and the operational overhead of a formal response.

The signal that points toward Path B: the inquiry reason suggests a product or service complaint, not a recognition or authorization question. If the cardholder told the bank "I didn't get what I ordered" or "the item was wrong," the inquiry is a preview of a SNAD or INR chargeback. Resolve it now.

The signal that points toward Path A: the inquiry is a recognition question ("I don't recognize this charge"), the order has clean delivery confirmation, and there's no prior customer complaint on record. Submit documentation and close it.

Customer outreach line for Path B:
"Hi [name] — we saw a question come through on your recent order and wanted to reach out directly. We'd like to make this right before anything escalates. Can you tell us what happened with your order?"

Do not mention the word "chargeback" or "dispute" in customer outreach. It signals awareness of the bank process and can accelerate escalation.

Step 4: Build the inquiry response — shorter than you think, faster than you want

For an inquiry, the evidence package is lean. Three to five documents maximum. Anything more suggests you misread the inquiry type.

For a recognition inquiry: order confirmation with billing descriptor match, IP/device match if available, AVS/CVV result from the authorization. One paragraph of narrative explaining what the charge was for.

For a delivery inquiry: fulfillment confirmation from Shopify (pull from Orders → [Order] → Fulfillment), carrier tracking with delivery timestamp, and the shipping address confirmed at checkout. If signature was collected, include it.

For a policy inquiry (cardholder asking about a return or cancellation): screenshot of the policy as it appeared at checkout, order confirmation showing policy acknowledgment if captured, and a timeline of any customer communications.

Evidence narrative line for a recognition inquiry:
"The charge appearing as [descriptor] on the cardholder's statement corresponds to Order #[XXXX] placed on [date] at [store URL]. The order was fulfilled on [date] and delivered to the address provided at checkout on [date], per carrier confirmation [tracking number]."

Step 5: Build the chargeback response — different logic entirely

Once you've confirmed you're looking at a chargeback (not an inquiry), the workflow shifts. Funds are already reversed. The reason code is the controlling document. Evidence must be reason-code-specific, not generic.

Pull the reason code from the dispute detail in Shopify Admin. Visa and Mastercard reason codes map to specific issuer expectations — what you need to prove for a Visa 10.4 (unauthorized transaction) is structurally different from what you need for a Visa 13.1 (item not received). Submitting the wrong evidence type for the reason code is a common loss that has nothing to do with the underlying facts of the order.

The chargeback response also has a harder deadline structure. Visa's standard merchant response window is 20 days from dispute initiation. Mastercard varies by reason code — confirm with your processor. Missing the deadline means automatic loss regardless of evidence quality. The issuer never reads a late submission.

One thing that trips up teams who handle both inquiry and chargeback in the same workflow: the inquiry response you already submitted does not carry over into the chargeback. If an inquiry escalates to a chargeback, you start the evidence process again — from scratch, under the chargeback deadline, with the reason code now controlling what you submit.

The $112 accessories order that converted — and what the team missed

A merchant selling phone accessories received an inquiry flagged as a recognition dispute. The cardholder's bank sent a pre-dispute notification through Visa Resolve Online. The merchant's team, seeing it in the dispute queue alongside active chargebacks, treated it as a lower-priority item and queued it for the following week's review cycle.

The inquiry window closed without a response. Four days later, a formal Visa 10.4 chargeback appeared for the same $112 order. The merchant now had 20 days to respond — but the order had clean delivery confirmation, AVS match, and a device fingerprint consistent with the cardholder's prior purchase history. It was a winnable case.

They submitted the evidence. The issuer ruled against them anyway. The reason noted in the processor's response memo: the cardholder had escalated the complaint during the inquiry gap, and the issuer's internal record showed no merchant response to the pre-dispute inquiry — which the issuer read as non-engagement. The evidence was sufficient. The process failure wasn't.

The operational fix was simple: separate the inquiry queue from the chargeback queue in their internal tracking sheet, assign inquiries a 48-hour first-review SLA, and flag any inquiry without a response logged within five business days for immediate escalation.

Where the workflows overlap — and where they don't

Both inquiry and chargeback responses benefit from the same underlying evidence: order confirmation, fulfillment data, delivery confirmation, customer communication logs. Pull all of it regardless of dispute type. The difference is in selection and framing.

For an inquiry: select the minimum evidence that answers the issuer's specific question. Frame it as clarification, not defense.

For a chargeback: select evidence that directly addresses the reason code's burden of proof. Frame it as a factual rebuttal to the cardholder's claim.

Automation can help with evidence assembly for both — pulling order data, fulfillment records, and tracking confirmations from Shopify into a structured package. But the triage decision (inquiry vs. chargeback, Path A vs. Path B, fight vs. concede) requires a human read of the dispute detail. Automation improves consistency in evidence packaging; it doesn't replace the classification step that determines which playbook you're running.

DisputeDesk organizes the evidence pull for both dispute types, but the Path A / Path B decision on inquiries — and the fight/concede call on chargebacks — stays with the merchant team. Those decisions depend on customer relationship context and margin math that no automation layer has access to.

Step 6: Log both outcomes — not just the losses

Most merchants log chargebacks. Few log inquiries — especially the ones that resolved without escalating. That's a data gap.

Inquiry patterns tell you where customer confusion is concentrated: which products generate recognition questions, which billing descriptors are unclear, which fulfillment gaps trigger delivery inquiries. A merchant seeing ten inquiries per month on the same product category has a product page or descriptor problem, not a dispute problem.

Log every inquiry in the same system as chargebacks. Record: dispute type, reason, order value, resolution path (A or B), outcome (closed, escalated, refunded), and days to response. Review monthly. The inquiry log is an early warning system for chargeback volume — it shows you what's about to become a formal dispute if nothing changes operationally.