demand-supply-rebalance

Ranks and prices supply reallocation moves across SKUs sharing a constrained component or line.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a shared component or production line cannot cover total demand across a SKU family, naive pro-rata splits breach firm customer commits and trigger penalty clauses. This Skill turns the scramble into a priced, defensible allocation that protects margin and strategic customers. ## Core Features & Use Cases - Per-SKU gap detection and pegging: Traces the shared constraint across the planning horizon, reconciles planning system vs MRP vs commit book, and classifies gaps as commit, service, or upside. - Value-density ranking: Ranks SKUs by margin and penalty exposure per unit of the scarce resource, handling step, per-unit, and tiered penalty structures deterministically. - Priced rebalancing options: Evaluates reallocate, pull-in, push-out, expedite, safety-stock draw-down, and alternate-component moves against explicit ROI and small-slip thresholds. - Gated execution: Writes the allocation to a reversible planning scenario first, then holds the commit/publish and any expedite PO for human approval. - Use Case: A component constrains a 5-SKU family for 3 weeks with a 15% shortfall; the Skill produces a priority fill that avoids a $150K penalty, protects the high-margin SKU, and rejects a $120K expedite that fails the ROI gate. ## Quick Start Ask the assistant to rebalance constrained supply across a SKU family, for example: our shared component covers only 85% of family demand for the next three weeks, rank the gaps and recommend a split.

Frequently Asked Questions about demand-supply-rebalance

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

FAQPage Schema
How do I allocate constrained supply across multiple SKUs?

Build the constraint peg per SKU, classify each gap as firm commit, service, or forecast, then rank by value density per unit of the scarce resource. Fill safety-stock floors first, allocate surplus to the highest-density SKUs, and let the residual shortfall land on recoverable forecast demand.

When should I expedite a component instead of reallocating supply?

Expedite only when protected value divided by the expedite cost is at least 1.5, using the high end of any premium range. If the residual gap is under roughly 5% of a SKU's demand and falls on low-penalty forecast demand, take the small slip instead.

How are penalty clauses handled in supply allocation ranking?

A step penalty is treated as one indivisible block priced at penalty dollars divided by the constraint units needed to close the commit, ranked against per-unit margin by density. Per-unit penalties add linearly to unit margin, and tiered penalties get one block per tier.

Does this workflow work with SAP IBP or Kinaxis planning systems?

Yes, the constrained plan and peg are read from Kinaxis, SAP IBP, o9, or Blue Yonder, while MRP coverage, on-hand, and purchase orders come from SAP MM. The allocation is written to a reversible scenario first and committed to the baseline only after human approval.

Why not use a simple pro-rata split for supply shortages?

Pro-rata spreads the shortfall evenly, which can breach firm commits and trigger full penalty clauses while starving high-margin SKUs. Value-density ranking concentrates the shortfall on recoverable forecast demand, avoiding penalties and protecting the most valuable demand.

What happens if supply data changes between analysis and commit?

The workflow re-reads the constraint's remaining quantity, on-hand stock, and open orders at the moment of commit because other planners may have consumed the supply. If the figures drifted, the split is re-solved before committing rather than publishing on stale data.