Styxis
Company
Knowledge

Shopify inventory reactivation: omitted quantity is not an explicit zero

When reactivation defaults change, the operational assumption that activation resets stock must change with them.

Activation is separate from quantity adjustment

Activation state and inventory quantity are different facts. When quantity arguments are omitted during reactivation, preservation of the existing quantity should be an acceptance condition. Treating a location's return to service as permission to start with empty stock can leave the activation display correct while operators hand over incompatible quantities. [1, 2, 3]

What omission means in 2026-04

Shopify's 2026-04-17 announcement says that inventoryActivate preserves pre-activation quantities in 2026-04 and later when available and onHand are not supplied. Earlier behavior reset quantities to 0; the preservation change also applies to the REST connection request. This does not mean that explicitly supplied quantities must always be replaced with historical values. [1]

Preserve the request as part of the handoff

The reactivation owner should hand over the quantity immediately before the call and whether quantity arguments were omitted. If the subsequent value changes, investigate business logic that relied on initialization. Match before and after values by item and location, and record any concurrent stock movements. Separate a test with concurrent changes: its raw difference cannot establish the API's preservation behavior. [1, 3]

A fixture that retains 7 items

Define an illustrative inactive location with available quantity 7 and no other stock changes during the test. Reactivation with both quantity arguments omitted should leave 7, satisfying preservation. A result of 0 calls for investigation of request transformations or subsequent adjustments that still initialize stock. The expected 7 comes from the pre-call record, not from copying the response. This is not a reproduction performed against Shopify. [1, 3]

Place Truthound at the comparison table

ColumnPairValidator in Truthound Core 3.3.2 can compare quantity columns prepared for the same item and location. It skips pairs containing null, so required-value checks must precede the comparison. Truthound does not activate inventory or lock transactions. If initialization is the intended operation, express it through an approved stock-adjustment procedure instead of relying on an old side effect of omission. That also makes the handoff unambiguous. [1, 2, 3]

Application conditions

Use reactivation in 2026-04 or later with both available and onHand omitted. Obtain nonmissing before and after values for the same item and location, and separate concurrent adjustments into another batch.

Alternatives

If initialization is required, express it through an approved inventory-adjustment procedure rather than relying on a side effect of omission.

Limitations

  • Truthound neither activates inventory nor locks concurrent transactions. Do not impose preservation on requests that explicitly supply a quantity.

Evidence

Event checked
Subject checked
Modified