Most sellers don't realize they need anything beyond the reports Amazon generates. That changes the moment your inventory moves past ten SKUs or you start managing multiple warehouses. At that point, the Amazon reports stop being enough because they show you what happened but not the connections between your shipping decisions and your actual profit margins. I started seeing this around 2018 when a client of mine was getting charged storage fees on inventory she swore she had already pulled from her shipment records. She'd merged two POs into a single inbound plan to save on shipping, but only one carried the FBA shipment ID forward. Amazon charged her a year in storage for those units, and without a logbook she couldn't map the discrepancy back to the split order.
What I use now is a spreadsheet system, and I've been refining it for nearly a decade. You don't need fancy software at first. A well-structured Google Sheet or Excel file does the job if you track the right fields consistently.
The Fba Logbook Best Approach to Tracking
Your logbook needs three sections. One for inbound shipments, one for ongoing fees and adjustments, and one for outbound reconciliation. Start with the inbound section first because that is where most problems begin.
Every shipment you send gets a row. The columns I use are: shipment ID, creation date, warehouse code, SKU, quantity shipped, quantity received, any discrepancies noted on the packing slip, and the cost per unit including freight allocation. Freight allocation matters more than people think. If you're shipping fifty cartons from China and only some contain a particular SKU, you need a way to assign that $2,400 ocean freight to the right items. I use a simple proportional method: total freight divided by total units in the shipment, then multiplied by the unit count for each SKU. It isn't perfect, but it keeps your landed cost within a reasonable range without requiring a full customs broker analysis on every order.
I always flag received quantity against shipped quantity immediately. Amazon's reconciliation happens monthly through their Inventory Adjustment reports, but those come weeks after the fact. If you catch a discrepancy within forty-eight hours of receiving the shipment, you can open a case while the carrier details are fresh and the warehouse still has your case labels on file. After ninety days, Amazon closes those tickets automatically.
The second section tracks fees. Not the summary report they email you quarterly, but the actual line items. I pull the Payments report every Friday and match each charge to the corresponding shipment or sale. Storage fees are the usual suspects. I've seen sellers lose four to six percent of their margin to long-term storage charges that could have been avoided with a simple reorder point calculation. I build a column for expected storage duration based on my sell-through rate. If a SKU is moving at two units per week and I have twelve weeks of stock, I know I'll hit the six-month mark and need to plan a removal order or a promotion before the higher storage rate kicks in.
The third section is for outbound reconciliation. This is where you verify that what you sold matches what Amazon actually charged you in referral fees, fulfillment fees, and any unexpected adjustments. I cross-reference the Sales Report with the Reimbursements Report. Amazon sometimes charges referral fees on returned items that were resold, or they forget to credit you for damaged inventory they disposed of without your request. I've recovered between two and five thousand dollars per year per seller by finding these gaps. The process takes about twenty minutes a week if you keep it consistent.
Here is the part nobody talks about. Amazon creates what they call closed-attribute data for certain SKUs. This means the reports will show you a quantity was returned but won't tell you the condition code unless you dig into the Inventory Action Report. I had a shipment of twelve headphones go to a warehouse in Phoenix. Six came back as damaged. Amazon's standard report showed zero returns for that period. I found them only by pulling the Inventory Adjustment report and filtering for disposition code 57, which is the code for seller-requested disposal. Without knowing that code, you would never see those units in the return data. I filed a reimbursement claim and got credited for the six units within eleven business days.
The logbook becomes less useful as you scale past twenty SKUs because manual entry starts consuming actual time. At that threshold, I recommend integrating a tool like Sellbery or Helium 10's inventory module to automate the inbound tracking while keeping your spreadsheet for the fee reconciliation layer. The integration handles the data entry grind, and you use the spreadsheet to catch the edge cases the automation misses.
One common mistake is tracking only what you ship and ignoring what comes back. Your cost analysis is incomplete without the reverse logistics component. Returns eat into margin faster than you expect, especially on electronics and clothing where restocking fees from Amazon can be as high as twenty percent of the product cost. I add a returns column to every SKU row in my inbound section and track the return rate alongside the received quantity. If a SKU shows a return rate above fifteen percent, I flag it for supplier review before the next reorder.
The other mistake is not accounting for removal orders in the same log. When you decide a SKU isn't moving, the removal cost plus the original freight you already paid creates a double hit. I calculate a breakeven window for each SKU based on my average monthly sell-through. If a SKU hasn't moved in ninety days, I run a quick calculation on whether removing it and switching to FBM makes more financial sense than paying the continued storage fees. This usually saves me three to four hundred dollars per underperforming SKU per quarter.
If you are just starting out, I would suggest building the spreadsheet before you build the inventory. Take two weeks to log every shipment and every fee adjustment. By the end of that period, you will know exactly where your money is leaking. Most sellers ignore the leak until it costs them several thousand dollars.
Gallery Fba Logbook Best
Best Amazon Fba Book at Becky Craig blog
Best Amazon Fba Book at Becky Craig blog
Amazon FBA Inventory Receiving & Shipping Log Book: 110 Pages Shipment Tracker, COGS Calculator ...
Amazon.com: Amazon FBA Inventory Receiving & Shipping Log Book: 110 Pages Shipment Tracker, COGS ...
Digital FBA Data Sheet, Functional Behavior Data Spreadsheet, Editable Behavior Tracker, Autism ...