Shopify Admin Low Inventory Restock

Purpose

Queries all tracked product variants at or below a configurable stock threshold and exports a restock CSV grouped by vendor. By pulling live inventory counts directly from the Shopify Admin API and sorting results by vendor name, this skill gives procurement teams an immediately actionable reorder list without manual exports from the Shopify admin inventory view.

Prerequisites

• Authenticated Shopify CLI session: shopify auth login --store <domain>
• API scopes: read_products, read_inventory

Parameters

Workflow Steps

1. OPERATION: productVariants — query Inputs: first: 250, query: "inventory_quantity:<= <threshold>", pagination cursor Expected output: List of variant objects with inventoryQuantity, product title, vendor, SKU; paginate until hasNextPage: false

GraphQL Operations

# productVariants:query — validated against api_version 2025-01
query LowInventoryVariants($first: Int!, $after: String, $query: String) {
  productVariants(first: $first, after: $after, query: $query) {
    edges {
      node {
        id
        title
        sku
        inventoryQuantity
        product {
          id
          title
          vendor
        }
        inventoryItem {
          id
          tracked
        }
      }
    }
    pageInfo {
      hasNextPage
      endCursor
    }
  }
}

Session Tracking

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

On start, emit:

╔══════════════════════════════════════════════╗
║  SKILL: low-inventory-restock                ║
║  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>

On completion, emit:

For format: human (default):

══════════════════════════════════════════════
OUTCOME SUMMARY
  Variants below threshold:  <n>
  Unique products:            <n>
  Vendors:                    <n>
  Errors:                     0
  Output:                     restock_list_<date>.csv
══════════════════════════════════════════════

For format: json, emit:

{
  "skill": "low-inventory-restock",
  "store": "<domain>",
  "started_at": "<ISO8601>",
  "completed_at": "<ISO8601>",
  "dry_run": false,
  "steps": [
    { "step": 1, "operation": "LowInventoryVariants", "type": "query", "params_summary": "threshold <= 10, all locations", "result_summary": "<n> variants", "skipped": false }
  ],
  "outcome": {
    "variants_below_threshold": 0,
    "unique_products": 0,
    "vendors": 0,
    "errors": 0,
    "output_file": "restock_list_<date>.csv"
  }
}

Output Format

CSV file restock_list_<YYYY-MM-DD>.csv grouped by vendor, sorted by vendor name then product title. Columns: vendor, product_title, variant_title, sku, current_stock.

Error Handling

Best Practices

1. Run without location_id first to get store-wide low stock; then filter by location if you operate multiple warehouses. 2. Only variants with inventoryItem.tracked: true have meaningful stock counts — untracked variants always appear as 0. 3. The restock CSV is sorted by vendor — share the vendor-grouped output directly with your procurement team without reformatting. 4. Set include_zero_stock: false to skip variants already on back-order to focus on nearly-depleted items. 5. Schedule this skill to run weekly via cron and pipe the CSV to your purchasing workflow.