Amazon tells you what sold. SelfPub Go tells you what you kept.
Your Kindle Direct Publishing reports arrive as yesterday's numbers in a download: one row per marketplace, in marketplace currency, with no idea what those sales cost you. SelfPub Go turns the same files into a live KDP sales dashboard — royalties, units, and KENP page reads per book, with ad spend and refunds already subtracted.
A KDP sales dashboard that shows profit, not just units.
Same reports, read properly. Every title gets one line with the money coming in and the money going out on it.
Profit per ASIN, per day
Royalty in, ad spend out, refunds deducted — one line per title, per day. The question stops being how many units you moved and becomes which of these thirty books is paying for itself.
KENP page reads in the same view
Page reads sit next to paid sales instead of in a separate tab, so a Kindle Unlimited title stops looking like a failure on the days it earns most of its money.
Every marketplace, one currency
Sales from every marketplace your books sell in, converted to the currency you actually bank in and totalled. The original amount is always one click away.
Ad spend already subtracted
Spend comes from Amazon's Advertising API and is joined to the royalty it produced, per book. No export, no VLOOKUP, no second browser tab open next to the first.
Rank and reviews on the same row
Best Sellers Rank and review counts are tracked per book with history, so the effect of a price change, a new cover or a campaign is something you look at rather than something you remember. Included on every plan.
Your reports stay on your computer
Royalty reports are parsed and stored locally on your machine and never uploaded to us. That constraint is why SelfPub Go is a desktop app and not a website.
Four numbers that trip up every new KDP dashboard.
Most of the confusion about Kindle Direct Publishing reports comes down to four terms that don't mean what they look like. Here they are in plain English — the app uses the same definitions.
- Net units sold
- Orders minus returns and refunds. A strong launch week can shrink two weeks later, which is why a dashboard that only ever counts up is lying to you.
- Royalty
- What actually reaches you: the list price minus Amazon's share, minus delivery cost on ebooks or printing cost in print. It changes by marketplace, by format, and by price band — so one book can have half a dozen different royalty rates at once.
- KENP page reads
- Pages read by Kindle Unlimited subscribers. They're paid out of a monthly fund, and Amazon publishes the per-page rate after the month closes — so any dollar figure attached to page reads before then is an estimate, including ours.
- Estimated vs. final royalty
- Current-month numbers in KDP are estimates. They firm up when the month closes and payments are calculated, which is why last month's total can move after you already wrote it down.
KENP royalties, counted like income.
For a lot of KDP Select titles, page reads are the larger half of the earnings — and they're the half that ad platforms built for Amazon Sellers cannot see at all. A campaign that looks like it lost money on paid sales can be the reason a book got read at all.
SelfPub Go imports KENP page reads from your reports and shows them beside paid sales, per book and per marketplace. Their dollar value is an estimate — Amazon publishes the KENP rate after the month closes, so the app uses the rate you set and labels the result as estimated. Update the rate when Amazon announces it and past months recalculate.
What a title's line looks like
- Paid units and the royalty they earned, per marketplace
- KENP page reads, with an estimated value at your rate
- Ad spend attributed to the same title, same day
- Refunds deducted, not quietly dropped
- One profit figure at the end of the row
Estimated figures are labeled as estimates everywhere they appear.
Track the book, not just the campaign.
Best Sellers Rank and review counts are collected through the day and kept as history, per book and per marketplace. A sparkline sits in your book table and the full chart is one click away — so when a price change, a new cover or a campaign moves a book, you see it next to the spend and the royalty from the same days.
Elsewhere this is a product of its own, sold by the book. BookBeam's published plan table, checked on 21 August 2026, caps its Book Tracker at 20 / 40 / 150 books depending on plan and limits Best Sellers Rank history to one year on the entry plan. Here it is a column in a table you already have open, on every plan, for every book you publish.
What gets tracked
- Best Sellers Rank per book and marketplace, with history
- Review count over time, next to the launch that moved it
- Hourly refresh on the books you're working, every few hours on the rest
- Rank, reviews, ad spend and royalty on one row
- Included on every plan
Collected from your own computer, so Amazon sees a reader opening a book page rather than a data centre.
A KDP sales tracker that runs on your machine.
KDP's terms restrict handing your reports to third parties. Rather than ask you to ignore that, SelfPub Go parses royalty reports locally and keeps them there. Advertising data comes from Amazon's Advertising API through our servers, because that is the only way the API works — those are campaign metrics, not your earnings.
Questions about KDP reports and royalties.
What does this add on top of the KDP reports I already have?
Kindle Direct Publishing gives you yesterday's numbers as a download: one row per marketplace, in marketplace currency, with no idea what those sales cost you. SelfPub Go reads the same reports and joins them to your Amazon Ads spend, per book and per day, in one currency — so you get a profit line instead of a units line.
How is this different from Book Report or ScribeCount?
They answer "what did I earn?" We answer "what did I earn, and what did it cost me?" Book Report and ScribeCount are royalty dashboards — good ones — and both read advertising data: ScribeCount's Ad Tracking module says it “matches your ad spend against the royalties those campaigns actually generated — so you see profit, not just impressions.” What neither one's own documentation describes is managing those campaigns: creating them, changing bids, or handling keywords and negative keywords. SelfPub Go joins both sides per book, so ACOS is measured against your royalty instead of the cover price.
Do you support KENP and Kindle Unlimited page reads?
Yes. Page reads are imported from your KDP reports and shown next to paid sales, per book and per marketplace. Their dollar value is an estimate: Amazon publishes the KENP rate after the fact, so the app uses the rate you set and labels the result as estimated. Update the rate when Amazon announces it and past months recalculate.
Does it track Best Sellers Rank and reviews too?
Yes, on every plan and for every book you publish. BSR and review counts are collected through the day and kept as history, with a sparkline in the book table and the full chart one click away. Books you're actively working on refresh hourly and the rest every few hours. Because it sits in the same table as your royalties and your ad spend, you can line a rank move up against the campaign or the price change that caused it.
Where is my royalty data stored?
On your computer. Royalty reports are parsed and stored locally and never leave your machine — KDP's terms restrict handing your reports to third parties, and we'd rather respect that than ask you to ignore it. Advertising data comes from Amazon's Advertising API through our servers, because that's the only way the API works; those are campaign metrics, not your earnings.
Do I have to upload a report every time?
No. You point the app at the report KDP gives you, and it can watch your Downloads folder so the next export imports itself.
Does it handle multiple pen names or several KDP accounts?
Reports are grouped per book and per marketplace, so a catalog spread across pen names lands in one view as long as the reports are yours to import. If you run several separate KDP accounts, drop us an email once you're in — that setup is exactly what we want to test.