Platform policies change

Treat this as a map of what to expect rather than a current rulebook. Amazon's requirements change, and they differ between marketplaces and categories. Check the current policy for the specific marketplace before you launch.

Platform compliance reviews usually arrive as a document request. The most common problem is not that the documentation does not exist — it is that it exists somewhere and nobody can find it under time pressure. The second most common problem is that the seller did not expect a category of requirement at all.

This article explains what tends to be requested, what the most common causes of enforcement action are, and how to build a documentation folder once rather than reconstructing it under pressure.

What gets requested

The categories below cover most cases seen with phone accessories.

CategoryWhat it usually involves
Product identificationWhat the item is, what model it fits, what it is made of. Sometimes as simple as a photograph of the item and its packaging.
Material and safety documentationWhere you have it — the test reports discussed in the REACH article.
Brand authorisation If the listing uses a brand you do not own, expect to be asked for a letter. This is one of the most common reasons accessories listings are removed.
Regional regulatory informationFor EU sales, the responsible person details that GPSR requires to appear on the listing.
Importer or supplier informationSometimes requested to establish the chain of supply.
Labelling and packaging evidencePhotographs of the actual unit showing the markings and warnings in the destination language.

Why checks happen when they do

Enforcement tends to arrive at predictable moments, and being ready at those moments is most of the work.

The pattern to take from this

There is no moment when you can say the documentation is no longer needed.

Building the folder

The practical answer is to assemble it once, properly, and keep it current. A single folder per product, containing:

That last item sounds trivial and is the one people omit

When a document request arrives eighteen months after you assembled the folder, being able to tell what was current at the time is worth more than the document itself.

Reducing future problems

Most avoidable issues with phone case listings come from four habits:

1 · Listing a brand you do not have the right to sell

If your supplier is the brand owner, you need their authorisation letter before the listing goes live, not after it is removed. This is the single most common cause of removal we see in this category.

2 · Reusing listing copy across models

If the compatibility text mentions a model the case does not fit, that is a listing accuracy problem with a return-rate consequence — and a returns spike is itself a trigger for review.

3 · Leaving compliance fields empty until asked

Filling them in at creation is faster than reconstructing them under a deadline.

4 · Testing after production rather than before

A batch already in an FBA warehouse cannot be retrofitted with a test report. Test or verify before the goods leave.

What we can and cannot do

Being clear about this saves time on both sides.

We can

We cannot

Those are decisions and arrangements that belong to the seller of record. A supplier who says they can handle all four is either misunderstanding their role or saying what you want to hear.

Preparing for an FBA launch?

Tell us your target marketplace and your compliance requirements. We will tell you which documentation exists, what we can print onto the packaging, and what you will need to arrange yourself.