How to read an Amazon processing report

Confirm the report belongs to the workbook

Start with the report created by the same submission as the workbook under review. Seller SKUs and row numbers can change between versions, so a report from an earlier upload may point to the wrong record even when the message looks relevant.

Keep the source file unchanged and record the submission time. If several reports exist, compare the reported SKUs and file-level totals before selecting one for diagnosis.

• Match the submission time and filename when available.
• Compare the number of processed, successful, and failed records.
• Confirm that reported SKUs exist in the workbook.
• Keep unmatched messages visible instead of forcing a match.

Read from the most specific field to the least specific

An explicit cell address is the strongest pointer. Next use a seller SKU and attribute together, then a record number and attribute, and finally the SKU by itself. The message text explains the rule, but it should not override a more precise row or cell reference.

Column names can vary across report formats. Normalize familiar labels such as SKU, seller-sku, record number, error code, error type, message, attribute, row, column, and cell before deciding that a field is missing.

Separate the reported problem from the safe action

A report can identify the failed field without proving the replacement. A blank required value may need seller knowledge. An invalid value may require the current template's allowed-values sheet. A catalog conflict may describe an existing Amazon value but still require evidence or support.

Treat the report as evidence of what Amazon rejected, not permission to invent the value Amazon will accept. Record the repairability separately from the severity and error code.

Build a reviewable next step

For each finding, retain the code, message, SKU, worksheet, row, column, cell, original value, proposed value if deterministic, confidence, and next owner. This creates a traceable repair plan and prevents a generic message from becoming an unreviewed bulk edit.

When a message cannot be mapped to a cell, keep it at the report level. It can still be useful for template selection, seller research, or an Amazon Support case.