Shopify Admin Tracking Update Bulk

Safety

⚠️ fulfillmentUpdate overwrites existing tracking info. Set notify_customer: false unless you explicitly want to resend shipment notifications — customers will receive a new email for every updated fulfillment if enabled. Run with dry_run: true to confirm the fulfillment list before committing.

Workflow Steps

1. OPERATION: order — query Inputs: id: <order_id> for each order in updates Expected output: Order with fulfillments { id, trackingInfo } to confirm existing fulfillment IDs match

2. OPERATION: fulfillmentUpdate — mutation Inputs: fulfillmentId: <id>, trackingInfoUpdateInput: { company, number, url }, notifyCustomer Expected output: fulfillment { id, trackingInfo }, userErrors

GraphQL Operations

# order:query — validated against api_version 2025-01
query OrderFulfillments($id: ID!) {
  order(id: $id) {
    id
    name
    fulfillments {
      id
      status
      trackingInfo {
        company
        number
        url
      }
    }
  }
}

# fulfillmentUpdate:mutation — validated against api_version 2025-01
mutation FulfillmentUpdate($fulfillmentId: ID!, $trackingInfoInput: FulfillmentTrackingInput!, $notifyCustomer: Boolean) {
  fulfillmentUpdate(
    fulfillmentId: $fulfillmentId
    trackingInfoUpdateInput: $trackingInfoInput
    notifyCustomer: $notifyCustomer
  ) {
    fulfillment {
      id
      status
      trackingInfo {
        company
        number
        url
      }
    }
    userErrors {
      field
      message
    }
  }
}

Session Tracking

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

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: Tracking Update Bulk                 ║
║  Store: <store domain>                       ║
║  Started: <YYYY-MM-DD HH:MM UTC>             ║
╚══════════════════════════════════════════════╝

After each step, emit:

[N/TOTAL] <QUERY|MUTATION>  <OperationName>
          → Params: <brief summary of key inputs>
          → Result: <count or outcome>

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
  Fulfillments targeted:   <n>
  Tracking numbers updated: <n>
  Notifications sent:       <n>
  Errors:                   <n>
  Output:                   tracking_update_<date>.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "tracking-update-bulk",
  "store": "<domain>",
  "started_at": "<ISO8601>",
  "completed_at": "<ISO8601>",
  "dry_run": true,
  "outcome": {
    "targeted": 0,
    "updated": 0,
    "notifications_sent": 0,
    "errors": 0,
    "output_file": "tracking_update_<date>.csv"
  }
}

Output Format

CSV file tracking_update_<YYYY-MM-DD>.csv with columns: order_name, fulfillment_id, old_tracking_number, new_tracking_number, carrier, notify_customer, status

Error Handling

Best Practices

• Keep notify_customer: false unless the carrier is tracking a replacement shipment — customers find repeated shipping emails confusing and may open unnecessary support tickets.
• Provide fulfillment_id directly in the updates input when possible to skip the order lookup step entirely.
• For 3PL integrations that send corrected tracking via CSV, parse the CSV into the updates array before running this skill.