cycle-count-triage

Triage cycle-count discrepancies against WMS and ERP on-hand to auto-post, recount, or escalate variances.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Daily cycle counts routinely disagree with system on-hand across dozens of locations, and treating every gap the same either floods planners with noise or lets real losses quietly corrupt available-to-promise (ATP) and replenishment. This Skill separates tolerance noise from material variances, traces each gap to a likely cause, and decides whether to auto-post, recount, or escalate with an availability hold. ## Core Features & Use Cases - Tolerance-based classification: Applies percent, value, and ATP-criticality bands (with zero/negative on-hand guards) to split noise from real variance. - Cause tracing and disposition: Maps variance signatures (offsetting pairs, short-picks, unscanned returns, LPN mis-scans) to bin-to-bin transfers, adjustments, recounts, or process fixes. - Gated writes with idempotency: Auto-posts only within the planner's post limit, mirrors every WMS adjustment with its ERP variance posting, holds phantom ATP quantities, and checks for duplicate postings before any write. - Use Case: A day's cycle count posts 34 discrepancies including a $9,000 shortfall on a fast-moving SKU; the Skill auto-posts the 31 in-limit lines, tasks 2 recounts, and escalates the $9K line with a 300-unit availability hold instead of clearing it as a rounding fix. ## Quick Start Triage today's posted cycle-count discrepancies and tell me which lines to auto-post, recount, or escalate with an availability hold.

Frequently Asked Questions about cycle-count-triage

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

FAQPage Schema
How do I triage cycle count discrepancies in a warehouse?

Classify each posted discrepancy against three bands: percent variance, absolute value, and ATP criticality. Lines clearing all bands auto-post as in-tolerance corrections; material lines are traced to a cause and disposed as auto-post, recount, or escalate with an availability hold.

When should a cycle count variance be auto-posted vs escalated?

Auto-post only when the variance is within the planner's post limit, the cause is confirmed, and the SKU is not ATP-critical. Escalate with an availability hold when the value exceeds the post limit, correcting on-hand would break committed demand, or the cause is unconfirmed.

How does a cycle count variance affect available-to-promise?

A downward variance on a fast SKU with thin coverage can make the system promise stock that is not on the shelf. The Skill computes atp_at_risk from open demand minus uncommitted corrected on-hand and holds the phantom quantity from the available pool until resolved.

Why do WMS and SAP on-hand quantities disagree after a count?

WMS holds operational on-hand while SAP holds valuation, and a posted adjustment can land on one side without its mirrored variance posting. The Skill verifies the ERP leg landed for every WMS adjustment and escalates unmirrored pairs rather than adjusting one side to force a match.

What causes repeated cycle count variances at the same location?

Repeating variances at the same SKU or location signal a systematic fault such as slotting errors, label problems, or scanner dead zones, not a record error. The Skill routes these to a process fix and tighter count cadence instead of repeatedly clearing adjustments.