Getting Your Inventory Movement Straight
Most people think a Products Journal is just a fancy spreadsheet for tracking stock. It's not. It's the record that keeps your cost of goods sold from looking like nonsense when tax season hits. I spent three years watching companies lose thousands because they mixed up their product movement logs with their general expense accounts. It's a boring problem until you're trying to explain it to an auditor. The basics are straightforward. You log every time product inventory moves — incoming from suppliers, outgoing to customers, adjustments for shrinkage, transfers between warehouses. Each entry needs a date, a product identifier, quantity, unit cost, and the direction of movement. That's it. But the devil is in the edges, and that's where people mess up.
Setting Up Your Products Journal
I usually start people off with a clean structure. Column A is the date. Column B is the transaction ID — something unique like INV-001 or PUR-452. Column C is the action type: purchase, sale, return, adjustment, transfer. Column D is the product SKU or ID. Column E is quantity. Column F is unit cost at time of transaction. Column G is total value. Column H is a notes field. Keep it simple. You can add columns later. Adding them all at once is how you end up with a mess you can't maintain. The transaction ID column is the one everyone skips. Don't skip it. When you find an error three months from now — and you will — that ID is the only thing that lets you trace it back without pulling your hair out. I once had a client who wanted to reconcile a discrepancy across 4,700 line items. They didn't have transaction IDs. We spent two days matching by date, product, and amount. It was painful.
How to Actually Use It Day to Day
Log entries the same day the transaction happens. That's rule one. If you batch-log at the end of the week, your costs will drift, especially if supplier prices change mid-week. I've seen COGS calculations go off by 8% because someone waited until Friday to enter purchases made on Tuesday and Thursday at different price points. Here's a real case that took me way too long to fix. A client was running a Products Journal for a small e-commerce business that dropped its prices halfway through the month on clearance items. The business was using average cost for the unit cost column. Every time they logged a sale, the journal pulled the average of the entire month's purchase prices. The clearance sales looked profitable because the average unit cost was still inflated. In reality, they were selling below cost on those items and losing money they didn't know about. The fix was switching to FIFO or specific identification for that product line. Took me about ten minutes to diagnose once I spotted the pattern in the numbers. That's the kind of thing that doesn't show up in any beginner guide. Your journal is only as good as the costing method you pair with it. Average cost works fine for commodities where prices don't fluctuate much. For anything with promotions, seasonal pricing, or bulk discounts, FIFO or LIFO (depending on your region and tax situation) will give you a truer picture.
Get the Full Details
Common Mistakes That Cost Money
Here are the ones I see constantly. First, mixing up returns and adjustments. A return means a customer sent product back — inventory goes up, revenue goes down. An adjustment means you found your physical count didn't match your records — inventory goes up or down with no revenue effect. People log both the same way and then wonder why their gross margins are wrong. Second, ignoring partial shipments. If a supplier sends you 100 units but your order was for 200, and you only log the 100 you received, your journal is fine. But if you then sell 150 units before the remaining 100 arrive, you're selling inventory you don't have yet. Log the partial receipt. Don't pre-log what you expect to receive. Third, using retail price instead of cost in the unit cost column. The journal tracks what you paid, not what you sell for. Those are two different numbers. Your gross profit margin comes from the difference between them, not from the journal alone. The journal gives you the cost side. Your sales ledger gives you the revenue side. You combine them to get margins.
When a Products Journal Isn't Enough
Let me be clear about the limitations. A Products Journal in a spreadsheet works fine for businesses moving under 500 SKUs and doing fewer than a few hundred transactions per month. Beyond that, you're going to hit friction. Formula errors. Copy-paste mistakes. Version control issues where three people are editing different copies. If you're at that scale, you need something like TradeGecko, Brightpearl, or even a well-configured Shopify Plus inventory module. Those tools handle the journaling behind the scenes and reduce human error significantly. Even with those tools, the underlying logic is the same. Know what your system is tracking and what it isn't. Export your inventory reports monthly and cross-check against your COGS calculation. If they don't align within a reasonable tolerance — say, plus or minus 2% — something is wrong. It could be a missed return. It could be a supplier invoice you never entered. It could be a product category mapped to the wrong asset account. These things accumulate silently.
A Practical Workflow That Works
Start each month with a physical count on at least your top 20 SKUs by revenue. Compare that to what your journal says. Log the variance as an adjustment entry. This catches shrinkage, theft, and data entry errors before they compound. It takes about 30 minutes for a small operation and saves hours of reconciliation work later. Keep your journal separate from your general ledger. Don't combine them. Your journal is the detail. Your GL is the summary. When you close out the month, summarize the journal and post the totals to your inventory asset and COGS accounts in the GL. This separation makes audits cleaner. It also means if you need to dig into a specific transaction, you don't have to search through general expenses. The Products Journal concept isn't complicated. What makes it hard is maintaining it consistently when you're juggling supplier calls, customer complaints, and shipping deadlines. The simplest systems beat the most sophisticated ones because people actually use them. Build something you can maintain. Check it monthly. Fix discrepancies the same week you find them. That's all there is to it.
