Bulk Product Update Reference
A complete guide to fields, formats, and rules for bulk updates.Updated 20 days ago
/ /
Everything the bulk product update workbook accepts, and exactly what Kintsugi does with each row. Use this page while you are editing the workbook, and again if a row does not do what you expected.
Product Report File Structure
Sheet | Purpose | Editable |
|---|---|---|
Products sheet tab | One row per product in your organization, exported from the Products page | Category, Subcategory, and Status columns only |
Product Codes sheet tab | The full list of valid category and subcategory pairs, with a description of each | No, reference only |
Keep both sheets in the file, keep the sheet names as exported, and keep the column headers exactly as exported. Kintsugi matches on those headers, so a renamed or reordered header stops the whole file.
Editable Fields
Column | Accepted values | Notes |
|---|---|---|
Category | Any category listed on the Product Codes sheet | Matched without regard to capitalization. Cannot be blank. |
Subcategory | Any subcategory that is valid for the category in the same row | The pair must exist on the Product Codes sheet. Cannot be blank. |
Status | APPROVED | The only status you can set. |
Every other column is read-only, including product name, description, SKU, price, and external identifiers. Changing one of them invalidates that row.
Row Outcomes
Kintsugi classifies every row in your workbook into one of the outcomes below. When a row has more than one problem, only the highest priority reason is reported, in the order they appear here.
Updated
Field | Value |
|---|---|
Trigger | At least one of Category, Subcategory, or Status is changed to a valid value |
What Kintsugi does | Applies the change after you confirm, records it in the product history, and marks the product as manually edited |
Reason shown | None, the row appears in the update count and in the before and after preview |
What to do | Review the preview, then confirm |
Ignored
Field | Value |
|---|---|
Trigger | All three editable values match what Kintsugi already has |
What Kintsugi does | Leaves the product alone |
Reason shown | None, the row is counted as ignored rather than skipped |
What to do | Nothing, this is a normal outcome for any row you did not edit |
Skipped, invalid product
Field | Value |
|---|---|
Trigger | The product identifier is blank, unknown, or duplicated in the file, the row is new, the product is archived, or a read-only column was changed |
What Kintsugi does | Leaves the product alone |
Reason shown | Invalid product |
What to do | Re-export, make your edits again in the fresh file, and change only the three editable columns |
Skipped, invalid category
Field | Value |
|---|---|
Trigger | The Category cell is blank or is not on the Product Codes sheet |
What Kintsugi does | Leaves the product alone |
Reason shown | Invalid category |
What to do | Copy the category value directly from the Product Codes sheet |
Skipped, invalid subcategory
Field | Value |
|---|---|
Trigger | The Subcategory cell is blank, or the category and subcategory pair does not exist |
What Kintsugi does | Leaves the product alone |
Reason shown | Invalid subcategory |
What to do | Check the pairing on the Product Codes sheet, since a subcategory is only valid under its own category |
Skipped, invalid approval status
Field | Value |
|---|---|
Trigger | The Status cell is set to anything other than APPROVED, or to a status the product cannot move to |
What Kintsugi does | Leaves the product alone |
Reason shown | Invalid approval status |
What to do | Set the cell to APPROVED, or restore the exported value to leave the status as it is |
Skipped, conflict
Field | Value |
|---|---|
Trigger | The product changed in Kintsugi after you exported the file, and you edited one of the three supported fields |
What Kintsugi does | Leaves the product alone rather than overwriting the newer data |
Reason shown | A conflict reason with the detail of what changed |
What to do | Re-export, redo those edits in the fresh file, and upload again |
A change made in Kintsugi to a column you did not edit does not create a conflict. For example, a connected platform renaming a product does not block your category change.
Whole-file Rejections
Some problems stop the file before any row is read. When that happens, no products are changed and you see a single error rather than a row breakdown.
Cause | What to do |
|---|---|
The file is not an Excel workbook (.xlsx) | Save the workbook as .xlsx and upload again |
The expected worksheet is missing or renamed | Start over from a fresh Products export |
Column headers were renamed, removed, or reordered | Start over from a fresh Products export and edit the cell values only |
The file cannot be read, for example it is corrupted or was saved mid-edit | Close the spreadsheet tool, save the file again, then upload |
What Happens after you Confirm
Behavior | Detail |
|---|---|
Order of operations | Kintsugi applies valid rows in batches in the background, so you can keep working |
Progress | The Products page shows how many products have been processed out of the total |
Partial outcomes | If some rows fail while others succeed, the successful rows stay applied and are counted separately |
Product history | Every applied change is recorded against the product, attributed to the bulk update |
Connector protection | Applied products are marked as manually edited, so a later sync does not overwrite your values |
Tax impact | Kintsugi reprocesses the affected transactions that have not been filed yet, which flows into your exposure and filing data |
Need Help?
For further concerns, we're always here to help. If you can't find the answer you're looking for, just reach out to us using the chat in the bottom right corner of your screen.
Was this article helpful?