Why were some rows skipped after my bulk product update?

You uploaded a Product Report file, and the Review Changes screen reports fewer updates than you expected, with a count of skipped products alongside a reason for each one.

What you will see

Review Changes shows two counts, one for the products Kintsugi will update and one for the products it will skip. Under the skipped count you see a breakdown by reason, and a download that lists every skipped row with its reason. The reasons you are most likely to see are Invalid product, Invalid category, Invalid subcategory, Invalid approval status, or a conflict.

Skipped products are never changed. Your existing categories and statuses stay exactly as they were.

Why this happens

1. A category or subcategory value is not on the Product Codes sheet. This includes values typed by hand, values carried over from another system, and pairs where the subcategory belongs to a different category.

2. A column other than Category, Subcategory, or Status was edited. Sorting or reformatting a Product Report file can change cells you did not intend to touch, and any edit outside the three supported columns invalidates that row.

3. The Status cell was set to something other than APPROVED. APPROVED is the only status the Product Report file can set.

4. The product changed in Kintsugi after you exported the file. If you then edit one of the three supported fields, Kintsugi skips that row as a conflict rather than overwriting the newer data.

5. The row is not a product Kintsugi can update. New rows added to the sheet, duplicated rows, blank identifiers, and archived products are all reported as an invalid product.

How to fix it

Start by downloading the skipped list from Review Changes. It names the reason for every row, which tells you which fix below applies.

If the reason is Invalid category or Invalid subcategory:

1. Open the Product Codes sheet in the same Product Report file you downloaded or edited.

2. Copy the category value and the subcategory value from that sheet directly into your rows, so the pair matches an entry exactly.

3. Save the file as .xlsx and upload it again.

If the reason is Invalid approval status:

1. Set the Status cell to APPROVED for the rows you want to approve.

2. For any other row, restore the value that was in the exported file so the status stays as it is.

3. Save the file and upload it again.

If the reason is Invalid product:

1. Export a fresh Product Report file from Products, since the safest fix is to start from clean data.

2. Make your edits again in the new file, in the Category, Subcategory, and Status columns only.

3. Delete nothing, add nothing, and leave the row order as exported.

4. Save the file and upload it again.

If the reason is a conflict:

1. Export a fresh Product Report file. The conflict means the product changed after your last export, and Kintsugi protects the newer value.

2. Reapply your edits to those rows in the fresh file.

3. Save the file and upload it again.

If many rows come back as conflicts, your export is stale. Exporting immediately before you edit, and uploading soon after, resolves most of these in one pass.

How to confirm it is resolved

Upload the corrected Product Report file and check the Review Changes counts. The rows you fixed should now appear in the update count and in the before and after preview, and the skipped count should drop by the same number. Confirm, wait for the progress banner to finish, then spot check a few of the affected products on the Products list.

If this did not work

Reach out via the chat bubble in the bottom right. To help us resolve this quickly, please include:

• The email address on your Kintsugi account

• The skipped-products file you downloaded from Review Changes

• The Product Report file you uploaded, if you are able to share it

• The reason shown for the rows you cannot resolve

• Roughly when you exported the Product report file and when you uploaded it