Financials · P&L · Reconciliation · FIFO · Inventory truth · Tax
Amazon FBA profit tracking, from the settlement. Not what you probably made. What the deposits say you made.
This page is why Remworth exists. Your P&L is computed from Amazon's settlement statements — the reports behind your actual bank transfers — plus the real cost of the real units that filled each sale. When a number can't be proven yet, you see the gap, labeled. Never a guess wearing a dollar sign.
7 days free · the full product on your real data · card required · cancel any time
- Deposits
- read order by order — picture a $12,000 payout, every line explained
- Sales settled
- every sale, matched to the money it actually brought in
- Reconciliation
- every statement checked line by line, delta shown per statement
- Held funds
- visible under their own label, never blurred into profit
- Scale
- built to run at thousands of ASINs without rounding anything
- Their revenue
- never matches Seller Central, so you stop trusting the rest
- Their fees
- a table that ages, finalized weeks late, unmarked
- Their costs
- whatever you typed, averaged per ASIN
- Their returns
- the double-count most profit tools silently keep
- Their deposit
- the one unarguably real number — never looked at
Three screens, three profit numbers, one shrug.
Seller Central says you sold $40K. Your card says you spent $28K. Your old tool says a third number it can't explain, built from estimated fees over a cost you typed once in 2024. At tax time the gaps are your problem. The tools you pay for estimate fees off stale tables, average your costs per ASIN, book returns wrong, and drop statement lines they don't recognize — silently. You don't have a profit problem. You have a proof problem.
- The statement
- profit per product, from settlements
- The trail
- every sale's cost, traceable to the supplier order
- The check
- every deposit reconciled line by line
- The truth
- Amazon's live inventory next to your books
- The switch
- your old listing tool's history imported, match rate shown first
The money questions, each with its own screen.
P&L per product per period → FIFO cost layers → Settlement reconciliation → Payout tracking → Phantom-stock detection → Cost Basis → Supplier profitability → Velocity → Sales tax by state → Ledgers for refunds, reimbursements, removals, and freight → SKU economics → Sales trends → Subscribe & Save → Your history, imported.
- Cards
- revenue (confirmed + pending), FBA/FBM split, buyer-paid shipping and gift wrap, itemized Amazon fees, COGS, inbound shipping, other fees by category, ad spend, misc (coupons, chargebacks, SAFE-T), profit, net refunds, reimbursements — each with a prior-period delta
- Drill-down
- any product → recent sales with full order IDs, per-sale profit, Settled/Pending badges, and a batch timeline: Purchased → Received → Prepped → Shipped → Live → Depleted
- Held funds
- DD+7 banner keeps "earned" and "available" visibly separate
- Quarantine
- orders Amazon hasn't confirmed sit in their own section — visible, never inflating profit
- Periods
- today, 7d, MTD, last month, 30/90d, YTD, all time, any month or week of your history, custom ranges
A profit statement, not a profit vibe.
Computed per product and per period from Amazon's own settlement data plus your recorded costs. The formula nets FIFO COGS, inbound freight, refunds after fee returns, reimbursements, storage and service fees, ad spend, promotions, and removal outcomes — searchable by ASIN, SKU, or title, running at real scale — thousands of ASINs without averaging anything. Revenue is principal-only, so it reads against Seller Central exactly. Run that comparison on day one of your trial; we built the number to survive it. Returned-and-restocked units get their cost credited back — the double-count most profit tools silently keep, removed. And the export is tax-ready in one click: a one-page P&L Summary, by ASIN, by supplier, or by month — CSV or Excel, honoring any range, footing line by line with contra-COGS credit lines included. A year of monthly P&L rows in one file is what keeps your accountant calm in January.
- Layers
- per received batch, at the price actually paid — later edits on other orders never contaminate it
- Pack sizes
- buy in cases, sell in a different configuration — unit conversion happens once, at the right boundary
- Freight
- inbound freight split per sellable unit Amazon receives, folded into COGS — landed cost, not invoice cost
- Corrections
- fix a buy cost later and it applies to that supplier order only; siblings keep their locked cost
- Edge honesty
- layers sold through → fallback to your last known purchase price, so profit never silently overstates; unknown cost → a dash, never a fake $0.00
Every sale carries the exact cost of the units that filled it.
Every received batch becomes its own cost layer at the exact price paid. Every sale consumes layers first-in-first-out — so each individual sale carries its true cost of goods. No ASIN-level averaging. A sale spanning two purchase prices gets the exact weighted cost, stored on the sale itself, forever. And the trail is permanent: any sale traces back to the exact supplier purchase that supplied its units. Ask your current tool why a sale shows $4.12 of cost. If it can't answer, neither can you.
- Badge
- Settled / Pending, on every sale row
- Refresh
- projections refreshed automatically, from Amazon's fee estimates
- Rate card fidelity
- peak season, price bands, apparel, DG, fuel surcharge
- Long tail
- storage, long-term storage, disposal, removal, subscription, inbound transport, refund-admin fees — all from settlement data
- Self-audit
- projections vs. settled reality, on a schedule
You always know which math you're looking at.
Actual FBA, referral, closing, and other fees are recorded per sale from Amazon's financial events as they settle. While Amazon takes its 2–4 weeks, projections stand in — refreshed automatically, computed from the official rate card including peak-season pricing, price-band tiers, apparel and dangerous-goods programs, and the fuel surcharge. Every sale row wears a Settled or Pending badge. And the projections are graded: checked against what Amazon actually settles, on a schedule. A tool that audits its own estimates — find another one.
- Refund ledger
- date, ASIN, qty, amount, fees returned, net impact including Amazon's kept commission — searchable, period totals
- Reimbursement ledger
- reason, case ID, order ID — matched to Amazon's payout report to the cent, net of unit cost, quarantined unmatched credits shown
- Removals ledger
- count, units, fees, liquidation proceeds per period
- Freight ledger
- every FBA shipment's cost, boxes, weight, carrier
- Self-healing
- orphan refunds re-matched to their original sale automatically; re-syncs apply cleanly, no duplicates
Profit doesn't end at the sale. Neither do the books.
Customer returns subtract their true net cost — refund paid, minus fees Amazon returns, plus the administration fee Amazon keeps: the cost most sellers have never seen itemized. Reimbursements count as income without double-counting the unit's cost. Removals book as the losses or credits they really are, restated into the correct period. And double-count protection is structural: a returned or reimbursed unit's cost is recognized exactly once no matter what order Amazon's events arrive in — enforced by the engine, not by cleanup jobs. This is the part where DIY spreadsheets die.
- Granularity
- per statement, per money category, with a delta each
- Red flags
- internal-check failures, deposit orders missing from the books, never-seen line types — surfaced on tiles, detailed on expand
- Unmatched orders
- surfaced by order ID, never silently absorbed
- Unknown line shapes
- flagged the moment Amazon invents one — never dropped
- Lifetime
- total deposits tracked, to the cent
A deposit you can read. Order by order, line by line.
Every settlement statement Amazon issues is checked against your books, line by line — revenue, fees, promotions, refunds, reimbursements, ad spend, each with a per-statement delta, plus a lifetime deposit total. Statement lines the categorizer doesn't recognize are flagged loudly, never silently dropped. Take a $12,000 deposit as a worked example: Remworth reads it order by order and shows where every dollar came from — and if the books disagree with the statement by $40, you see the $40, per category, instead of a shrug. A light deposit stops being a mystery. It becomes a list.
- Expected
- amount, date, statement period, account type
- Completed
- date, amount, status, payment method with account tail
- Trace ID
- on-screen, bank-ready
- Warnings
- AT_RISK, DISABLED, NO_PAYOUT_EXPECTED, FAILED, CANCELLED — verbatim, highlighted
- Held
- the DD+7 balance visible under its own label — never blurred into profit
The one reason you still log into Seller Central, retired.
Every expected payout — amount, scheduled date, statement period, account type — and every completed bank transfer on one card, synced automatically, with the held balance refreshed around the clock. Cash-movement only, so it can never contradict the profit numbers. Completed transfers show the bank trace ID you'd quote when a deposit hasn't shown — the twenty-minute hunt, reduced to reading a field. If Amazon flags a payout, you see it in amber, in Amazon's own words, before it blindsides you.
- On-hand
- one true number per product, hover-split across Amazon / warehouse / prep / staged boxes
- Aging
- Amazon's six age buckets per SKU, aged-inventory surcharge estimates months before the fee hits, sell-through, days of supply, recommended action, dated CSV export
- Shrinkage
- movement ledger ingested continuously; disappearing units alarmed by ASIN
- Claims
- reimbursements tracked automatically; opportunities flagged; expiring claim windows highlighted
- Valuation
- the inventory dollar figure anchors to what Amazon actually reports, not what the books wish
The books say you own units Amazon doesn't hold. This screen finds them.
The Inventory Workbench puts Amazon's live feed next to your cost ledger, per product: fulfillable, reserved, inbound, unsellable — beside your warehouse, units mid-prep, and boxed shipments Amazon hasn't been told about yet. When the books claim more than reality holds, the row flags as phantom stock — shown honestly with a one-click filter, never silently zeroed. Picture 40 phantom units scattered across a dozen ASINs: paid-for inventory most tools quietly keep counting as owned. The watch runs deeper than the snapshot: Amazon's inventory movement ledger is ingested continuously with automatic alerts when units disappear outside a sale, and reimbursements are ingested automatically — with potential claim opportunities flagged and expiring claim windows highlighted, so found money doesn't time out. What's recovered is yours.
- Policy
- no cost, no fake profit — held out and shown
- The fix
- one save per product corrects all its sales and reports the COGS added
- Stakes
- dollars excluded, listed per product
- Reimbursements
- quarantined credits reviewed and booked with a preview before anything is written
- Returns
- inline costing for units Amazon restocked, right in the workbench
Every uncosted sale, listed with the dollars at stake. Fix each in one save.
Sales with no recorded cost are excluded from profit rather than booked at a fake $0 — and this tab is where the policy becomes livable. It lists exactly those products: image, sale count, units, the revenue currently held out. Type what you paid per unit — supplier autocomplete included, create a new supplier inline — and one save re-costs every uncosted sale of that product and folds the revenue back into your P&L. Green all-clear when everything is costed. Started tracking mid-year? This is your first afternoon, and it's shorter than you think.
- Columns
- committed / stuck / realized / unique ASINs
- Basis
- reconciled sales only — clean, not optimistic
- Attribution
- by the cost layer that sold, not the ASIN
- Drill-down
- per-ASIN ranking inside each supplier
- Use
- the drop-this-supplier detector
Committed. Stuck. Realized. One row per supplier.
Profit rolled up where wholesale decisions actually happen: total capital committed to each supplier, dollars sitting in their unsold stock, realized profit, unique ASINs — each row expanding to a per-ASIN ranking within that supplier. Realized profit counts only sales Amazon has fully reconciled; pending revenue is shown separately with tooltips, never mixed in. And because attribution runs on cost layers, sales credit the supplier whose stock actually sold — dual-sourced products never double-count in both rollups. Take this table into your next price negotiation.
- Clock
- full cycle, purchase → sold out
- Segments
- supplier / your prep / Amazon's dock / the shelf
- Scope
- account average + per ASIN
- Companions
- sell-through and turnover
- Search
- by ASIN or supplier
How long does your dollar take to come home?
Purchase to sold out, timed — account averages and per-ASIN rows, searchable by ASIN or supplier, with sell-through and inventory turnover. Broken into segments: supplier lead time, your internal turnaround, Amazon check-in, and sell-through at FBA. Slow is a symptom; the segment tells you whose slow it is. Three different problems, three different fixes, finally distinguishable. Cash-cycle time is what caps a wholesale seller on fixed capital — and almost nothing in this category measures it.
- View
- one line per state, per period — year, quarter, or month
- Separation
- item tax ≠ facilitator tax, strictly, with disclosures
- Detail
- state-by-month grid for any metric
- Export
- flat CSV for your accountant or filing tool
- Geography
- by-state and by-city demand, addressless orders bucketed honestly
Open tab. Pick quarter. Read your state's line.
Pick a year, then full year, any quarter, or a single month — every state on one line: gross sales, taxed sales, tax collected, marketplace-facilitator tax, and tax refunded shown as the negative it is. Item tax and facilitator tax are kept strictly separate — different bases, never summed into a misleading "total tax" — with plain-English disclosures saying what each figure includes. That separation is the difference between filing correctly and filing marketplace-collected tax as your own liability. Next door, Geographic Sales maps orders, units, revenue, and distinct ASINs by ship-to state with share bars and a by-city toggle — and orders without address data are counted honestly in their own bucket rather than skewing the map.
- Trends
- 30 days to 24 months, live from Amazon's own sales numbers each view
- Cuts
- FBA/FBM, B2B/B2C, single ASIN, by category
- Honesty
- dashed "to date" bars; ordered-vs-settled basis stated on screen
- SKU economics
- which SKU the storage and ad money is going to — answered
- S&S
- forecasts next to stock risk; funding percentages side by side; CSV export
Amazon's own numbers, cut the ways you actually ask.
Sales Trends: interactive charts on Amazon's ordered-basis numbers, fetched live each view — the same numbers behind Seller Central's business reports — units as bars, sales as a line, presets to 24 months, day/week/month granularity, FBA/FBM and B2B/B2C filters, single-ASIN drill-down, and a sales-by-category table filled automatically from Amazon's catalog. The current incomplete period renders as a dashed bar labeled "to date," and every chart states its basis on screen — a partial month never masquerades as a sales dip. SKU Economics: Amazon's per-product attribution the settlement structurally can't provide — per-ASIN ad charges and per-ASIN storage, under Amazon's verbatim fee names, smaller fees folded into "Other" with the math shown; group by MSKU, ASIN, or parent; the CSV carries the same basis disclosure as the screen; if Amazon hasn't published today, the freshest covered window is named instead of faked. Subscribe & Save: the whole program synced automatically — eligibility, price, inventory, stock risk, active subscriptions, all four discount-funding percentages side by side (see who's actually paying for that 15%), and 15/30/60/90-day delivery forecasts beside stock risk so a subscription SKU never dies mid-cycle — with honest deep links to Seller Central for the two actions Amazon reserves to itself, enrollment and discount edits.
- Scorecard
- per scan: passes, hit rate, avg ROI, best profit, scan-value score
- The unique column
- Real Est. Order Profit — predictions meet purchases
- Stats bar
- 24h / 7d / 30d / 1y, sparklines and change vs. prior period
- Scan control
- live progress, cancel mid-flight, resume skips finished steps
- Reminders
- refunds approved but not yet posted, surfaced
Which price lists actually make you money?
Every scan, scored: products, passes, hit rate, average ROI, best profit, total estimated profit — and the column no scanning tool has: Real Est. Order Profit, the estimated profit of the items you actually ordered from that scan. Prediction tied to purchase. Rescan the lists that pay; drop the ones that don't. A stats bar runs 24-hour to 1-year views of scans, products, matches, SKUs ordered, and purchased ROI, with sparklines and deltas. Live progress on running scans with cancel and resume. The supplier-refund follow-through banner sits here too — approved refunds awaiting card verification, with order numbers, amounts, and days waiting.
- Orders
- as fast as Amazon allows, with automatic re-syncs and a corrector that heals history
- Settlements
- ingested automatically; a rolling reconciliation pass catches late-posting fees, refunds, and reimbursements
- Returns
- synced continuously; sellable-graded units restored to cost tracking unit by unit
- Inventory
- snapshots, stranded checks, age, SKU economics, S&S, and the held balance — all refreshed automatically, around the clock
- Safety net
- connection health checked automatically, with an email before data stops flowing; off-site backups, 30 days retained
No sync button. It runs itself.
Connect once through Amazon's official consent flow — approve in Seller Central, done, no developer keys to paste. Verification runs live before anything saves; a wrong or non-US account is refused with nothing stored; saved secrets are write-only, never echoed back to a browser, and encrypted at rest. Then it runs itself, around the clock — and if a notification ever hiccups, scheduled syncs still cover everything: data arrives a little later, never wrong.
- Preview
- everything shown before anything is written — match rate included
- Costs
- from your own SKU history, nothing estimated; every held-back unit listed by reason; a checkbox holds back possible re-listed returns so a cost never counts twice; optional FBA Inventory export prices never-sold units
- After import
- fees, refunds, freight, and service fees re-book across history automatically; ad spend imports only after your explicit review, with a full preview
- Safety
- idempotent — re-running a file books nothing twice; if the books changed between preview and apply, it demands a re-preview; very large files chunked automatically
- Access
- owner-only, like every operation that restates the books
Your years of history come with you. Match rate shown before you commit.
Upload the FBA sales export from the listing tool you're leaving. Before anything is written, you see exactly what will happen: new sales, skipped duplicates, date range, revenue, costs, fees, gross profit — including a percentage reconciliation against your old tool's own profit numbers. Then years of orders import with a live progress bar. The Disposition Management import goes further: it finds units Amazon removed or destroyed that your old tool still counted as owned, previews the exact dollar total, and books each loss into the year it actually happened — per-year restatement shown openly. And the Amazon Settlement History import is a guided four-step flow — deep link straight to Seller Central's statements page, request, download, drop the files here — that ingests years of statements; ten minutes of clicking brings in years of real costs. Migration here isn't a copy job. It's the first honest audit your books ever got.
- Cadence
- automatic, plus Sync Now on demand
- Preview
- dry-run shows the exact would-change diff before any push
- Your edits
- min/max set by hand in Aura are left alone until your cost basis actually changes — and the sync summary counts how many of your tweaks it deliberately preserved
- Exclusions
- per-SKU list for products you manage by hand
- Audit
- a recent-pushes log of every update that went out
Aura never reprices below your true break-even. Because we feed it the truth, automatically.
Connect your Aura account and each SKU's current true FIFO cost and min/max prices push automatically, staying in lockstep with your real purchase history. A repricer running on a stale or guessed cost will win the Buy Box at a loss a hundred times before you notice. This one can't — its cost is the same figure your P&L uses. Aura is live today, and more repricers — BQool among them — are being added, so you can sync whichever repricer you run.
The audit, self-serve
Seven days is enough to catch us being wrong. Try.
Connect, import, compare to your bank deposit. If our number doesn't hold up, cancel from the billing portal yourself.