Amazon Identity and Utility-Bill Verification Failures: Fixing a Stalled Reverification

Why this exists: it's federal law, not an Amazon whim

The INFORM Consumers Act requires online marketplaces to collect and verify certain information from “high-volume third-party sellers” — anyone with 200 or more individual sales and at least $5,000 in gross revenue in any continuous 12-month period across the previous 24 months. For an individual seller that means a name and a working email and phone number; for a business it means a working email and phone number plus a government-issued form of identification tied to the business. Marketplaces have 10 days to verify that information once it's submitted, and sellers must re-certify that it's still accurate at least once a year.

That's worth knowing before anything else, because it reframes the whole process: this isn't a policy Amazon invented and can waive for a seller it likes, and it isn't a punishment. It's a federal compliance requirement Amazon has to run against every qualifying seller, which is also exactly why the process is rigid about document format and matching rather than about a human reviewer's judgment call.

What Amazon's own verification actually checks

Amazon's global seller identity, address, and business verification asks for a government-issued identity document — a passport, national ID, or driving license — plus a separate address-verification document, commonly a utility bill or bank statement dated recently. The stated bar is that every field on those documents needs to match what's already on file in Seller Central, and that documents be valid, unexpired, high-resolution, and unobstructed. None of that is unusual by KYC standards; what trips sellers is how literally “match” is applied.

The mismatches that actually cause most stalls

What we've watched happen inside stuck cases, and what shows up repeatedly across the seller-forum record of this exact process, isn't fraud detection working as intended — it's formatting. A street address spelled out as “North” on one document and abbreviated “N” on another reads as two different addresses to an automated match, even though a person would recognize them instantly as the same place. A utility bill in a spouse's or business partner's name, without a document proving the relationship to the registered seller, reads as an unrelated third party's bill. A document that's been cropped, screenshotted, or photographed off a screen reads as lower-confidence than a clean full-page PDF or original scan, even when every field is legible.

None of this is published as an official list of rejection reasons — it's what we observe from the pattern of cases that get stuck and then clear once the specific mismatch is corrected, and it should be read as observation rather than as Amazon's stated policy.

The fix, step by step

Start by pulling every document side by side — the registration record in Seller Central and every document you're about to submit — and compare them character by character, not by general impression. Fix any formatting mismatch before resubmitting rather than after a second rejection. If a utility bill specifically keeps failing, switching document type is usually faster than trying to force the same bill through again: a bank statement or a government-issued document showing the same name and address is generally accepted in its place, and starting from a different document type sidesteps whatever specific issue the utility bill kept tripping.

Submit only through the dedicated Identity Verification page inside Seller Central — documents attached elsewhere, including through a general support case, are reported not to count, which turns a correct document into an effectively missing one simply because of where it landed. And submit a full, uncropped page rather than a cropped image or a photo of a screen; a real PDF or original scan consistently performs better than either.

When the documents are genuinely correct and it's still stuck

Sometimes every document matches, every field is current, and the case still sits unresolved for far longer than the review should reasonably take. That's the point to stop resubmitting the same file hoping a different reviewer reads it differently, and instead request that the existing case be looked at again — the same internal-review logic that applies to a denied appeal applies here: if the submission was genuinely complete, ask for review of what's already there rather than generating a new submission that adds nothing. Keep the one case ID the whole way through; opening a second verification case rarely speeds anything up and can instead split your documentation across two threads a reviewer has to reconcile.

What a stalled verification costs, and where it fits with everything else

An unverified or uncertified high-volume seller's offers can be hidden from buyers until the process clears, which is a real revenue cost even though it isn't a policy strike or a suspension — it's a separate, parallel track that can run at the same time as ordinary account-health casework, and it's worth treating that way rather than assuming it will resolve itself while attention goes elsewhere. Across the 53 seller accounts we run casework on, a stalled reverification is one of the standing categories that quietly costs a seller weeks of visibility even when nothing else about the account is actually wrong.

Dr. Shield tracks verification cases as their own track inside a portfolio, priced on the call as a contingency against what's actually resolved; most useful when a seller is juggling a stuck reverification alongside other open cases and needs it not to get lost, less necessary for a single, first-time mismatch a careful side-by-side document check will usually clear on its own.