with one click
shopify-admin-cross-sell-opportunity-finder
// Read-only: identifies products with high single-purchase rates that could benefit from cross-sell pairing based on category and price affinity.
// Read-only: identifies products with high single-purchase rates that could benefit from cross-sell pairing based on category and price affinity.
Master skill collection for Shopify store operators. Provides access to all merchandising, marketing, support, and operations capabilities.
Read-only: calculates the true ROI of each discount code and automatic discount by comparing incremental revenue against discount cost.
Read-only: mines order history to find product pairs and triplets frequently purchased together, generating cross-sell and bundle recommendations.
Read-only: extracts gift messages, gift recipients, and gift flags from order custom attributes and notes for fulfillment teams to print on packing slips.
Read-only: identifies orders 7ā14 days post-fulfillment that are eligible for a post-purchase survey campaign, excluding refunded or cancelled orders.
Identifies customers with disputed or charged-back orders and tags their customer record for proactive review on future orders.
| name | shopify-admin-cross-sell-opportunity-finder |
| role | conversion-optimization |
| description | Read-only: identifies products with high single-purchase rates that could benefit from cross-sell pairing based on category and price affinity. |
| toolkit | shopify-admin, shopify-admin-execution |
| api_version | 2025-01 |
| graphql_operations | ["orders:query","products:query"] |
| status | stable |
| compatibility | Claude Code, Cursor, Codex, Gemini CLI |
Finds products that are almost always purchased alone (single-item orders) and identifies potential cross-sell partners based on category affinity, price complementarity, and customer overlap. While frequently-bought-together finds existing patterns, this skill finds MISSING patterns ā products that SHOULD be cross-sold but aren't. Read-only ā no mutations.
shopify store auth --store <domain> --scopes read_orders,read_productsread_orders, read_products| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| store | string | yes | ā | Store domain |
| days_back | integer | no | 180 | Order lookback window |
| solo_threshold | float | no | 70 | % of orders where product is bought alone to flag as "solo" |
| min_orders | integer | no | 10 | Minimum orders for a product to be analyzed |
| format | string | no | human | Output format: human or json |
ā¹ļø Read-only skill ā no mutations are executed. Safe to run at any time.
OPERATION: orders ā query
Inputs: query: "created_at:>='<NOW - days_back days>'", first: 250, select lineItems { product { id, title, productType, vendor }, quantity, originalTotalSet }, pagination cursor
Expected output: All orders with product data
For each product, calculate:
Flag products with solo rate ā„ solo_threshold as "cross-sell candidates"
OPERATION: products ā query (enrichment)
Inputs: Product IDs for solo items and potential partners
Expected output: Product type, vendor, price, collections for affinity matching
For each solo product, suggest cross-sell partners:
# orders:query ā validated against api_version 2025-01
query OrdersForCrossSell($query: String!, $after: String) {
orders(first: 250, after: $after, query: $query) {
edges {
node {
id
customer { id }
lineItems(first: 50) {
edges {
node {
product { id title productType vendor }
quantity
originalTotalSet { shopMoney { amount currencyCode } }
}
}
}
}
}
pageInfo { hasNextPage endCursor }
}
}
# products:query ā validated against api_version 2025-01
query ProductEnrichment($ids: [ID!]!) {
nodes(ids: $ids) {
... on Product {
id
title
productType
vendor
priceRangeV2 {
minVariantPrice { amount currencyCode }
}
totalInventory
status
}
}
}
Claude MUST emit the following output at each stage. This is mandatory.
On start, emit:
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
ā SKILL: Cross-Sell Opportunity Finder ā
ā 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):
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
CROSS-SELL OPPORTUNITY REPORT (<days_back> days)
Products analyzed: <n>
High solo-rate products: <n>
āāāāāāāāāāāāāāāāāāāāāāāāāāāāā
TOP CROSS-SELL OPPORTUNITIES:
"<product A>" (solo rate: <pct>%, <n> orders)
ā Suggested partner: "<product B>" (same vendor, complementary type)
ā Price fit: $<main> + $<partner> = $<combined>
ā Potential AOV lift: +$<amount> per order
Revenue opportunity: $<total> (if <pct>% of solo orders add partner)
Output: cross_sell_opportunities_<date>.csv
āāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāāā
CSV file cross_sell_opportunities_<YYYY-MM-DD>.csv with columns:
product_id, product_title, total_orders, solo_orders, solo_rate, suggested_partner_id, suggested_partner_title, affinity_type, potential_aov_lift
| Error | Cause | Recovery |
|---|---|---|
THROTTLED | API rate limit exceeded | Wait 2 seconds, retry up to 3 times |
| All multi-item orders | Store naturally has high cross-sell | Report as healthy ā no action needed |
| Small catalog | Too few products for meaningful pairs | Suggest expanding catalog |
frequently-bought-together to see what IS working vs. what's missing.discount-ab-analysis to test a "buy X, get Y at 15% off" promotion.