forecast-reconciliation

Reconciles customer EDI 830 forecasts against internal plans to separate real demand from noise.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a key customer's forecast (EDI 830 or supplier portal) suddenly jumps while POS sell-through and CRM signals stay flat, planners must decide how much of the step-up to believe before committing supply. Chasing phantom demand triggers costly expedites (around $300K per chased spike), while dismissing a real ramp means missing the program. ## Core Features & Use Cases - Signal decomposition: Normalizes the 830 (cumulative vs discrete, firm vs planning zone), quantifies the gap, and splits it into bias, corroborated new-demand, and one-off residual. - Corroboration scoring: Scores evidence 0-100 across firm-zone commitments, POS trends, CRM programs, and release persistence, then maps the score to a credibility weight for the consensus number. - Priced options and gated writes: Builds accept / dampen / hold options with expedite cost, runs reconciliation in a scenario or what-if version, and holds the baseline commit for human planner approval. - Use Case: A customer's 830 jumps 40% on a platform part three weeks before quarter-end with flat POS and no CRM program. The skill zone-splits the release, scores corroboration at 0, prices all three options, and recommends Hold + confirm instead of committing supply. ## Quick Start Ask the assistant to reconcile the latest customer 830 forecast step-up against the consensus plan and recommend whether to accept, dampen, or hold before committing supply.

Frequently Asked Questions about forecast-reconciliation

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

FAQPage Schema
How do I reconcile a customer EDI 830 forecast with my demand plan?

Normalize the 830 first by converting cumulative quantities to discrete buckets and splitting firm versus planning zones. Then quantify the gap versus plan, decompose it into bias, corroborated demand, and residual, and weight the customer signal by a corroboration score before blending it into the consensus number.

How to tell if a customer forecast step-up is real demand or noise?

Score corroborating evidence: a rising firm-zone or 862 commitment, POS sell-through trending up, a logged CRM program, and persistence across releases all add points. A shrinking firm zone alongside a planning-zone jump is the classic phantom pattern and subtracts points.

Does this workflow support Kinaxis, o9, and SAP IBP?

Yes, the reconciliation runs in a scenario or what-if version and the commit defers to the vendor-specific expertise skill: commit a scenario in Kinaxis, commit a version in o9, or promote a version to baseline in SAP IBP. The baseline write is always gated for human approval.

Why does a cumulative EDI 830 inflate the forecast step-up?

Many 830s send cumulative required quantities rather than per-bucket discrete values. Reading CUM as discrete double-counts prior buckets, so convert with discrete_bucket = CUM_this - CUM_prior - received_to_date before computing any gap.

What happens when a new part has no POS history?

Flat or missing POS on a new platform is absent by design, not disconfirming. The POS points are redistributed to firm-zone and CRM evidence so a missing signal does not force a false reject, and the skill leans on firm-zone commitments and account-team confirmation.

When should I hold the plan instead of accepting a forecast spike?

Hold when the corroboration score falls below 15: no firm-zone rise, flat POS, no CRM program, planning-zone-only step, or a quarter-end timing pattern. Hold for at most two release cycles, request customer confirmation, and escalate if the firm zone rises.