How to Calculate TACoS on Amazon

The formula, and where each number actually comes from

TACoS stands for Total Advertising Cost of Sale. The formula is (total ad spend ÷ total sales) × 100. That's it — the whole calculation is two numbers and a division. The work is making sure those two numbers are the right numbers, for the same window, in the same currency.

Ad spend comes from the Amazon Ads console — Sponsored Products, Sponsored Brands, Sponsored Display, all added together. If you run DSP, add that spend in too; it's real ad spend even though it lives in a different console and a lot of sellers forget it exists until their TACoS looks suspiciously good.

Total sales comes from Business Reports in Seller Central, or Retail Analytics in Vendor Central — not from the ads console's "sales" column, which only shows ad-attributed sales. That distinction is the single most common source of a wrong TACoS number, and it's covered in its own section below because it's worth getting right on the first try.

A worked example with real numbers

Say a product spent $8,400 on ads in a month and did $64,000 in total sales — ad sales plus organic sales combined, pulled from the same 30-day window.

TACoS = ($8,400 ÷ $64,000) × 100 = 13.1%.

Now put ACoS next to it for contrast, because the two numbers together tell a story neither tells alone. If ad sales for that same period were $22,000, ACoS = ($8,400 ÷ $22,000) × 100 = 38.2%. That's a high ACoS on its own — you'd normally want to pull back. But TACoS at 13.1% tells you organic sales ($42,000 of the $64,000) are doing most of the work, and the ads are likely supporting rank rather than propping up a product that can't sell without them. Read alone, either number would have pushed you toward a different decision. Read together, they explain each other.

The mistake that quietly breaks the number

The most common error is using ad-attributed sales instead of total sales in the denominator — which turns TACoS into a second copy of ACoS and hides the organic picture entirely. The second most common is mismatched date ranges: pulling ad spend for a calendar month but total sales for a fiscal month that starts three days earlier. Small gap, wrong number, and it compounds if you're tracking trend lines week over week.

We've seen this ourselves on handoff accounts: a seller's internal TACoS looked healthy for months because DSP spend was tracked in a separate spreadsheet nobody added back in. The number wasn't fake, it was just incomplete — and incomplete in the direction that made the account look fine when it wasn't. If you run DSP, add it before you divide. If you sell in more than one marketplace, calculate TACoS per marketplace, not blended — a blended number can hide a marketplace that's bleeding.

What a good number looks like — and what to do when it's bad news

There's no single healthy TACoS. It depends on category margin and where the product sits in its life. A new launch with zero reviews often needs to run TACoS well above 20% to build the sales velocity that earns organic rank — that's not a mistake, it's the cost of the position you're trying to buy. A mature product with strong reviews and price competitiveness should be doing most of its volume organically, with TACoS closer to 5–15%.

The bad-news scenario is a TACoS that keeps climbing while ACoS holds steady. That combination means ad efficiency hasn't changed, but organic sales are shrinking underneath it — a negative sales cycle, and cutting spend further usually makes it worse, not better, because you're removing the one lever propping up total sales while the organic side is already falling.

The reflex to avoid is cutting ad spend hard the moment TACoS looks high. That fixes the ratio and breaks the rank. The better habit, whether you're running this by hand or through software, is writing down what you expect before you touch the budget. Every proposed change carries three things before it runs: the evidence behind it, a measurement plan, and a rollback trigger. That discipline is what separates "TACoS is bad, cut spend" from an actual diagnosis.

How often to recalculate, and at what level

Calculate TACoS weekly at minimum, monthly for trend reporting, and daily only if you're mid-launch and need to catch a problem before it compounds. Below the account level, calculate it per ASIN, not just portfolio-wide — a portfolio TACoS of 10% can be hiding one product at 2% and another at 40%, and averaging them tells you nothing useful about either.

Set a target range per product stage rather than one number for the whole catalog. The table below is a starting point, not a rule — category margin moves all of these bands.