GETIDA review: a recovery model that genuinely works, and one question almost nobody asks it

The commercial model, and why it deserves credit

Start with what is on GETIDA's own pricing page, read on 20 August 2026. There is no monthly subscription. Their published rate is performance-based pricing starting at 25% of reimbursements actually recovered, invoiced periodically, and new accounts pay nothing on the first $400 recovered. The company describes itself as free to join with no commitment.

That structure is the strongest thing about the product, and it is worth being explicit about why rather than treating it as a bullet point. A contingency fee makes the vendor's downside identical to yours. If the audit finds nothing, you have spent nothing beyond the hour it took to connect the account. If it finds a great deal, the fee scales with a number that was previously zero. There is no scenario in which you are worse off in cash terms than you were before you started — which is a claim almost no other software purchase in this category can make.

It also removes the objection that stops most sellers from ever addressing reimbursements: not the cost, but the fear of committing budget to something they cannot size in advance. With contingency pricing you do not have to size it. You find out by doing it.

Set against that, understand what a quarter of the recovery means at scale. On $100,000 recovered in a year, 25% is $25,000 — and 25% is the published floor rather than a ceiling, so confirm your own rate in writing. That is a large number in absolute terms, and it is the correct number to negotiate on if your volumes are substantial — contingency rates in this category are commonly banded by volume, and it is entirely normal to ask. But it is a percentage of found money, which is a materially different thing from a percentage of revenue you would have earned anyway.

What Amazon changed in 2025, and what it did to the arithmetic

This is the part missing from nearly every ranking review of this service, and it matters more than any feature comparison.

Amazon's updated FBA inventory reimbursement policy took effect on 31 March 2025, having been announced for earlier in that month. The central change: reimbursements moved towards being valued at the manufacturing or sourcing cost of the lost or damaged item rather than at its selling price, with sellers given access to a portal for submitting their cost documentation ahead of the switch.

Three consequences follow, and they cut in different directions.

• The pool shrank in dollar terms. A unit that would once have been reimbursed near its retail price is now reimbursed nearer what you paid for it. Every historical recovery figure quoted in older reviews — including impressive ones — describes a world with a bigger pool than the current one.
• Your own data now sets the payout. If your sourcing cost information is missing or wrong, the valuation is decided without your input. This is the single highest-leverage thing a seller can fix, it costs nothing, and no recovery vendor can do it for you. Before you evaluate any service, go and check your cost data is complete.
• The easy categories got easier for Amazon to handle itself. Where Amazon identifies and settles an issue automatically, there was nothing for a third party to find. That pushes the value of a recovery service towards the harder categories — inbound discrepancies, removals that never arrived, damage attribution, fee-level errors — and away from the simple lost-unit case.

None of this makes the service less worth having. It makes the basis of comparison different, and it means a review written before spring 2025 is describing a different economic product.

The question almost nobody asks a recovery vendor

Given the above, here is the diligence question that matters most and that we have never seen printed in a ranking article:

How does the vendor distinguish recoveries it caused from reimbursements Amazon would have issued anyway?

Ask it directly, and ask how the answer is reflected on the invoice. A vendor whose commission is calculated on cases it opened, evidenced and pursued is charging for work performed. A commission calculated on the total movement in your reimbursements report is a different thing, and at scale the difference is not small. This is not an accusation against anybody — it is a question every buyer should be able to answer about their own supplier, and a good vendor will have a clear answer ready.

Four more worth asking any recovery service, in this order:

• Which claim categories do you cover, specifically? Lost and damaged units, inbound shipment discrepancies, removal orders, customer return and refund mismatches, and fee-level errors are separate disciplines. Few vendors cover all of them well.
• How quickly do you file relative to the window? Filing windows are counted in days per issue type. A vendor with a backlog can identify a claim perfectly and still miss it. Ask for median days from detection to filing.
• Do you touch size-tier and dimension overcharges? Most recovery services do not, because it is a dispute rather than a claim. It is also frequently the largest recurring leak in the account.
• What happens to my data and my rate if you are acquired? Ownership in this category moves often. Change-of-control, price-protection and data-portability clauses are ordinary diligence, and you should ask us the same thing.

How to read the evidence on this company

GETIDA publishes a set of claims about its own performance: that its sellers recover substantially more than sellers who do not use it, that it secures a high proportion of the claims it opens, that it gets a meaningful share of previously unsuccessful claims approved, and that it audits an enormous volume of FBA transactions daily. It also states that it is an authorised Amazon selling partner, available through the Selling Partner Appstore, and describes involvement in beta testing Seller Central features.

Handle those the way you would handle any vendor's self-reported numbers: they are not dishonest, they are not independently audited, and they are presented by the party with an interest in them. The Appstore listing is the most useful item there, because it is a third-party fact rather than a claim — it means the integration has been through Amazon's own review process.

The public review corpus is a weaker guide than it looks. It is scattered across consumer and B2B directories, the samples on each are small, and small samples in a contingency business skew hard: sellers with nothing to recover leave disappointed reviews about a service that worked exactly as designed and found little, while sellers with large recoveries are unusually happy. Averaging those tells you about the accounts, not the vendor.

The evidence that is actually decisive is your own. Because the model is contingency, you can run the experiment for the price of an integration and a month. If the audit surfaces material money, you have your answer. If it does not, you have learned something valuable about your account for free — namely that your leak is somewhere else.

What a recovery service does not cover, and where the bigger leak usually is

Recovery is one line in the supply-side ledger, and for most brands it is not the largest one. Here is what sits alongside it, untouched by any contingency claims service:

• Size-tier and dimension errors. Amazon bills fulfilment against its own recorded measurements. When those are wrong, the overcharge repeats on every unit shipped, indefinitely, and correcting it is a dispute someone has to raise and follow through. This is a recurring leak, not a one-off claim, which is precisely why it falls outside most recovery mandates.
• Ageing stock. Amazon's FBA page states that units held in a fulfilment centre beyond 181 days attract an aged-inventory surcharge, monthly, on top of ordinary storage. Nobody claims that back. You either decide before the assessment or you pay.
• Reorder timing. Stockouts cost rank, and rank bought back through advertising costs more than the stock would have. No recovery service is watching that.
• Returns economics. The true landed cost of a return by SKU — reverse logistics, disposition, grading, restocking — is rarely calculated and frequently changes which products are worth selling at all.

It is also worth knowing that recovery is increasingly bundled. One suite we read on 20 August 2026 attaches a reimbursement commission to each subscription tier — 15% on its lower plans and 5% on its top one — which is a different economic shape from a standalone contingency and, at the top tier, a notably low rate. Worth modelling against a pure contingency arrangement if you are already paying for a suite.

Where we come in, and where we would rather not

Dr. Stock does not fulfil orders, is not a system of record and is not an ERP. Nor is it a contingency recovery service — we do not price on a percentage of what we find, and if pure reimbursement recovery is the only thing you want, a specialist charging nothing unless it succeeds is a sound purchase and we will not argue you out of it.

What Dr. Stock is: the whole supply-side queue run as a product. Fable 5 on Amazon inventory and supply chain — reorder timing and stockout risk, storage and aged-inventory exposure, remove-or-liquidate decisions, fee and dimension disputes, inbound discrepancies, claim recovery and returns cost per SKU — with human operators supervising at an autonomy level you set. Purchasing decisions always come back to a person.

Those operators come from Full Circle, a full-service Amazon management company with $500M+ in managed revenue across 100+ brands. We publish no price for Dr. Stock — a demo, the first 30 days free, and a figure agreed on the call. On transparency, a vendor publishing a flat percentage on a public page is ahead of us, and we would rather concede that than talk around it. Orbit is included at no extra cost.

One redirect worth making: brands often start hunting reimbursements because margin has slipped and recovery feels like the fastest lever. Frequently the money is not in the warehouse at all — it is spend landing on search terms that never convert, which is an ad account repair and Dr. PPC's job, not ours.