From shopify-admin-skills
Calculates lifetime spend per customer and applies Bronze/Silver/Gold/Platinum tags via Shopify Admin API. Useful for VIP segmentation without third-party apps.
How this skill is triggered — by the user, by Claude, or both
Slash command
/shopify-admin-skills:shopify-admin-customer-spend-tier-taggerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Queries all customers, calculates their lifetime spend using order history, and assigns a spend-tier tag (Bronze/Silver/Gold/Platinum by default). Enables VIP segmentation for loyalty programs, exclusive offers, and CX prioritization without a third-party loyalty app. Extends the existing `loyalty-segment-export` skill with a write step.
Queries all customers, calculates their lifetime spend using order history, and assigns a spend-tier tag (Bronze/Silver/Gold/Platinum by default). Enables VIP segmentation for loyalty programs, exclusive offers, and CX prioritization without a third-party loyalty app. Extends the existing loyalty-segment-export skill with a write step.
shopify store auth --store <domain> --scopes read_customers,read_orders,write_customersread_customers, read_orders, write_customers| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| store | string | yes | — | Store domain (e.g., mystore.myshopify.com) |
| tiers | object | no | see below | Spend thresholds per tier (in store currency) |
| tag_prefix | string | no | tier | Tag prefix (e.g., tier:bronze, tier:silver) |
| remove_old_tiers | bool | no | true | Remove existing tier tags before applying new ones |
| dry_run | bool | no | true | Preview without executing mutations |
| format | string | no | human | Output format: human or json |
Default tiers (store currency):
bronze: $0–$249
silver: $250–$999
gold: $1,000–$4,999
platinum: $5,000+
⚠️
tagsAddadds tags to customer records visible to staff and used by marketing segments. Ifremove_old_tiers: true, existing tier tags matchingtag_prefixare removed before new ones are applied. Run withdry_run: trueto review the tier distribution before committing.
OPERATION: customers — query
Inputs: first: 250, select id, amountSpent, pagination cursor
Expected output: All customers with lifetime spend; paginate until hasNextPage: false
Assign tier to each customer based on amountSpent.amount vs. tiers thresholds
OPERATION: orders — query (optional — for verification of spend figures)
OPERATION: tagsAdd — mutation
Inputs: Customer id, tags: ["<tag_prefix>:<tier>"]
Expected output: Updated customer tags; userErrors
# customers:query — validated against api_version 2025-01
query CustomerSpendLevels($after: String) {
customers(first: 250, after: $after) {
edges {
node {
id
displayName
defaultEmailAddress {
emailAddress
}
amountSpent {
amount
currencyCode
}
numberOfOrders
tags
}
}
pageInfo {
hasNextPage
endCursor
}
}
}
# orders:query — validated against api_version 2025-01
query CustomerOrderHistory($customerId: String!, $after: String) {
orders(first: 250, after: $after, query: $customerId) {
edges {
node {
id
totalPriceSet {
shopMoney {
amount
currencyCode
}
}
}
}
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
}
}
}
Claude MUST emit the following output at each stage. This is mandatory.
On start, emit:
╔══════════════════════════════════════════════╗
║ SKILL: Customer Spend Tier Tagger ║
║ 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
Customers processed: <n>
Bronze: <n> (<pct>%)
Silver: <n> (<pct>%)
Gold: <n> (<pct>%)
Platinum: <n> (<pct>%)
Tags applied: <n>
Errors: <n>
Output: tier_tagging_<date>.csv
══════════════════════════════════════════════
For format: json, emit:
{
"skill": "customer-spend-tier-tagger",
"store": "<domain>",
"started_at": "<ISO8601>",
"dry_run": true,
"tier_distribution": { "bronze": 0, "silver": 0, "gold": 0, "platinum": 0 },
"tags_applied": 0,
"errors": 0,
"output_file": "tier_tagging_<date>.csv"
}
CSV file tier_tagging_<YYYY-MM-DD>.csv with columns:
customer_id, name, email, lifetime_spend, currency, tier, previous_tags, new_tags
| Error | Cause | Recovery |
|---|---|---|
THROTTLED | API rate limit exceeded | Wait 2 seconds, retry up to 3 times |
userErrors on tagsAdd | Invalid customer ID | Log error, skip customer, continue |
| No customers | Empty store | Exit with 0 results |
remove_old_tiers: true to ensure each customer has exactly one tier tag at any time.tiers thresholds to your store's AOV and LTV distribution — the defaults work for stores with $50–100 AOV.npx claudepluginhub 40rty-ai/shopify-admin-skills --plugin shopify-admin-skillsIdentifies top-spending customers by lifetime value or order frequency, exports a CSV of VIP candidates, and optionally tags them as VIPs in Shopify.
Manages Shopify customers via GraphQL Admin API mutations/queries for create/update/delete/tags/metafields, Customer Account API, Multipass SSO, segmentation, B2B accounts.
Manages Shopify orders, customers, and fulfillments via GraphQL Admin API. Query orders, process fulfillments, handle customer records, create draft orders.