🐞 Bug Report: Inventory Threshold UI and Behavior Inconsistencies (Vendure 3.5.1)

[wangliminsz]

Summary
In Vendure 3.5.1, the “Use global out-of-stock threshold” checkbox in the Admin UI does not persist correctly after saving, and the local outOfStockThreshold field appears to have no effect even when explicitly set.

Steps to Reproduce
Go to Admin UI → Product Variants → Edit Variant.

Check “Use global out-of-stock threshold” and click Update.

Refresh the page or revisit the variant.

Observe that the checkbox is visually reset to unchecked.

Try setting a local outOfStockThreshold value (e.g. 100) and save.

Observe that the variant still behaves as if the threshold is not applied.

Expected Behavior
The checkbox should remain checked after saving and reflect the actual backend value.

The local outOfStockThreshold should override the global threshold when useGlobalOutOfStockThreshold = false.

Actual Behavior
The checkbox resets visually after save/refresh, even though the global threshold is applied.

The local threshold has no effect, even when trackInventory = true and useGlobalOutOfStockThreshold = false.

Verified via Admin API
graphql
query {
productVariant(id: "variantId") {
trackInventory
stockOnHand
outOfStockThreshold
useGlobalOutOfStockThreshold
}
}
useGlobalOutOfStockThreshold = true is returned correctly.

But the Admin UI does not reflect this state.

Setting outOfStockThreshold manually does not change behavior.

Environment
Vendure version: 3.5.1

Channel: Default

User role: Super Admin

Browser: Chrome (latest)

Screenshots
I can provide screenshots of the Admin UI before and after saving if needed.

Suggested Fix
Ensure the checkbox state is bound to useGlobalOutOfStockThreshold correctly.

Validate that outOfStockThreshold is respected when useGlobalOutOfStockThreshold = false.

[wangliminsz]

I think it's because of user cannot setup "Use global out-of-stock threshold", I found by default it's always true, and the checkbox not works, you cannot setup it to false, I setup it to false by graphql, and the behind logic is correct: the local threshold could take its effect then. so please check the checkbox and the state of the "global out-of-stock threshold", thanks!