What This Template Actually Is
A Template For Amazon Fba Diy is a spreadsheet or document you use to map your product listings, shipping plans, and inventory data before they go into Seller Central. Most people who start doing FBA DIY are trying to avoid paying for software that does the same thing, or they want full control over how their data is structured. I built mine from scratch because the free templates online had missing columns and outdated fields that didn't match what Amazon was actually asking for at the time. The core of the template is two sheets. One sheet holds your product catalog, and the other holds your shipment creation data. The catalog sheet needs SKU, ASIN, product title, dimensions, weight, FNSKU, and a category field. The shipment sheet pulls from that catalog and adds shipment ID, destination warehouse, case pack quantity, shipped quantity, and the expected arrival date you put into Amazon. That's the minimum that works. I started with a blank Google Sheet because it syncs across devices and I can share it with my warehouse guy without exporting files. The moment I switched to Sheets, I lost the ability to do some of the bulk validation checks I used to run locally, so I ended up building a second tab that cross-references SKU against Amazon's API to flag any mismatches. It takes about four minutes to populate once per week.
Here's something beginners consistently get wrong. The ASIN column is not the same as the FNSKU. The ASIN is Amazon's universal product identifier. The FNSKU is the barcode Amazon sticks on your individual units when they receive them at the warehouse. If you use the ASIN as your primary tracking key, you will have a bad time when you restock the same product through a different supplier. I learned this the hard way when I switched packaging providers and got three identical products mixed up in one inbound shipment. Amazon flagged two of them as discrepancies and held the entire batch for four days while I pulled records to prove which box was which. After that, I added a separate "packaging variant" column to the catalog and started tracking FNSKU as the unique identifier for every physical unit.
What Fields You Actually Need
Your product catalog sheet should have these columns at minimum: SKU, Product Title, ASIN, FNSKU, Category, Dimensions (L x W x H in inches), Weight (oz), Cost Per Unit, Selling Price”, Reorder Point, Last Reorder Date. The reorder point column is where most DIYers skip ahead and fail. Without it, you're guessing when to restock, and the guess is usually wrong. The shipment tab needs: Shipment ID, Destination Warehouse, SKU, Case Pack Size”, <“>Shipped Quantity”, <“>Expected Arrival”, <“>Actual Received Quantity”, <“>Discrepancy Notes. When Amazon receives your shipment, they report back a received quantity that may differ from what you declared. The discrepancy notes column is where you record the reason. I don't use automated alerts for this. I just sort by received quantity versus shipped quantity once a week and write down whatever explains the gap, whether it's damaged cases, missing cartons, or Amazon miscounting during the receiving process.
Get the Full Details
How I Use It Day to Day
When I create a new shipment in Seller Central, I pull the SKUs I need from the catalog tab, fill in the shipment tab with case pack sizes and quantities, and then upload the file directly into the shipment creation workflow. Amazon accepts .xlsx or .csv. The upload takes about thirty seconds for a batch of fifty units. Validation runs in under a minute. If there's an error, Amazon highlights the exact row and column. I fix it inline and resubmit. That part is fast. What takes time is the reconciliation after the shipment arrives. I compare the received quantity against my shipped quantity and note any differences. If the discrepancy is more than five percent, I open a case with Seller Support and attach my shipment file plus a photo of the packaging. I keep a separate folder in Google Drive for each shipment with photos of the packed boxes, the packing slip, and the carrier tracking. This has saved me from losing inventory three separate times because Amazon's dispute system requires proof, not just a claim.
Pitfalls I've Hit
The biggest issue is that Amazon changes their upload format occasionally. A column header that worked last quarter might get renamed or deprioritized this quarter. I've lost shipments because I didn't check the Amazon Seller Central help page for the latest template spec before uploading. The workaround is to save a fresh copy of the current template from Seller Central every time you start a new bulk listing or shipment, even if your old one still looks like it works. Another problem is dimension and weight accuracy. If you enter dimensions that are off by even an inch, your FBA fulfillment fees can shift into a higher tier. I once listed a product as 8x6x4 inches when the actual packaging was 8x6x5. That one extra inch pushed it into the next size bracket and cost me roughly $0.40 more per unit in fulfillment fees. Over thousands of units, that's not trivial. The fix is to measure every product variant with a real tape measure and scale, not to rely on the supplier's specs. Suppliers often round down on purpose.
When This Approach Breaks
A DIY template works fine if you're moving under two hundred units per month and you have maybe ten to fifteen SKUs. Once you hit that range, the manual reconciliation starts eating into your day. You'll spend more time updating spreadsheets than actually sourcing or marketing. At that point, tools like ShipBob's analytics dashboard, Helium 10, or even Amazon's own inventory management reports will save you time. I'm not saying the template approach is bad. I'm saying it has a ceiling, and you'll know when you've hit it because you stop finding the work useful and start finding it tedious. There's also the risk of data loss. I had a Google Sheet get accidentally shared with a vendor who scraped the pricing column and posted it on a forum. I didn't notice for two weeks. If you use a shared spreadsheet, restrict editing to view-only for anyone outside your team, and use a password-protected backup stored locally. One lost file or one leaked pricing list is enough to cause real problems.
Where to Get Started
If you want to build your own, start with the column list above and populate it with your current SKUs. Export your existing Seller Central inventory report as a baseline. Compare what you have to what the template asks for and fill in the gaps. Use conditional formatting to highlight rows where the weight or dimension fields are blank. That will show you which products need measurement before you can list them for FBA. I keep mine in Google Sheets and export a CSV before every shipment creation. The export step is the one people skip, and it's also the one that prevents errors. If you upload directly from Sheets without checking the preview, you'll sometimes get garbled characters or mismatched columns because of locale settings. Always preview the CSV in a text editor before Amazon validates it. Takes about twenty seconds and saves you from a rejected shipment.
