How to Bulk Edit Inventory Policy in Shopify
To bulk edit inventory policy in Shopify, open the bulk editor from the Products page, then switch its view from Products to Variants at the top of the grid. Inventory policy isn’t a product field: it lives on each variant, so the Products view won’t show it no matter which columns you add. Once you’re in the Variants view, add the “Continue selling when out of stock” column from the column picker, then check or uncheck it per row, or set one row correctly and paste that value down the rest of your selection.
Why this setting lives on the variant, not the product
Every variant, even the single default variant a simple product gets automatically, carries its own inventory record: quantity tracked, quantity on hand, and a policy for what happens when that quantity reaches zero. A product with three sizes has three separate policy settings, one per variant, and there’s no product-wide switch that sets all three at once outside the bulk editor. That’s also why the Products page selection toolbar, which handles product-level fields like status and tags in one click, has nothing for this field. Shopify has to hand you the variant grid for anything that lives at the variant level.
Filtering before you switch views
Build your filter on the Products page the same way you would for any bulk edit: by tag, vendor, product type, or collection. Select the matching products, then open the bulk editor. The view toggle sits near the top of the grid, usually labeled “Editing products” with a dropdown to switch to “Editing variants.” Switching pulls in every variant belonging to your selected products, which can be a much longer list than the product count if your catalog has size or color options. Confirm the row count in the variants view lines up with what you expected before touching the column, since a filter that looked tight at the product level can expand fast once every variant lands as its own row.
What continue selling when out of stock actually does
Shopify offers two policy values: deny, which stops a variant from being added to a cart once its tracked quantity hits zero, and continue, which lets checkout proceed anyway. Continue is the setting behind backorders and preorders: a store selling a book before its release date, or a made-to-order item with no real ceiling, wants continue so a zero count doesn’t block sales. Deny is the safer default for anything with a hard supply limit, since it’s what actually stops a shopper from buying stock you don’t have. The two values only matter for variants where quantity tracking is turned on; a variant with tracking off never reaches a real zero, so its policy setting sits unused.
Where this collides with multi-location stock
Continue selling when out of stock is set once per variant. It applies across every location that stocks the variant, never location by location. Picture a variant sitting at three warehouses: once the combined count across all three drops to zero, a policy of continue keeps accepting orders no matter which location would have shipped it, and a policy of deny blocks new orders even if one location still has a unit sitting in a bin nobody counted correctly. Bulk-setting this field without checking which variants carry multi-location stock can turn on backorder behavior for items your fulfillment team thought had a firm ceiling.
The failure mode to watch for
Someone builds a filter to catch “preorder” or “made to order” tagged products and sets them all to continue. Fine, until that same filter also snags a few items missing the tag, or a later batch reuses a selection that was scoped for something else. Deny-only stock quietly becomes backorderable, and nobody notices until a customer places an order for something that was never going to ship. The bulk editor grid gives no summary of how many rows moved from one value to the other. The only real check afterward is filtering by policy value, comparing the count against what you expected, and opening a few variant pages to confirm.
Where a preview would have caught this
SafeBulk treats inventory policy as one of its bulk-editable fields, alongside price, tags, status, vendor, and product type. Before a job runs, it lays out the current and proposed policy for every variant in the batch, so an oversized filter shows up on screen instead of in a customer’s cart. Every job also gets an automatic pre-job snapshot, and a policy change that reached the wrong variants can be rolled back with one click. SafeBulk reverses edits that SafeBulk made. It cannot restore products or variants you deleted through Shopify itself, or changes made by other apps: those never pass through our snapshot. That distinction matters here specifically because there is no undo for a sale that already went through. A preview only helps with the mistake that happens before checkout opens, not the one that happens after.
Switch to the variants view on purpose rather than by accident, and treat the row count as a checkpoint rather than a formality. Bulk editing vendor in Shopify walks through the same filter discipline for a product-level field, if that habit needs reinforcing elsewhere in your workflow. Stock-affecting batches are also a good moment to glance at what to export before running a bulk edit, since inventory policy changes are harder to reconstruct from memory than a tag. For the broader question of which app to run these edits in, SafeBulk stacked up against Ablestar, and the SafeBulk listing is live on the Shopify App Store if a before-you-save preview is the deciding factor.
FAQ
What’s the difference between inventory policy and Track quantity in Shopify?
Track quantity decides whether Shopify counts stock for a variant at all. Inventory policy (continue or deny) only matters once tracking is on, since it decides what happens at checkout after that count hits zero. Turn tracking off and the policy setting has nothing to act on.
Does bulk editing inventory policy affect orders already placed?
No. Inventory policy only governs checkout behavior going forward. Orders placed before the change keep whatever line items and stock deductions they already recorded, and reserved stock from open orders is untouched by a policy switch.
Is there a toolbar shortcut for bulk editing inventory policy in Shopify?
No. The Products page selection toolbar has quick actions for tags, status, and sales channels, all product-level fields. Inventory policy lives on the variant, so changing it in bulk means opening the bulk editor grid, switching it to the Variants view, and editing the column there.
Can continuing to sell out of stock cause overselling across multiple locations?
Yes. Continue selling when out of stock applies to the variant as a whole, not to any one location. If your combined stock across every location hits zero and the policy is set to continue, Shopify keeps accepting orders regardless of which location a customer’s order would ship from.
Frequently asked questions
What's the difference between inventory policy and Track quantity in Shopify?
Track quantity decides whether Shopify counts stock for a variant at all. Inventory policy (continue or deny) only matters once tracking is on, since it decides what happens at checkout after that count hits zero. Turn tracking off and the policy setting has nothing to act on.
Does bulk editing inventory policy affect orders already placed?
No. Inventory policy only governs checkout behavior going forward. Orders placed before the change keep whatever line items and stock deductions they already recorded, and reserved stock from open orders is untouched by a policy switch.
Is there a toolbar shortcut for bulk editing inventory policy in Shopify?
No. The Products page selection toolbar has quick actions for tags, status, and sales channels, all product-level fields. Inventory policy lives on the variant, so changing it in bulk means opening the bulk editor grid, switching it to the Variants view, and editing the column there.
Can continuing to sell out of stock cause overselling across multiple locations?
Yes. Continue selling when out of stock applies to the variant as a whole, not to any one location. If your combined stock across every location hits zero and the policy is set to continue, Shopify keeps accepting orders regardless of which location a customer's order would ship from.