Chargeback fundamentals
Shopify Chargeback Reasons: A Plain-English Map for Merchants
A Shopify chargeback reason is a routing label for the customer’s allegation. Use it to identify the business question that needs review before deciding what the merchant’s position should be. The label does not automatically tell you whether the customer is correct or which records will be decisive.
Shopify lists its native categories in Reasons for a chargeback or inquiry. The map below translates those labels into operational questions. It is an orientation tool; a detailed response must address the actual case and any available issuer claim.
Translate the label into a question
| Reason label | Main question to investigate | Common interpretation error |
|---|---|---|
| Fraudulent | Did the cardholder authorize the purchase? | Treating delivery as a complete answer about authorization |
| Unrecognized | Can the buyer connect the statement entry to this purchase? | Assuming confusion proves intentional misuse |
| Duplicate | Were multiple completed payments taken for the same obligation? | Counting a pending authorization as another completed charge |
| Subscription canceled | Did the charge occur consistently with the actual cancellation history? | Looking only at the subscription’s present state |
| Product not received | Was the promised product or service received? | Equating an internal fulfillment flag with every delivery fact |
| Product unacceptable | Did the supplied product or service match what was promised? | Answering only that a parcel arrived |
| Credit not processed | Was an expected credit due and actually processed? | Treating refund approval as the refund transaction |
| General | What specific concern sits behind the broad label? | Building a response before identifying the complaint |
The same order can contain facts relevant to several questions. That does not mean the reasons are interchangeable. Start with the allegation assigned to the case, then establish what the underlying details say.
Use the reason to assign the first reviewer
The label can help choose who investigates first. Payment operations may be best placed to inspect a duplicate-payment allegation. Customer support may know the cancellation conversation. Fulfillment may hold shipment details. A product specialist may understand whether a described feature matched the purchased version.
This is a request for factual input, not a transfer of all responsibility. The merchant still needs one owner for the case decision. Otherwise every specialist can finish their narrow check while nobody determines what the store should do with the result.
Write the assignment as a question with a defined scope. “Confirm which completed transactions relate to this purchase” is better than “prove this duplicate dispute wrong.” The second instruction presupposes the outcome and can discourage discovery of a real processing mistake.
A useful review can conclude that the customer is right. Routing should improve accuracy, including the ability to recognize a valid claim.
Read beyond broad or unfamiliar categories
General is a signal to obtain the specific allegation. It does not mean the bank has made no claim or that the merchant should submit every document associated with the order.
For example, a price disagreement could concern an item charge, shipping, a discount that did not apply, or an amount the customer expected after an adjustment. Those possibilities raise different business questions even if the native category remains General.
Shopify’s Admin dispute guidance explains that issuer claim information may be present. Where available, use it to narrow the question. Where absent, say what is uncertain and identify the purchase records or existing customer conversation that can clarify it.
Do not translate an unfamiliar network code into a convenient familiar reason without checking the provider’s interpretation. Preserve the original label and any code alongside your plain-English working description.
A hypothetical routing exercise
A fictional subscription coffee store receives three cases. One says Subscription canceled, one says Product not received, and one says Credit not processed. All three orders have a delivery record.
For the cancellation case, the useful first question is when cancellation was requested and when it took effect relative to the disputed charge. For nonreceipt, the question concerns what shipment or service the claim addresses. For the credit case, the question is whether the expected refund was due and what payment record exists.
Sending the delivery record as the opening answer for all three cases would ignore those distinctions. The correct routing asks the subscription operator, fulfillment colleague, and payments colleague to investigate their respective questions, while one dispute owner coordinates the decisions.
The merchant should preserve a shared case reference so the specialists are investigating the same transaction. Similar customer names or repeated subscription amounts are insufficient on their own.
Keep a two-line reason note
A reusable note can be very short: “Assigned reason: [exact native label]. Working question: [specific allegation to verify].” Add “Uncertainty: [missing detail]” when the claim is unclear.
This format leaves the bank’s classification intact while making the operational task readable. It also lets a later reviewer see whether the team answered the right question.
A reason map is successful when it narrows attention. It should prevent unnecessary document gathering, reduce contradictory interpretations, and make it easier to acknowledge a valid complaint. It cannot replace the actual case details or guarantee how the bank will evaluate the merchant’s position.
Explore Lower Chargeback to review the reason attached to each Shopify dispute.
Related reading in this collection:
- What Is a Chargeback? A Shopify Merchant’s Starting Guide
- Shopify Dispute Labels vs Card-Network Reason Codes: Build a Useful Crosswalk
- Does a Chargeback Prove Fraud? What a Dispute Label Actually Tells You