Overview

The Max Push Quantity setting puts a hard ceiling on the inventory figure Luminous sends to a channel. Once set, the channel will never be told you have more than that number, regardless of how much stock is on hand. This is separate from a buffer: a buffer subtracts a reserve from your available quantity; a cap simply clamps the result from above.

Key rules:

  • The cap is applied after any buffer. Buffer is subtracted first; the cap clamps the result.
  • The cap is a ceiling only — it never raises a quantity. If your real (post-buffer) stock is 40 and the cap is 200, the channel receives 40.
  • Setting the cap to 0 tells the channel you have no stock, regardless of on-hand levels.
  • Leaving it blank means no cap is in effect and the channel receives the full buffered quantity.

Option 1 — Channel-wide default (applies to every product on the channel)

  1. Go to Manage → Channels and open the channel you want to configure.
  2. Click Edit.
  3. Scroll to the Stock Push Defaults section (under Push Inventory Stocks and Costs; it only appears when Push Stock to Integration is turned on).
  4. Enter a number in the Max Push Quantity field. Leave blank for no cap.
  5. Click Save.

Every product on this channel that has not set its own Max Push Quantity value will use this default on the next push cycle.

Apply to all products now: If you want to overwrite per-product values that were already set, use the Apply to all products in this channel button on the same screen. This cannot be undone.

Option 2 — Per-product override (one SKU on one channel)

  1. Go to Manage → Channels → [your channel] → Product Mapping.
  2. Find the product row and open its mapping dialog (click the edit icon or the channel SKU).
  3. Enter a value in the Max Push Quantity field.
    • Leave blank to inherit from the channel default.
    • Enter 0 to suppress stock for this SKU on this channel only.
  4. Click Save mapping.

Per-product values take precedence over the channel-wide default.

Option 3 — CSV bulk upload

The channel product mapping CSV import accepts a MAX_PUSH_QUANTITY column. Include it alongside your channelSku and any other fields you want to update:

channelSkumaxPushQuantity
WIDGET-RED200
WIDGET-BLUE0
WIDGET-GREEN(leave blank to clear/inherit)

Leaving the cell blank removes a previously set cap and causes the product to inherit from the channel default.

Option 4 — External API

Include maxPushQuantity in the integrationProducts array when calling POST /channels/{channelId}/integration-products:

{
  "integrationProducts": [
    {
      "channelSku": "WIDGET-RED",
      "maxPushQuantity": 200
    }
  ]
}

Pass null to clear a cap and inherit from the channel default.

Precedence order

When a push runs, Luminous resolves the cap in this order (most specific wins):

  1. Per-product channel override — set via the mapping dialog, CSV, or API
  2. Channel-wide default — set on the channel edit page
  3. Base product default — a product-level fallback (less commonly used)
  4. No cap — the hard default; the full buffered quantity is pushed

Verify what was applied

Open the Stock Push Explanation dialog for any product (available from the Product Mapping grid) to see which layer the resolved Max Push Quantity came from and how it affected the final published quantity.