Shopify Admin
Where to Find All Open Chargebacks and Inquiries in Shopify Admin
To find Shopify’s native list of chargebacks and inquiries awaiting a response, open Orders and filter Chargeback and inquiry status to Open. Start from a broad order list so unrelated filters do not hide relevant cases. Shopify documents this route in its Admin dispute instructions.
The word Open here refers to the dispute stage. It does not mean the same thing as an open order. A fulfilled or archived order can still be associated with a case that needs attention.
Build the filter from the Orders page
In the correct store’s Shopify Admin, open Orders. Use Search and filter, choose Add filter, select Chargeback and inquiry status, and choose Open. Review the filter chips that remain visible before trusting the result.
If you began in a specialized view, remove constraints that do not belong to this lookup. Examples include a recent order-date range, a particular fulfillment status, a staff tag, or a sales-channel restriction. Their presence can narrow the results even when the dispute filter itself is correct.
Shopify’s order filtering guidance explains how filters shape the order list. For this first lookup, the useful result is the native open-dispute set within your authorized store scope.
Do not change order records to make them appear in the list. The task is to inspect the appropriate query, not to relabel historical orders.
Check what “all open” actually covers
The native Open filter concerns cases that have not yet been submitted through the ordinary response workflow. It is not a list of every dispute ever recorded, every case under bank review, or every payment concern reported by a customer.
Submitted cases belong to a different state. Final outcomes belong to different states again. Cases handled through an automatic resolution arrangement may not pass through the ordinary open-response stage. A third-party provider may also have its own case location.
These boundaries are important when the list is empty. An empty Open result can be accurate while the store still has submitted disputes or another provider’s active cases. State the finding precisely: “No cases in this native Open filter at the time checked.”
Avoid the broader claim “there are no payment problems” unless a much wider review supports it.
Validate the list with one known case
If you have a recent notice, open its referenced order independently and inspect the native case. Compare its actual state with the filtered list.
| What the known case shows | What to expect from the Open filter |
|---|---|
| Open and within the correct store | It should be included when no unrelated filter excludes it |
| Submitted | Its absence from Open is consistent with the state |
| Final outcome | Its absence from Open is consistent with the state |
| Another provider’s case | Verify that provider’s workflow rather than assuming native coverage |
| Order cannot be accessed | Resolve identification or access before interpreting list completeness |
This is a focused confidence check. It does not require testing every status or creating a sample dispute. One known case can expose an accidental date restriction or a confusion between order and dispute status.
A hypothetical hidden historical order
A fictional sportswear store receives a chargeback for an order placed several months earlier. The employee opens Orders from a view restricted to purchases created this week, then adds the Open dispute filter. The list is empty.
The employee removes the recent order-date restriction and repeats the lookup. The historical order now appears because its dispute is open even though the purchase is older.
The mistake was the intersection of filters, not the absence of a case. This distinction matters because escalation to technical support would have been premature before checking the actual query.
A good lookup note records the store, filter, and observation time. If the known case still fails to appear after scope is corrected, the employee can describe a concrete mismatch rather than simply saying “chargebacks are missing.”
All details in this example are hypothetical; the method is to inspect the conditions defining the list.
Leave with an accurate result
Before finishing, confirm the correct store, the Chargeback and inquiry status filter, the Open value, and the absence of unintended constraints. Open any case you plan to act on and verify its live state and deadline directly.
The list is an entry point. It helps locate cases, but it does not decide their merits or replace their detailed records. A visible order row also does not establish that the dispute amount equals the order total.
If the lookup produces no rows, preserve that scoped result and investigate any specific known mismatch through its order and processor. If it produces rows, you have the native set needed for the next case-level review.
The outcome of this task is a correct first view of open native disputes. Saving views, building team routines, and analyzing history are separate jobs that should begin from this verified foundation.
Explore Lower Chargeback for a focused view of Shopify dispute status and deadlines.
Related reading in this collection:
- How to Accept a Chargeback in Shopify Admin
- Where to Review a Shopify Payments Chargeback Account-Health Notice