Short answer: A Seller Support ticket that gets approved is short, factual and easy to verify. It names the issue and LPN in the subject, lists every identifier for the unit, states one clear issue, contrasts what should have been returned with what was received, attaches labeled photos and ends with one specific request.
Key takeaways
- Put the issue and the LPN in the subject line so the case is searchable and the agent knows what to look for before opening it.
- Include every identifier you have: LPN, ASIN, FNSKU, SKU, customer order ID, Shipment ID, VRET ID, RA# and process date.
- Describe the problem as "expected" versus "received" in plain, neutral language, without accusing the customer or Amazon.
- Group several units from the same removal shipment into one ticket, with one item block per LPN and never the same LPN twice.
- Attach a photo ZIP with files named by content, such as LPNR8K2M4QX7T-01-lpn-sticker.jpg.
- End with one clear request, and answer follow-up questions with exactly what was asked.
What should a Seller Support ticket for a return dispute include?
A strong return dispute ticket has six parts: a descriptive subject, a full set of identifiers, one issue line, an expected-versus-received description, attached photos and a single request. Each part answers a question the agent would otherwise have to ask.
Think about who reads the ticket. A Seller Support agent handles many cases and needs to locate the unit, understand the problem and verify it against photos quickly. Every missing ID or vague sentence adds a round of back-and-forth. If you are new to the process, start by confirming that the unit is eligible for a dispute under the current rules in Seller Central Help.
The subject line
The subject should state the ticket type, the issue and the LPN. For example: "FBA Return Dispute — Charging Cable and Guide Combs Missing — LPNR8K2M4QX7T". When a ticket covers several units, name the shared issue and add the number of units, then list the LPNs in the body.
Avoid subjects like "Problem with return" or "Please help urgently". They tell the agent nothing, and they are hard to find later when you need to reference the case.
The identifiers block
List every identifier for the unit in a consistent order, one per line. The agent can then copy each value directly into internal tools. The identifiers that matter most are:
- LPN: from the sticker on the returned unit, also found in the license-plate-number column of the FBA Customer Returns report.
- ASIN and FNSKU: ASINs usually start with B0 and FNSKUs usually start with X0.
- SKU: your own product code.
- Customer order ID: from the order-id column of the FBA Customer Returns report.
- Return date and detailed disposition: from the same report row.
- Shipment ID, VRET ID, RA# and process date: from the return slip in the removal box.
If a value is genuinely unavailable, say so rather than leaving the field out. "LPN: not present on unit" is more useful than silence, because it shows you checked.
The issue line
Write one sentence that states the problem. For example: "The returned unit is incomplete: the charging cable and two guide combs are missing." One issue line per unit keeps the ticket focused. If a unit has two problems, such as a missing storage case and a missing cap, list both in the same sentence rather than splitting them into separate paragraphs.
Expected vs. received
This is the core of the ticket. Describe what the unit should contain when sold, then describe what actually came back. Use your catalog listing and packaging as the reference, not memory.
For a wrong-item case, name the physical differences the agent can see in the photos: a different brand name on the housing, a different model shape, a different color, or a missing barcode label. The guide on documenting a switched return covers these details. For an incomplete set, list each missing piece by name and quantity, as described in incomplete-set claims for missing parts and accessories.
Photos attached
State that photos are attached and what they show. A short line such as "Attached: LPN sticker, return slip, product label and full contents laid out" tells the agent the evidence is complete before they open the ZIP.
The request
Close with one clear request. For example: "Please review this returned unit and reimburse it as a customer return that came back incomplete." Do not list several options for the agent to pick from.
How should the ticket be worded?
The best tone is factual, neutral and specific. Describe what you observed, attach proof and let the evidence carry the argument.
Stay factual and neutral
Write as if you were filling in an inspection report. "The unit received is a different model with another brand name on the housing" is factual. "The customer obviously scammed us" is an accusation, and it gives the agent nothing to verify.
Avoid blaming the fulfillment center too. Even when you believe a return was graded incorrectly, describe the gap between the report and the physical unit, for example "The report shows SELLABLE, but the unit arrived without its charging cable," and leave the conclusion to the agent.
Do not suggest alternatives
Offering options such as "or you could just return it to my inventory" or "a partial refund is also fine" invites the agent to choose the easiest outcome for them. Make one request and stop.
Keep it short
Short paragraphs and labeled fields beat long narratives. If the explanation for one unit runs longer than a few sentences, you are probably including background that does not help verify the claim.
How do I group several units from the same removal shipment into one ticket?
Units that arrived in the same removal shipment can usually go into one ticket, with a shared header for the shipment and a separate item block for each LPN. Each LPN appears exactly once.
Grouping saves time for you and the agent, because the shipment-level identifiers only need to be stated once. It also shows a pattern when several units from the same shipment came back wrong or incomplete.
- Put the Shipment ID, VRET ID, RA# and process date in a shared header at the top of the ticket body.
- Create one item block per unit, numbered Item 1, Item 2 and so on.
- In each block, list the LPN, ASIN, FNSKU, SKU, customer order ID, return date and disposition.
- Give each block its own issue line and its own expected-versus-received description.
- Check that no LPN appears in two blocks. Each LPN identifies one returned unit, so a duplicate usually means a misread sticker or a mislabeled photo.
- Match the photo filenames to the item blocks so every photo starts with the LPN it belongs to.
- End the ticket with a single request that covers all listed items.
Keep units from different removal shipments in separate tickets. Mixing shipments makes the agent cross-check several return slips and increases the chance of a partial answer. Check the current guidance in Seller Central Help if you are unsure how many items one case should contain.
What should I leave out of the ticket?
Leave out anything the agent cannot verify or does not need to decide the case. Extra material slows the review and can distract from the evidence.
- Emotional language and accusations: words like "fraud", "scam" or "unacceptable" do not help.
- Account history and unrelated complaints: past cases, other listings or general frustration with returns belong elsewhere.
- Guesses presented as facts: if you do not know when a part went missing, do not claim to.
- Duplicate LPNs: never list the same unit twice, even under two different issues.
- Personal or customer data you do not need: the customer order ID is enough to locate the return.
- Invented policy references: do not quote deadlines or policy sections from memory. Check the current rule in Seller Central Help if you need to cite one.
- Alternative requests: one clear request only.
How should I prepare and name the photo attachments?
Attach the photos as a single ZIP file, with every file named by LPN, sequence number and content. Clear names let the agent find the right photo without opening every file.
A naming pattern like LPN, then a two-digit number, then a short description works well:
- LPNR8K2M4QX7T-01-lpn-sticker.jpg
- LPNR8K2M4QX7T-02-return-slip.jpg
- LPNR8K2M4QX7T-03-product-label.jpg
- LPNR8K2M4QX7T-04-contents-laid-out.jpg
Each unit needs at least a clear LPN sticker photo, the return slip, a product or label shot and a photo of the full contents. The 4-photo checklist for every return dispute explains how to frame each shot so the details are readable. Keep photos sharp, well lit and uncropped around the IDs. A blurry sticker is one of the easiest reasons for an agent to ask for more information.
If you would rather not assemble this by hand, Return Disputes reads the IDs from your photos, checks the unit against your catalog, and produces both the ticket text and a named photo ZIP that you then file yourself in Seller Central.
What does a complete example ticket look like?
The example below shows a grouped ticket for two units from one removal shipment, using fictional data. One unit is an incomplete cordless hair clipper kit, and the other is a wrong item returned in place of the same product.
Subject: FBA Return Dispute — Charging Cable and Guide Combs Missing — LPNR8K2M4QX7T (+1 unit) Hello, I am requesting a review of two customer-returned units that arrived in the same removal shipment. Details for each unit are below, and labeled photos are attached in one ZIP file. Removal shipment Shipment ID: 518203947261830 VRET ID: VRET4830916257204 RA#: QW3M7-tRk8Vn2pLx-CHA1-1 Process date: 2026-06-18 Item 1 LPN: LPNR8K2M4QX7T ASIN: B0C7XK2P9M FNSKU: X00ABC1234 SKU: CLIP-KIT-PRO-BLK Customer order ID: 114-5820193-7736401 Return date: 2026-05-29 Detailed disposition: SELLABLE Issue: Incomplete set. The charging cable and two guide combs are missing. Expected: Cordless hair clipper, charging cable, charging stand, four guide combs, cleaning brush, storage case. Received: Clipper, charging stand, two guide combs, cleaning brush, storage case. No charging cable. Two guide combs missing. Photos: LPNR8K2M4QX7T-01 to LPNR8K2M4QX7T-04 Item 2 LPN: LPNT5W9J3HB2D ASIN: B0C7XK2P9M FNSKU: X00ABC1234 SKU: CLIP-KIT-PRO-BLK Customer order ID: 113-2947615-0482937 Return date: 2026-06-02 Detailed disposition: CUSTOMER_DAMAGED Issue: Wrong item returned. The unit is not our product. Expected: Our black cordless hair clipper kit with our brand name printed on the housing and our FNSKU label on the box. Received: A silver clipper of a different model with another brand name on the housing, in unbranded packaging with no FNSKU label. Photos: LPNT5W9J3HB2D-01 to LPNT5W9J3HB2D-04 Attachment: return-dispute-518203947261830.zip Request: Please review both units and reimburse them as customer returns that did not come back as sold. Thank you.
Notice what the example does. Every identifier is on its own line, each LPN appears once, both issue lines are one sentence, and the request is a single sentence covering both items.
What should I do when Seller Support asks for more information?
Answer exactly what was asked, in the same case, and restate the relevant LPN and identifiers in your reply. Do not open a new case for the same units unless Support tells you to.
Common follow-up requests include a clearer photo of the LPN sticker, a photo of the return slip, confirmation of the customer order ID, or a description of how the product is normally packaged. Reply with the specific item, name the new files the same way as the originals, and keep the tone as neutral as the first message.
If the reply seems to misread your ticket, restate the issue line and the expected-versus-received comparison for that LPN in two or three sentences. Avoid repeating the whole ticket or arguing. When a case ID comes back, record it next to each LPN so you can match it later in the Reimbursements report; the process is covered in tracking reimbursements and matching payouts to cases.
Ticket section checklist
Use this table as a final check before you submit. Each row lists a ticket section, what it should contain and the mistake that most often weakens it.
| Ticket section | What to include | Common mistake |
|---|---|---|
| Subject line | Ticket type, issue and LPN (plus unit count if grouped) | Vague subject like "Return problem" |
| Shipment header | Shipment ID, VRET ID, RA#, process date | Missing RA# or mixing two shipments |
| Item identifiers | LPN, ASIN, FNSKU, SKU, customer order ID, return date, disposition | Pasting the removal order ID as the customer order ID |
| Issue line | One sentence naming the problem | Several paragraphs of background |
| Expected vs. received | Full contents as sold, then exact contents received | "Some parts missing" without naming them |
| Photos | Named ZIP, files starting with the LPN | Unlabeled files or blurry LPN sticker |
| Request | One clear, specific request | Offering alternatives or several options |
| Tone | Factual and neutral | Accusing the customer or the warehouse |
Frequently asked questions
Should I file one ticket per LPN or group them?
Group units that arrived in the same removal shipment into one ticket, with one item block per LPN. Keep units from different removal shipments in separate tickets. Never list the same LPN twice, even if the unit has more than one problem.
What if the returned unit has no LPN sticker?
Say so clearly in the item block, for example "LPN: not present on unit," and include every other identifier you have, such as the FNSKU, SKU and return slip details. Attach a photo showing where the sticker would normally be. Do not guess an LPN from the report.
How long should a return dispute ticket be?
As long as it takes to list the identifiers and describe the issue, and no longer. For a single unit, a subject, an identifiers block, one issue line, a short expected-versus-received description and a request are usually enough. Grouped tickets grow by one item block per unit.
Can I mention Amazon policy or deadlines in the ticket?
Only if you have checked the current wording in Seller Central Help. Policies, claim windows and menu names change, and quoting an outdated rule can confuse the review. In most cases a clear description and good photos are more persuasive than a policy citation.
What if my case is closed without a reimbursement?
Read the reply carefully to understand the reason, then check whether any identifier or photo was missing or unclear. If you have evidence that addresses the stated reason, reply in the same case with that specific evidence. Keep the tone neutral and avoid resubmitting the identical ticket.
Does Return Disputes file the ticket for me?
No. It prepares the ticket text and the named photo ZIP from your photos, but you file the ticket yourself in Seller Central. The tool never logs into Amazon on your behalf.