Content updates: Edit Products, bulk spreadsheets, and locked attributes

Write the change record before you open anything. One line per change, six parts: the ASIN, the field, the current value as the live page shows it, the requested value exactly as approved, the source that approved it (copy deck version, specification sheet, packaging artwork), and the evidence you could attach to a case (a page screenshot, the artwork file, a GS1 certificate). The current value matters as much as the requested one: it is what you compare against later, and it proves the change was needed.

Keep the record at field level, because that is how the outcome arrives: forty title changes are forty lines. Mark each line requested, then submitted with the date.

In 1P, evidence is not bureaucracy. Amazon Retail and other contributors supply data on the same ASIN, and when their value outranks yours, the case you eventually open is decided on what you can show.

Items → Edit Products is the one-at-a-time path. Search the ASIN, open it, and the form shows the detail page content grouped by section: title, bullet points, product description, search terms, and the attributes the product type carries (material, capacity, color, country of origin and so on, varying by product type). Images are replaced per slot from the same form or a separate Upload Images tool (labels vary by account), and A+ Content has its own manager; Media and A+ Content covers both. Edit the fields, submit, and note the date.

Read the form before you type: fields that show as locked (greyed out or marked read-only; the presentation varies by account) cannot be changed here whatever you enter; the locked attributes section below covers them.

Amazon reviews some changes before they appear, so submitted and live can be days apart. A clean status the same afternoon is neither a failure nor a verification: it says the submission was taken.

For dozens or hundreds of ASINs, use a spreadsheet, in five steps:

1. Export a pre-filled spreadsheet of the items from Edit Products or the catalog view (labels vary by account), and keep an untouched copy as your before snapshot.
2. Edit only the columns you mean to change. Every edited column is applied — Amazon does not know which you intended, so a tidied title column changes titles. Identifiers must survive the edit as text; Foundations → Spreadsheet skills covers the mechanics.
3. Re-upload the file through Items → Bulk product submissions.
4. Track it in the submission status view, and download the error sheet if any row is flagged.
5. Check the live page field by field.

New item setup is the same mechanism with a different file: the new item setup spreadsheet (NIS) for the product type, downloaded from Bulk product submissions or Add Products (by account), filled (Vendor catalog covers the packaging levels) and uploaded through Bulk product submissions. A bulk upload is the same submission as Edit Products, on the same review.

Some attributes cannot be changed once the ASIN exists, through either path. The usual four are brand name, product ID (UPC/EAN), product type and browse node; others vary by category and account (the parent-child relationship is one; Variation families covers it); the Edit Products form shows which are locked. A spreadsheet is no workaround: depending on the template, a changed value in a locked column comes back as a row error or a warning, or is dropped silently — never applied.

Changing a locked attribute takes a Support → Contact Us case in the matching category (product detail page or item setup; labels vary) with evidence: packaging photos showing brand and barcode, a GS1 certificate for an identifier, the specification for a product type. Case management covers how to write it: one attribute per case, with the current value, requested value and evidence from your change record.

Do not work around a lock by creating a new ASIN with the "right" values; that is a duplicate, and it will be merged.

Read the submission, then the page, per field.

Submission status (Bulk product submissions, in most accounts) shows each row as accepted, rejected or pending. Rejected rows carry an error sheet (Unavailable pages); pending is not a verdict; accepted means the submission was taken, not that the page changed.

Compare each line of the change record against the live page. Each field ends as verified (shows the requested value; note the date) or unresolved (keep the evidence).

Three usual reasons an accepted field does not display:

• A contribution conflict — another contributor's value, often Amazon Retail's, outranks yours; re-submitting rarely changes that. Request a BIN check (the support request asking Amazon to review which contributor's data is displaying; Retail readiness covers the ranking) or open a Contact Us case on the change record.
• A lock — the field was locked and your value was never applied.
• Propagation delay — hours to a few days is common, longer at peak or under review; re-check before escalating, which Retail readiness puts at five days.