Riggr works across the full range of Shopify merchants. To make it concrete, here are five archetypes with the operational pain points they hit, and which Riggr Spark best addresses each.
Riggr ships eight Sparks. A project can attach up to eight — first two Compose into one local app; Sparks 3+ are Add-ons. See Sparks → Compose + Add-ons.
Each profile below is a general pattern grounded in real Shopify merchant data. Your store may match one archetype closely or straddle several. Pick the Spark whose pain point resonates most.
Who this fits:
Operational pain points:
Where Riggr fits: Start with the Returns Triage Workspace Spark. It builds you a returns review app with auto-detected patterns, unusual return rates, reasons trending up, specific SKU spikes. Instead of finding a quality issue after 500 refunds, you catch it after 20.
Strong alternatives: Daily Ops Command (morning checklist + attention inbox) or WISMO At-Risk Desk if support tickets are the loudest pain.
Once returns are under control, attach Fulfillment Lag Operations Tool on the same project (max two) and copy Talk to your AI — Compose merges both into one app. Or start a second project if you want separate apps.
Who this fits:
Operational pain points:
Where Riggr fits: The Inventory Transfer Decision Workspace is the natural fit. It surfaces a queue of imbalanced products, shows per-location horizontal bar visualizations, and lets you capture transfer or reorder decisions in one click. Filter by product category or urgency when the imbalance list gets long.
Pair with Reorder Buy Plan on the same project when buy decisions and transfers both matter.
Inventory Transfer only shines if you have multiple Shopify locations configured. Set them up in Shopify Admin → Settings → Locations first.
Who this fits:
Operational pain points:
Where Riggr fits: The Fulfillment Lag Operations Tool builds you a queue of late shipments ranked by urgency. Escalation forms capture root cause and warehouse handoff. The Patterns page surfaces chronic issues, "Warehouse B is 2 days late on 30% of orders this month," with the data to back it up in vendor conversations.
Order Exception Desk is a good Compose partner when holds and splits are as noisy as late carriers.
Who this fits:
Operational pain points:
Where Riggr fits: Same Fulfillment Lag Spark as marketplace sellers, but with heavier customization. Ask your AI to add per-3PL performance scorecards, SLA tracking against contracted rates, and dispute-ready reporting after Autopilot scaffolds v1.
Attach Fulfillment Lag + Returns Triage on one project (max two), then copy Talk to your AI. Your AI loads Compose over MCP — you do not freeform “merge two prompts” in chat as the primary path.
Who this fits:
Operational pain points:
Where Riggr fits: There isn't a dedicated subscription analytics Spark yet. Strong starters: Reorder Buy Plan (velocity-driven buys) and Daily Ops Command. For retention-specific analytics, ask your AI to build a custom tool using Riggr MCP after Autopilot (or from scratch with a project API key). Real data your AI can pull today (PCD Level 1): order history, line items, and product mix — not customer name/email/phone.
Give your AI clear intent and a project API key. Explore data in Claude Desktop / ChatGPT if you want, then hand off scaffolding to Claude Code, Cursor, or Codex.
Who this fits:
Operational pain points:
Where Riggr fits: Use multiple projects over time, and Compose pairs (max two Sparks per project). Example week: Daily Ops + Exceptions on project A; Fulfillment + Returns on project B; WISMO alone on project C for support. Each project has its own Talk to your AI handoff and API key.
Every Spark your AI builds becomes a starting point for the next. By your 4th or 5th custom app, your AI has learned your data patterns, your naming conventions, and your workflow preferences. Speed compounds.
If your store spans multiple archetypes (common for stores over $1M ARR), start with the pain point that hurts most this quarter. You can attach a second Spark later, or create another project.
An order that works for many merchants:
Daily Ops Command if you want a morning home base; Returns Triage if refunds quality is the loudest cost.
Attach as the second Spark on the same project (Compose), or start a new project if you want a separate app.
Fulfillment Lag for carrier/3PL delays; Inventory Transfer only if you're multi-location; Reorder Buy Plan for purchase planning.
By now your AI knows your store's shape. Ask for the analytics tool that lives in your head but not in any dashboard.
Ready to try? Head to the Setup guide or the Sparks guide. Running into issues? Check Troubleshooting.