Shopify Admin High Risk Order Tagger

Purpose

Queries recent high-risk orders and takes two protective actions: tags the order for staff visibility and optionally places a fulfillment hold to prevent the order from shipping until reviewed. Complements order-risk-report (which only reads) with write actions that create a reviewable queue.

Prerequisites

• Authenticated Shopify CLI session: shopify store auth --store --scopes read_orders,write_orders,write_fulfillments
• API scopes: read_orders, write_orders, write_fulfillments

Parameters

| Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | store | string | yes | — | Store domain (e.g., mystore.myshopify.com) | | daysback | integer | no | 1 | Lookback window (default: last 24 hours) | | minordervalue | float | no | 0 | Only flag orders above this value | | tag | string | no | fraud-review | Tag applied to flagged orders | | holdfulfillment | bool | no | true | Also place a fulfillment hold on flagged orders | | holdreason | string | no | UNKNOWNPAYMENTRISK | Fulfillment hold reason | | dryrun | bool | no | true | Preview without executing mutations | | format | string | no | human | Output format: human or json |

Safety

> ⚠️ fulfillmentOrderHold prevents orders from being fulfilled until the hold is explicitly released. Customers will experience a shipping delay while on hold. Use hold_fulfillment: false if you only want to tag without blocking fulfillment. Run with dry_run: true to confirm the order list before committing. Release holds with the order-hold-and-release skill after review.

Workflow Steps

1. OPERATION: orders — query

Inputs: query: "risk_level:high created_at:>=''", first: 250, select riskLevel, fulfillmentOrders, totalPriceSet Expected output: High-risk orders in window

1. OPERATION: tagsAdd — mutation

Inputs: Order id, tags: [] Expected output: Updated order tags; userErrors

1. OPERATION: fulfillmentOrderHold — mutation (if hold_fulfillment: true)

Inputs: fulfillmentOrderId, reason: , reasonNotes: "High-risk order — awaiting fraud review" Expected output: heldFulfillmentOrder { id, status }, userErrors

GraphQL Operations

# orders:query — validated against api_version 2025-01
query HighRiskOrders($query: String!, $after: String) {
  orders(first: 250, after: $after, query: $query) {
    edges {
      node {
        id
        name
        riskLevel
        totalPriceSet {
          shopMoney {
            amount
            currencyCode
          }
        }
        tags
        fulfillmentOrders(first: 5) {
          edges {
            node {
              id
              status
            }
          }
        }
        customer {
          id
          displayName
          numberOfOrders
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

# tagsAdd:mutation — validated against api_version 2025-01
mutation TagsAdd($id: ID!, $tags: [String!]!) {
  tagsAdd(id: $id, tags: $tags) {
    node {
      id
    }
    userErrors {
      field
      message
    }
  }
}

# fulfillmentOrderHold:mutation — validated against api_version 2025-01
mutation FulfillmentOrderHold($id: ID!, $fulfillmentHold: FulfillmentOrderHoldInput!) {
  fulfillmentOrderHold(id: $id, fulfillmentHold: $fulfillmentHold) {
    fulfillmentOrder {
      id
      status
    }
    userErrors {
      field
      message
    }
  }
}

Session Tracking

Claude MUST emit the following output at each stage. This is mandatory.

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: High Risk Order Tagger               ║
║  Store:                        ║
║  Started:              ║
╚══════════════════════════════════════════════╝

After each step, emit:

[N/TOTAL]   
          → Params: 
          → Result: 

If dry_run: true, prefix every mutation step with [DRY RUN] and do not execute it.

On completion, emit:

For format: human (default):

══════════════════════════════════════════════
OUTCOME SUMMARY
  High-risk orders found:  
  Orders tagged:           
  Fulfillment holds placed: 
  Errors:                  
  Output:                  risk_tagging_.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "high-risk-order-tagger",
  "store": "",
  "started_at": "",
  "dry_run": true,
  "outcome": {
    "orders_found": 0,
    "tagged": 0,
    "holds_placed": 0,
    "errors": 0,
    "output_file": "risk_tagging_.csv"
  }
}

Output Format

CSV file risk_tagging_.csv with columns: order_name, order_id, risk_level, total_price, currency, tag_applied, hold_placed, customer_name

Error Handling

| Error | Cause | Recovery | |-------|-------|----------| | THROTTLED | API rate limit exceeded | Wait 2 seconds, retry up to 3 times | | userErrors on hold | Order already fulfilled or hold already exists | Log as skipped, continue | | No high-risk orders | Clean period | Exit with 0 flagged |

Best Practices

• Run within 1–2 hours of order placement — most fraud orders are placed and expected to ship same-day.
• After a hold is placed, use order-risk-report to review the risk indicators in detail before deciding to cancel or release.
• Release legitimate orders with the order-hold-and-release skill to minimize shipping delay.
• Orders from repeat customers (numberOfOrders > 3) are unlikely to be fraudulent — consider filtering them out with min_order_value or a separate query.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: 40RTY-ai
• Source: 40RTY-ai/shopify-admin-skills
• License: MIT
• Homepage: http://skills.40rty.ai

Install and usage instructions live in the source repository linked above.