amazon tacosamazon TACoSseller centralamazon ads

Amazon TACoS: Formula, ACoS vs TACoS and Benchmarks

Amazon TACoS is ad spend divided by total sales. See the formula, worked examples, how it differs from ACoS, and which reports supply each input.

Amazon TACoS: Formula, ACoS vs TACoS and Benchmarks

Amazon TACoS (total advertising cost of sales) is your ad spend divided by your total sales, multiplied by 100. A seller who spends $2,000 on ads and sells $20,000 in total, counting both ad-attributed and organic orders, has a 10% TACoS. ACoS divides the same spend by ad-attributed sales only, so TACoS shows how much of the whole business advertising is carrying.

Table of Contents

What does TACoS mean on Amazon?

TACoS stands for total advertising cost of sales. Sellers, agencies and Ads managers often type it as “tacos”, which is why the same search also returns taco kits and other grocery products. This guide is about the advertising metric.

TACoS relates paid activity to the full revenue base. ACoS evaluates ad-attributed sales against the spend assigned to those ads. TACoS evaluates whether total ordered sales are growing enough for advertising to represent a sustainable share of revenue. ROAS shows the revenue generated per unit of ad spend.

How do you calculate TACoS on Amazon?

TACoS measures advertising spend as a percentage of total sales. Total sales include ad-attributed revenue and organic revenue. The standard formula is:

TACoS = (Amazon ad spend ÷ total sales) × 100

For example, a seller that spends $2,000 on advertising and generates $20,000 in total revenue has a 10% TACoS ($2,000 ÷ $20,000 × 100). The denominator includes orders attributed to ads, orders generated through organic visibility, and other non-ad sales paths.

Build the calculation from matching reports

The arithmetic is simple. Selecting comparable data is where operators usually make mistakes.

  1. Amazon Ads reports provide ad spend and attributed sales. Select the relevant Sponsored Products, Sponsored Display, Sponsored Brands, or DSP reporting scope before evaluating account-level performance.
  2. Seller Central's Sales and Traffic business report provides total ordered product sales. Use this figure as the denominator for account-level TACoS because it represents the full product revenue being assessed.
  3. Match the date ranges. A seven-day advertising report compared with a calendar-month sales report produces a ratio that accurately describes neither period.
  4. Document attribution windows. Amazon Ads assigns sales to ad interactions under its attribution rules: for sellers, Sponsored Products uses a 7-day click lookback, and a report date stays incomplete until that window ends (Amazon Ads attribution help). Seller Central records ordered product sales through its own reporting view. Record the selected window and avoid treating mismatched periods as directly comparable.

A launch week compared with a full month can distort the result. Promotions, delayed reporting, and order timing may make one period appear unusually strong or weak. Review a trend across several months instead of relying on one month, particularly when launches or promotions affect demand.

What is the difference between ACoS and TACoS?

ACoS divides ad spend by the sales Amazon attributes to those ads; TACoS divides the same spend by all sales. With $2,000 of spend, $8,000 of ad-attributed sales and $20,000 of total sales, ACoS is 25% and TACoS is 10%. ROAS is the inverse view of ACoS: $8,000 ÷ $2,000 = 4.

MetricFormulaPrimary Use Case
TACoSAd spend ÷ total sales × 100Measures advertising cost against the complete revenue base
ACoSAd spend ÷ ad-attributed sales × 100Evaluates efficiency of ad-attributed revenue
ROASAd-attributed sales ÷ ad spendShows revenue generated per unit of ad spend

ACoS and ROAS use ad-attributed sales. TACoS uses total sales, so it can decline when organic revenue grows faster than advertising spend. That decline does not establish profitability. Contribution margin, inventory availability, refunds, fees, and attribution timing still affect the commercial result.

Amazon-specific inputs should remain grounded in the applicable Ads and Seller Central reports. Teams documenting report fields, extraction limits, and recurring workflows can use this Amazon Seller Central reports guide as a reference.

An AI client connected through Agent Central can handle the handoff between these data sources: it collects matching periods, keeps the report definitions, calculates TACoS and shows what changed from the previous period. That helps when advertising movement coincides with stock constraints, listing changes, or fulfillment issues. The metric still requires operator judgment, but the recurring collection and comparison work becomes easier to audit.

Product-level TACoS has a narrower scope

Account-level TACoS can include the advertising spend being evaluated across the account. Product-level TACoS requires more care because Amazon attributes Sponsored Products and Sponsored Display spend to individual products, while Sponsored Brands and DSP spend are not assigned to products in the same direct way.

Product-level TACoS by ASIN or parent ASIN therefore generally covers Sponsored Products and Sponsored Display. Do not present it as the product's complete advertising burden when brand or DSP investment is material. Agent Central's product-level TACoS follows the same rule: it divides Sponsored Products and Sponsored Display spend by Business Report sales and leaves Sponsored Brands and DSP out. For Sponsored Products, Agent Central uses Amazon's 14-day same-product ad-attributed sales field, so its ACoS can differ from the seller console's seven-day view. The TACoS denominator is still total Business Report sales, not ad-attributed sales.

What is a good TACoS on Amazon?

Amazon doesn't publish a target TACoS. A good TACoS is one your margin can carry at the stage the product is in. A new listing can spend heavily on ads before shoppers recognize the brand, while a mature listing may convert demand with much less paid support. One TACoS target cannot serve both situations, even when the products compete in the same category.

New listings often run a higher TACoS because advertising generates much of the early sales volume before the detail page builds organic ranking, reviews, and sales history. Established, well-ranked listings usually need less paid support, so their TACoS tends to be lower. The "good TACoS" ranges that circulate online come from agencies and tool vendors, not from Amazon, so treat them as reference points rather than targets. Margin, cash flow, conversion, and the purpose of the spend determine whether the result is acceptable.

Launch economics differ from mature economics

During launch, advertising can introduce the listing to shoppers, create initial sales history, and support the growth of organic visibility. A high TACoS may therefore reflect deliberate market entry rather than inefficient bidding. The operator still needs to test whether the added sales justify the spend and whether available margin can carry the investment.

For a mature ASIN, the same ratio can signal a weakening organic position. If organic sales decline, advertising may be replacing revenue the listing once earned with less paid support. Rising TACoS alongside flat total sales points to growing advertising dependence, although inventory, ranking, conversion, pricing, and competitive conditions must be checked before changing bids.

A lifecycle review should separate these operating states:

  • Launch: Higher TACoS can be an expected investment when margin and cash flow support it.
  • Growth: Total sales should expand while advertising becomes a smaller share of revenue.
  • Maturity: Lower, stable TACoS matters more when organic visibility and contribution margin remain healthy.
  • Decline or disruption: A sudden shift may result from stock interruptions, listing edits, competition, price movement, or demand changes rather than bid quality alone.

Use trends instead of isolated snapshots

Promotion-heavy periods can distort TACoS. A temporary sales surge may lower the ratio, while aggressive launch spending may raise it even as the listing develops as intended. Review the trend across several months instead of relying on one month.

Segment the trend by ASIN, parent ASIN, marketplace, and advertising type when the reports support that level of detail. The Amazon performance metrics workflow provides a practical structure for defining those comparisons. A connected AI client can then repeat the same collection each period and show what changed, while the operator decides whether a benchmark still fits the product's lifecycle.

A falling TACoS is evidence, not a finish line. It matters when total sales, margin, stock position, and organic performance support the same conclusion.

Automating TACoS Reporting With Agent Central

Manual reporting often fails at the joins. An operator exports Amazon Ads data for one date range, downloads a Seller Central business report for another, then tries to reconcile ASINs, parent-child relationships, attribution windows, and marketplace scope in a spreadsheet. Amazon's own reports are asynchronous, so the workflow also depends on report generation and retrieval timing.

Agent Central connects the AI already in use to Amazon Seller Central and Amazon Ads accounts. It is a hosted MCP server that gives Claude, ChatGPT, OpenClaw, Cursor, and other MCP clients structured access to advertising, sales, inventory, orders, catalog, ranking, finance, and fulfillment data. Account data syncs on a schedule, so the client can read prepared records instead of waiting for each Amazon report request to complete.

A controlled calculation workflow

The useful workflow is deterministic:

  1. The seller connects the relevant Seller Central and Amazon Ads accounts.
  2. The AI client retrieves ad spend and attributed sales for the selected scope.
  3. It retrieves total ordered product sales from the corresponding Seller Central business-report records.
  4. It aligns marketplace, ASIN or parent ASIN, dates, and applicable reporting definitions.
  5. It calculates TACoS and presents the underlying fields so the operator can inspect the result.

A trial includes the most recent 30 days of data, and paid plans can import longer history where Amazon makes it available (history details). Amazon Ads history is kept while the account remains connected. That boundary matters for trend analysis. The first report isn't a complete lifetime view, and a seller shouldn't describe it as one.

Agent Central returns facts, metrics, classifications, and source-provided fields. It doesn't decide whether a seller should cut spend, increase a budget, change a listing, or accept a launch loss. The user's agent or workflow makes that judgment from the returned evidence. A deeper explanation of this hosted MCP approach is available in the MCP server integration guide.

Ask for the scope, not a vague summary

A useful request identifies the product and reporting boundaries. For example, an operator can ask an MCP client to calculate TACoS by ASIN or parent ASIN, specify a synced date range, separate Sponsored Products from Sponsored Display, and return the spend, attributed sales, total ordered product sales, and resulting formula.

That structure makes an audit possible. If the result changes, the operator can determine whether the cause was new sales data, an attribution-window difference, a parent-child mapping issue, or a genuine change in advertising dependence.

Connecting Seller Central to AI Clients

The connection process should be treated like an access-control change, not a casual spreadsheet integration. Amazon authorization determines which Seller Central and Amazon Ads accounts can be connected, while the AI client determines how the returned records are queried and used.

Setup follows a defined path

The practical sequence is straightforward:

  1. Create the account: Sign up at agentcentral.to.
  2. Authorize Amazon access: Connect Seller Central and Amazon Ads through Amazon's authorization flow.
  3. Add the connection: Add the connection to Claude, ChatGPT, OpenClaw, Cursor, or another compatible MCP client.
  4. Define the reporting scope: Specify marketplace, seller account, date range, ASIN or parent ASIN, and the advertising data required.
  5. Validate the output: Check the returned source fields before using the calculation in a recurring report or downstream workflow.

The quickstart documentation for Claude is available at Agent Central's Claude quickstart. The process should preserve the separation between retrieving facts and authorizing changes.

Scoped access matters

Scoped API keys and OAuth provide a way to limit how an AI client reaches the connected account. The exact permissions should match the workflow. A reporting client may need access to advertising, sales, and catalog records without needing permission to submit operational changes.

Guarded writes add another control when a workflow supports changes. Supported changes are previewed before execution, protected against duplicate submissions, and recorded in audit logs with before-and-after values. That model gives an agency or internal operator a review point instead of allowing an ambiguous natural-language request to become an unreviewed account change.

Security boundary: The AI client can interpret returned facts, but the seller's permissions, approval process, and audit trail should govern any write.

Plans are priced by monthly Amazon order volume and include a 14-day free trial with no card required. Current plan details are listed in the Agent Central pricing documentation, where operators should verify the commercial terms before connecting production accounts.

Interpreting TACoS Beyond the Surface Metric

A lower TACoS is not automatically a better result. Cutting advertising spend can reduce the ratio while organic visibility, total sales, market position, or inventory velocity deteriorates. TACoS is a diagnostic measure. It needs commercial context before it supports a budget or listing decision.

A falling TACoS may mean organic sales are growing faster than ad spend. Analysts should verify that interpretation against contribution margin, inventory availability, and the relevant attribution windows. A stockout can suppress advertising activity and distort the ratio. A low-margin product can remain unprofitable despite apparently efficient TACoS.

The margin check comes first

Take a product with a 29% margin after Amazon fees and product cost that runs at a 30% ACoS. Every ad-attributed sale costs more in advertising than the margin it earns: on $10,000 of ad-attributed sales, the ads cost $3,000 while the margin on those sales is $2,900. The same product can still show a modest TACoS if its organic sales are large, which is why ACoS and TACoS both need a margin comparison rather than an isolated efficiency judgment.

Contribution margin must reflect the product that reaches the customer. Referral and fulfillment fees, storage, damage, returns and discounts all affect the money left after an order, and product cost stays a seller-supplied input. TACoS measures advertising spend against revenue. It does not measure cash profit or fulfillment loss.

Use the metric as evidence

Treat each TACoS change as a question about the account:

  • Are organic ordered sales revenue expanding, stable, or declining?
  • Did advertising spend change, or did the revenue denominator change?
  • Was the ASIN in stock for the whole period?
  • Are Sponsored Products and Sponsored Display separated from spend that is not assigned at product level?
  • Does the ratio remain below the gross margin available to absorb advertising?
  • Are the compared dates and attribution windows consistent?

Agent Central can return the underlying Amazon Ads and Seller Central records and calculate TACoS by ASIN or parent ASIN across a synced date range. It provides the evidence, not the business decision. The seller, agency, or connected AI workflow must determine whether the result supports a budget change, listing correction, inventory intervention, or no change.

Agent Central connects Claude, ChatGPT, OpenClaw, Cursor, and other MCP clients to structured Seller Central and Amazon Ads data for ASIN-level TACoS reporting, inventory checks, and auditable workflows. See how an Amazon PPC AI agent works with that data, or connect an account through the Claude quickstart.

Related Agent Central pages

Related reading

Connect Amazon seller data to your AI client.

Agent Central gives Claude, ChatGPT, OpenClaw, Cursor, and other MCP clients structured access to Amazon Ads, Seller Central, inventory, orders, catalog, finance, and fulfillment data.