Your P&L Tool Has One COGS Number. That's Why It's Lying to You.
Most Amazon sellers have one number entered as their cost of goods. One number. For every order. Every month. Every batch.
That's not profitability analysis - that's guesswork with a nicer interface.
Here's the reality: your supplier raised prices after COVID. Freight rates spiked. Import duties changed. You switched manufacturers. Somehow, the P&L tool you're using is still pulling the same COGS figure you entered when you first set up the account - and telling you your margins look fine.
They're not fine. They're wrong. And wrong margins lead to wrong decisions on ad spend, wrong decisions on scaling, and wrong decisions on which SKUs to push.
This is exactly the operational gap that sellerview.AI's COGS History feature was built to solve.
Why Most Amazon P&L Tools Get COGS Wrong
The fundamental problem is architectural. Most analytics tools treat COGS as a static field - you enter a number, it applies that number to every order. Forever.
That works in a world where your supplier never changes their price, freight never fluctuates, and geopolitical events don't exist. We don't live in that world.
Consider what's happened to Amazon sellers' cost structures over the last few years alone:
COVID-19 (2020-2022): Supply chain disruptions, raw material shortages, factory shutdowns. Sellers who were buying at $6.50/unit were suddenly paying $9.00–$11.00/unit for the same product.
US-Iran tensions and Red Sea shipping disruptions: Freight costs through key shipping corridors doubled or tripled overnight for sellers importing from Asia.
Import duty changes: US tariff adjustments on Chinese goods, for instance, changed landed costs for thousands of Amazon sellers without a single thing changing at the factory.
Supplier switches: You moved from one manufacturer to a cheaper or better one. Your new COGS is $7.20. Your old one was $8.80. But your P&L tool doesn't know the difference - it applies one number across the board.
The result? A P&L that lies to you systematically. And the dangerous part isn't that the numbers are wrong - it's that they look right.
The Real Cost of Inaccurate COGS: Fake Margins and Bad Decisions
Let's be specific about what happens downstream when your COGS data is wrong.
Say you're selling a kitchen product. Your old batch had a landed cost of $9.00/unit. A new batch after a tariff change costs you $12.50/unit. You're selling at $29.99.
If your P&L tool still shows $9.00 COGS, it's telling you a 65%+ gross margin. You look at that number and decide to scale ad spend aggressively — 18% TACoS feels totally justified at those margins.
But your actual current margin is closer to 45% because the real COGS on orders being shipped today is $12.50. You're making ad spend decisions based on a margin that stopped existing two months ago.
This isn't a minor rounding error. At any meaningful volume — 50, 100, 200 units a day — this is real money being misallocated in real time.
Most sellers don't discover this until a quarterly review, a CA audit, or when cash doesn't reconcile. By then, you've already spent the margin you didn't have.
How sellerview.AI Handles COGS History Differently
sellerview.AI was built on the premise that your cost structure changes over time, and your profitability tool needs to respect that reality.
Instead of one static COGS value per product, sellerview.AI lets you create batch-level COGS periods - each with its own start date, cost value, and duration. Orders are matched to the COGS value that was active when they were received.
This means:
Orders from January, when your COGS was $19.20, get calculated at $19.20
Orders from March, after your supplier increased prices and COGS moved to $24.00, get calculated at $24.00
Orders from April, after you negotiated a volume discount and COGS dropped to $21.60, get calculated at $21.60
The P&L you see in your dashboard reflects the actual economics of each batch - not a blended average, not a guess, not a static number you entered 8 months ago.
Step-by-Step: Using the COGS History Feature in sellerview.AI
Step 1: Open Your Dashboard and Select the Product
Log into sellerview.AI and go to your main dashboard. You'll see your active product listings.
Find the product whose COGS history you want to configure. You can also access this through the Products tab - both paths work - but the dashboard route is faster if you already know which SKU you're working on.
Step 2: Click the Pencil Icon to Edit COGS
Next to the product, you'll see a pencil icon. Click it.
This opens the COGS editing popup. By default, you'll see your current COGS value and a date field. This is where most tools stop. sellerview.AI goes further.
Step 3: Enter Your First COGS Batch - Set the Start Date
This is the critical part most sellers overlook. You're not just entering a cost number - you're entering a cost period.
Say your landed cost was $19.20/unit and that's been the case since January 1, 2026. Enter $19.20 as the COGS value, set the batch start date to January 1, 2026, and save.
sellerview.AI creates a log entry for this batch. Every order from January 1 onward (until you create the next batch) will be calculated using $19.20 as the COGS.
A note on the earliest possible date: sellerview.AI limits how far back you can set a batch start date - you can only go back to the date when your seller account was connected to sellerview.AI . This is by design, since order data before that date wasn't tracked in the system.
Step 4: Add a New COGS Batch When Your Costs Change
Two months later, your supplier increases prices. Your new per-unit landed cost is $24.00, effective March 1, 2026.
Go back to the same COGS editor. Set the date to March 1, enter $24.00, and save.
sellerview.AI now has two entries in your COGS history:
January 1 → February 28: $19.20/unit
March 1 → present: $24.00/unit
Every order received between January 1 and February 28 will use $19.20 for P&L calculations. Every order from March 1 forward uses $24.00.
That's batch-level accounting. That's real margin visibility.
Step 5: Add More Batches as Your Costs Continue to Change
Cost structures aren't static. They evolve. A month after the increase, maybe you negotiate a better rate or switch to a domestic supplier. New landed cost: $21.60/unit, effective April 1.
Add another batch entry. Now your COGS history looks like:
January 1: $19.20
March 1: $24.00
April 1: $21.60
Each batch is logged, timestamped, and applied accurately to the orders that fall within that window.
Step 6: Edit Batch Start Dates If You Need to Adjust
Maybe you realize your new COGS actually kicked in a few days earlier than you logged, or you want to align the batch date to when the shipment was received rather than when you updated the system.
sellerview.AI lets you edit batch start dates retroactively - as long as the date doesn't go beyond the account connection date. Click on any existing batch entry and change the date.
In practice, this is useful when you receive a new inventory batch mid-month and want to be precise about exactly which orders were fulfilled from which batch.
Step 7: Read the COGS Trend Chart
Once you have multiple batch entries, sellerview.AI generates a visual COGS trend chart for that product. This isn't decorative - it's operationally useful.
The chart shows you:
When your costs were lowest
When they spiked and by how much
Whether cost increases were temporary or permanent
The full cost trajectory of that SKU over its history on your account
Looking at a product that started at $19.20, jumped to $24.00, and then came down to $21.60, you can immediately see the cost pressure spike and the partial recovery. Now overlay that with your sales volume and ad spend from the same period - and you have a real picture of what happened to that product's economics over time.
Step 8: See the Impact on Your P&L Dashboard
This is where everything comes together.
With accurate, batch-level COGS applied, your sellerview.AI P&L dashboard now reflects the actual profitability of every order - not a blended approximation.
If you run a report for Q1, the orders from January and February are calculated at $19.20 COGS. The March orders are at $24.00. The report doesn't need you to remember what COGS was when - sellerview.AI handles the matching automatically.
For sellers running any kind of scale, this is the difference between knowing your business and thinking you know your business.
Why Historical COGS Accuracy Matters at Scale
Here's something most sellers don't think about until it's too late: bad COGS data compounds.
When you're doing 10 orders a day and COGS is off by $1.50/unit, it's a $15/day error - noticeable but not catastrophic. When you're doing 300 orders a day and COGS is off by $3.00/unit because you didn't update after a supplier price change, that's a $900/day discrepancy. Over a quarter, that's $81,000 in P&L variance.
Sellers scaling quickly are the most at risk. The faster you grow, the more your old COGS number misrepresents your current economics. And scaling ad spend on the basis of inflated margins is one of the fastest ways to burn cash while your dashboard looks green.
COGS history isn't a feature for accountants. It's a risk management tool for operators.
The Operational Takeaway
Your P&L is only as accurate as your cost data. And your cost data is only accurate if it reflects what you actually paid - per batch, per period, per supplier change.
Every time your COGS changes - a new shipment, a supplier renegotiation, a freight rate shift, a duty change - that's a new batch. Log it. Date it. Move on.
If you're not doing this, your P&L is showing you a fictional version of your business. You might be making money. You might not be. The margin between those two outcomes is exactly the margin you're not tracking.
sellerview.AI's COGS History feature exists because real seller economics are messy - costs change, supply chains shift, and the world doesn't operate on fixed input prices. Your profit analytics tool should be able to handle that reality.
If your current tool can't - and most can't - you're flying with a broken altimeter.