How to File a Claim on Amazon: Buyer, Chargeback, and Seller

A customer says an order never arrived, a seller sees an unexpected refund, or an operations team finds a returned unit that doesn't match the item shipped. Each situation may be described as “filing a claim on Amazon,” but Amazon routes them through different systems. The correct portal, deadline, and evidence package depend on who is filing, what transaction occurred, and whether Amazon or a payment provider controls the dispute.

Table of Contents

• Finding the Right Claim Path as a Buyer or Seller
  • Choose the portal before assembling evidence
• Filing an A-to-z Guarantee Claim
  • Buyer timing and seller response
• Handling Chargebacks and Amazon Pay Claims
  • Chargeback evidence follows the payment rail
• Submitting Seller-Side Reimbursement Claims
  • SAFE-T evidence should match the reason code
• Preparing the Evidence Package That Wins Claims
  • Match proof to the dispute
• Handling Rejections and Follow-Up Actions
  • A disciplined rejection review
• Automating Claim Preparation With Structured Seller Data

Finding the Right Claim Path as a Buyer or Seller

The first decision isn't which button to click. It's identifying the role and transaction type.

A buyer seeking a refund generally uses the Amazon marketplace's A-to-z Guarantee process. The buyer must contact the seller first and give the seller an opportunity to resolve the issue. For delivery disputes, Amazon requires the buyer to wait one calendar day after contacting the seller, and also three days after the maximum estimated delivery date before the claim becomes eligible, as described in Amazon's buyer claim guidance.

A seller defending against an A-to-z claim works inside Seller Central, under the A-to-z Guarantee claims area. A seller requesting reimbursement for a seller-fulfilled order uses Seller Central > Orders > Manage SAFE-T Claims. FBA reimbursement claims follow separate workflows and deadlines. A chargeback sits outside Amazon's claim system and must be handled through the payment provider or acquiring bank.

Choose the portal before assembling evidence

The same order may generate different records depending on the path:

Practical rule: A claim submitted in the wrong system can fail before Amazon evaluates the underlying facts.

This classification prevents a common operational mistake. A seller shouldn't send a SAFE-T evidence package to an A-to-z case, and a buyer shouldn't search Seller Central for a refund mechanism. Start with the role, identify the transaction channel, then record the relevant date before opening a case.

Filing an A-to-z Guarantee Claim

A-to-z is the standard buyer-side route for marketplace order problems, but it isn't an instant refund button. Amazon's framework covers claims involving items not received, late, damaged, defective, missing parts, or incorrectly charged, provided the buyer follows the required contact and timing process.

The buyer should begin in the order history, open the affected order, and contact the seller through the available message or customer-service flow. The message should state the specific defect, the requested resolution, and the order facts that can be verified. A vague complaint creates room for delay, while a concise record gives Amazon a cleaner timeline if escalation becomes necessary.

Buyer timing and seller response

For delivery disputes, the buyer must wait three days after the maximum estimated delivery date, and the seller must be given the opportunity to respond. Amazon's seller guidance requires a response to the buyer's first message within 48 hours, as stated in Amazon's A-to-z Guarantee policy. For return-related issues, the seller must authorize or respond within that same 48-hour period with a valid domestic return address, a prepaid label, or a returnless resolution.

The buyer's filing deadline is 90 days after the incident or one year from the purchase date, whichever comes first, and Amazon says claims are usually resolved within 90 days, according to its customer claim timeline.

Sellers receive five business days to respond to Amazon's notification once an A-to-z claim is filed. That formal window shouldn't be treated as the first response opportunity. The earlier Buyer-Seller Messages exchange is where a seller can often resolve the issue before Amazon takes over the case.

A strong submission should preserve:

• Order confirmation: Include the order identifier, promised delivery estimate, and item details.
• Tracking evidence: Provide carrier scans and delivery confirmation where available.
• Message history: Keep the seller's response and the buyer's original request in the case record.
• Issue-specific proof: For damage or defects, use clear photographs and a precise description rather than unsupported conclusions.

The seller's objective is resolution first, defense second. The buyer's objective is a complete, chronological record that shows contact was attempted and the problem remained unresolved.

Handling Chargebacks and Amazon Pay Claims

A buyer may recognize Amazon's brand while paying on a separate merchant website. That transaction belongs in Amazon Pay Activity, not the marketplace order-history path. The merchant transaction claim process treats it as an Amazon Pay purchase, and the merchant responds inside that environment.

For physical goods, the buyer must wait 15 days from the charge or order date before filing an Amazon Pay claim, then has 75 days to proceed, according to Amazon's Amazon Pay claim framework. Covered problems include non-delivery, late delivery, damage, defects, missing parts, and incorrect charges. Sellers should confirm the transaction type before choosing a response workflow, because Amazon Pay disputes, marketplace A-to-z claims, and card chargebacks use different portals and decision rules.

Chargeback evidence follows the payment rail

A chargeback starts with the cardholder's bank or payment provider. The seller answers through that provider's representment process, not through Amazon's retail claim screens. Payment notifications therefore need separate monitoring, while the underlying records should remain consistent across submissions.

For an Amazon Pay response, organize the evidence around the disputed transaction:

• Shipment proof: Carrier acceptance, tracking events, and delivery confirmation.
• Order confirmation: The item, address, transaction details, and purchase terms.
• Customer communication: Messages showing the merchant's offer and the customer's response.
• Resolution record: Refund, replacement, return, or refusal details tied to the transaction.

Keep the timeline readable. Match each record to the disputed point, and identify gaps instead of making unsupported conclusions. A reviewer should be able to reconcile the order, payment, shipment, contact history, and resolution without searching across unrelated files.

Amazon's policy announcement states that customers can file claims up to $1 million. It also reports that more than 80% of claims were under $1,000, with claims under $1,000 typically resolved by Amazon for insured selling partners. Those figures describe the policy framework, not a guaranteed merchant outcome, as documented in the announcement linked above.

A payment dispute is a records problem before it is a writing problem. The response should let an adjudicator reconcile the transaction without guessing.

For broader payment exposure, the Paylithix guide to recovering revenue provides context on chargeback recovery beyond Amazon's marketplace workflow.

Submitting Seller-Side Reimbursement Claims

Seller-fulfilled reimbursement claims use a specific Seller Central workflow: Seller Central > Orders > Manage SAFE-T Claims. Select the order, choose the closest reason code, and attach records that address that code directly. A claim built around the wrong path or vague explanation gives the reviewer more work and leaves key facts unverified.

The filing window is 30 calendar days from the refund charge or receipt of the returned item. If Amazon requests more information, respond within seven days or the claim is denied, according to Amazon's SAFE-T claim guidance.

SAFE-T evidence should match the reason code

The reason code sets the proof standard. Put the decisive record next to the allegation instead of submitting a broad narrative that requires an investigator to reconstruct the case.

FBA reimbursement follows separate calendars. A customer return claim can be filed no sooner than 60 days and no later than 120 days after the customer refund or replacement. A shipment-to-Amazon claim must be filed no later than nine months after the verified delivery date to the fulfillment center or an Amazon-operated third-party facility. The shipment must also appear eligible for investigation in the shipment workflow status fields.

A returned item that arrives after the return window can produce a reimbursement cap of up to 20% of the order sales price under the restocking-fee policy. Sellers should record the refund date, return receipt, replacement date, and fulfillment-center delivery date as separate fields. Amazon financial reconciliation helps connect those dates with the actual refund and inventory movement. Keep the order identifier attached to each record so finance and Seller Central show the same transaction history.

Preparing the Evidence Package That Wins Claims

Entitlement doesn't compensate for missing proof. Amazon's reviewers need records that connect the order, event, policy condition, and requested outcome without relying on a seller's interpretation.

A useful evidence package is built by claim type rather than stored as one generic folder.

Match proof to the dispute

For an A-to-z defense, the core set is verifiable tracking, delivery-estimate proof, and order-confirmation records. The seller should also preserve the Buyer-Seller Message thread, particularly the first customer message and the response sent within the applicable response window.

For a SAFE-T claim, the package should show the outbound state, the return event, and the financial impact. That can include shipment and tracking records, return delivery scans, item-condition photographs, buyer communications, and discrepancy evidence such as weight differences between outbound and return labels. A photo without an order association is weak; a photo tied to the order, return scan, and product identifier is operationally useful.

For an Amazon Pay response, merchants should tailor the submission to that portal. Amazon identifies shipment proof, order confirmation, and customer communication as relevant response material. A marketplace screenshot may not establish the third-party transaction context, so the merchant should use records that identify the Amazon Pay payment and the fulfillment event together.

Evidence standard: A reviewer should be able to answer what was ordered, what shipped, what happened in transit or return, what the customer reported, and why the requested decision follows from the records.

Manual assembly commonly fails at the joins. Tracking lives in one system, order confirmation in another, return scans in carrier tools, and messages in Seller Central. A practical folder or case record should use the order ID as the key, retain original timestamps, and label every attachment with the fact it proves.

Customer complaints also belong in the same operating record. The workflow described in how to handle customer complaints is useful because it preserves the communication trail that later supports an A-to-z defense, SAFE-T filing, or payment dispute response. Structured records matter most when a deadline arrives before an operator has time to reconstruct the order from scratch.

Handling Rejections and Follow-Up Actions

A rejection usually points to a process failure: the wrong portal, an expired eligibility window, or evidence that does not prove the disputed event. Repeating the same explanation rarely changes the outcome. First identify the exact defect, then correct the record or filing path.

Timing comes first. For A-to-z claims, sellers have five business days to respond to Amazon's notification. Delivery-related issues should be addressed through Buyer-Seller Messages within 48 hours of the first customer message. Buyer eligibility then depends on that response period and the delivery-date condition described in Amazon's A-to-z policy guidance.

A disciplined rejection review

Review the case in a fixed order:

1. Verify eligibility dates. Check the refund charge, return receipt, customer refund or replacement, verified fulfillment-center delivery, and maximum estimated delivery date where relevant.
2. Confirm the portal. Keep A-to-z, SAFE-T, FBA reimbursement, Amazon Pay, and external chargeback workflows separate. Each uses different submission rules and evidence.
3. Map evidence to the reason code. Select the specific record supporting delivery, condition, identity, communication, or financial loss.
4. Read every information request. Amazon may require additional details within seven days for a SAFE-T case. Missing that response window can result in denial. Follow the stated request and submission instructions rather than reusing a general defense.
5. Resubmit only after a material correction. Add a missing source record, correct the portal or reason code, or answer the rejection reason directly. A longer narrative without new proof adds little.

FBA shipment claims need their own status check. A seller's belief that Amazon lost or under-received inventory does not by itself make a shipment fileable. Confirm that the workflow marks the shipment as eligible for investigation and that the applicable filing deadline remains open.

Track rejected cases alongside account health. Recurring disputes can reveal fulfillment or customer-service breakdowns rather than isolated support problems. Amazon seller account health helps connect the dispute queue with broader operational controls, so corrective work addresses the pattern as well as the individual claim.

Automating Claim Preparation With Structured Seller Data

Claim preparation becomes unreliable when the operator starts looking for evidence only after a refund, A-to-z notification, or chargeback arrives. A structured data layer changes the sequence. It can preserve order history, shipment events, return records, inventory context, and finance entries before a filing window becomes urgent.

For Amazon sellers, agentcentral is a hosted MCP server that gives Claude, ChatGPT, OpenClaw, Cursor, and other MCP clients structured access to Amazon Ads, Seller Central, inventory, orders, catalog, ranking, finance, and fulfillment data. It pre-materializes account data, retains history from the first connection, and supports fast repeated reads instead of forcing an agent to wait for slow asynchronous reports.

That distinction matters for claims. An agent can retrieve source-provided fields and classifications, assemble an order-level evidence view, and identify missing records for a human to review. It doesn't decide whether the seller should file, recommend an unsupported outcome, or autonomously optimize the account. The workflow remains controlled by the operator, with guarded write tools, previews, idempotency keys, and audit logs that preserve before-and-after values where writes are used.

Operational principle: Automation should preserve facts and expose gaps. The user or the user's workflow decides the claim strategy.

The setup is designed for Amazon teams using MCP clients. A seller signs up, authorizes access through OAuth, adds the scoped API key to the chosen client, and asks the agent to retrieve the relevant data. Isolated datasets, encrypted credentials, and revocable access support account separation for agencies and multi-account operators.

The practical result isn't a promise that every claim will be approved. It is a repeatable evidence process: classify the claim, verify the deadline, retrieve the source records, review the package, and submit through the correct Amazon workflow. Visit agentcentral to connect Amazon seller and advertising data to an MCP-enabled workflow built for auditable claim preparation.