Hi all,
I submitted invoices and managed to get three of them reinstated.
However, today was the final date for submission, and along with my remaining two listings, Amazon has also deactivated the ones that were previously reinstated.
Has anyone else faced a similar issue in the past?
Need guidance.
Yeah, Amazon sometimes rechecks bundles and flags them again. Open a case under Product Authenticity, attach the same invoices, and mention that they were already reinstated before. They usually fix it quickly. Did you make the bundles yourself?
Yes, this happens more often than Amazon admits, and it’s usually not because your documents were suddenly “wrong”, it’s because bundles get swept up repeatedly by automated audits, especially after the US bundling policy changes. When one ASIN in the group gets flagged again, the system sometimes re-flags all related bundles, even ones previously reinstated, and forces you back into the same documentation loop. Sellers with multi-pack or bundle-heavy catalogs report this exact pattern: reinstated today, re-flagged a week later, even though nothing changed.
The most important thing to know is that this is almost always an automated reset, not a sign that Amazon believes your earlier documents were invalid. The usual fix is to resubmit the exact same invoices and POA that worked before, but include a short paragraph explaining that Amazon previously reinstated these ASINs with the same documentation and that no sourcing, supplier, or bundle components have changed. This usually helps push the case toward a manual review instead of another automated rejection.
If they keep rejecting everything at once, call Account Health and ask them to escalate specifically to the “Catalog Integrity” or “Notice Dispute” team, because bundle ASINs are grouped in the backend and can only be fully cleared when someone manually removes all associated flags. Most sellers eventually get them reinstated again, but it can take two or three rounds before the system stops re-triggering the violations.
In short, yes, this is normal with bundles right now, it’s fixable, and the solution is persistence plus escalation with a clear explanation that these ASINs were already approved with the same documents.