Locations & multi-location math

When you have one location, the forecast math is simple: one variant, one set of numbers. When you have multiple locations, the location picker in the toolbar changes how the simulation runs — across two independent axes. This page explains both.

The two axes — inventory scope and demand scope

The location picker has two settings that work together:

Inventory scope — which locations’ on-hand and incoming feed the simulation. Default: all locations.
Demand scope — which locations’ sales history feeds the forecast model. Default: matches inventory scope.

By default, both axes move together. When you select one location, both inventory and demand are scoped to it. The Global demand toggle (below) decouples the two — useful for warehouse setups where one location physically holds stock for demand that originated elsewhere.

Picking a single (or subset of) location(s)

Use the location dropdown in the toolbar and check the location(s) you want. The page recomputes within a second or two. Things that change:

Inventory Quantity — sums the available quantity at the selected location(s) (Shopify’s available bucket — on-hand minus committed). When all locations are selected, the column reverts to the variant’s on-hand across everywhere.
Incoming columns — only count POs and TOs heading to the selected location(s).
Reorder Point, Reorder Date, Reorder Quantity — the simulation runs against the selected-location subset.
Days of Stock — same simulation, scoped to the selection.
Sales / demand — by default, also scoped to the selected location(s)’ order history. Flip Global demand on if you want demand to stay global.

The Global demand toggle

Inside the location picker (visible only when you’ve filtered to fewer than all locations), there’s a Global demand switch.

Off (default): both inventory and demand are scoped to the selected location(s). Forecasts are local to those locations’ sales history.
On: inventory stays scoped to the selected location(s), but demand and sales data are pulled from all locations. Useful when one warehouse fulfills orders generated across regions you logically share — the demand signal lives at the catalog level, not the warehouse level.

Variant overrides per location

Min / Max / Target / Static Reorder Point can be configured per location. With All locations selected, Logistified shows the smallest value across locations — useful for spotting the bottleneck. With a single location selected, it shows the value configured for that location specifically.

To set per-location overrides, go to Settings → Products → Variant Constants.

What stays the same

Regardless of the location filter:

The choice of forecast model and the supplier-link inputs — lead time, MOQ, pack size, cost — don’t change per location.
Variant-constant cross-field validation rules (Min ≤ ROP ≤ Target ≤ Max) apply per location.

What does change: which sales history feeds the model — unless you flip Global demand on, in which case demand stays global while inventory becomes per-location.