inventory-positioning

Re-segments demand variability and re-solves multi-echelon safety-stock placement across distribution networks.

Updated Aug 17, 2026
One-click install
npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill inventory-positioning-metafloor-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: inventory-positioning
Source: https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai/tree/main/skills/business-workflows/inventory-positioning
Command: npx skills add https://github.com/MetaFloor-AI/metafloor-scm-plugin-openai --skill inventory-positioning-metafloor-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fill rate holds at target but days-of-inventory keeps climbing because safety stock sits in the wrong echelon relative to where demand variability now lives. This Skill re-segments demand variability by SKU-region-channel, re-solves safety stock per node using measured demand correlation, and prices re-positioning options on freed working capital versus service risk. ## Core Features & Use Cases - Multi-echelon re-cut: Computes safety stock per node with σ_DDLT and the correlation-adjusted pooling formula, deciding central vs forward-deployed placement per segment. - Priced options with a human gate: Builds three priced positions (forward-deploy, aggressive central pool, selective top-SKU), stages targets, and holds publish for human approval since publishing re-drives MRP. - Failure-to-recovery playbook: Covers mis-set safety stock, ignored demand correlation, freight eating the saving, variability noise churn, and destructive overwrites of live published targets. - Use Case: Days-of-inventory rose 41 to 49 over three months on a $210M base while fill rate held at 98%. The Skill re-segments store vs e-comm variability, thins smoothed store and DC buffers, pools volatile e-comm at a regional node, and frees roughly $8.5M in working capital at held service. ## Quick Start Ask the assistant to analyze where safety stock should sit across the network given that fill rate is on target but days-of-inventory has climbed for three straight months.

Frequently Asked Questions about inventory-positioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide where to hold safety stock in a multi-echelon network?

Re-segment demand standard deviation by SKU-region-channel on recent actuals, compute σ_DDLT per node, and compare pooling benefit using measured demand correlation. Centralize when correlation is low and lead time still meets service; forward-deploy when volatility is high and service targets are tight.

What is the risk-pooling benefit of centralizing safety stock?

Pooling N nodes with independent demand cuts safety stock by 1/sqrt(N), the square-root law. With correlated demand the benefit shrinks: at correlation near 1 there is no pooling gain, so always compute σ_pool with the measured correlation rather than assuming independence.

Why did days-of-inventory rise while fill rate stayed flat?

This pattern signals a positioning problem, not over-buying: demand variability shifted by channel or region while safety-stock targets stayed static. The fix is re-segmenting variability and re-solving where buffers sit, not cutting order quantities.

When should I not re-position inventory between echelons?

Skip a SKU when the re-cut moves its target under about 5%, when re-position freight exceeds 50% of the annual carrying saving, or when payback exceeds 6 months. Also hold for supply-constrained SKUs, new SKUs with under 13 weeks of history, and perishable stock.

Does publishing new safety-stock targets require approval?

Yes. Staging targets is reversible, but publishing re-drives MRP and deployment downstream, so it is treated as a committing write gated on human approval. Overwriting a live published target that already released procurement is classified as destructive.