Keeping Track of Your FBA Numbers Without Losing Your Mind
Most Amazon FBA sellers I talk to have a spreadsheet that looks like it survived a fire. Columns of data, formulas broken beyond repair, and a monthly close-out process that eats up a weekend. A logbook doesn't have to be that complicated. It's just a systematic way to record what you sold, what it cost, what Amazon took, and what actually landed in your bank account each month. Start with the bare essentials. Month, SKU, units sold, units purchased, units in inventory at start and end of month, COGS per unit, Amazon referral fee, FBA fulfillment fee, storage fee, refund rate, and net profit. That's it. Everything else is noise until you've been doing this for six months and know which metrics actually move the needle for your specific operation. I set up a basic template years ago and kept adding rows until it became useless. The breakthrough came when I stopped trying to capture everything and only tracked the numbers that affected my actual P&L. Ad spend goes in separately. Returns get their own column. Shipping costs to Amazon warehouses are logged as a one-time monthly entry rather than per-unit.
Here's the file structure I still use. One tab per month. Each row is a single ASIN. Summary sheet pulls totals with straightforward SUMIF formulas. No pivot tables inside the log itself. Keep the raw data tab clean and let the summary do the math. The exact Logbook For Amazon Fba Monthly approach most people need looks like this: open a blank Google Sheet or Excel file, create a header row with the columns I listed above, and use a consistent SKU format that includes your supplier code, size, and color variation. If your SKUs are inconsistent, you'll spend more time cleaning data than analyzing it. I keep mine in Google Sheets because it auto-syncs and I can share read-only access with my bookkeeper without risking formula edits. The tradeoff is that large sheets get sluggish past about eight thousand rows. If you're doing that much volume, switch to a local Excel file or move to a proper accounting tool.
How to Actually Use It Every Month
Data entry should take less than twenty minutes once you've done this three or four times. Pull your Seller Central report, export the Payments and the Business Report, match them against your purchase invoices, and fill in the gaps. Amazon gives you a detailed settlement report that covers most fee line items. You're mostly just verifying and supplementing. The trick that saves time is naming your exported files with a date stamp before you open them. January_2024_Payments, January_2024_BusinessReport, January_2024_FeeLedger. It sounds trivial but the amount of time lost digging through unmarked downloads on month-end is real. I've watched sellers burn two full days on that alone in their first year. For COGS, I recommend entering what you actually paid per unit including freight and customs, not just the product cost from your supplier invoice. The difference matters when you're calculating real margins on lower-ticket items. A $3 product with $1.50 in landed cost has a very different profitability profile than the $3 product you thought you had.
Get the Full Details
Refund rate tracking deserves its own mention. Amazon's refund report doesn't always align cleanly with your sales report because refunds can appear in a different settlement cycle than the original order. I learned this the hard way when my month-over-month profit looked impossibly low for two consecutive months. The numbers were right, just shifted to adjacent settlement periods. The fix was to track refunds by order date rather than by refund date and keep a separate column for timing adjustments. Storage fees are another area where beginners get burned. Long-term storage charges hit on February 15th and August 15th. If your logbook only captures monthly data, those semi-annual hits look like mysterious expenses. Add a quarterly note column and mark any storage fee events separately so they don't distort your monthly averages.
Common Pitfalls to Avoid
Don't mix personal and business transactions in the same sheet. I once spent an hour reconciling a $47 charge that turned out to be a software subscription I'd paid with my business card but logged it as a product purchase. Source your data from your actual bank feed, not from memory or a notes app. Another issue is double-counting FBA fees. Amazon charges fulfillment fees and referral fees separately, but some exports lump them together. Cross-reference with the Fee Ledger report in Seller Central before finalizing your monthly totals. One seller I work with missed this for four months and thought his margins had collapsed when they were actually fine. Don't overcomplicate your formulas early on. Nested IF statements and array formulas look impressive in a screenshot but they break the moment Amazon changes a fee structure. Simple SUM and SUMIF functions are easier to audit when Amazon sends out one of their periodic policy updates and you need to verify your calculations hold up.
When a Spreadsheet Isn't Enough
If you're managing more than fifty active SKUs, doing multiple sales channels besides Amazon, or handling international FBA programs, a spreadsheet logbook becomes a maintenance burden. The marginal utility drops off sharply after that point. Tools like Helium 10's profit calculator, Perpetua's profit tracking, or even a proper ERP like Zoho Inventory will handle the complexity better. That doesn't mean the logbook concept goes away. It just moves upstream. You'd use the tool for daily tracking and export a monthly summary to a simplified log for your own review and tax preparation. The habit of reviewing your numbers monthly is what matters, not the tool you use to get there. For most sellers running a single Amazon FBA account with under a hundred SKUs, a well-kept monthly logbook is the fastest path to actually knowing whether your business is profitable. The rest is decoration.
