name: ops-ecom\ndescription: Shopify store command center. Orders, inventory, fulfillment, analytics, and store health. Works with any Shopify store via Admin API.\nargument-hint: \"[orders|inventory|fulfillment|health|products|customers|analytics|setup]\"\nallowed-tools:
\nBefore executing, load available context:
\nPreferences: Read ${CLAUDE_PLUGIN_DATA_DIR:-$HOME/.claude/plugins/data/ops-ops-marketplace}/preferences.json
timezone — display all timestamps correctlyshopify_store_url, shopify_admin_token — check userConfig keys before env varsDaemon health: Read ${CLAUDE_PLUGIN_DATA_DIR}/daemon-health.json
action_needed is not null → surface it before running any store operationsSecrets: Resolve Shopify credentials via userConfig → env vars → Doppler (see Phase 1 below)
\n| Endpoint | \nMethod | \nDescription | \n
|---|---|---|
/admin/api/2024-10/shop.json | \nGET | \nStore info and plan | \n
/admin/api/2024-10/orders.json?status=any&limit=50 | \nGET | \nRecent orders | \n
/admin/api/2024-10/products.json?limit=250 | \nGET | \nProduct catalog | \n
/admin/api/2024-10/customers.json?limit=50 | \nGET | \nCustomer list | \n
/admin/api/2024-10/themes.json | \nGET | \nTheme list | \n
/admin/api/2024-10/variants/${ID}.json | \nPUT | \nUpdate variant price | \n
Auth header: X-Shopify-Access-Token: ${SHOPIFY_TOKEN}
| Endpoint | \nMethod | \nDescription | \n
|---|---|---|
https://api.shipbob.com/1.0/shipment?Status=Processing&PageSize=20 | \nGET | \nPending shipments | \n
Auth header: Authorization: Bearer ${SHIPBOB_TOKEN}
If CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 is set, use Agent Teams when probing store data in parallel. This enables:
Team setup (only when flag is enabled):
\nTeamCreate(\"ecom-team\")\nAgent(team_name=\"ecom-team\", name=\"orders-scanner\", prompt=\"Fetch recent orders, compute revenue for today/7d/30d\")\nAgent(team_name=\"ecom-team\", name=\"inventory-scanner\", prompt=\"Fetch all products, flag low stock and out-of-stock items\")\nAgent(team_name=\"ecom-team\", name=\"fulfillment-scanner\", prompt=\"Fetch unfulfilled orders and ShipBob shipment status\")\nAgent(team_name=\"ecom-team\", name=\"analytics-scanner\", prompt=\"Compute revenue analytics, AOV, and top products for 30d\")\nIf the flag is NOT set, use standard fire-and-forget subagents.
\nResolve Shopify credentials in this order:
\n# 1. Plugin userConfig\nSHOPIFY_STORE=\"${user_config.shopify_store_url}\"\nSHOPIFY_TOKEN=\"${user_config.shopify_admin_token}\"\nSHIPBOB_TOKEN=\"${user_config.shipbob_access_token}\"\n\n# 2. Environment variables (override userConfig if set)\n[ -n \"$SHOPIFY_STORE_URL\" ] && SHOPIFY_STORE=\"$SHOPIFY_STORE_URL\"\n[ -n \"$SHOPIFY_ACCESS_TOKEN\" ] && SHOPIFY_TOKEN=\"$SHOPIFY_ACCESS_TOKEN\"\n[ -n \"$SHIPBOB_ACCESS_TOKEN\" ] && SHIPBOB_TOKEN=\"$SHIPBOB_ACCESS_TOKEN\"\n\n# 3. Doppler fallback\nif [ -z \"$SHOPIFY_TOKEN\" ] && command -v doppler &>/dev/null; then\n SHOPIFY_TOKEN=$(doppler secrets get SHOPIFY_ACCESS_TOKEN --plain 2>/dev/null)\nfi\nif [ -z \"$SHOPIFY_STORE\" ] && command -v doppler &>/dev/null; then\n SHOPIFY_STORE=$(doppler secrets get SHOPIFY_STORE_URL --plain 2>/dev/null)\nfi\nif [ -z \"$SHIPBOB_TOKEN\" ] && command -v doppler &>/dev/null; then\n SHIPBOB_TOKEN=$(doppler secrets get SHIPBOB_ACCESS_TOKEN --plain 2>/dev/null)\nfi\nIf $SHOPIFY_STORE or $SHOPIFY_TOKEN is still empty after all resolution steps, route to setup flow below.
Set base URLs:
\nSHOPIFY_BASE=\"https://${SHOPIFY_STORE}/admin/api/2024-10\"\nSHOPIFY_GQL=\"https://${SHOPIFY_STORE}/admin/api/2024-10/graphql.json\"\nSHOPIFY_AUTH=\"X-Shopify-Access-Token: ${SHOPIFY_TOKEN}\"\n| Input | \nAction | \n
|---|---|
| (empty) | \nShow store summary | \n
| orders, order | \nOrders dashboard | \n
| inventory, stock, inv | \nInventory levels | \n
| fulfillment, fulfill, shipbob, shipping | \nFulfillment status | \n
| health, check, status | \nStore health check | \n
| products, product, catalog | \nProducts manager | \n
| customers, customer, crm | \nCustomer stats | \n
| analytics, revenue, stats, metrics | \nAnalytics dashboard | \n
| setup, configure, init, token | \nSetup flow | \n
Fetch recent orders and compute revenue:
\nTODAY=$(date -u +\"%Y-%m-%dT00:00:00Z\")\nWEEK_AGO=$(date -u -v-7d +\"%Y-%m-%dT00:00:00Z\" 2>/dev/null || date -u -d \"7 days ago\" +\"%Y-%m-%dT00:00:00Z\")\nMONTH_AGO=$(date -u -v-30d +\"%Y-%m-%dT00:00:00Z\" 2>/dev/null || date -u -d \"30 days ago\" +\"%Y-%m-%dT00:00:00Z\")\n\n# Recent orders (last 50)\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/orders.json?status=any&limit=50&order=created_at+desc\" | \\\n jq '{\n total: .orders | length,\n today: [.orders[] | select(.created_at >= \"'\"$TODAY\"'\")],\n orders: [.orders[:10] | .[] | {\n id: .order_number,\n name: .name,\n status: .financial_status,\n fulfillment: .fulfillment_status,\n total: .total_price,\n currency: .currency,\n customer: (.customer.first_name + \" \" + .customer.last_name),\n created: .created_at\n }]\n }'\nRender:
\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n OPS ► ECOM ► ORDERS — [store] — [timestamp]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nREVENUE\n Today [N orders] $[amount]\n 7 days [N orders] $[amount]\n 30 days [N orders] $[amount]\n\nRECENT ORDERS\n #[id] [customer] $[total] [status] / [fulfillment] [age]\n ...\n\n──────────────────────────────────────────────────────\n Actions:\n a) View order details for #[id]\n b) Mark order as fulfilled\n c) Export orders CSV\n d) Filter by status (unfulfilled/refunded/paid)\n──────────────────────────────────────────────────────\nUse AskUserQuestion for action selection.
Fetch all products and variant inventory:
\n# Get all products with variants\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/products.json?limit=250&fields=id,title,status,variants\" | \\\n jq '[.products[] | {\n id: .id,\n title: .title,\n status: .status,\n variants: [.variants[] | {\n id: .id,\n title: .title,\n sku: .sku,\n inventory_quantity: .inventory_quantity,\n inventory_policy: .inventory_policy\n }]\n }]'\nFlag low stock (inventory_quantity < 10) and out-of-stock (inventory_quantity <= 0).
\nRender:
\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n OPS ► ECOM ► INVENTORY — [store] — [timestamp]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nOUT OF STOCK\n [product] — [variant] — SKU: [sku]\n\nLOW STOCK (< 10 units)\n [product] — [variant] — [N] units — SKU: [sku]\n\nALL PRODUCTS\n [product]\n [variant] [N] units SKU: [sku]\n ...\n\n──────────────────────────────────────────────────────\n Actions:\n a) Update inventory for [product]\n b) Export inventory CSV\n c) Set reorder alerts\n──────────────────────────────────────────────────────\nUse AskUserQuestion for action selection.
Fetch unfulfilled orders and ShipBob status (if token available):
\n# Unfulfilled orders\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/orders.json?fulfillment_status=unfulfilled&status=open&limit=50\" | \\\n jq '[.orders[] | {\n id: .order_number,\n name: .name,\n customer: (.customer.first_name + \" \" + .customer.last_name),\n total: .total_price,\n created: .created_at,\n items: [.line_items[] | {title: .title, qty: .quantity}]\n }]'\n\n# Shipments with tracking (fulfilled)\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/orders.json?fulfillment_status=fulfilled&status=any&limit=20&order=updated_at+desc\" | \\\n jq '[.orders[] | .fulfillments[] | {\n order: .order_id,\n tracking_number: .tracking_number,\n tracking_url: .tracking_url,\n shipment_status: .shipment_status,\n carrier: .tracking_company,\n updated: .updated_at\n }]'\nIf $SHIPBOB_TOKEN is set, also query ShipBob:
# ShipBob pending shipments\ncurl -s -H \"Authorization: Bearer ${SHIPBOB_TOKEN}\" \\\n \"https://api.shipbob.com/1.0/shipment?Status=Processing&PageSize=20\" | \\\n jq '[.[] | {\n id: .id,\n status: .status,\n order_id: .reference_id,\n tracking: .tracking_number,\n created: .created_date\n }]'\nRender fulfillment dashboard with pending/in-transit/delivered counts.
\nUse AskUserQuestion for action selection (mark fulfilled, update tracking, etc.).
Run the health check script, then augment with API checks:
\n${CLAUDE_PLUGIN_ROOT}/bin/ops-ecom-health 2>/dev/null || echo '{\"error\":\"health script unavailable\"}'\nAlso check:
\n# Active theme\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/themes.json\" | \\\n jq '[.themes[] | select(.role == \"main\") | {id: .id, name: .name, updated: .updated_at}]'\n\n# Store info\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/shop.json\" | \\\n jq '.shop | {name: .name, domain: .domain, country: .country_name, plan: .plan_display_name, currency: .currency, timezone: .timezone}'\nRender:
\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n OPS ► ECOM ► HEALTH — [store] — [timestamp]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSTORE\n Name: [name]\n Plan: [plan]\n Currency: [currency]\n Timezone: [tz]\n\nAPI CONNECTIVITY [OK / FAIL]\nACTIVE THEME [theme name]\nPRODUCT COUNT [N] active\nORDERS (24h) [N] orders\n\nISSUES\n [any warnings from health check]\n\n──────────────────────────────────────────────────────\n Actions:\n a) Check theme assets for errors\n b) Run full SEO audit\n c) View API rate limit status\n──────────────────────────────────────────────────────\nUse AskUserQuestion for action selection.
List, search, and manage products:
\n# All products\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/products.json?limit=250&order=updated_at+desc\" | \\\n jq '[.products[] | {\n id: .id,\n title: .title,\n status: .status,\n handle: .handle,\n price: (.variants[0].price // \"N/A\"),\n inventory: ([.variants[].inventory_quantity] | add // 0),\n variants: (.variants | length),\n updated: .updated_at\n }]'\nIf $ARGUMENTS contains a search term (e.g., products shoes), filter by title.
For price updates, use:
\n# Update variant price\ncurl -s -X PUT -H \"$SHOPIFY_AUTH\" -H \"Content-Type: application/json\" \\\n \"${SHOPIFY_BASE}/variants/${VARIANT_ID}.json\" \\\n -d '{\"variant\":{\"id\":'${VARIANT_ID}',\"price\":\"'${NEW_PRICE}'\"}}'\nUse AskUserQuestion before making any product updates. Show before/after prices.
Fetch customer stats:
\n# Customer count and recent\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/customers.json?limit=50&order=created_at+desc\" | \\\n jq '{\n total_shown: (.customers | length),\n recent: [.customers[:10] | .[] | {\n id: .id,\n name: (.first_name + \" \" + .last_name),\n email: .email,\n orders: .orders_count,\n total_spent: .total_spent,\n currency: .currency,\n created: .created_at\n }]\n }'\n\n# Top customers by spend\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/customers.json?limit=10&order=total_spent+desc\" | \\\n jq '[.customers[] | {name: (.first_name + \" \" + .last_name), orders: .orders_count, spent: .total_spent}]'\nRender customer overview with LTV stats and top spenders.
\nPull revenue and order data for dashboard:
\nTODAY=$(date -u +\"%Y-%m-%dT00:00:00Z\")\nWEEK_AGO=$(date -u -v-7d +\"%Y-%m-%dT00:00:00Z\" 2>/dev/null || date -u -d \"7 days ago\" +\"%Y-%m-%dT00:00:00Z\")\nMONTH_AGO=$(date -u -v-30d +\"%Y-%m-%dT00:00:00Z\" 2>/dev/null || date -u -d \"30 days ago\" +\"%Y-%m-%dT00:00:00Z\")\n\n# Orders for revenue calculation\ncurl -s -H \"$SHOPIFY_AUTH\" \\\n \"${SHOPIFY_BASE}/orders.json?status=any&financial_status=paid&created_at_min=${MONTH_AGO}&limit=250\" | \\\n jq '{\n month_orders: (.orders | length),\n month_revenue: ([.orders[].total_price | tonumber] | add // 0),\n week_orders: ([.orders[] | select(.created_at >= \"'\"$WEEK_AGO\"'\")] | length),\n week_revenue: ([.orders[] | select(.created_at >= \"'\"$WEEK_AGO\"'\") | .total_price | tonumber] | add // 0),\n today_orders: ([.orders[] | select(.created_at >= \"'\"$TODAY\"'\")] | length),\n today_revenue: ([.orders[] | select(.created_at >= \"'\"$TODAY\"'\") | .total_price | tonumber] | add // 0),\n avg_order_value: ([.orders[].total_price | tonumber] | (add // 0) / (length // 1)),\n top_products: ([.orders[].line_items[] | {title: .title, qty: .quantity}] | group_by(.title) | map({title: .[0].title, total_qty: map(.qty) | add}) | sort_by(-.total_qty)[:5])\n }'\nRender:
\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n OPS ► ECOM ► ANALYTICS — [store] — [timestamp]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nREVENUE\n Today $[amount] ([N] orders)\n 7 days $[amount] ([N] orders)\n 30 days $[amount] ([N] orders)\n\nAVERAGES\n AOV (30d) $[amount]\n\nTOP PRODUCTS (30d)\n 1. [product] [N] sold\n 2. [product] [N] sold\n ...\n\n──────────────────────────────────────────────────────\n Actions:\n a) Export revenue report (CSV)\n b) View by product breakdown\n c) Compare to previous period\n──────────────────────────────────────────────────────\nUse AskUserQuestion for action selection.
Before asking the user for anything, auto-discover store URLs and tokens. Run ALL of these scans in a single batch:
\n# 1. Env vars\nprintenv SHOPIFY_ACCESS_TOKEN SHOPIFY_ADMIN_TOKEN SHOPIFY_STORE_URL SHOPIFY_ADMIN_API_ACCESS_TOKEN 2>/dev/null\n\n# 2. Shell profiles\ngrep -h 'SHOPIFY\\|myshopify' ~/.zshrc ~/.bashrc ~/.zprofile ~/.envrc 2>/dev/null | grep -v '^#'\n\n# 3. Doppler — ALL projects, not just default\nfor proj in $(doppler projects --json 2>/dev/null | jq -r '.[].slug'); do\n doppler secrets --project \"$proj\" --config prd --json 2>/dev/null | \\\n jq -r --arg proj \"$proj\" 'to_entries[] | select(.key | test(\"SHOPIFY|STORE\"; \"i\")) | \"\\(.key)=\\(.value.computed) (doppler:\\($proj)/prd)\"'\ndone\n\n# 4. Dashlane — URLs reveal store identity\ndcli password shopify --output json 2>/dev/null | jq -r '.[].url // empty' | grep -oE '[a-z0-9-]+\\.myshopify\\.com' | sort -u\n\n# 5. Keychain\nsecurity find-generic-password -s \"shopify-admin-token\" -w 2>/dev/null\nsecurity find-generic-password -s \"shopify-access-token\" -w 2>/dev/null\n\n# 6. Chrome history — reveals store URLs from admin sessions\nsqlite3 ~/Library/Application\\ Support/Google/Chrome/Default/History \\\n \"SELECT DISTINCT url FROM urls WHERE url LIKE '%myshopify.com/admin%' OR url LIKE '%admin.shopify.com/store/%' ORDER BY last_visit_time DESC LIMIT 10\" 2>/dev/null | \\\n grep -oE '[a-z0-9-]+\\.myshopify\\.com|admin\\.shopify\\.com/store/[a-z0-9-]+' | sort -u\n\n# 7. Project .env files\ngrep -rhE 'myshopify\\.com|SHOPIFY_STORE|SHOPIFY.*TOKEN' ~/Projects/*/.env* 2>/dev/null | grep -v '^#' | head -5\n\n# 8. Existing prefs + userConfig\njq -r '.ecom.shopify // empty' \"$PREFS_PATH\" 2>/dev/null\nToken acquisition — automate before asking. If store URL found but no token:
\ncommand -v shopify succeeds: shopify auth login --store <store>.myshopify.com (opens browser OAuth), then generate tokenadmin.shopify.com/store/<slug>/settings/apps/development and automate app creation with scopes: read_orders,write_orders,read_products,write_products,read_customers,read_inventory,write_inventory,read_fulfillments,write_fulfillments,read_analyticsNo automated path for <store>.myshopify.com.\n 1. Go to https://admin.shopify.com/store/<slug>/settings/apps/development\n 2. Create an app → Configure → grant scopes → Install → copy token\n Token starts with \"shpat_\"\nMulti-store: If multiple stores discovered, process each independently. Present all found stores with their token status before asking for input.
\nStore credentials via: userConfig (preferred) → Doppler → env vars. ShipBob optional — check SHIPBOB_ACCESS_TOKEN in same scan.
Verify connectivity after acquisition:
\ncurl -s -H \"X-Shopify-Access-Token: ${PROVIDED_TOKEN}\" \\\n \"https://${PROVIDED_STORE}/admin/api/2024-10/shop.json\" | \\\n jq '.shop | {name, domain, plan: .plan_display_name}'\nIf the connectivity check returns valid shop data, confirm success. If it fails with 401/403, explain the token is invalid and re-prompt.
\nWhen called with no arguments, show a compact store overview:
\nRun orders, inventory, and health checks in parallel (separate Bash calls), then render:
\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n OPS ► ECOM — [store] — [timestamp]\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nSTORE [name] ([plan])\nCURRENCY [currency]\n\nTODAY $[revenue] [N] orders\n7 DAYS $[revenue] [N] orders\n30 DAYS $[revenue] [N] orders\n\nINVENTORY [N] products | [N] low stock | [N] out of stock\nFULFILLMENT [N] unfulfilled orders pending\n\n──────────────────────────────────────────────────────\n /ops:ops-ecom orders — order management\n /ops:ops-ecom inventory — stock levels\n /ops:ops-ecom products — product catalog\n /ops:ops-ecom customers — customer stats\n /ops:ops-ecom analytics — revenue dashboard\n /ops:ops-ecom health — store health check\n /ops:ops-ecom setup — configure credentials\n──────────────────────────────────────────────────────\n