Ecommerce Operations Exception Workorders

Inputs

• - A UTF-8 CSV with one row per date + store_id + sku.
• A policy JSON that defines the lookback window and alert thresholds.
• An optional previous-state JSON used to suppress already-open workorders.
• An optional as_of date. When omitted, the newest date in the CSV is used.

Outputs

• - summary.json: run counts, gate status, and data-quality findings.
• INLINECODE3 and workorders.csv: prioritized evidence and owner queues.
• INLINECODE5: normalized input used for the decision.
• INLINECODE6: open deduplication keys for the next run.

Three-step workflow

1. 1. Validate non-negative metrics and build a weighted historical baseline for each store and SKU.
2. Compare the latest conversion, add-to-cart, refund, ROAS, and stock cover with policy thresholds.
3. Merge related findings into one deterministic workorder, suppress duplicates, and wait for a human decision.

Safety boundary

This skill never logs in to a commerce platform, changes price, adjusts advertising, contacts a customer, or creates a purchase order. It only reads an exported metric table and writes local review artifacts. A human owner must verify source data and approve every business action.

Run

CODEBLOCK0

See README.md and references/operations-playbook.md for field definitions, recovery, and acceptance checks.