How to Auto-Tag Risky Customers in Shopify
Every Shopify merchant knows the feeling: you look at a customer's order history and think "this person has returned way too much." But that knowledge stays in your head. It doesn't automatically affect how you handle their next return.
Customer tagging bridges that gap. By automatically applying risk-based tags, you can:
- Route returns to different handling queues
- Exclude high-risk customers from promotions
- Inform customer service before they pick up the phone
- Build segments for targeted communication
This tutorial walks through setting up auto-tagging with RefundSentry, then shows practical workflows that use those tags.
Prerequisites
Before starting, you'll need:
- RefundSentry installed on your Shopify store
- Returns flowing through (the scoring engine needs return data)
- Shopify admin access (for segment creation and Flow setup)
Optional but helpful:
- Shopify Flow, if you use it for automation
- Klaviyo or similar email marketing platform (for tag-based segments)
Understanding Risk Zones
RefundSentry scores every return on a 0–100 scale and classifies customers into risk zones:
| Risk Zone | Score Range | Tag Applied | Meaning |
|---|---|---|---|
| Low | 0–30 | refundsentry:low-risk | Normal return behavior |
| Medium | 31–65 | refundsentry:medium-risk | Some concerning signals |
| High | 66–100 | refundsentry:high-risk | Strong fraud/abuse indicators |
Tags update automatically with each new return. A customer who moves from low-risk to high-risk (through accumulated returns) will have their tag updated accordingly.
Step 1: Enable Auto-Tagging
Auto-tagging is enabled by default in RefundSentry. To verify or configure:
- Open RefundSentry from your Shopify admin
- Navigate to Settings → Tagging
- Confirm "Auto-tag customers by risk zone" is enabled
- (Optional) Customize tag names if your existing systems require specific formats
Tag Format
By default, tags follow the format:
refundsentry:low-riskrefundsentry:medium-riskrefundsentry:high-risk
The refundsentry: prefix prevents conflicts with other tags you might use. All three use the same prefix so you can easily search for "refundsentry" to find all risk-tagged customers.
Tag Behavior
- New returns trigger tag evaluation immediately
- Tag updates replace the previous risk tag (only one risk level tag at a time)
- No return activity leaves the tag unchanged
- Customer data deletion (GDPR request) removes all RefundSentry tags
Step 2: Verify Tags Are Applied
After enabling, verify that tags are working:
- Go to Customers in Shopify admin
- Find a customer who recently submitted a return
- Check their tags section
You should see one of the refundsentry: tags applied.
Troubleshooting:
- If no tag appears, check that the return was processed (scored) by RefundSentry
- Verify the Shopify scopes include
write_customers - Check the RefundSentry logs for any tagging errors
Step 3: Create Customer Segments
Shopify's customer segments let you filter by tags. Create segments for each risk zone:
High-Risk Segment
- Go to Customers → Segments
- Click Create segment
- Name: "High-Risk Returners (RefundSentry)"
- Filter:
customer_tags CONTAINS 'refundsentry:high-risk' - Save
Medium-Risk Segment
Same process with filter: customer_tags CONTAINS 'refundsentry:medium-risk'
Low-Risk Segment (VIP Candidates)
Same process with filter: customer_tags CONTAINS 'refundsentry:low-risk'
These segments update in real-time as tags change.
Step 4: Build Workflows with Tags
Now for the practical applications. Here are workflows that use your new risk segments.
Workflow 1: Exclude High-Risk from Free Return Promotions
The problem: You offer free return shipping to email subscribers, but serial abusers exploit this.
The solution: Exclude high-risk customers from free return promotions.
Implementation (Klaviyo):
- Go to Lists & Segments → Create Segment
- Add condition: "Shopify tags contains refundsentry:high-risk"
- Save as "High-Risk Returners"
- In your free-returns email campaign, add exclusion: "Not in segment: High-Risk Returners"
Implementation (Shopify Email):
- When creating email campaign, select audience
- Choose "Specific segment"
- Exclude the "High-Risk Returners" segment you created
Workflow 2: Route Support Tickets by Risk Level
The problem: High-risk customers contact support expecting easy refunds. Your team approves without context.
The solution: Tag support tickets with customer risk level for prioritized handling.
Implementation (Gorgias):
- Create a rule: When ticket created
- Condition: Customer tag contains
refundsentry:high-risk - Action: Add tag "VIP-Review-Required"
- Action: Assign to "Fraud Review" queue
Implementation (Zendesk):
- Create trigger: When ticket is created
- Condition: Requester tags contain
refundsentry:high-risk - Action: Add tag "high-risk-customer"
- Action: Set priority to High
- Optional: Route to specialized group
Workflow 3: Notify Team of High-Risk Returns (Shopify Flow)
The problem: High-risk returns slip through without review.
The solution: Slack notification when a high-risk customer submits a return.
Shopify Flow setup:
- Trigger: Customer tags changed
- Condition: Customer tags contains
refundsentry:high-risk - Action: Send Slack message to #fraud-review channel
Message template:
🚨 High-Risk Return Alert
Customer just submitted a return and was tagged high-risk.
Customer ID: {{customer.id}}
View customer: {{customer.admin_url}}
Workflow 4: Require Photo Proof for High-Risk Returns
The problem: High-risk customers claim "item not as described" without evidence.
The solution: Automatically request photos before processing refund.
Implementation:
This requires integration with your return management system (Loop, AfterShip, etc.) or custom development.
General approach:
- On return submission, check customer tags via Shopify API
- If
refundsentry:high-riskpresent, require photo upload - Do not generate return label until photos received
Workflow 5: Adjust Exchange Incentives by Risk
The problem: You offer 10% bonus credit for exchanges, but abusers exploit this.
The solution: Tiered incentives based on risk level.
| Risk Level | Exchange Bonus |
|---|---|
| Low-risk | 15% bonus credit |
| Medium-risk | 5% bonus credit |
| High-risk | No bonus (standard exchange) |
Implementation:
Use Shopify Flow or Scripts to check tags and apply different discount codes:
- Low-risk: Apply
EXCHANGE15discount - Medium-risk: Apply
EXCHANGE5discount - High-risk: No automatic discount
Step 5: Advanced Segment Combinations
Tags become more powerful when combined with other data.
High-Value + High-Risk
customer_tags CONTAINS 'refundsentry:high-risk'
AND
total_spent > 500
These customers have spent real money but show fraud signals. They may deserve a personal call before blocking.
New Customer + High-Risk
customer_tags CONTAINS 'refundsentry:high-risk'
AND
orders_count < 3
First-purchase fraud is a common pattern. This segment catches it early.
Repeat Buyer + Medium-Risk
customer_tags CONTAINS 'refundsentry:medium-risk'
AND
orders_count > 5
Longtime customers showing new concerning behavior. Worth investigation before escalation.
Step 6: Monitor and Iterate
Track Tag Distribution
In RefundSentry dashboard, monitor:
- % of customers in each risk zone
- Movement between zones over time
- False positive rate (legitimate customers tagged high-risk)
Expected Distribution
| Risk Zone | Typical % of Returners |
|---|---|
| Low | 70–85% |
| Medium | 10–20% |
| High | 5–15% |
If your high-risk percentage is above 20%, your thresholds may be too aggressive. If it's below 3%, you may be missing fraud.
Feedback Loop
When you identify a false positive (good customer incorrectly tagged high-risk):
- Note the return and customer for analysis
- The customer's tag will update naturally if their behavior changes
- Contact RefundSentry support if you see systematic false positives
Common Questions
Q: Will customers see these tags?
No. Customer tags are internal to Shopify admin. Customers never see them on their account or order confirmation.
Q: What happens if a customer is in multiple segments?
Shopify supports multiple tags, but RefundSentry only applies one risk tag at a time (the current risk level). Other non-RefundSentry tags remain unaffected.
Q: Can I manually change the risk tag?
You can remove RefundSentry tags manually, but they'll be re-applied on the next return. For persistent overrides, use a separate tag (e.g., trusted-customer) and build segments that exclude it.
Q: How quickly do tags update?
Tags update within seconds of return scoring. If using Shopify Flow, there may be additional delay (typically under 1 minute).
Q: What if a customer improves their behavior?
Tags update based on current risk calculation. A high-risk customer who makes several non-returned purchases will see their score improve and tag update accordingly.
What You've Built
By following this tutorial, you now have:
✅ Automatic risk tagging on all scored returns ✅ Customer segments for each risk zone ✅ Workflows that take action based on risk level ✅ Visibility into your customer risk distribution
This transforms return fraud detection from a reactive manual process to a proactive automated system. Your team can focus on the 5-15% of returns that actually need attention, while 85%+ process with zero friction.
Next Steps
- Set up Slack alerts for high-risk returns (see Workflow 3)
- Integrate with your helpdesk to tag incoming tickets
- Review your segments weekly to catch trends
- Export high-risk customers for quarterly manual review
Questions or need help with custom integrations? Contact the RefundSentry team through the in-app chat.