Limit Inventory Updates per Store

DropStream has two ways to control which inventory ends up on which store. Which one to use depends on whether you’re keeping the SKU off the channel entirely or just shaping the quantity pushed.

Keep a SKU off a store entirely

Inventory pushes are driven by listings: DropStream pushes the warehouse level for a SKU to every store that lists it. To stop pushing a SKU to a particular store, remove its listing on that store.

1. Open the master product in Products → Catalog, click Actions → Edit.
2. Switch to the Listings tab.
3. Disable the toggle for the store you no longer want to push to. Save.

You can also delete the listing outright from Products → Listings if you don’t expect to bring it back. Removing a listing stops DropStream from sending further inventory updates for that SKU to that store; existing levels on the channel are unchanged.

For SKUs without a listing, DropStream pushes the warehouse SKU as-is to every store the connection is enabled on. If you want to push the SKU to some stores but not others, you need to either create a listing per store you do want to push to (and rely on the absence of a listing elsewhere — depending on the platform integration), or use Inventory Partitioning.

Shape the quantity pushed per store

When you want to push a SKU to several stores but allocate different portions of the warehouse stock to each — to hold back safety stock, give priority to a channel, or distribute equally — use Inventory Partitioning instead.

From the left sidebar, Automation → Inventory Partitioning opens the Partitioning Strategies list. A strategy is configured per merchant and warehouse, applies to all SKUs in scope, and decides how the warehouse’s available stock is split among the connected stores before being pushed.

Available strategy types include Safety Stock — hold back a configurable buffer and distribute the rest across stores — with Percentage, Fixed Quantity, and Waterfall types in development.

See About Inventory Partitioning for an overview of all strategy types and how partitioning fits into the inventory flow.

Each merchant/warehouse pair has at most one active strategy; turning a strategy on changes what DropStream pushes on the next inventory sync.

What changed from the old filter UI

Older versions of DropStream had a per-SKU filter list on the Inventory page for blocking inventory exports to specific stores. That UI has been replaced by the listing-based approach above (which makes the relationship explicit on the product) and Inventory Partitioning (for quantity shaping). The new model is more accurate — DropStream now pushes inventory because a listing connects a SKU to a store, rather than pushing by default and filtering out exceptions.