dc-stock-split

Allocates scarce DC stock across stores and direct orders before the outbound wave cut-off.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a distribution center holds less of a fast-moving SKU than stores and open customer orders are pulling, someone must decide which nodes get the scarce units before the outbound wave loads. A flat fair-share split starves promo stores that would actually sell the stock, while deciding too slowly means the wave cuts without you. This Skill provides the operating method to size the real shortfall, rank nodes, price allocation options, and gate the committing writes. ## Core Features & Use Cases - Shortfall sizing on available-to-deploy: Computes ATD (on-hand minus allocated, held, damaged, and reserved) rather than raw on-hand, with a freshness rule that re-reads ATD at execute time. - Node ranking and tiering: Scores each store and direct order on days-of-supply, promo/planogram priority, lost-sale risk per unit, and SLA exposure, splitting nodes into protect and general tiers. - Three priced allocation splits: Constructs demand-weighted, protect-promo-plus-SLA, and safety-buffer options, each priced in lost-sale dollars for analyst comparison. - Gated cross-system writes: Holds the WMS wave allocation, OMS direct-order allocation, and deployment-plan commit for human approval, with a bounded protect-tier-only fallback when the wave clock runs out. - Use Case: Overnight replenishment shows DC on-hand covering only 78% of network pull for a promo SKU with the wave cutting in 3 hours; the Skill sizes the gap, protects the promo and SLA nodes, prices three splits, and deploys the approved vector before the cut. ## Quick Start Ask the assistant to split scarce DC stock for a SKU where store replenishment plus open orders exceed available-to-deploy before the outbound wave cut-off.

Frequently Asked Questions about dc-stock-split

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

FAQPage Schema
How do I allocate scarce DC stock across stores before the outbound wave?

Size the shortfall on available-to-deploy rather than raw on-hand, rank nodes by days-of-supply, promo flags, and lost-sale risk, then fill a protect tier first and greedily allocate the remainder. Price three splits in lost-sale dollars and hold the WMS wave write for human approval.

What is available-to-deploy and why not use raw on-hand?

Available-to-deploy equals DC on-hand minus already-allocated, on-hold, damaged, and reserved safety stock. Sizing on raw on-hand under-states the real gap, and ATD drifts during the day, so it must be re-read at execute time before writing the allocation.

How does the skill handle promo stores in a stock allocation?

Live promo or planogram nodes go into the protect tier and are filled to promo forecast or planogram minimum using promo velocity, not baseline. A flat fair-share split that haircuts these nodes is treated as the anti-pattern and priced only to show the dollars it gives away.

What happens if the allocation decision misses the wave cut-off?

A bounded fallback auto-writes a protect-tier-only allocation, filling protect nodes to need while leaving the general tier untouched, with a mandatory logged reason flagged for review. It never holds the whole wave chasing a perfect split.

Can a wave allocation be reversed after it is written to the WMS?

Reversal is free before release and cheap until pick-start by de-allocating the lines. After pick-start, de-allocation unwinds physical work and is treated as destructive, and once shipped it is gone, so the allocation lifecycle state must be known before touching a line.

When should the safety-buffer split be chosen over the protect-promo split?

Choose the safety-buffer option when the on-hand read is shaky, such as a pending cycle count or a recently posted adjustment. It holds back a small percentage of ATD to absorb the surprise at the cost of slightly higher lost sales.