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.

Only push selected SKUs to a store

If you want to limit which SKUs are pushed to a store, you can control it using product listings

1. Click Connections in the left sidebar and select a connection.
2. Switch to the Settings tab, then select Store.
3. In Inventory Settings, enable Use Products for Inventory filtering.
4. Click Save changes.

From now on, DropStream pushes the warehouse levels to this store only when a product with matching SKU has a listing for that store.

See Add or edit a listing on how to create listings.

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.