Claude-Skills/shared/delay-processor/SKILL.md

name, description

name

description

delay-processor

Daily delay list processing skill for the traffic team. Fetches the delay list via API, categorizes orders, auto-snoozes packaged orders from known suppliers, sends bundled supplier emails, notifies customers, logs complaints, and updates tracking. Use this skill whenever the user mentions: delay list, delayed orders, dispatch delays, snooze orders, supplier outreach, delay processing, traffic team workflow, daily delays, or order not shipped. Also trigger when the user asks to process delays or check today's delays.

Delay Processor — Daily Traffic Team Workflow

Overview

Each day, orders that have surpassed their expected dispatch date appear on the delay list — whether still in production or packaged. This skill processes that list systematically: auto-snoozing where safe, emailing suppliers (bundled per supplier), notifying customers, logging complaints, and flagging edge cases for human review.

Scale: ~4,000 orders/day, delay list can be extensive.

---

Inputs

1. Delay List — Fetched via the n8n-mcp delaylist workflow. It returns the current delay list with the following fields per order:

   • Order (order number)
   • id_order_detail (order line ID)
   • Assigned (team member or blank)
   • Status (Open, Customer Informed, Checking, etc.)
   • Delay Reason (No delay reason given, Email Sent to Supplier, etc.)
   • New Target Dispatch (updated date if any)
   • Product (product type/SKU)
   • Supplier (supplier name)
   • Sales Price
   • State (production/packaging state)
   • Delay (days past target dispatch)
   • Carrier (carrier name if available)
   • Tracking Link (if available)
   • Target Dispatch Date
   • Actual Dispatched Date
   • Latest Delivery Date

2. Operator context — Any special notes for the day (supplier outages, holidays, known issues).

3. Supplier Complaint Classification Spreadsheet — Reference for whether a supplier is volume-based (zero cost complaint) or discount-based (10% discount complaint). Read from references/supplier-classification.md if available.

---

Processing Workflow — Execution Order

Process in this exact order to ensure data is fresh for downstream decisions:

Step 1: Fetch & Validate the Delay List

• Fetched via the n8n-mcp delaylist workflow.
• Validate expected fields are present in the API response
• Flag any records with missing critical data (Order, Supplier, State) for MANUAL_REVIEW
• Calculate correct delay days: business days between Target Dispatch Date and today (note: the system's built-in delay count can be incorrect)

Step 2: Auto-Snooze Packaged Orders (High Confidence)

Criteria — ALL must match:

Field	Required Value
State	Your order has been packaged
Target Dispatch Date	Previous working day
Carrier	One of: UPS-UPS_STANDARD, UPS-UPS_SAVER, DPDINT-STANDARD_UK, DPDINT-STANDARD
Tracking Link	Must be present (non-empty)
Supplier	One of the approved auto-snooze suppliers (see list below)

Approved Auto-Snooze Suppliers:

• De Groot Drukkerij B.V.
• The Postermen
• Intervlag
• Vila Etiketten
• VG Print BV
• Zalsman BV
• Oakdene Services
• I print 1925
• Digiforce
• Enson
• Probo
• Promio
• Inpromo
• Today's Media
• Pressing
• Drukkerij Van As

Action: Write down which orders to snooze for 12 hours.

Confidence: If ALL criteria match exactly → auto-execute (99%+ confidence). If any field is ambiguous or missing → MANUAL_REVIEW.

Action: If you want to snooze an order call n8n-mcp snooze-order workflow. with a body like this:

• id_order: %order_id%
• id_order_detail: %id_orderdetail%
• status: %status%
• assigned: %assigned%