Shopify Chargeback Inquiry Playbook: Respond Before It Escalates

The inquiry window is shorter than the chargeback window — and merchants treat it like it's longer

A chargeback inquiry lands in Shopify Admin → Orders → Disputes looking nearly identical to a full chargeback. Same queue. Same dispute label. Different clock. Most issuers give you 20–30 days to respond to an inquiry; some Amex retrieval requests run as short as 10 business days. Miss the window and the issuer closes it as a chargeback automatically — no additional notice, no second chance to submit evidence.

The operational failure here isn't evidence quality. It's triage speed. Merchants who lose inquiry windows almost always had the evidence. They just didn't recognize the dispute type in time to act on it.

When an inquiry lands, do this — in order, before you pull a single screenshot.

Step 1: Identify the dispute type before you open the order

In Shopify Admin, open Orders → Disputes and check the dispute status field. Inquiries surface with a status of Needs Response and a reason that reads as a retrieval request or clarification — not a reversal. The dollar amount is flagged but not yet debited in most cases (confirm with your processor — Amex sometimes holds funds immediately even on retrievals).

If the reason code maps to a retrieval request (Visa uses Request for Information, Mastercard uses Retrieval Request, Amex uses Request for Documents), you're in inquiry territory. If it maps to a chargeback reason code — Visa 10.4, Mastercard 4853, Amex C08 — it's already a full dispute and the inquiry window has either passed or never existed.

Do not start building evidence until you've confirmed which one you're looking at. The response format differs. The deadline differs. The stakes differ.

Step 2: Lock the deadline — then set your internal cutoff two days earlier

Inquiry deadlines are not standardized across networks. Visa retrieval requests typically allow 30 days from issuance. Mastercard retrieval requests run 30 days as well, but the clock starts from when the acquirer receives the request — not when it surfaces in your Shopify Admin queue. That gap can cost you 3–5 days you didn't know you were losing. Amex document requests can run as short as 10 business days.

Pull the dispute creation date from the Shopify Admin dispute detail view. Then confirm the actual deadline with your acquirer or payment processor — Shopify Payments merchants can check the response deadline displayed in the dispute panel, but always cross-reference with your processor if the timeline feels compressed.

Set your internal response target two business days before the stated deadline. Carrier delays, internal approval loops, and evidence formatting all eat time you don't have at the end of the window.

Step 3: Read what the issuer is actually asking

Inquiries are not all the same request. The three most common types require different responses:

• Transaction verification: The cardholder doesn't recognize the charge. The issuer wants proof the transaction was authorized and the cardholder was the buyer. Submit order confirmation, billing address match, IP address, device fingerprint if available, and any customer communication referencing the order.
• Fulfillment verification: The cardholder claims non-receipt. The issuer wants proof of shipment and delivery. Submit tracking with carrier scan history, delivery confirmation, and the shipping address as entered at checkout.
• Merchant identity clarification: The billing descriptor on the cardholder's statement doesn't match your store name. The issuer wants to confirm who charged the card. Submit your DBA name, the descriptor as it appears on statements, and the order record tying the charge to the transaction.

Sending a full evidence packet when the issuer only asked for a descriptor clarification creates noise and doesn't help. Read the request, then respond to exactly what was asked — nothing more.

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

Before you submit anything to the issuer, check whether the customer has contacted you directly about this charge. If they have — and the inquiry is a recognition dispute — you have two paths:

Path A: Respond to the issuer with documentation. Submit the evidence packet, let the issuer close the inquiry in your favor, and do nothing further. This works when the cardholder is genuinely confused (billing descriptor mismatch, family member made the purchase) and you have clean authorization signals. The inquiry closes, no chargeback is filed, funds stay put.

Path B: Resolve directly with the customer first, then notify the issuer. If the cardholder has a legitimate complaint — wrong item, damaged goods, billing error — issue the refund or correction before the inquiry converts. Then submit documentation to the issuer confirming resolution. This path costs you the refund but avoids the chargeback fee, the dispute notation on your account, and the risk of losing a full chargeback later. For orders under $100, Path B is almost always cheaper even when you're confident you'd win.

The consequence of choosing Path A on a legitimately unhappy customer: they escalate, the inquiry converts to a chargeback, and you fight the same dispute with worse odds because the issuer now has a complaint history attached to the case.

The consequence of choosing Path B on a fraudulent inquiry: you've refunded a transaction you would have won. For high-value orders with strong authorization signals and no customer contact, Path A is correct.

Step 4: Build the response — what to actually include

For a transaction verification inquiry, the response narrative should be tight and specific. Generic submissions lose inquiries the same way they lose chargebacks.

Sample evidence narrative (adapt to your order):

"Order #[XXXX] was placed on [date] at [time] from IP address [X.X.X.X], which geolocates to [city, state] — consistent with the billing address on file. The billing address provided at checkout matches the card's registered address (AVS result: Y). The order confirmation was sent to [email] and opened at [timestamp]. The item shipped on [date] via [carrier], tracking [number], and was delivered on [date] with carrier confirmation. No cancellation or return request was received prior to this inquiry."

That's the full narrative. Don't pad it. Attach the supporting documents — order confirmation, AVS result, tracking with delivery scan, email open log if available — and submit.

For a descriptor clarification inquiry, the response is even shorter:

"The charge of $[amount] on [date] was processed by [your legal entity name], operating as [store name]. Our billing descriptor appears as '[DESCRIPTOR]' on cardholder statements. The attached order record confirms this transaction corresponds to Order #[XXXX] placed by the cardholder on [date]."

The $94 apparel inquiry that converted — and why it didn't have to

A Shopify merchant selling mid-range women's clothing received an inquiry flagged as a transaction verification request. The cardholder didn't recognize the charge — the store's billing descriptor read as a parent company name, not the brand. The merchant had a clean order: AVS match, email confirmation opened twice, delivery confirmed.

The merchant's ops team queued the response but waited for a manager to review the evidence packet. The review took four days. By the time the response was submitted, it was two days past the issuer's deadline. The inquiry auto-converted to a Visa 10.4 chargeback. The merchant then submitted the same evidence packet — and lost, because the issuer noted the inquiry had gone unanswered and weighted that against the merchant's credibility.

The evidence was never the problem. The merchant had everything needed to close this at the inquiry stage for zero fee exposure. The loss came from an internal approval loop that wasn't calibrated to inquiry timelines.

The fix isn't faster evidence. It's a triage rule: inquiries get a 24-hour internal response target, not a standard dispute workflow. They are not the same thing.

Step 5: Submit and log — don't just submit

After submitting the response through Shopify Admin's dispute response interface, create an internal note on the order. This matters more than most merchants realize. If the inquiry converts to a chargeback anyway — which can happen even after a timely response, particularly with Amex — your internal log becomes the starting point for the chargeback response. You won't have to reconstruct the timeline from scratch.

Sample internal order note:

"Inquiry response submitted [date]. Reason: transaction verification. Evidence submitted: order confirmation, AVS result, tracking + delivery scan, email open log. Deadline was [date]; submitted [X] days early. If this converts to a chargeback, pull this note first — evidence packet is complete."

Log the dispute ID from the Shopify Admin dispute panel alongside the note. If you're using DisputeDesk, the evidence packet is already attached to the case record — but the internal note on the Shopify order keeps the context visible to anyone working the order queue, not just the disputes workflow.

Where inquiry responses fail operationally

The most common failure isn't a bad response — it's a delayed one. Inquiry windows are shorter than chargeback windows, but most merchant dispute workflows treat them identically. The result: inquiries sit in the queue at the same priority as full chargebacks, get reviewed on the same cadence, and convert before anyone acts.

Second most common failure: responding to the wrong question. A merchant receives a descriptor clarification inquiry and submits a full fraud-defense evidence packet — tracking, IP data, device fingerprint, the works. The issuer wanted one thing. The merchant sent ten. The issuer closes it as resolved but the cardholder, who was genuinely confused about the descriptor, still doesn't recognize the charge and files a chargeback a week later. A one-sentence descriptor explanation would have closed it permanently.

Third failure: no internal record. The inquiry closes in the merchant's favor. Three weeks later, the same cardholder files a chargeback on the same transaction. The merchant has no log of what was submitted, no record of the inquiry outcome, and has to rebuild the evidence from scratch — often missing context that was available at the inquiry stage.

Automation improves consistency here, not certainty. A tool that flags inquiry deadlines separately from chargeback deadlines and routes them to a faster review queue eliminates the timing failure. It doesn't eliminate the need to read the request correctly before responding.