Home
Upload your Amazon unified transaction report and the engine works out what you really made — per product, per batch, to the cent.
Start with your Amazon transaction file
In Seller Central: Reports → Payments → All statements / transaction view, or the unified transaction report you download for a date range. Drop the CSV here — everything is calculated in your browser; the file never leaves your computer.
Your costs and batches are already loaded (Barnetts batch + Sellerboard estimates, all editable under Data). The moment the file lands, every screen fills in.
Capital recovery — by batch
Biggest movers
Where the account-level money went
Every charge Amazon levied outside a specific product, itemised from this file. Note: the international shipping, customs and AWD rows for the Neeta sea shipment (and a $72 placement fee for the late air shipment) are already inside those batches’ landed costs — they appear here too because this is the complete account picture; don’t count them twice.
How to read these numbers
Confirmed profit uses landed costs worked from real invoices. Estimated profit uses Sellerboard COGS that nobody has verified against an invoice yet — treat it as a guide, not the truth. A product with no cost on file is never guessed: it shows as “profit unknown” and stays out of every total. Storage and other account-level charges are shown separately, never smeared across products.
Profit Truth
Every product, what Amazon actually settled, what the goods cost, and what is left. Click any profit figure to see the per-unit bridge.
| Product | Units | Sales | Settlement | COGS | Profit | Per unit | Cost basis | Reimbursed |
|---|
Profit unknown — no cost on file
These products sold, but with no landed cost anywhere (not even in Sellerboard) any “profit” would be fiction. Add a cost under Data and they join the table above as Estimated.
Monthly
Your business month by month — what sold, what Amazon charged, and what was actually made. Profit is computed by the batch engine running month by month in order, so a unit sold in May carries the cost of the batch it really came from.
Load a transaction file to see your months
Monthly figures come from your Amazon unified transaction report. Upload it under Data (the same file Home uses) and this page fills in — the Jan–Oct 2026 file gives you all ten months.
Fees
Every fee and charge in the file, three ways: what Amazon took overall, what it took per product, and the account-level charges month by month. All of it is Amazon's own numbers — Confirmed evidence. Costs that live inside your batches (like a courier duty bill) stay in Batches; they are not Amazon fees.
Amazon's cut — whole file
Upload a transaction file first.
Fees by product
Upload a transaction file first.
Account-level charges by month
Charges Amazon levied outside any product — storage, placement, subscription, AWD, the sea shipment's import charges. Always the whole file, month by month; the same charges itemised on Home.
Upload a transaction file first.
Investment Position
Where the money in this file actually sits — recovered, still in stock, or gone — shipment by shipment. Profit and capital recovery are kept separate: a shipment can be profitable and still have most of its cash sitting in stock.
Tracked shipments
| Shipment | Received | Invested | Recovered | % back | Still to recover | Stock units | Stock at cost | Dead at cost | Profit so far |
|---|
Still to recover is what remains of the cash you put in, after the settlement that batch has earned so far. Stock at cost is what the unsold units cost you. They differ by the profit (or loss) already made. Dead is the cost of units lost or damaged — reimbursements Amazon paid for them are already inside “Recovered”.
Cash picture — this file
Upload a transaction file first.
Not fully counted yet
Upload a transaction file first.
Estimated-cost products — profit so far only
These products carry a flat cost per unit (from Sellerboard), so profit on units sold is computable — but how many units were bought was never recorded, so their invested and stock position is unknown, not zero. Add purchase records and they move up into the tracked table.
| Product | Units sold | Settlement | COGS consumed (est.) | Profit so far |
|---|
Batches
Your batch catalogue — every shipment, what it cost and what is left. Cost lives on the shipment, not the product. Sales consume batches oldest-first (FIFO); refunds return units to the batch they came from; lost and damaged units post against their batch. Each card shows exactly how its unit cost was built.
Floor Prices
The lowest price each product can sell at without losing money — built from the fees Amazon actually charged you, not a fee table.
| Product | Landed | FBA avg | FBA regime | Regime since | Referral | Floor (avg fees) | Floor (regime) | Recent avg price | Status |
|---|
How the floor is built
Floor = (landed cost + FBA fee per unit) ÷ (1 − referral %). The regime floor uses the fee level Amazon is charging now: the engine reads that product’s orders backwards until the per-unit FBA fee changes — that unbroken run of orders is the current fee regime, and its typical (median) fee is what a sale today will actually pay. When Amazon raises fees — as it did on 15 October 2026 — the regime floor moves fully to the new level at once, instead of blending old and new fees for a month. A regime resting on fewer than 3 orders is marked thin: treat it as provisional. The average-fees floor is kept for reference. For a product held in several batches, this table uses the batch your next sale will come out of (oldest first) — every batch’s own floor is listed on its card under Batches.
Data
Your transaction file, your batches and your costs. Edits save automatically in this browser and every screen recalculates instantly.
Amazon transaction file
No file loaded this session. Upload the unified transaction CSV (the file itself is not stored — only the numbers it produces).
Batches (shipments)
Each batch is one shipment from one supplier. A unit cost is a build-up of named cost parts (product, courier, duty…) — edit any part, add a cost you discover later (per unit, or as a total the app divides by the units), or add a shipment-wide cost and the app allocates it across the shipment’s products by value. The landed cost is always the sum of the parts, and every screen recalculates the moment you change one. A new shipment of the same product is a new batch — the engine consumes the oldest batch first.
Simple costs (no batch tracking)
One cost per product, used where batch history isn’t available yet. These start as Sellerboard COGS — Estimated, unverified. Replace them with invoice costs as you get them.
Your cost data
Costs live in this browser’s storage on this device. Downloading the JSON is your backup and the way to move them to another computer.