The record behind this case
Illustrative LOST report line: SKU TRAIL-01, potential value $126. The prepared message still needs the correct record identifiers and any missing details. Amazon decides eligibility and the amount.
← How Rivet Rocket helpsYour refunds.
For US Seller Central brands with FBA inventory
Your refunds.
A clear next step.
Turn Amazon’s reimbursement report into a clear case board. Review the prepared message, file in Seller Central and track each case through to payment.
Refund Logic · Rivet Rocket
RrivetrocketIllustrative data
A conversation with context
Example exchangeYour AI brand manager
What needs my attention this week?
R
Restock your top seller first.
Your top seller has 18 days of stock against a 30-day lead time. Without inbound stock, that leaves a 12-day gap. Confirm whether incoming stock can arrive in time. Make that check before running a price test.
Stock: example snapshotLead time: brand assumption
↗
Ask the follow up question
“How many units should I send in?”
Reimbursement-report cases
Illustrative statesTrack the next case step
| Case | State | Next step |
|---|---|---|
| RR-1042 | Ready to file | File in Seller Central |
| RR-2086 | Follow-up due | Check the response |
| RR-3191 | Payment matched | Review the match |
↗
The report and case history together
Your team files in Seller Central and records the case ID and responses. Refund Logic flags a 14-day follow-up and matches payment records. It does not audit shipments or file cases automatically.
A decision you can explain
Example productReview the price test
Current price$24.80
→Suggested test$25.10
Sales trendReview recent demand
Stock contextCheck available cover
ExecutionYou choose the change
↗
Small change. Clear reasoning.
Review the recommendation and supporting data before choosing your next test.
Plan your next shipment
Example forecastInventory cover
TodayLead timeTarget cover
Stock on handCompare with inbound units
ReplenishmentReview timing and quantity
↗
Check the lead time assumption
Your shipment plan depends on when the next units can reach Amazon.
Where shoppers leave
Example findingSearch performance
People see us. Why aren’t they buying?
R
Start with the step where share drops.
Compare your share of clicks, cart adds and purchases with the market. Review the listing and price before deciding where to spend.
↗
A weekly list of searches to investigate
Ask AI about the finding and choose your next check.
Inside Refund Logic
From a report line to a resolved case.
See what needs your action, review a prepared message and keep every case moving. Payment matching closes the loop.
US Seller Central · FBAFollow the four steps or replay the animation. The interface is simplified and all figures are illustrative; no live account is connected.
Coverage and boundaries
Positive report lines become cases; this is not a warehouse or shipment audit. You file in Seller Central and record Amazon’s replies. Payment detection needs the exact case ID. Managed filing is a separate service.
RRefund LogicIllustrative workflow
01Amazon reimbursement report
02Case board + prepared message
03You file and record replies
Ready to file
Filed
Follow-up needed
RETURN · $48You · Follow up14 days without a recorded reply
Approved
Resolved
LOST · Sample case$126.00SKU TRAIL-01Payment matchedSUCCESS
Five case stages · Scroll the board to explore
Case record · illustrative
Potential value: $126 · Actual recovered: $126
Recorded case ID: EXAMPLE-1042 · Matched on Amazon’s reimbursement report.
01 / Report → board
A positive reimbursement-report line becomes a Ready to file case. Amazon decides eligibility and the amount.
02 / Review the message
Open the case and review its prepared message. Copying it does not file anything.
03 / You file + record
Submit in Seller Central, then record the Amazon case ID. Record replies yourself; 14 days without a recorded reply triggers a follow-up.
04 / Payment matched
When Amazon posts a payment matching the recorded case ID, the case closes as won. The time between these steps varies.
Time compressed · Sample data
A positive reimbursement-report line becomes a Ready to file case. Amazon decides eligibility and the amount.
Open the case and review its prepared message. Copying it does not file anything.
Submit in Seller Central, then record the Amazon case ID. Record replies yourself; 14 days without a recorded reply triggers a follow-up.
When Amazon posts a payment matching the recorded case ID, the case closes as won. The time between these steps varies.
Illustrative interface and prewritten example. No live connection or account action.
Read the example in detail
The filing handoff
Review the message → submit it in Seller Central → record submitted case EXAMPLE-1042 in Rivet Rocket. Copying the message alone never submits a case or starts the reply clock.
When the case needs you again
Record Amazon’s response yourself: approved, more information requested or closed. With no recorded reply after 14 days, the case needs follow-up. Refreshing reimbursements does not read the case inbox.
What closes this sample case
The example assumes Amazon approved the case and later posted a $126 payment against EXAMPLE-1042. The matched case ID closes it as won. Reversals are tracked separately and never become cases to file.
A more useful view
Know where to start
See cases ready to file, follow-ups due and payments received.
Spend less time preparing
Copy a prepared case message, check the details and submit it in Seller Central.
Keep the case moving
Record Amazon’s replies. Follow-up flags appear after 14 days, and matching payments are detected automatically.
From the finding to a decision
Know what the case needs.
Refund Logic organizes positive lines from Amazon’s reimbursement report into a case board. It does not audit warehouse or shipment records for claims missing from that report.
Identify the event
Inbound shipments, fulfillment-center inventory, customer returns and removal orders need different records. These are investigation categories, not a claim that Rivet Rocket currently supports all four. Start with the policy guide.
Reconcile the records
Match product and event identifiers, affected units, inventory restoration, prior cases and reimbursement transactions. An unresolved flag still needs an eligibility and deadline check.
Choose who files
Your team can retain responsibility for submission and follow-up. Ask Alfredo whether additional filing help is available for your account and what it includes. Compare a written quote in the fee calculator.
Prepare one case packet
Bring marketplace, event type, SKU or FNSKU, order or shipment ID, dates, unresolved quantity, evidence references and the existing case ID. Download the blank case log (CSV) and follow the filing checklist.
Before connecting data, confirm the supported authorization route, required permissions, history available, refresh timing and how to revoke access. This website does not collect Amazon account data.
How it works
A question.
A useful next step.
- 01
Review your refund brief
Start with the cases that need your action.
- 02
File and record the case
Submit in Seller Central, then save the Amazon case ID in Rivet Rocket.
- 03
Follow it through
Record replies and review payments. Managed filing help is a separate service.
Questions, answered
The details matter.
A few things worth knowing about the tools and the next step.
Does a flagged case guarantee a reimbursement?
No. A flag is a case to investigate. Eligibility, evidence, filing windows and Amazon’s decision determine whether a reimbursement is approved.
Which accounts does this support?
Refund Logic supports the US marketplace and FBA reimbursement records in Seller Central. Vendor Central accounts are not supported.
How much does it cost?
Brands: $297/month. FBA Builders: $97/month + usage. Agencies: $497/month + usage. Confirm account scope, usage rates where applicable and any separate services on your demo.
Are the examples real customer results?
The website uses illustrative examples. On the demo, we show how the workflow applies to your business and confirm the data and features your account can use.
Keep exploring
The thinking behind the tool
Put the finding in context.
Amazon reimbursement policy: eligibility, timing and valuation
Check the claim type, marketplace rules and evidence before treating an FBA discrepancy as money owed.
Read the guideHow to file an Amazon reimbursement claim
Build an evidence packet, check eligibility and track one case through its resolution.
Read the guideAmazon reimbursement fees: DIY, tool access and managed recovery
Compare the fee basis, filing work and net recovery before choosing reimbursement support.
Read the guideFBA returns reimbursement: reconcile the refund and the unit
Match customer refunds to return, inventory and reimbursement records before preparing a claim.
Read the guideAmazon lost inventory reimbursement: trace the missing units
Follow inventory events and existing resolutions to document an unresolved loss or damage case.
Read the guideStart with your work
Find your next
useful move.
Show us what you manage or want to build. We’ll walk through the features, confirm your setup and give you clear next steps.
Book a demo No account connection needed for the call.