Overview

When you export and re-import the integration account product mapping CSV, any row that re-maps or deletes a mapping that is currently feeding on-hand or pending stock to an externally managed warehouse is rejected by default. This prevents a stock sync from silently zeroing out inventory on the product you move away from.

The rejection message names the affected SKU, the warehouses involved, and the on-hand and pending quantities that would move. It also tells you which column to set to allow the row to proceed.

The CONFIRM_STOCK_MOVE column

Every mapping CSV includes a CONFIRM_STOCK_MOVE column (allowed values: true / false, default false).

To allow a specific row to move warehouse stock, set that row's CONFIRM_STOCK_MOVE cell to true before re-uploading. The system treats this as your explicit acknowledgement that stock will move on the next sync.

Leave the column false (or blank) for all other rows. Only set it to true on rows you have reviewed and intentionally want to re-map or delete.

Step-by-step

  1. Export your current mapping CSV from Settings → Integrations → [your account] → Products → Actions → Export Products.
  2. Make your SKU changes in the file.
  3. Before uploading, review any row where you changed LUM_SKU or set DELETE to true.
  4. For each such row, check whether the row currently feeds a warehouse (look at the QTY_AVAILABLE column in the export, or review the mapping grid before exporting).
  5. On rows that do feed a warehouse and you still intend to change: set CONFIRM_STOCK_MOVE to true.
  6. Re-upload the file. Rows without CONFIRM_STOCK_MOVE=true that would move stock will be reported as row-level errors; all other rows in the file continue to process normally.

What 'moving stock' actually means

Each integration mapping row tells the stock-pull job which Luminous SKU receives the on-hand figures from the external feed. When you re-point a row:

  • The new SKU gains whatever quantity the feed delivers on the next sync.
  • The previous SKU either drops to zero (if no other active feed mapping on this account still supplies it) or is re-sourced from another mapping (if a sibling row with its own live feed continues to point at it).

The rejection message tells you which outcome applies so you can decide before committing.

Rows that are never blocked

A row is not blocked even if CONFIRM_STOCK_MOVE is false when:

  • The mapping is flagged as Ignore Stock — the stock pull already skips it.
  • The row has no current Luminous SKU (first-time mappings bring stock from nobody).
  • The mapping does not feed any externally managed warehouse group.
  • The SKU currently carries zero on-hand and zero pending at all fed warehouses.

For the same stock-move warning when editing mappings directly in the grid, see: How do I safely remap a product in the integration mapping grid, and what does the stock-move warning mean?