Unavailable pages: submission errors, suppression, and why a vendor ASIN is not selling

Submissions report in the submission status view (Items → Bulk product submissions, in most accounts). Row states, labels varying by account and template: accepted (ASIN created or update applied), pending (in Amazon's review, not a verdict), or rejected. Some templates add a warning to accepted rows whose value was ignored or normalized; re-check it, do not count it as success.

Download the error sheet: row, field, error description. Read it first; one field fails for several reasons. Common families:

• Missing required attribute for the product type.
• Invalid value: outside the allowed list, wrong unit or format.
• Identifier problems: the GTIN already exists (a match: add the ASIN, per Vendor catalog), fails GS1 validation or belongs to another brand.
• Product type mismatch, relationship errors (parent not found, mismatched theme values), image URL unreachable.

Fix the source value, not the symptom. Resubmit only the failed rows: re-sending accepted rows exposes them to stray edits and buries the outcomes you need. Confirm acceptance, then check the live page; acceptance is not display (Content updates).

"Not selling" has four causes with four owners.

• Catalog suppression. A required attribute or image is missing, or a title or claim breaks a content policy; the page hides from search or shows no Add to Cart button. Yours to fix through the catalog.
• No Amazon offer. The page is fine; Amazon Retail has no stock or active offer, so it reads Currently unavailable or shows only third-party offers. First check your own availability status in the catalog: a vendor-set temporarily unavailable or discontinued status stops Amazon ordering, and resetting it is yours. Otherwise the purchase-order side owns it.
• A retail decision not to carry the item. Amazon marks it not currently buying (labels vary). The page stays, the offer does not. A commercial conversation with your buyer or Vendor Manager, not a catalog case.
• A safety or quality halt, the Andon Cord. Sales stop and a reason code arrives; Case management covers the response.

The first two are confused most often: alike to shoppers, different owners.

Stop at the first failure:

1. Confirm the page exists. No page or a redirect means a merge, whole-page suppression or an unaccepted setup; check submission status.
2. Check search visibility. A loaded page that never appears is usually suppressed, though an ASIN nobody offers drops out too; no offer at step 3 makes absence a symptom, not proof.
3. Check for an Amazon offer on a complete page (required attributes, main image present). Currently unavailable means nobody has an offer; a third-party offer without an Amazon one is the same signal. Incomplete page: still catalog.
4. Read the notice or reason code. Catalog and item status views and notifications carry flags; a halt arrives as a reason code (labels change; see Vendor Central's help and Support → Resource Center).
5. Assign the owner. Catalog: you. Stock: your availability status, then retail. Buying decision: retail. Safety: Andon Cord.

Shoppers see one message for every cause, so Case management uses unavailable loosely; here, by owner: suppressed is content, yours; unavailable on a complete, unflagged page is the offer, Amazon Retail's.

Each catalog cause has one fix path; verification is always the same.

• Missing attributes and images: fill them through Items → Edit Products for one ASIN, or export, correct and re-upload the spreadsheet (Content updates). An unreachable image URL rejects a row as a missing main image suppresses a page.
• A clean submission that changes nothing: the contribution-conflict signature. Request a BIN check, the support request asking Amazon to review which contributor's data is displaying (Retail readiness), with the ASIN, attribute, your value and evidence.
• Locked attributes and relationships: brand, product ID, product type and browse node (Content updates) and family structure go through Support → Contact Us in the matching category (Case management).
• A policy-breaking title or claim: rewrite inside the rules and resubmit; the suppression lifts once the content passes.

After any fix, verify in the same order: submission status accepted → live page shows the value → the ASIN returns in search. Accepted but not displayed is unresolved, not done.

Most suppressions trace to a short list per product type: safety and compliance fields (batteries, hazmat, age range, country of origin), the main image, and unit and pack counts. Check it before every setup and bulk update.

Two habits catch the rest:

• Check the page the week a change ships. A packaging or specification change often means a new image or unit count, and sometimes a new GTIN under GS1 rules, any of which can suppress a page or break a family. Look that week, not when a sales report drops.
• Log every incident with its cause bucket: catalog, retail stock, retail decision or safety. Three unavailable ASINs in a month mean different things if they are stock-outs or missing compliance fields; the bucket shows the pattern.

Amazon 3P → Reports and catalog health runs the same loop at scale; a weekly sweep of the catalog views does the same for a vendor.