Skip to main content
FHAVI

Research · Merchant Center

A warning is the cheapest suspension you will ever get

Merchant Center warnings and suspensions look similar in the interface and are completely different in consequence. What each one means, and why acting inside the warning window is the whole game.

2 min read

In brief

  • A warning is a notice that enforcement will follow if the condition persists; a suspension is enforcement already applied.
  • The warning window is the only period where you can fix the cause without a review, a request, or lost serving time.
  • Most suspensions we see had a warning attached to the same issue first — the warning was scrolled past or never seen.

The difference that matters

WarningSuspension
Account stateStill serving, usually with reduced reachNot serving
What is requiredA fix, no requestA fix and a review request
Who decidesYou, by fixing itA reviewer, on evidence
Time costDays, if acted onWeeks, sometimes longer
Risk if ignoredEscalates to suspensionEscalates to account-level enforcement

The trap is that a warning often does not stop anything. Products still show, spend still runs, and the notice sits behind a bell icon that nobody opens. By the time it becomes a suspension, the warning is weeks old and the evidence of a fix that could have resolved it nobody kept.

What to do inside the window

  1. 1

    Screenshot the wording and the date

    The message is the specification. Copy it exactly into your log; paraphrasing loses the category detail that tells you what to fix.

  2. 2

    Scope it

    Account-level, category, or named items. Scope decides whether this is a two-hour fix or a catalogue project.

  3. 3

    Find the cause, not the symptom

    If the warning names missing policy pages, the cause is a redirect that broke. If it names price accuracy, the cause is a sale price the feed does not know about.

  4. 4

    Fix at the source

    Store records or supplier mapping, never the feed alone — the next sync reverts a feed-only fix, and the warning returns with a history attached.

  5. 5

    Verify as an outsider

    Check from a fresh browser, logged out, in the target country. Your own session hides exactly the mismatches the crawler sees.

The habit that prevents the escalation

  • Open the account notices weekly, not when something breaks. Most warnings have no visible symptom.
  • Log every warning the day it appears, with the wording and the fix date — this is the history a later review is judged against.
  • Treat an unresolved warning older than a fortnight as a live risk, not a to-do.
  • After fixing, confirm the notice has cleared. A fix that did not clear the notice did not fix the cause.

A warning is the version of this problem that costs days instead of weeks. The whole skill is noticing it while it is still a warning — which means looking at the account when nothing appears to be wrong.

Questions

Asked about this directly

Can I ignore a warning if products are still serving?
That is exactly when the warning is most valuable and most likely to be ignored. Serving continues right up until it does not, and the escalation removes the option to fix it quietly.
Does a warning affect my account permanently?
It forms part of the account history a reviewer sees when a later problem arises. A warning that was fixed and documented reads very differently from three warnings that were not.
Should I request a review of a warning?
Usually no. A warning needs a fix, not a request. Requesting review of a warning you have not fixed is a way to turn a warning into a documented failure.

Keep reading

Other pieces in the library

All research

Numbers first, promises second

Send your store and we will tell you which of these failure modes is already happening — before you pay for a fix.

Prefer email? Write to md@fhavi.com