← Friday Seller Tools

Seller guide

How do I verify Amazon Low-Price FBA fees below my supplied threshold?

Match seller-redacted FBA fee rows to a seller-supplied standard and low-price rate card, then separate threshold arithmetic from Amazon's actual eligibility decision.

Freeze one fee window and the terms you intend to test

Choose one reporting currency and as-of date. For each redacted row, keep a seller-owned reference, SKU, optional ASIN, item price, fulfilled units, size tier, shipping weight, and recorded fulfillment-fee total. Separately enter the seller-observed Low-Price FBA price threshold and a dated rate card containing standard and low-price per-unit rates for each size-tier and weight band. Remove buyer, order, address, contact, payment, and message fields. A historical charge should be tested against terms from the same period, not today's schedule or a remembered threshold.

Validate every rate-band join before doing fee math

Give each rate row a unique code, exact size-tier label, exclusive lower weight bound, inclusive upper bound, standard rate, and low-price rate. Reject overlapping bands and any fee row that does not match exactly one band. Treat a weight equal to the upper bound as inside that band and a weight equal to the lower bound as outside it. Never choose the nearest band merely to calculate a result; a missing join is a source-data task, not a zero fee or an automatic standard-rate row.

Recompute both scenarios and choose only by the supplied price rule

Mark a row inside the supplied price threshold when item price is less than or equal to that threshold. Multiply fulfilled units by the matched low-price rate for that scenario; otherwise multiply by the standard rate. Round the batch row once to cents. Keep the low-price total, standard total, selected basis, recorded total, and signed recorded-minus-expected difference together. Also show the standard-minus-low scenario saving for inside-threshold rows so the seller can see the supplied rate-card impact without calling it realized.

Separate a standard-like charge from other differences

When an inside-threshold row's recorded total is close to the supplied standard scenario, put it in a dedicated source-review band. Rank that band before other positive and negative differences, then keep reconciled rows as context. Total recorded-above-expected and recorded-below-expected amounts separately rather than netting them. This pattern is useful evidence for checking price timing, offer state, category, program status, measurements, and adjustments, but it does not prove Amazon used the wrong fulfillment fee.

Confirm live eligibility and source rows before acting

Open the authorized fee record and current program terms for the highest-ranked aliases. Verify the price basis, effective time, offer and item eligibility, size tier, shipping weight, units, credits, taxes, and other omitted rules. Being inside a seller-supplied threshold is arithmetic, not an Amazon eligibility conclusion. Friday reads no Amazon account, embeds no threshold or fee table, opens no case, requests no credit, changes no price, offer, listing, fulfillment setting, inventory, or account, and publishes no listing.

Tools that help with this

Prices below are exact x402 per-call prices. Human card checkout uses fixed $3, $9, and $29 bundles; follow a tool page to see its applicable bundle.

Every paid output is a draft for your review before you publish, appeal, or activate anything. Friday does not access your seller account.

More seller guides

Browse all guides →