Choose the right removal method

There is no single general rule for the delete column for CSV deletions. The deletion method depends on the Data Transfer profile used, so always check the correct file structure before previewing.

• Customer-specific included products: use a row-specific delete=CONFIRM value in addition to the customer and product ID.
• Delete product inventory lines: use only products_stock_model column and validate the entire run in a separate execution step.

Do not copy the delete column or confirmation method from another profile to another file. The preview should show exactly the intended additions, deletions, overrides, and errors before execution.

Do not add a deletion column to the CSV file by default. Open the correct data exchange profile and follow its description, preview, and validation. An incorrect header row will prevent the inventory line deletion file from being processed.

Remove customer-specific inclusion link

CSV deletion validation in data exchange uses customers_id column and at least one product identifier: products_id , products_model , or products_api_model to import customer-specific included products. The optional delete column determines whether to add or remove the customer/product link.

A regular line adds a link if it doesn't already exist. A line with delete value of CONFIRM deletes an existing link. An empty delete means an addition; any other non-empty value is an error. Links missing from the file are not touched.

Preview customer-specific changes

CSV deletion validation in data exchange checks the customer and product before execution. Unknown or invalid customers_id , missing product ID, unknown product, and invalid delete value are flagged as errors and prevent execution.

Adding an existing link and deleting a non-existent link are ignored no-op rows. Both additions and deletions are visible in the preview. Confirm only when there are no error rows and the addition/deletion quantities match the intent.

Example of removing a customer-specific link

For example, CSV deletion validation in data exchange accepts the following structure:

customers_id,products_model,delete
1827,SKU-123,CONFIRM
1827,SKU-456,CONFIRM

The same file may also contain insertion rows with an empty delete . Do not use a different validation value or multiple conflicting product identifiers without the preview unambiguously resolving the intended product.

In the example, customer 1827 loses two named inclusion links. Verify in the preview that both SKUs are found as the intended products and that the lines appear as deletions, not errors or skips.

Delete inventory lines with a single column file

CSV deletion confirmation in data exchange uses a CSV file with the only header products_stock_model to delete product inventory lines. Each data line contains one inventory SKU to delete. There is no row-specific delete column or CONFIRM value used.

The operation progresses from file selection to preview and a separate commit. The first step does not delete rows: it shows the items to be deleted and errors. The only commit commit makes the database changes.

products_stock_model
RED-TSHIRT-M
BLUE-JEANS-32

The file must not contain products_stock_model,delete header pair. The current processor requires exactly one header.

Check the inventory write-off preview

CSV Depreciation Validation in Data Exchange matches the inventory line with products_stock_model value. Unknown inventory SKU is an error. Empty data lines do not constitute a row to be deleted, and a file without data lines is rejected. Subsequent occurrences of the same inventory SKU are ignored as duplicates.

Preview classifies matched deletions as changes. Execution requires explicit confirmation from the run level; without a confirming administrator, the run is blocked. Review the SKUs and target products to be deleted before confirming.

What happens after you delete an inventory line?

Confirming CSV depreciation in data exchange deletes the matched inventory line in the transaction. If the quantity of the line to be deleted is not zero, the system records a negative change in the inventory history with the reason Destroyed stock via CSV . The total quantity of each changed product is then synchronized from the remaining inventory lines.

Review the performance report for deletions, skips, and failures. Also, verify the product's Inventory Lines view, total quantity, and inventory history. You should not blindly retry the deletion if the report shows a partial failure.

Safe use

Confirming CSV deletions in data exchange is done with a small, unambiguous file:

1. Export or compile identifiers from an approved information system.
2. Use the headers from the profile you just selected.
3. Start with a few lines and check the preview.
4. Please correct any errors before confirming.
5. Compare the number of deletions and overrides to the expectation.
6. Only confirm the run in the correct tenant and with the correct permissions.
7. Check the performance report and target information after the run.

Retain the source file and report of the run according to an approved retention policy. The CSV deletion must be restored from the source system or with a new import if there is no separate undo function.