How Amazon Removals Partners Price Their Service: Three Fee Models Compared

![]()
FBA Removals Europe
Turn Amazon Removals Into Controlled Inventory Recovery. FLEX. receives, identifies, checks and processes your removed FBA stock in Europe, helping sellers separate sellable units, damaged inventory, rework cases and disposal decisions before value disappears from the operation.
A seller running a routine ASIN cleanup gets three quotes for the same 500-unit removal order: one flat fee, one priced per unit, one priced as a share of recovered value. The totals look close on paper, but six months later the outcomes are not close at all. The partner paid a flat fee did the minimum sort-and-ship. The per-unit partner processed everything at the same speed regardless of item value. The recovery-share partner quietly deprioritized the slow-moving SKUs because reworking them wasn’t worth their time.
This is the real decision behind choosing an Amazon removals partner: not who is cheapest, but whose pricing structure rewards the behavior you actually need. Fixed-fee, per-unit and recovery-share pricing are not interchangeable options with the same economics wearing different labels. Each one changes what the partner is incentivized to do with your stock, and that incentive shows up directly in your recovery rate. This comparison works through a 500-unit example under each model, then flags where recovery-share pricing can quietly work against sellers holding aged or low-turnover inventory.
What each pricing model actually charges for
Fixed-fee pricing charges a flat amount per removal order or per shipment, regardless of how many units are inside or what happens to them afterward. It is simple to quote and simple to budget, which is why many sellers default to it without checking what is included. The catch is scope: a flat fee covering receiving and disposal is a very different service than one covering receiving, grading, relabeling and resale routing.
Per-unit pricing charges a set rate for each item processed, sometimes with tiers based on size or handling complexity. This model scales more predictably with volume and gives sellers a clearer per-SKU cost to weigh against resale value. It also means the partner gets paid the same whether an item is worth two euros or twenty, which matters when volume is mixed.
Recovery-share pricing takes a percentage of whatever value the partner recovers through resale, liquidation or relabel-and-return, and charges little or nothing upfront. This aligns cost with outcome on paper. In practice it aligns the partner’s effort with whichever units are fastest and cheapest to resell, not with the ones the seller most needs handled. That distinction becomes the core comparison question below.
Fixed-fee: what it controls
Under fixed-fee pricing, the seller controls scope in the contract, not through ongoing incentive. If the agreement specifies grading, photos, condition notes and a resale-or-dispose decision per unit, the partner has to deliver that regardless of item value. If the agreement is vague, the partner has room to do the fastest acceptable version of the work and still get paid in full.
This makes the initial statement of work the real control point, not the invoice. Sellers using fixed-fee removal order processing EU-wide should check whether the quote lists per-unit actions or just a shipment-level outcome. A one-line fee for “process removal” with no defined steps is a fee for ambiguity, and ambiguity favors the party being paid the same either way.
Fixed-fee: what breaks without it
Without a defined scope, a flat-fee partner has no financial reason to rework a slow-moving SKU carefully versus writing it off to disposal. The seller pays the same fee either way, so the partner’s margin improves by moving fast, not by maximizing resale. On a 500-unit batch with mixed SKU value, this can mean high-value items get proper attention while mid-tier stock gets bulk-disposed to protect turnaround time.
The commercial consequence shows up as a lower blended recovery rate than the seller expected, discovered only after the removal order closes and the units are gone. There is no mid-process signal that this is happening, because the invoice looks identical whether the partner reworked every unit or none of them.
Per-unit pricing changes the check the seller needs to run
Instead of auditing scope language, the seller should audit the rate table: does the per-unit fee vary by category, condition, or size tier, and does that tier structure match the actual SKU mix in the batch. A flat per-unit rate applied to a batch containing both bulky low-value items and small high-value electronics will misprice both ends.
The practical control point is asking for a sample invoice from a comparable past batch, not just a quoted rate. This shows whether the partner’s per-unit pricing has hidden minimums, handling surcharges for oversized cartons, or separate line items for relabel-and-return versus straight disposal. Amazon returns management service quotes that hide this detail tend to surprise sellers on the second invoice, not the first.

Worked example: 500 units under each model
Take a 500-unit removal order with a mixed batch: 100 higher-value units worth reworking, 400 lower-value units where resale value barely covers handling cost. Under a flat fee of, say, a fixed amount for the whole batch, the seller’s cost per unit averages out low, but the partner has no reason to spend extra time on the 400 marginal units — they get bulk-processed fast, and total recovery on that segment stays weak.
Under per-unit pricing, the seller pays roughly the same total handling cost as the flat fee example, but the cost is transparent per SKU. The seller can see exactly what the 400 low-value units cost to process and decide, batch by batch, whether it is worth continuing to send that SKU through removal versus disposing at source next time. That visibility is the main advantage over fixed fee.
Under recovery-share pricing, the partner earns nothing extra for the 400 low-value units unless they resell, so the rational move for the partner is to spend minimal effort there and concentrate rework on the 100 high-value units where the percentage cut is worth chasing. The seller’s cost looks lowest on paper — no fee unless something sells — but the low-value segment often ends up disposed rather than reworked, because reworking it for a small resale value is not worth the partner’s time at that percentage.

The owner-map question sellers skip
Who decides whether a slow-moving SKU gets reworked, relabeled, or written off. Under fixed-fee and per-unit pricing, that decision usually sits with the seller, because the partner is paid the same regardless of the outcome chosen. Under recovery-share pricing, the partner effectively makes that call, because their pay depends on it.
This matters most for aged stock and long-tail SKUs, where resale value is uncertain and rework takes staff time either way. A removal and return handling DE process built on recovery-share can quietly become a filter that discards anything below a margin threshold the seller never agreed to. If the seller wants control over that decision, recovery-share is the wrong default model for that segment of inventory, even if it looks cheapest at the quote stage.
Choose fixed-fee if
Batch is uniform in value, scope is fully defined in writing, and the seller wants predictable budgeting over per-unit visibility. Works best for single-SKU or narrow-range removal orders.
Choose per-unit if
SKU mix varies in size or value and the seller wants line-item visibility to decide, batch by batch, which SKUs are worth continuing to process versus disposing earlier in the flow.
Choose recovery-share if
Inventory is genuinely high-value and resale-likely, and the seller is comfortable letting the partner’s commercial interest decide rework priority within that segment.
Match the pricing model to the SKU, not the quote
The three models are not ranked best to worst; they are matched to different inventory profiles. A seller with a tight, high-value catalog and a partner who reworks consistently can do well on recovery-share pricing, because the partner’s incentive and the seller’s goal point the same direction. A seller with a long tail of aged, low-value SKUs is better served by per-unit pricing, because it keeps the cost and the decision visible batch by batch rather than letting a percentage-based incentive quietly filter out anything unprofitable to chase.
The practical next step is to stop comparing quotes as single numbers. Ask each amazon removals partner candidate for their rate structure broken down by SKU tier, their default action on low-recovery items, and a sample invoice from a comparable batch. If a recovery-share partner cannot show what happens to the units that do not sell, that gap is the answer to whether the model fits a mixed or aged batch.
Before signing anything, map the current batch against these three models side by side using real unit counts and estimated resale value, not averages. That single exercise usually makes the right model obvious faster than any quote comparison.
If you are weighing quotes across fixed-fee, per-unit and recovery-share pricing for an upcoming removal order, it helps to run the numbers against your actual SKU mix before committing. FLEX. can walk through the batch with you, flag where a given pricing model misaligns with your slow-moving stock, and outline how removal order processing EU-wide is scoped and invoiced in practice. Contact FBA Removals for a quote.

CONTACT
FBA Removals at Jakob-Uffrecht-Straße 16-18, 39340 Haldensleben, Germany


