The Core Thesis: ROAS is an output, not a diagnosis. It can flatten because product eligibility has fallen, core sizes are unavailable, discounting has changed conversion value, creative has exhausted its audience, demand has shifted, or attribution has been redefined. A credible recovery partner starts with a shared baseline, observable failure hypotheses, and a dated plan for testing the catalog system from measurement through channel allocation.

System Audit • Evidence Pack Baseline • Failure Hypotheses • Multi-Domain Controls • 30/60/90-Day Decision Gates

A new agency can promise a higher ROAS target, new audiences, or more aggressive bidding. The useful question is: can the incumbent—or a candidate agency—make the system visible enough to repair?

A Nine-Month ROAS Plateau Requires an Operating-System Audit

Nine months is long enough to require a structured investigation. It is not long enough, by itself, to assign blame.

A catalog campaign is a chain of connected decisions. Product data determines whether items are eligible to serve. Inventory determines whether a click can plausibly convert. SKU selection determines which products receive exposure. Creative affects attention and product discovery. Audience and channel allocation determine where the budget is placed. Measurement determines whether the resulting activity is being interpreted correctly.

A weakness anywhere in that chain can produce the same headline: stagnant ROAS.

For example, Google Merchant Center documents product-data quality requirements and item-level approval issues that affect catalog eligibility. If high-intent products have approval or attribute issues, an agency may respond to falling revenue by changing bids while the stronger products remain unable to serve. The work looks active; the underlying constraint remains untouched.

Possibility 1 & 2

Measurement & Reporting

A Measured Plateau: Same metrics, attribution, and product availability show little movement.
A Reporting Artifact: Conversion definitions, attribution windows, or return treatments changed.

Possibility 3 & 4

Commercials & Execution

A Commercial Constraint: Target ROAS doesn't reflect inventory, pricing, or discounting shifts.
An Execution Gap: Known constraints are not being surfaced, tested, or resolved.

ROAS should remain distinct from CAC, ACOS, revenue contribution, and net profit. A campaign can have an acceptable platform ROAS while acquisition cost rises elsewhere. A marketplace ACOS can improve while revenue contribution declines. None of those metrics proves audited net profitability after returns, COGS, shipping, fees, and taxes.

Objective: The goal is not to defend the current agency or justify a replacement. It is to establish whether the account has an observable operating model.

Recovery Starts by Establishing a Trustworthy Baseline and Failure Hypotheses

A recovery plan should begin with a baseline that both the brand and agency accept as the reference point. Without one, each weekly report becomes an argument over whether a movement in ROAS represents progress, seasonality, attribution drift, or a temporary change in mix.

The Stagnant Catalog Account Evidence Pack

Before approving a recovery plan, request these artifacts with a date range, owner, and metric definition: attribution and conversion settings; account and channel spend/revenue trends; SKU-level spend, sales, stock, and discount status; feed diagnostics and product rejections; creative fatigue and asset coverage; audience and campaign change history; channel allocation rationale; experiment log; and a list of paused, scaled, and unresolved actions.

Output: A one-page baseline that labels each problem as verified, suspected, or unmeasured and assigns the next test.

This is a buyer-facing diagnostic request, not proof that the incumbent caused the plateau. A brand may find that the agency has been flagging inventory or feed issues that were never resolved internally. It may find the opposite: repeated bidding changes with no record of the conditions that prompted them.

The important shift is from observations to hypotheses. “Catalog campaigns are underperforming” is an observation. “High-spend products are becoming unavailable before exclusions take effect” is a hypothesis that can be tested against stock, product status, spend, and conversion data. “Creative fatigue is reducing response among a defined audience” should also lead to a test with a stated comparison, decision date, and owner.

Granular reporting alone does not make the baseline trustworthy. A SKU report can be precise and still mislead if inventory status is stale, discounts are omitted, or the conversion definition differs across channels. Google Merchant Center provides item-level diagnostics for identifying product-data issues and affected inventory, which is useful evidence for investigating catalog eligibility; it does not settle an attribution or commercial-value question.

An agency that cannot state what would change its mind is reporting activity rather than managing a recovery.

Catalog Recovery Requires Controls Across Feed Health, Inventory, SKU Selection, Creative, Audiences, and Channels

The reason catalog accounts become difficult to repair is that each domain can mask another.

A feed problem can resemble weak demand when products stop serving or lose required attributes. Inventory can resemble a landing-page problem when shoppers arrive on products with missing core sizes. A weak SKU mix can resemble a bidding problem when budget follows products that attract clicks but do not convert. Creative fatigue can look like an audience issue when the same assets have exhausted their ability to earn attention.

The agency should be able to trace the path from product state to media decision.

Consider a product set where top-selling SKUs face stockouts or missing variant sizes. Without dynamic catalog filtering, performance marketing spend continues to flow towards these low-converting landing pages, systematically depressing account ROAS regardless of bid optimizations.

Ready to Uncover Your Catalog ROAS Bottlenecks?

Stop guessing why performance has flattened. Request an independent operating system audit and receive a structured 30/60/90-day recovery plan tailored to your ecommerce catalog.