Shopify dispute stages
Shopify Chargeback Inquiry vs Chargeback: Why the Difference Matters
Shopify merchants often talk about inquiries and chargebacks as if they are the same event, but the economics and urgency are different.
If your team can respond well during the inquiry stage, you may avoid a full chargeback, protect margin, and keep the workflow more controlled. If you treat every dispute as the same, you usually react too late.
An inquiry is still a warning stage, not the full loss event
Shopify documents that when an inquiry opens, your funds are not yet removed during the investigation. A chargeback is different: the disputed amount and the chargeback fee are pulled immediately.
That means the inquiry stage is operationally valuable. It gives the merchant a chance to answer the bank's questions, assemble evidence, and potentially stop the problem from becoming a more expensive dispute.
- Inquiry: no funds withdrawn while the case is under review.
- Chargeback: disputed amount and fee are withdrawn immediately.
- If the inquiry closes against you, it can escalate into a full chargeback.
The evidence workflow is similar, but the business consequence is not
Shopify explains that the inquiry evidence process works much like the chargeback process. The team still needs order context, customer communication, delivery proof, and policy support.
The difference is that an inquiry lets you intervene before the financial hit lands. That makes response speed, packet quality, and customer communication even more important at the start of the case.
- Review the issuer claim when available so the team understands why the case opened.
- Put the strongest evidence first because issuers review large volumes of disputes.
- Keep customer communication organized in case the inquiry becomes a chargeback later.
Use inquiry volume as a signal that the workflow needs tightening
If inquiries are rising, the store usually needs clearer billing descriptors, better shipping communication, or more disciplined evidence ownership. That is not just a support issue. It is a revenue-protection issue.
When the same patterns repeat, move from ad hoc reaction into a checklist, pricing review, and a tighter software evaluation path.