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
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.
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 recent | Referral | Floor (avg fees) | Floor (recent fees) | Recent avg price | Status |
|---|
How the floor is built
Floor = (landed cost + FBA fee per unit) ÷ (1 − referral %). “Recent” uses the last 30 days of that product’s orders, so a fee rise (like Amazon’s 15 October peak increase) lifts the floor automatically — but gently: if fees jumped mid-window, the recent floor still blends a few pre-rise days. Full fee-regime detection is the next Phase 1 milestone; until then, treat the recent floor as a minimum and the peak-day floor as the safe line. 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.