Amazon Case Log 2026: The Official Rules for Contacting Seller Support
What the Case Log actually is
The guidelines Amazon asks every case to follow
| Guideline (Amazon's wording) | What it actually prevents |
|---|---|
| Review your case log and check the case status instead of opening a new case | Two tickets for the same issue, handled by two different people with no shared context |
| Create one case per issue, since multiple teams resolve issues more efficiently when each team gets its own specific contact | A single case stalling because it was routed to a team that only owns half of what you asked about |
| Don't open a new case if one is already under review for the same issue | A duplicate case competing with the original for the same specialist team's time |
| If you need more time to respond to a case, ask Amazon to keep the case open | A case auto-expiring while you are still gathering the documents Amazon asked for |
| If you have questions about a closed case or think it was handled incorrectly, reopen it instead of opening a new case | Losing the full history and evidence already attached to the original case |
| Do not reopen a case or raise it as a new case once Amazon has said no further action will be taken | A case being closed again immediately, with no new information to change the outcome |
What actually counts as "one issue"
- A suppressed listing and a separate question about an unrelated return are two issues, even if they happened the same week and even if you only want to talk to Support once about your account in general.
- A shipment discrepancy and the reimbursement that should follow from it are often treated as two issues by Amazon's own teams, even though sellers reasonably see them as one connected problem; expect to file the reimbursement case once the discrepancy itself is resolved, not alongside it.
- An account health warning and the specific policy violation behind it are usually one issue; don't split a single root cause into two cases just because it shows up in two places in Seller Central.
- If you are not sure whether something is one issue or two, a useful test is whether a single specialist team could plausibly resolve all of it; if the answer clearly needs two different teams, it is two cases.
Building a case that does not bounce back for more information
- State the ASIN or order ID, the exact date the issue started, and what you expected to happen, in the first message, not scattered across a back-and-forth.
- Attach the specific screenshot or document the help topic you chose typically asks for; the help flow usually hints at this when you select the issue category.
- Avoid pasting a long narrative where the actual request is buried in the third paragraph; lead with what you want Amazon to do.
- If the issue is time-sensitive, say so in the first message and flag the case Urgent there, rather than mentioning urgency only after a slow first reply.
When the Seller Forums can help, and when they can't
Multi-user accounts and who can see the Case Log
- Before assuming a teammate can see or follow up on a case, confirm they actually have the Seller Central permission that covers it, rather than assuming account-wide access.
- When a contractor's engagement ends, any case they opened still belongs to the account, not to them personally; make sure someone with ongoing access is tracking it so it does not sit unanswered.
- For a case that needs continuity across a long investigation, it helps to have one named owner inside your team who checks the Case Log on a schedule, rather than leaving it to whoever happens to remember.
Keeping your own record outside the Case Log
- Keep your own dated note of when a problem started, not just when you opened the case; Amazon's team may ask for this and a vague memory answers slower than a note you wrote the same day.
- Screenshot a listing, price, or inventory state the moment you notice something wrong, before a case even exists; by the time a case is open, the page may already look different.
- If a case spans weeks, keep a short running log of what each reply actually asked for and what you sent back, so you are not re-reading the whole thread to figure out where it stands.
- A pattern across several cases (the same issue type recurring every few months, for example) is easier to spot from your own notes than from the Case Log's per-case view, and it is useful evidence the next time you open a related case.
Why you sometimes only see chat and phone, not a case
- You may already have an open case for the same issue: per the guideline above, Amazon's system can hide the new-case option entirely and only offer chat or phone once a case for that issue already exists and is under review.
- The issue type you selected may only support chat or phone for that specific help topic; Amazon routes different categories to different teams, and some categories are chat/phone-only regardless of how urgent they feel to you.
- Picking a more specific help topic, deeper in the category tree, sometimes unlocks the written-case option where the broader category only offered chat or phone.
- If your issue is genuinely time-sensitive and only chat or phone is offered, Amazon's own advice is to use that channel and flag the issue as urgent there rather than hunting for a way to force open a written case.
Flagging a case Urgent: what it is actually for
Reopening a case versus opening a new one
| Situation | What to do | Why |
|---|---|---|
| A case is still open or under review for your issue | Do not open a new case; wait, or add information to the existing one | A second case for the same issue competes with, rather than helps, the first |
| A case was closed and you disagree with how it was handled | Reopen that exact case | Reopening keeps the full history and evidence attached; a new case starts from zero |
| A case was closed and Amazon said no further action will be taken | Do not reopen it and do not open a new case for the same issue | Amazon's guidelines treat this as a final answer unless you have genuinely new information |
| You need more time to gather documents Amazon asked for | Ask Amazon to keep the case open | Prevents the case expiring and forcing you to restart the whole thread |
Common mistakes that get a case closed without a real answer
- Opening a second case because the first one has not had a reply yet; per Amazon's guidelines this is treated as a duplicate and is more likely to be closed than to speed anything up.
- Bundling two unrelated problems into one case to save time; Amazon routes by issue type, so the case usually only gets fully handled for the part that matched its assigned team.
- Letting a case expire while still gathering documents, instead of asking Amazon to keep it open, which forces the whole case to restart from a blank thread.
- Reopening a case, or filing a new one on the same topic, after Amazon has already said no further action will be taken, which Amazon's guidelines explicitly rule out.
- Marking a routine case Urgent out of frustration rather than genuine time pressure, which does not speed up that case and dilutes the flag for the cases that actually need it.
A simple checklist before you open your next case
- Check the Case Log first: is there already a case open or under review for this exact issue?
- Write down the one issue this case is about; if you have a second, unrelated issue, that is a second case.
- If the issue genuinely cannot wait, use whichever channel is offered, chat, phone, or a written case, and flag it Urgent there.
- If a case is closed and you disagree, reopen that case; do not start a new one on the same topic.
- If Amazon told you no further action will be taken, treat that as final unless you have genuinely new information to add.
- If you need more time to respond, ask Amazon to keep the case open instead of letting the clock run out.
What is the Amazon Case Log?
Should I open a new case if my existing one has not had a reply?
Can I combine two issues into one Amazon support case?
Why does Seller Central only offer me chat or phone, not a written case?
Should I reopen a closed case or start a new one?
What happens if Amazon tells me no further action will be taken on a case?
When should I flag a case as Urgent?
Can Amazon close my case just for not following these guidelines?
Does posting my case ID in the Seller Forums speed up a stuck case?
Should I report a shipment discrepancy and its reimbursement in the same case?
Can every user on a multi-login Seller Central account see all cases?
Stop Juggling Tools. SellerMagnet Combines Everything You Need.
Join a smarter way to manage your Amazon store.
Recommended Articles
Amazon Case Log 2026: The Official Rules for Contacting Seller Support
What Amazon's own Case Log guidelines say about opening, reopening and escalating a Seller Central support case, why you sometimes only see chat or phone, and the mistakes that get a case closed without a real answer.
Amazon Grade and Resell 2026: One Program, One Fee
Amazon merged Restore to New and Sell as Used into one Grade and Resell program, and extended the Sell as Used processing fee to Restore to New units. What it costs, with a worked example.
Amazon Two-Step Verification 2026: Setup, Backup Methods and Recovery
How Amazon's mandatory Two-Step Verification works on Seller Central: primary and backup method pairing rules, the setup steps, and the documented account-recovery process if you lose access to both devices.
Amazon Creator Connections 2026: How Affiliate+ Campaigns Really Work
Eligibility, the 3 ways to pay a creator, campaign setup, how commission is calculated, a worked cost-per-sale example, and what sellers who ran real campaigns report about accepts versus actual posts.
Amazon Shop Direct Merchant Workspace 2026 Explained
Amazon's new free Shop Direct Merchant Workspace explained: who can join, the 3-step signup, Buy for Me checkout, and why an existing Amazon seller might use it for products they don't sell on Amazon.
Amazon Seller University 2026: The Free Training Hub
What Amazon Seller University actually covers, the course categories inside Seller Central, recent real course additions on compliance and logistics, how to access it, and a worked example of what skipping it can cost.