Overview

When Luminous is connected to an external warehouse management system (WMS) or OMS, each integration mapping row tells the stock-pull job which Luminous SKU should receive the stock figures that come in from that feed. Changing a mapping row's SKU — remapping — redirects where that feed's quantities land on the next sync. Luminous shows a pre-save warning any time this would move meaningful stock, so you can review the impact before it happens.

Where to find the mapping grid

  1. Go to Settings → Integrations.
  2. Find your integration and click the storefront (Manage Products) icon in the row's action icons (next to the Field Mappings, Edit Account, and ⋮ menu icons) to open the mapping grid.
  3. Open the Products tab. Each row represents one item from the external system alongside the Luminous SKU it is currently mapped to. (Warehouse Mapping and Field Mappings are separate tabs alongside it.)

When does a dialog appear?

Every time you change the Luminous SKU on any mapping row — integration-level or channel-level override — Luminous shows a generic confirmation dialog asking you to confirm the update. This appears on every SKU change, regardless of stock impact.

For integration-level rows only (not channel-level override rows), Luminous also checks whether the change would move meaningful stock. If it would, a second, richer dialog appears after you confirm the first one. That second dialog appears if all of the following are true:

  • The row is not flagged as Ignore Stock.
  • The row is already mapped to a Luminous SKU (first-time mappings bring stock from nobody, so no impact dialog is needed).
  • The row feeds at least one externally managed warehouse group whose on-hand is owned by this integration account.
  • That SKU currently has non-zero on-hand or non-zero pending at one or more of those warehouses.

If none of those apply — for example, you're mapping a row that never had a Luminous SKU, or the SKU carries zero stock everywhere — only the generic confirm dialog appears; there's no second prompt.

Reading the stock-impact dialog

This dialog is titled "This mapping is supplying stock." Its body is a short paragraph rather than a table of fields: it names the current ("from") SKU, states what it currently receives at each affected warehouse (on-hand and pending), and explains whether the vacated product will drop to zero or keep receiving stock from another mapping after you save. Two buttons appear: Move the stock (confirm) and Cancel.

'drops to zero'

No other mapping row on this integration account actively feeds that product. After the next stock sync the product's on-hand will be written to zero by the pull job. Choose Cancel if that is not intended.

're-sourced from another connection'

At least one other mapping row on the same account currently delivers per-location stock figures (or a non-zero current stock count) for that product. The product will continue receiving stock from that sibling after you remap this row.

Note: A sibling row that merely points at the same SKU but has no live feed of its own does not count as "re-sourcing" the product. Luminous checks for actual feed data, not just the presence of another row.

If the check itself fails

If Luminous cannot load the impact (e.g. a network timeout), a fallback dialog appears stating the check could not complete. You can choose Save anyway or Cancel. If you are unsure, cancel and try again after a moment.

What happens after you confirm

The mapping row is saved immediately. On the next scheduled stock sync the pull job reads the new mapping and writes quantities to the newly selected Luminous SKU. The previously mapped SKU's on-hand at this warehouse will be updated to reflect whatever the integration now reports for it (typically zero if no other mapping feeds it).

Pending inventory (open order reservations) is not automatically rebalanced — if the vacated product had pending orders, those remain until fulfilled or cancelled.

Tips

  • Check before you change. Look at the current on-hand shown in the dialog. If the numbers are large and unexpected, cancel and investigate whether the product mapping was intentional.
  • Multiple mappings on the same product. If you have more than one mapping row pointing at the same SKU, verify that at least one remaining row has an active feed before remapping or removing others.
  • Unmapping (clearing to no SKU) triggers the same warning. Clearing a fed mapping row leaves the product at zero on the next sync — the dialog will tell you this explicitly.