eBay MC999 Notice: What It Means and How to Respond

An MC999 notice lands in Seller Hub with language that sounds serious but explains surprisingly little about what's actually being flagged — no specific document requested, no single clear reason stated, just a notice that your account or listing activity is under review. That ambiguity is exactly what makes MC999 stressful, and exactly why the right first move isn't drafting a response, it's figuring out what's actually going on.

Got an MC999 notice and not sure what triggered it? Message me directly on WhatsApp — send a screenshot or the exact wording and I'll help you work out what's actually being flagged.

If you want a shorter starting point, the MC999 triage checklist covers what to check in your account before you draft a response.

Why sellers often confuse MC999 with a simple glitch

Because the notice can arrive without a clearly stated single cause, some sellers initially assume it's a system error or a mistake that will resolve itself without any action. This is a genuinely risky assumption — even if a notice's underlying trigger turns out to be minor or based on a misunderstanding, ignoring it rather than investigating and responding appropriately can allow an automated review process to escalate toward a broader restriction simply because no clarifying information was ever provided. Treating every MC999 notice as something requiring genuine attention, even when the eventual explanation turns out to be straightforward, is the safer default.

Why MC999 is harder to respond to than other notices

Some eBay notices are specific about what they need — MC011, for instance, is generally document-and-verification focused, asking for a specific piece of proof. MC999 is different: it's generally tied to a review of recent account or listing activity, without necessarily stating a single, specific trigger. eBay doesn't publish an official breakdown of exactly what causes an MC999 notice, and the underlying reason genuinely varies from seller to seller, which means there's no universal template response that works for every case — the right response depends on what's actually happening on your specific account.

Why the ambiguity is actually a deliberate part of the system

It's worth understanding that MC999's vagueness likely isn't an oversight — a review system designed to catch a wide range of different suspicious patterns often uses a general-purpose notice rather than a highly specific one, partly because publishing exact trigger criteria would make it trivial for genuinely bad actors to learn exactly how to avoid detection. This is cold comfort to a legitimate seller caught by the same general notice, but it explains why eBay is unlikely to ever publish a precise, specific breakdown of MC999 triggers the way sellers often wish it would — the ambiguity itself is part of what makes the review system effective against genuine violations, even though it makes life harder for an honest seller trying to understand what happened.

What MC999 generally relates to

Area	What to review
Recent listings	New listings created, or existing listings edited, in the days before the notice
Buyer disputes	Cases, returns, or complaints opened around the same period
Account changes	Address, bank details, or contact information recently updated
Selling pattern	Any sudden change in volume, category, or listing activity

A notice that feels completely generic on first read usually has a specific, identifiable trigger once your own account activity is reviewed carefully against the exact date the notice was issued.

The investigation steps that actually matter

1. Note the exact date the notice was issued — this is your anchor point for everything else.
2. Review every listing created, edited, or ended in the days immediately before that date, since a listing change is one of the most common triggers for this kind of review.
3. Check for recent buyer complaints, returns, or cases opened around the same window, since disputes clustering right before a notice are rarely a coincidence.
4. Confirm whether any account details changed recently — a new bank account, address, or contact detail update can itself trigger a review, independent of anything related to listings or buyers.
5. Look for a pattern connecting the notice timing to a specific action, rather than assuming the notice is unrelated to anything you did recently.

Why guessing produces the wrong response

It's tempting to draft a general, reassuring reply — "my account is in good standing, please review" — when a notice feels vague. This rarely works, because it doesn't address anything specific, and a specific review process is specifically looking for a specific answer. A response built on an actual identified trigger, addressing exactly what's likely being reviewed, gives eBay something concrete to evaluate rather than a general assurance that doesn't engage with the actual review.

Where to check your account status directly

Always verify the notice and your current account status directly in Seller Hub, under Messages or the account status and restrictions section — never rely purely on an email preview or subject line, which can be abbreviated or unclear. Confirm the exact code referenced, whether any account function is currently restricted, and read the full notice text carefully for any detail that might point toward the actual trigger, even a detail that seems minor on first read.

MC999 versus MC011 versus a VeRO complaint

These three get confused constantly, and mixing them up means preparing the wrong kind of response entirely:

	MC999	MC011	VeRO complaint
Generally about	Account or listing activity flagged for review	Account or listing verification — documentation	Intellectual property — a rights holder reporting infringement
Who raises it	eBay's internal review systems	eBay's internal review systems	A third-party rights holder via eBay's VeRO programme
Typical response	Review recent activity, respond to what's specifically flagged	Submit the specific documentation requested	Address the specific IP complaint directly

This reflects general patterns rather than an official classification — eBay doesn't publish a precise breakdown of what triggers each code, so any individual notice should ultimately be read on its own specific terms. For a fuller comparison, see MC011 vs MC999 vs VeRO compared.

A worked example

A seller running a mixed-category eBay store received an MC999 notice with no specific reason stated. Working backward from the notice date, the seller found that three listings had been edited two days prior to update pricing and add new photos, and one buyer had opened a "not as described" case in the same window on an unrelated listing. Rather than responding generically, the seller specifically addressed the recent listing edits — confirming the changes were accurate updates, not an attempt to mislead — and separately addressed the open buyer case, showing it was already being resolved directly with the buyer. This specific, evidence-based response, built from the actual investigation rather than a generic reassurance, led to the review being resolved within the notice's stated window.

How long an MC999 review typically takes

There's no single, universal timeline eBay publishes for how long an MC999 review takes to resolve, and it can genuinely vary based on the complexity of what's being reviewed and current review volume on eBay's side. What matters more than trying to predict an exact timeline is making sure your side of the process — the investigation and any response submitted — is done thoroughly the first time, since a rushed or incomplete response that comes back for clarification typically adds far more total time than a slower, more careful first submission would have taken.

Why documentation matters even before you're asked for it

Even though MC999 doesn't typically request a specific document upfront the way MC011 does, having your own records organized — order history, buyer communication, listing edit history, supplier information if relevant — puts you in a much stronger position if the review does end up requesting supporting evidence, or if you need to reference specific dates and details in your response. Sellers who keep basic records organized as a matter of course, rather than scrambling to reconstruct a timeline after a notice arrives, consistently respond faster and more accurately than those starting from scratch.

The emotional side of an ambiguous notice

It's worth naming directly: an MC999 notice's vagueness is often more stressful than a notice that states a specific, fixable issue, precisely because there's no clear checklist to work through. That stress is a real part of the experience, but it shouldn't drive the response — a calm, methodical review of recent account activity, rather than a rushed, anxious reply sent to make the notice "go away," consistently produces a better outcome. Taking the time to actually investigate before responding is not the same as ignoring the notice; it's the step that makes the eventual response worth something.

What not to do while a notice is under review

• Don't make further significant account changes — new listings in bulk, another bank detail update — while a review is active, since additional activity during a review window can complicate rather than help resolve it.
• Don't ignore the notice hoping it resolves itself. A notice that isn't responded to within any stated window can escalate to a broader restriction.
• Don't submit a generic, templated response copied from a forum or general advice page without adapting it to your account's actual specific situation.
• Don't panic-close or relist affected items without understanding whether that action itself could complicate the specific review underway.

When to get help versus handling it yourself

A straightforward MC999 notice with a clearly identifiable trigger — a recent listing edit, a specific buyer dispute — is often manageable to address yourself once you've done the investigation steps above. A notice that remains genuinely unclear after a careful review, or one that's part of a broader pattern of account restrictions, is where getting an outside, experienced read on the situation tends to save real time and reduce the risk of a response that misses what's actually being evaluated.

How MC999 fits into a wider account health picture

An MC999 notice rarely exists in complete isolation from the rest of your account's health signals — it's worth checking your overall seller performance dashboard, defect rate, and any other open cases or notices at the same time, rather than looking at the MC999 notice as a fully separate issue. Sometimes a notice is the first visible sign of a broader pattern the review system has flagged, and addressing only the notice itself while ignoring an underlying performance issue that's still actively developing means the same kind of review is likely to recur. Treating the notice as a prompt to review overall account health, not just the specific flagged window, produces a more durable resolution.

What a genuinely resolved notice looks like

A properly resolved MC999 review typically results in the notice clearing from your account status without any further restriction being applied, and no repeat notice shortly afterward referencing the same underlying activity. If a notice appears to clear but a very similar one reappears within a short window, that's a signal the original response addressed the surface issue without resolving whatever the review system is actually continuing to flag — worth investigating further rather than assuming it's simply bad luck or an unrelated second review.

Building account habits that reduce this risk going forward

Beyond resolving a specific notice, sellers who experience MC999 reviews often benefit from tightening a few ongoing habits: keeping listing edits deliberate and well-documented rather than frequent and unexplained, responding to buyer disputes quickly and thoroughly rather than letting them sit, and treating any account detail change as something to do carefully and rarely rather than routinely. None of this guarantees avoiding a future review, but it does reduce the number of plausible triggers an automated review system has to flag.

If you've got an MC999 notice and the trigger isn't obvious, message me directly on WhatsApp with the exact wording or a screenshot — I'll help you work through what's actually being flagged, review your recent account activity against it, and put together a response that addresses the actual situation rather than a generic reassurance.