Why is ABC-XYZ better than ABC alone, in plain terms?

ABC sorts SKUs by financial impact (annual consumption value). XYZ sorts them by demand variability (coefficient of variation of demand). ABC tells you which items are expensive to mismanage; XYZ tells you which items are predictable. An item can be a high-value A but with wildly erratic demand (AZ), which is the hardest segment to plan. It can also be a cheap C with rock-steady demand (CX), which is the easiest. ABC alone forces planners to treat AZ and AX identically, even though they need opposite replenishment policies. Adding XYZ converts a 3-bucket simplification into a 9-bucket matrix that actually reflects how items behave.

How is variability (the XYZ axis) calculated in dvstock?

dvstock computes the coefficient of variation of demand (standard deviation divided by mean) over a rolling window — usually 12 months for stable industries, 6 months for fast-moving consumer goods or seasonal businesses. SKUs with CV under 0.5 are classified X (predictable), 0.5 to 1.0 are Y (moderately variable), above 1.0 are Z (erratic). The thresholds are configurable per company and can be tuned per product family. Seasonality is deseasonalized before the CV calculation so that a genuinely predictable seasonal item is not mislabeled as Z just because of its summer peak.

How often should segments be recalculated?

Monthly is the right cadence for most industries. Quarterly is enough for stable B2B with long product life cycles; weekly is overkill outside fast fashion or very perishable food. dvstock runs the recalculation as a background job, produces a transition report (which SKUs moved segment and why), and lets the planner review changes before policies update automatically. The single biggest mistake we see is recalculating too often: SKUs ping-pong between segments based on short-term noise, replenishment policies thrash, and trust in the system collapses.

What replenishment policy goes with each segment?

Briefly: AX uses tight reorder points with low safety stock and frequent small orders. AY adds safety stock buffers and forecast-driven planning. AZ requires the highest service-level commitment with built-in slack, often combined with supplier-managed inventory or contractual minimums. BX–BY are continuous review with standard formulas. BZ moves to periodic review with conservative buffers. CX–CY use simple min-max with low review frequency. CZ items are candidates for make-to-order, drop-ship or — sometimes — discontinuation. The article below details each cell.

Can I do ABC-XYZ in standard Business Central without an extension?

Partially. Standard Business Central supports ABC classification through item categories and stockkeeping unit fields, but it is a manual classification — there is no built-in calculation of consumption value rankings or demand variability. You can recreate ABC-XYZ in Power BI on top of BC data, but feeding those classifications back into reorder policies has to be done by hand or with custom code. dvstock adds the native calculation, automatic segment assignment, and policy-per-segment configuration directly inside Business Central, which is what turns the analysis into operational behavior instead of a report nobody acts on.

What kind of inventory reduction is realistic?

Across the dvstock customer base, the typical result at 12 months post-segmentation is a 20 to 30% reduction in average inventory value at the same or better service level. The exact number depends on starting maturity. Customers coming from flat safety-stock policies (everyone gets 2 weeks of cover) see the high end of the range, because they were over-stocking predictable items. Customers already running differentiated policies but without proper segmentation see 10 to 18%. Stockout reduction usually lands at 50 to 75% in the same window. Carrying-cost savings depend on what the company actually counts as carrying cost — many do not include obsolescence, which is where the largest gains often hide.

Volver a dvstock

Logistics

ABC-XYZ Inventory Segmentation in Business Central

ABC-XYZ matrix for inventory in Business Central with dvstock: 9 segments, real policies, and 20-30% stock reduction at same service level.

7 min

ABC-XYZ inventory segmentation matrix in Microsoft Dynamics 365 Business Central with dvstock

ABC-XYZ inventory segmentation on Microsoft Dynamics 365 Business Central with dvstock, deployed by Davisa — Microsoft Solutions Partner for Business Central since 2003

Every inventory planner has done an ABC analysis at some point. Most have done one, looked at the output, agreed that the A items deserve more attention, and then quietly gone back to flat replenishment policies because there was no practical way to act on the classification. The analysis without the operating model is theater.

ABC-XYZ fixes that. It pairs the financial axis (ABC) with a variability axis (XYZ), produces nine actionable segments instead of three abstract ones, and — when you wire it into the replenishment engine — actually changes how stock behaves. This article walks through the matrix, the policies per segment, the gap in standard Business Central, and the realistic numbers you should expect.

REQUEST A DVSTOCK DEMO

Why ABC alone is not enough

ABC classifies items by annual consumption value. A items typically carry 70–80% of value with 10–20% of SKUs; B is the middle 15–20%; C is the long tail of 50–70% of the catalog.

The blind spot is variability. Two A items with identical annual consumption can behave completely differently:

Item A1: 1,000 units/month, every month, ±50 units. Easy to plan, low safety stock, predictable supplier relationship.
Item A2: 1,000 units/month on average, but 200 some months and 3,500 others. Stocking the average leaves you out half the time; stocking the peak ties up cash.

ABC tells you both are A and “give them more attention.” That is a category label, not a policy.

The same problem exists at the bottom. A C item with predictable demand needs almost no attention: simple min-max works forever. A C item with erratic demand needs make-to-order, drop-ship or obsolescence monitoring. ABC lumps them together as “low-value, deprioritize.”

XYZ separates them. That is the entire value of the second axis.

The 9 segments of ABC-XYZ matrix

Combining the two axes produces a 3×3 grid. Each cell has a distinct profile:

	X — predictable	Y — moderate variability	Z — erratic
A — high value	AX: high attention, low buffer	AY: high attention, moderate buffer	AZ: highest attention, highest buffer
B — medium value	BX: standard policy, low buffer	BY: standard policy, moderate buffer	BZ: standard policy, conservative buffer
C — low value	CX: light-touch min-max	CY: light-touch min-max with review	CZ: candidate for MTO or discontinuation

The four corners are the most useful to internalize:

AX is the dream segment. High value, perfectly predictable. JIT works, safety stock is minimal, supplier integration pays off.
AZ is the hardest. High value, unpredictable demand. The answer combines demand sensing, contractual supplier flexibility, and explicit acceptance of slightly higher stock-outs on the worst Z items.
CX is the boring win. Cheap, predictable, automatable. Simple min-max, quarterly review, never touch again.
CZ is the cleanup pile. Cheap, erratic — where dead stock accumulates. Move to make-to-order, drop-ship, or rationalize out of the catalog.

The middle cells (BX, BY, BZ, CY, AY) get standard policies with different safety-stock multipliers. They are the bulk of the catalog and rarely the source of major value creation — but consistent treatment frees planner attention for the corner cases.

Replenishment policies per segment (AX vs CZ vs AZ)

Policy recommendations from real dvstock rollouts:

AX — Just-in-time, low safety stock. Reorder point at lead-time demand plus 0.5–1.0 lead-time standard deviations. Daily or weekly review. Tight supplier collaboration, ideally VMI or scheduling agreement. Service level 98–99%.

AY — Forecast-driven, moderate buffer. Statistical forecasting (Holt-Winters) drives replenishment. Safety stock at 1.5–2.0 standard deviations. Weekly review. Service level 97–98%.

AZ — High buffer with demand sensing. Safety stock at 2.5–3.5 standard deviations. Continuous review. Combined with supplier-side flexibility (call-off contracts, expediting). Demand sensing — promotions calendars, customer order patterns, early CRM signals — outperforms pure statistical forecasting. Service level 96–98%, accepting that the last points cost disproportionately.

BX / BY / BZ — Standard continuous review. Reorder-point logic with safety stock scaled by variability. The middle of the matrix is where standard formulas earn their keep.

CX — Min-max, quarterly review. Two-bin systems or simple reorder points. Almost zero planner attention. Order multiples sized for purchasing convenience.

CY — Min-max with periodic review. Like CX but semi-annual review to catch slow degradation. Many obsolete-stock incidents start as CX items that quietly became CY without anyone noticing.

CZ — Make-to-order, drop-ship, or rationalize. Stocking erratic low-value items is almost always a net loss. Sell on order with longer lead time, drop-ship from the supplier, or accept they are loss leaders and price accordingly.

For broader context, see dvstock versus Slimstock for Business Central and the dvstock inventory optimization overview.

Native BC limitations + how dvstock extends

Standard Business Central has the building blocks — reorder points, safety stock fields, reordering policies, planning worksheets — but no native ABC-XYZ classification or segment-driven policy application:

No built-in ranking. Item categories are manual; no system-calculated ABC based on actual consumption value over a configurable window.
No variability calculation. Coefficient of variation is not a standard field.
No segment-to-policy binding. Even with external classification, BC cannot apply “for all AX items, this policy template” without custom code.
No transition tracking. When an item shifts from AY to AZ next quarter, the policy does not follow automatically.

dvstock adds exactly these layers: calculated ABC ranking on a configurable window; XYZ via rolling-window coefficient of variation with optional seasonality decomposition; policy templates assigned per segment and applied automatically on membership change; a monthly transition report for planner review; planning worksheet integration so PO proposals already reflect segment-aware logic.

The key word is “automatic.” Without dvstock, you can analyze in Power BI and update items by hand, but in any catalog over a few hundred SKUs that work is never done consistently — and the moment it stops, the model decays.

Implementation: from Excel-segmented to dynamic auto-segmentation

A typical dvstock segmentation rollout has three phases:

Phase 1 — Baseline analysis (weeks 1–3). dvstock runs the initial ABC-XYZ on 12 months of history. Planners review the segment distribution — for most B2B industrial customers, AX is small (5–10% of SKUs, 30–40% of value), CZ is large by SKU count, and BY/BZ is where most catalog mass lives. Anomalies are flagged: broken history, recently launched SKUs, items distorted by one-time large orders.

Phase 2 — Policy design (weeks 4–6). Replenishment policies defined per segment with planners. Service-level targets explicitly assigned. Safety-stock multipliers calibrated against historical stockout incidents, not textbook formulas. Customer tolerance for stockouts on Z items is negotiated honestly; promising 99% on AZ is the fastest path to losing project credibility.

Phase 3 — Operational handover (weeks 7–10). Automated monthly recalculation. Transition reports routed to planners. Planning worksheet integration. KPI dashboards: segment distribution, stock value per segment, service level per segment. Training focuses on exception handling, not on running the analysis manually.

In ten weeks the team moves from spreadsheet segmentation reviewed twice a year to dynamic monthly segmentation that drives replenishment automatically.

Real numbers: 20-30% inventory reduction at same service level

What customers see twelve months after a clean dvstock segmentation rollout:

Average inventory value: down 20–30% at the same or better aggregate service level.
Stockouts on A items: down 50–75%, because attention concentrates where it matters.
Obsolete-stock write-offs: down 30–50%, mostly from cleaning up the CZ tail.
Planner time: redistributed, not reduced. Less routine PO work, more AY/AZ exception handling. Quality of attention dramatically improved.
Working capital: for a €15M inventory base, a 25% reduction is €3.75M of cash freed. At 6% cost of capital that is €225k/year, before warehousing, insurance and obsolescence savings.

These are not brochure ranges; they are what shows up at the 12-month mark. Customers running flat safety-stock policies see the high end. Customers already doing partial segmentation see the lower end but cleaner service-level gains.

ABC-XYZ is not new science — the 1960s textbooks already had the math. What changed in 2026 is that Business Central plus dvstock make it cheap to apply that math continuously. The edge is no longer in knowing the technique — it is in using it.