Luminous holds on-hand steady when a WMS omits a SKU from its feed

When your warehouse group is configured to pull inventory from a specific external location inside your WMS or 3PL, Luminous needs a per-location stock row for each SKU in that feed. If the WMS doesn't include a row for a SKU in a given pull cycle, Luminous leaves the existing on-hand count unchanged rather than overwriting it with zero.

Why does this happen?

A missing row in the WMS feed is ambiguous — it could mean:

  • The SKU is genuinely out of stock at that location, or
  • The WMS had a partial sync and simply didn't include the SKU this cycle

Because Luminous writes on-hand as an absolute value, treating a missing row as zero would destroy real inventory data. A partial sync would look identical to genuine zero stock, and the data would only be restored on the next successful full pull.

What you'll see

  • The SKU's on-hand in Luminous remains at its last known value.
  • The stock pull will log a notice that the SKU was skipped this cycle (visible to support in the system log).
  • On the next pull cycle where the WMS does include the SKU, the on-hand is updated normally.

When should I investigate further?

If a SKU's on-hand appears frozen for multiple consecutive pull cycles, the WMS may have permanently stopped reporting it (e.g. a discontinued variant). In that case:

  1. Check the WMS or 3PL portal to confirm whether the SKU is still being tracked there.
  2. If the product mapping in Luminous is stale, remove or remap the product under Settings → Integrations → [your account] → Manage Products.
  3. Contact support if the WMS is reporting the SKU but Luminous still isn't updating it.

This only applies to warehouse groups pinned to a specific external location

If your warehouse group aggregates stock from all external locations (no specific location pinned), stock is pulled from whatever rows the WMS reports and this hold-steady behaviour does not apply.