Chargeback fundamentals
Chargeback vs Inquiry: What Changes for a Shopify Merchant?
A Shopify inquiry and a chargeback both begin with a cardholder raising a concern through their bank, but they do not have the same immediate financial effect. An inquiry asks for information while the disputed funds remain with the merchant during investigation. A chargeback involves a disputed debit. Shopify makes this distinction in its chargeback process comparison.
For the merchant, the correct response starts by reading the actual case type. The word “dispute” in an email subject or internal conversation is too broad to tell finance whether funds have moved or operations which live case they should review.
Compare the two records before choosing a route
The distinction is easiest to use when broken into practical questions:
| Question | Inquiry | Chargeback |
|---|---|---|
| What is the immediate request? | Information about a challenged payment | A response to a disputed payment reversal |
| Does the case label alone establish a debit? | No | It identifies a debit process; verify its ledger entry |
| Is a merchant response potentially relevant? | Yes, where an open response route exists | Yes, where an open response route exists |
| Can a customer-service conversation close it by itself? | Do not assume so | Do not assume so |
| Which deadline matters? | The current inquiry deadline | The current chargeback deadline |
This table is a classification tool, not a substitute for the processor’s instructions. Some payment products use different labels, and automatic resolution arrangements can bypass an ordinary response stage. Inspect what is actually available for the transaction.
A team that records only “open dispute” loses a useful distinction. Add separate fields for type, status, and money movement. Type describes the process. Status describes its current stage. The transaction ledger shows the financial event.
An inquiry deserves attention even without a debit
“No money taken yet” is an observation about the present. It is not a forecast that the case will disappear. The bank is asking a question about the purchase, and the merchant may hold information that explains what happened.
Read the concern before assigning work. A query about a duplicate charge calls for a review of the payment history; a query about an expected credit calls for a review of the credit event. Sending the same generic packet for every inquiry misses the advantage of having a specific question to answer.
The absence of an immediate debit can also change who needs to be informed internally. Finance may need a contingent exposure note rather than a posted-loss entry. Operations still needs a named owner and a decision about the response. These are separate tasks with different outputs.
Avoid treating an inquiry as a normal support ticket simply because money remains in the balance. Customer service can address the underlying complaint, while the bank-facing case continues under its own process.
A chargeback changes the money question
For a chargeback, the team needs to identify the disputed amount and its associated account movement. That does not mean the entire order has necessarily been challenged, or that the eventual outcome is already known.
Separate “amount challenged” from “total order value” in your record. Separate the disputed principal from any fee. Those distinctions let the person reviewing the case work on its merits while finance follows the relevant transactions.
The merchant response deadline is also not the bank’s decision date. Recording a due date as an expected cash recovery date creates a misleading forecast. The response date concerns your action; the outcome comes from a later decision.
Shopify’s Admin dispute guidance explains its native case states. Read the state alongside the type instead of inferring one from the other.
Work through a hypothetical pair of cases
A fictional accessories store sees two notices, both involving a $90 purchase. Case A is an open inquiry about an unrecognized charge. Case B is an open chargeback about a product not received.
For Case A, the intake owner records the inquiry, confirms the current deadline, and checks the purchase context. Finance checks whether any related movement exists but does not invent a $90 debit because the subject line contains “dispute.”
For Case B, the owner records the chargeback and identifies the challenged transaction. Finance locates the actual debit and any associated fee separately. The operational review focuses on the delivery allegation.
Both cases can be urgent. Their identical order totals do not make their financial state, business question, or next action identical. A shared review board can hold both as long as its columns preserve those differences.
Use a simple classification checkpoint
Before choosing the response route, answer these questions in a short note: What exact type does the provider show? What exact state does it show? Has a disputed debit appeared? What question is the issuer raising? Which action remains available, and until when?
If two sources disagree, timestamp both observations and check the current native page. An older email can accurately describe an earlier stage while being unsuitable for today’s decision.
The goal is not to decide that one category matters and the other does not. It is to understand which process you are in, preserve the correct financial interpretation, and direct the merchant’s attention to the live action available now.
Explore Lower Chargeback’s dispute view before deciding what needs review.
Related reading in this collection:
- What Is a Chargeback? A Shopify Merchant’s Starting Guide
- Chargeback vs Refund: Who Initiates Each and Why It Matters
- Why Can a Chargeback Amount Be Smaller Than the Shopify Order Total?