{"section":"known-issues","requestedLocale":"en","requestedSlug":"amazonmatch-in-some-cases-sku-reverts-to-pending-review-after-match-confirmation-with-no-indication-of-amazons-rejection-reason","locale":"en","slug":"amazonmatch-in-some-cases-sku-reverts-to-pending-review-after-match-confirmation-with-no-indication-of-amazons-rejection-reason","path":"docs/en/known-issues/Marketplace Out/amazonmatch-in-some-cases-sku-reverts-to-pending-review-after-match-confirmation-with-no-indication-of-amazons-rejection-reason.md","branch":"main","content":"## Summary\n\nIn the ad matching flow, some SKUs go back to showing \"Pending Review\" shortly after being approved, with no message explaining why on the screen. The screen doesn't indicate when Amazon rejects the match for a reason that requires seller action (for example, when the product's brand requires prior authorization to be sold by that seller).\n\n\n1. In Bridge, this error message may appear, but it can be replaced if the SKU receives any other update, and the real reason ends up getting lost.\n2. In the match, the \"Pending Review\" status looks identical to a SKU that simply hasn't been processed yet, so the user ends up confirming the same match repeatedly without understanding why it never completes.\n\n\n**Important:** this scenario doesn't happen with every SKU it only occurs in specific cases.\n\n## Simulation\n\n- Go to Marketplace > Amazon > Product Publication.\n- Find a SKU with a suggested match for a product whose brand requires direct authorization from the owner (not recoverable through a simple request within Amazon itself).\n- Open the suggestion details and click \"Confirm and publish\".\n- Wait some time after publishing (processing is asynchronous).\n- No warning is shown on the screen before confirmation, and the button remains enabled normally.\n- The SKU goes back to showing \"Pending Review\" in the listing, with no indication that Amazon rejected the ad.\n- Check whether the error message was logged in Bridge in some cases it may not appear, having been replaced by another SKU update.\n\n## Workaround\n\nCheck whether the error message was logged in Bridge in some cases it may not appear, having been replaced by another SKU update."}