Inventory Value by Warehouse, Microsoft Dynamics 365

Inventory Value by Warehouse breaks down on-hand stock value at cost across every warehouse and legal entity. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Ecommerce Platform

On-hand inventory value at cost, split per warehouse and site across every legal entity, so you can see where stock is concentrated.

At a glance

The current value of on-hand inventory, valued at cost, broken out per warehouse / site. In Finance & Operations this is the sum of on-hand quantities times the costing-method unit cost across each Warehouse (and its Sites), rolled up per legal entity. The card surfaces concentration and imbalance: which distribution centre holds the most working capital, and which sites are over or under stocked relative to demand.

What it counts	On-hand inventory value at cost per warehouse. Conceptually SUM(on-hand quantity x unit cost) grouped by Warehouse / Site. In F&O this draws on the inventory transaction layer (the InventTrans / on-hand store, exposing the AvailablePhysical concept) and the active costing method (standard, FIFO, weighted average, or moving average) per item. In Business Central the equivalent is Item Ledger Entry plus Value Entry summed by Location.
Costing basis	At cost, not retail. The valuation uses the item’s configured costing method per legal entity. Standard-cost items value at the frozen standard; FIFO and average items value at the running ledger cost. Retail / list price is never used here.
Currency	Per-warehouse values report in each legal entity’s accounting currency, then consolidate to the dashboard reporting currency using the period FX rate. Multi-entity setups with warehouses in different currencies are translated before the bar chart renders.
Multi-Company / legal entity	Card respects the selected legal-entity (Company) filter. By default it rolls up every entity the connected Azure AD identity can see, so a single bar chart can span warehouses across UK, US, and EU entities.
Time window	RT (real time, current on-hand snapshot)
Alert trigger	Not applicable. This is a descriptive breakdown card with no drop / spike alert.
Roles	owner, operations, finance

Calculation

Calculated automatically from your Microsoft Dynamics 365 data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A UK home-and-garden brand running Finance & Operations across two legal entities (UK Retail Ltd in GBP, EU DTC BV in EUR) with five physical warehouses. The snapshot is taken 18 Mar 26. Reporting currency is GBP. All values are at cost.

Warehouse	Legal entity	On-hand value (local)	FX	GBP equivalent	Share
MAIN-DC (Birmingham)	UK Retail Ltd	£1,840,000	1.0000	£1,840,000	48.1%
NORTH-DC (Leeds)	UK Retail Ltd	£760,000	1.0000	£760,000	19.9%
RETAIL-STORES (pooled)	UK Retail Ltd	£312,000	1.0000	£312,000	8.2%
EU-DC (Rotterdam)	EU DTC BV	€690,000	0.8540	£589,260	15.4%
RETURNS-WH (quarantine)	UK Retail Ltd	£323,000	1.0000	£323,000	8.4%
Total on-hand value				£3,824,260	100%

Four things to notice:

1. Almost half the working capital sits in one DC. MAIN-DC holds 48.1% of all stock value. That concentration is normal for a hub-and-spoke network, but it also means a single-site disruption (a flood, a WMS outage, a stock-take freeze) puts nearly half the inventory off-line. Pair this with Inventory Aging to check that the hub stock is actually moving.
2. RETURNS-WH is holding £323,000 at full cost. Quarantine and returns warehouses often value at full standard cost even though much of the stock is impaired or destined for liquidation. That is 8.4% of working capital potentially locked in stock that will sell at a markdown. This is the kind of finding Dead Stock Value escalates.
3. The EU-DC value moves with FX even when units do not. Rotterdam holds €690,000. At the 18 Mar 26 rate that is £589,260; a 3% euro move shifts the GBP figure by ~£17,700 with zero change in physical stock. When the bar chart wobbles week to week, check whether it is a unit change or an FX translation effect.
4. RETAIL-STORES is a pooled site, not a single building. Where F&O pools many small store locations under one logical warehouse, the bar lumps them together. To see per-store detail the merchant drills into the underlying Sites. The headline single-number version of this whole picture lives on On-Hand Inventory Value (by Warehouse).

Sibling cards merchants should reference together

Inventory Value by Warehouse tells you where stock value sits. Pair it with these to understand whether that distribution is healthy.

Card	Why pair it with Inventory Value by Warehouse
On-Hand Inventory Value (by Warehouse)	The executive single-number headline of this same data. This card is the bar breakdown; that card is the one KPI tile. Read them together for the total plus the per-site split.
Total Inventory Value	The all-warehouse total without the per-site cut. Use it to sanity-check that the bars in this card sum to the company-wide figure.
Top SKUs by Value	Drills from “which warehouse” to “which item”. A concentrated warehouse usually maps to a handful of high-value SKUs.
Inventory Carrying Cost	Turns stock value into a cash cost. The warehouse holding the most value is also the one costing the most to carry.
Inventory Aging	Tells you whether the value in each warehouse is fresh or stale. High value plus old age in the same site is a markdown risk.

Reconciling against Microsoft Dynamics 365

Where to look in Business Central / Finance & Operations:

The closest native equivalents in the Dynamics UI are:

F&O > Inventory management > Inquiries and reports > On-hand inventory (filter or group by Warehouse / Site) F&O > Cost management > Inventory accounting > Inventory value report (the audit-grade valuation, run per dimension) Business Central > Inventory > Item Availability by Location (the BC equivalent, grouped by Location) Business Central > Reports > Inventory Valuation (BC’s costed valuation report)

When you run the F&O Inventory value report grouped by warehouse for the same snapshot date, the per-warehouse subtotals should match this card to within rounding, provided you select the same legal entities and the same costing date. For BC, the Inventory Valuation report filtered by Location is the audit reference.

Common mistakes when comparing against the native reports:

• Physical vs financial on-hand. On-hand inventory inquiries show AvailablePhysical, which can differ from the financially updated quantity when receipts or issues are physically posted but not yet financially posted. The Inventory value report uses the financial layer. Small timing gaps are normal.
• Costing date matters. The Inventory value report values as of a chosen date. If you run it for a different date than the card snapshot, recent receipts at different costs will move the number.
• Quarantine, transit, and blocked warehouses. Some native views exclude non-nettable or transit warehouses by default. This card includes every warehouse unless you filter it out, so transit stock can make the card read higher than a default report.

Why our number may legitimately differ:

Reason	Direction	Why
Physical vs financial posting lag	Either	The card reads the current on-hand layer; the F&O Inventory value report uses financially updated cost. A receipt posted physically but not financially shows in one and not the other until the inventory close or recalculation runs.
Costing recalculation not yet run	Card may be higher or lower	FIFO and average-cost items settle their true cost at inventory close. Between closes the running cost is an estimate, so the card can drift from the post-close valuation.
Local vs reporting currency	Either	The card translates each entity to the reporting currency at the period FX rate. A native report run in a single entity’s accounting currency will differ by the FX translation. Run both at the same scope.
Warehouse inclusion filters	Card usually higher	Native reports often exclude transit / quarantine / non-nettable warehouses by default. This card includes all warehouses unless filtered.
Sync cache lag	Card up to a few minutes behind	Vortex IQ reads the on-hand layer on a short cache. A just-posted movement can appear in F&O before the card refreshes.

Cross-connector note: This card values stock as F&O / BC sees it, the system of record. Your commerce platform’s “inventory” number reflects only the sellable quantity it has been told about, which can lag the ERP. Where they disagree at the SKU level, the ERP-vs-Ecom Inventory Variance % gauge is the place to start.

Known limitations / merchant FAQs

Is this at cost or at retail? At cost. The valuation uses the item’s configured costing method per legal entity (standard, FIFO, weighted average, or moving average). Retail or list price is never used. If you want a sellable-value view, that is a different question and a different card.

Why does a warehouse value change when no stock moved? Two reasons. First, FX: warehouses in non-reporting currencies are translated at the period rate, so a currency move shifts the GBP / USD figure with no physical change. Second, costing: FIFO and average-cost items revalue as new receipts post at different unit costs, and they settle fully at inventory close. The physical count can be flat while the value moves.

Does this include in-transit and quarantine warehouses? Yes, unless you filter them out. Transit warehouses (stock moving between sites) and quarantine / returns warehouses are included by default, which is why this card can read higher than a native report that excludes non-nettable locations. If you only want sellable-location value, apply a warehouse filter.

How does this differ from On-Hand Inventory Value (by Warehouse)? That card is the executive single-number headline; this card is the per-warehouse bar breakdown of the same underlying data. They are designed to be read together: the tile for the total, this chart for the distribution.

What happens with negative on-hand? If a warehouse has gone negative on-hand (issues posted ahead of receipts), that line can value negative and drag the warehouse total down. Persistent negatives are a data-quality signal, not a real valuation, and are tracked on Inventory On-Hand Went Negative (any warehouse).

Does it respect my dimension and financial dimension structure? The grouping is by Warehouse / Site, the physical inventory dimension. If you need value by financial dimension (business unit, brand, cost centre), that is a separate cut. This card is deliberately warehouse-shaped because the operational question is “where is my stock”, not “which P&L line owns it”.

Single-entity accounts: does it behave differently? Same logic, simpler scope. A single legal entity skips the FX translation and consolidation steps, and every bar is in the local accounting currency.

---

Tracked live in Vortex IQ Nerve Centre

Inventory Value by Warehouse is one of hundreds of KPI pulses Vortex IQ tracks across Microsoft Dynamics 365 and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.