Skip to content

Substitution Unpopularity Report Documentation

Menu Location: Reports > Products > Substitution Unpopularity

Access Level: Manager and above

Last Updated: 2026-03-01

Overview

The Substitution Unpopularity Report identifies product substitutions that customers reject, complain about, or rate poorly. This critical quality assurance tool helps prevent customer dissatisfaction, refine substitution rules, and protect brand reputation by identifying and eliminating problematic product pairings.

Primary Functions:

  • Track unsuccessful substitution attempts
  • Identify customer-rejected substitute pairs
  • Remove poor substitutions from automatic rules
  • Reduce customer complaints and refunds
  • Protect customer relationships and retention
  • Improve overall substitution quality standards

Page Layout

Header Section

  • Date Range Selector: Filter by delivery date period
  • Product Filter: Search for specific original or substitute products
  • Complaint Threshold: Set minimum complaint percentage to display
  • Export Button: Download problem substitution data

Main Content Area

Table displaying substitute product pairs sorted by rejection metrics, showing original product, poor substitute, complaint frequency, and customer feedback severity.

Alert Dashboard

  • Total failed substitutions in period
  • Overall complaint rate percentage
  • Most complained-about substitutes
  • Products triggering most refund requests

Report Data & Columns

Column Description Calculation/Source
Original Product Product that was unavailable Ordered item
Poor Substitute Product given that was rejected Actual delivered item
Times Attempted How many times this pair was tried Count of substitutions
Complaint Rate Percentage who complained (Complaints / Total) × 100
Rejection Rate Percentage who rejected delivery (Rejections / Total) × 100
Refund Rate Percentage who requested refunds (Refunds / Total) × 100
Avg Rating Average customer rating (1-5 stars) Customer feedback scores
Price Difference Cost difference causing complaints Substitute price - original price
Common Complaints Most frequent complaint themes Analyzed feedback text
Auto vs Manual How substitution was made Substitution method

Filters & Search Options

Date Filters

  • Delivery Date Range: Period when problematic orders were delivered
  • Complaint Date: When complaint was registered
  • Quick Select: Last 7 days, Last 30 days, Last 90 days

Product Filters

  • Original Product: Search for specific requested product
  • Substitute Product: Search for specific substitute given
  • Product Category: Filter by category (Produce, Meat, Dairy, etc.)
  • Brand: Filter by product brand

Severity Filters

  • Complaint Rate Threshold: Show only pairs with X% or higher complaints
  • Refund Requested: Filter to substitutions that triggered refunds
  • Rating: Show only substitutions rated 2 stars or below
  • Rejection Type: Delivery Rejected, Credit Requested, Cancellation Threatened

Method Filters

  • Substitution Method: Automatic (system rule), Manual (staff selected)
  • First Occurrence vs Repeat: New problems vs ongoing issues
  • Customer Segment: VIP customers, Regular customers, New customers

Sorting & Display Options

Sort Options:

  • Complaint Rate (highest first) - DEFAULT
  • Times Attempted (most frequent failures first)
  • Refund Rate (most costly first)
  • Average Rating (worst first)
  • Most Recent Complaint (latest first)

Display Options:

  • Show individual customer complaint text
  • Show refund amounts issued
  • Show response/resolution actions taken
  • Compact view (more rows)
  • Detailed view with customer service notes
  • Group by original product
  • Group by substitute product (to find "serial offenders")

Export & Download Options

Export Formats:

  • Full Report CSV: All problem substitution pairs with complete data
  • Worst Offenders: Highest complaint rate substitutions only
  • Active Problems: Issues from last 30 days requiring action
  • Cost Impact: Sorted by refund amounts and revenue lost

Export Process:

  1. Apply filters to focus on actionable problems
  2. Click "Export" button
  3. Select export format
  4. Download CSV
  5. Share with product management and quality assurance teams

Actions & Operations

Remove Problematic Automatic Substitutions

Purpose: Stop system from making poor substitutions automatically

Steps:

  1. Sort by complaint rate (highest first)
  2. Filter to automatic substitutions only
  3. Review pairs with 20%+ complaint rate
  4. For each problem pair:
    • Navigate to original product settings
    • Remove poor substitute from automatic rules
    • Add note: "Do not auto-substitute with [X] - high complaints"
    • Require manual approval for this substitution
  5. Save changes and monitor future reports

Requirements:

  • Administrator access to modify substitution rules
  • Understanding of why substitution failed (quality, price, category mismatch)

Issue Customer Recovery Credits

Purpose: Compensate affected customers and rebuild trust

Steps:

  1. Filter to complaints from last 7-14 days
  2. Identify customers who haven't been compensated yet
  3. Review severity of each complaint
  4. Determine appropriate compensation:
    • Minor issue: $3-5 credit
    • Moderate issue: $5-10 credit
    • Severe issue: $10-20 credit or full refund
  5. Apply credit to customer account
  6. Send personalized apology email
  7. Mark as "Resolved with Compensation"

Analyze Root Causes

Purpose: Understand why specific substitutions fail

Steps:

  1. Select high-complaint-rate substitution pair
  2. Read individual customer complaint text
  3. Identify common themes:
    • Quality downgrade (premium to standard)
    • Category mismatch (beef to pork)
    • Dietary violation (regular to organic swap)
    • Use-case mismatch (cooking to eating raw)
    • Quantity/size difference
    • Taste/flavor incompatibility
  4. Document findings
  5. Update substitution strategy to avoid root cause

Train Staff on Prohibited Substitutions

Purpose: Prevent manual selection of known bad substitutes

Steps:

  1. Export "Worst Offenders" list
  2. Create "Do Not Substitute" reference guide
  3. For each bad pair, document why it failed
  4. Distribute to packing and customer service staff
  5. Include in onboarding training for new team members
  6. Update guide monthly based on new report data

Common Use Cases

Use Case 1: Emergency Substitution Rule Review

Goal: Quickly identify and disable worst automatic substitution rules

Steps:

  1. Open report and sort by complaint rate (highest first)
  2. Filter to "Automatic" substitution method
  3. Filter to complaint rate ≥ 30%
  4. Review top 10 worst performing pairs
  5. For each:
    • Open product settings page
    • Disable automatic substitution immediately
    • Add manual approval requirement
    • Document reason for change
  6. Monitor No Substitution Found Report for increase (expected)
  7. Find better substitute alternatives
  8. Create new rules with better substitutes

Example: "Wild-Caught Salmon" auto-substituted with "Farm-Raised Tilapia" has 45% complaint rate. Customers complain about: quality downgrade, different fish type, different use case. Immediate action: disable this rule. Better alternatives: Wild-Caught Cod (87% acceptance in Popularity Report) or manually contact customer.

Tips:

  • Act quickly on very high complaint rates (30%+)
  • Don't disable all automatic rules (causes operational problems)
  • Replace bad rules with better alternatives same day if possible

Use Case 2: Customer Retention - VIP Recovery

Goal: Proactively reach out to VIP customers who received poor substitutes

Steps:

  1. Filter to last 7 days
  2. Filter to "VIP" or high-value customers
  3. Sort by complaint severity (refund requests, cancellation threats first)
  4. For each VIP customer affected:
    • Review their complete complaint
    • Check their account history and lifetime value
    • Call or email personally (not template)
    • Apologize specifically for the issue
    • Offer generous compensation ($20-50 credit)
    • Guarantee it won't happen again
  5. Set account flag to prevent this substitute in future
  6. Document recovery action in customer notes
  7. Follow up on their next order to ensure satisfaction

Example: VIP customer (3-year member, $8,500 lifetime value) complained that grass-fed ribeye was substituted with conventional chuck roast. Customer threatened cancellation. Personal call: "I'm so sorry - this was completely wrong. I've added $40 to your account and flagged your preferences to ensure you only receive grass-fed premium cuts or we'll contact you first. Can we send you the ribeye in your next order as an apology gift?"

Use Case 3: Product Quality Issue Investigation

Goal: Determine if substitution problem is product quality or pairing problem

Steps:

  1. Identify substitute product with high complaints across multiple original products
  2. Filter report to show this substitute with all original products
  3. If complaints are consistent regardless of original product:
    • Problem is with substitute product itself (quality issue)
    • Check with supplier about product quality
    • Review recent inventory batches
    • Consider temporary removal from catalog
  4. If complaints vary by pairing:
    • Problem is matching logic (wrong pairings)
    • Update substitution rules
    • Focus on category/use-case matching

Example: "Organic Romaine Lettuce" appears in 8 different substitution pairs, all with 25-40% complaint rates. Customer complaints: "Wilted on arrival", "Half was brown", "Poor quality". Investigation reveals: supplier quality issue, not substitution pairing problem. Action: Switch to backup supplier, notify current supplier, offer credits to affected customers.

Use Case 4: Category Mismatch Prevention

Goal: Identify and prevent cross-category substitutions customers reject

Steps:

  1. Generate full report for last 90 days
  2. Export to Excel and add "Category Match" column
  3. Mark whether original and substitute are same category
  4. Filter to "Different Category" pairs
  5. Calculate average complaint rate for same-category vs different-category
  6. Review specific cross-category substitutions with high complaints
  7. Create policy: no automatic cross-category substitutions
  8. Update all substitution rules to respect category boundaries
  9. Train staff on category matching importance

Example: Analysis shows same-category substitutions average 12% complaint rate, cross-category average 38% complaint rate. Specific problem: "Chicken Breast" substituted with "Pork Chops" (different meat category) has 52% complaints. Policy update: Never auto-substitute across meat categories (beef/pork/chicken/fish are separate). Religious, dietary, and preference reasons make this critical.

Use Case 5: Price Sensitivity Analysis

Goal: Understand maximum acceptable price difference for substitutions

Steps:

  1. Export full report to Excel
  2. Add "Price Difference %" column: ((Substitute - Original) / Original) × 100
  3. Group substitutions by price difference ranges:
    • Same price (0-5% difference)
    • Small upgrade (5-15%)
    • Medium upgrade (15-30%)
    • Large upgrade (30%+)
    • Downgrade (negative %)
  4. Calculate average complaint rate for each range
  5. Identify maximum acceptable upgrade threshold
  6. Set substitution rules to limit price differences
  7. Require manual approval for substitutions exceeding threshold

Example: Analysis results:

  • 0-10% upgrade: 8% complaint rate
  • 10-20% upgrade: 18% complaint rate
  • 20-30% upgrade: 35% complaint rate
  • 30%+ upgrade: 58% complaint rate
  • Downgrades: 42% complaint rate

Conclusion: Limit automatic upgrades to 15% maximum. Offer credit for upgrades over 10%. Never downgrade without customer approval.

Troubleshooting

Too Many Results to Process

Symptoms: Report shows hundreds of problematic substitutions

Solutions:

  1. Focus on highest priority first: sort by complaint rate
  2. Filter to automatic substitutions only (manual require different approach)
  3. Filter to last 30 days to focus on recent/active problems
  4. Set complaint threshold to 25%+ to see worst offenders only
  5. Process top 10-20 worst, then expand

This May Indicate:

  • Systemic substitution quality problem
  • Need for overall process review
  • Staff training required
  • Automated rules need comprehensive overhaul

Complaint Rate Seems Low But Issues Persist

Symptoms: Report shows low complaint percentages but customers still seem unhappy

Check:

  1. Many customers don't complain directly but silently churn
  2. Check cancellation rates and correlate with substitutions
  3. Review "rating" column - may have low ratings without explicit complaints
  4. Consider that report only captures documented complaints
  5. Survey customers specifically about substitution satisfaction

Hidden Costs:

  • Silent customer churn (not captured in complaint rate)
  • Reduced reorder frequency
  • Negative word-of-mouth (not measurable)
  • Lower customer lifetime value

Can't Determine Why Substitution Failed

Symptoms: High complaint rate but reasons unclear

Investigation Steps:

  1. Read individual customer complaint text (detailed view)
  2. Check if multiple themes appear (quality AND price AND category)
  3. Review product descriptions - may be misleading expectations
  4. Check if substitute product has general quality issues
  5. Ask customer service team for their observations
  6. Consider calling 2-3 affected customers for direct feedback

Numbers Don't Match Popularity Report

Symptoms: Same substitution pair appears in both Popularity and Unpopularity reports

Explanation: This is possible and indicates mixed customer reception:

  • Some customers accept/like the substitution
  • Others reject/complain about same substitution
  • Average acceptance may be moderate (60-70%)
  • Appears in Unpopularity due to significant complaint minority

How to Handle:

  • Review what differs between accepting and complaining customers
  • May be customer segment difference (VIP vs regular, dietary preferences, etc.)
  • Consider making this a manual-approval substitution (not automatic)
  • Offer choice when this substitution needed
  • Substitution Popularity Report - Successful substitutions for comparison
  • No Substitution Found Report - Failed automatic substitution attempts
  • Customer Feedback - Direct customer complaint details
  • Refund and Credits Report - Financial impact of poor substitutions
  • Product Quality Tracking - Overall product quality issues

Typical Workflow:

  1. Review Substitution Unpopularity Report weekly
  2. Identify worst offenders (high complaint rate)
  3. Remove problematic automatic substitution rules immediately
  4. Issue credits to affected customers
  5. Find better alternatives in Substitution Popularity Report
  6. Update rules with proven good substitutes
  7. Monitor next week's report for improvement

Permissions & Access

Required Access Level: Manager or higher

Access Level Capabilities:

  • Manager: View report, export data, flag issues for administrator
  • Administrator: All Manager capabilities + modify substitution rules, issue bulk credits
  • Kiva Admin: All features + access to system configuration, bulk rule updates

Restricted Features:

  • Modify Substitution Rules: Requires Administrator
  • Bulk Credit Issuance: Requires Administrator approval
  • Delete Complaint Records: Requires Kiva Admin (generally not allowed)

Best Practices

Weekly Monitoring

  1. Review report every Monday for previous week
  2. Immediately disable any automatic rules with 30%+ complaint rates
  3. Contact affected customers from past week
  4. Share insights with packing and purchasing teams
  5. Track week-over-week improvement

Rapid Response

  1. Set alert for any substitution pair reaching 40%+ complaints
  2. Disable automatic rule same day
  3. Contact all affected customers within 48 hours
  4. Issue appropriate compensation immediately
  5. Root cause analysis within 1 week

Customer Communication

  1. Always acknowledge the mistake
  2. Be specific about what went wrong
  3. Explain how you're preventing it in future
  4. Compensate generously to rebuild trust
  5. Follow up on next order

System Optimization

  1. Review "Do Not Substitute" list monthly
  2. Train new staff on problematic pairings
  3. Update substitution rules based on data, not assumptions
  4. Test new substitution rules manually before automating
  5. Measure improvement: track overall complaint rate trend

Things to Avoid

  • Don't ignore low-frequency high-complaint-rate pairs (rare but severe)
  • Don't blame customers for "being picky" (respect preferences)
  • Don't keep trying bad substitutions hoping they'll work eventually
  • Don't automate substitutions without testing manually first
  • Don't prioritize operational convenience over customer satisfaction

Quick Reference Card

Task Action/Location
Find worst substitutions Sort by complaint rate (highest first)
Disable bad automatic rule Filter to automatic, find pair, edit product settings
Compensate affected customers Filter to unresolved, review severity, issue credits
Weekly problem review Last 7 days, complaint rate ≥ 20%, sort by severity
Find cross-category errors Export to Excel, analyze category matching
Emergency response Complaint rate ≥ 40%, disable rule immediately
Track improvement Compare this month vs last month overall complaint rate
Identify quality issues Group by substitute product, check if consistent complaints

FAQs

What's an "unacceptable" complaint rate?

Context matters, but generally: 20%+ requires investigation, 30%+ requires immediate action, 40%+ requires emergency response and rule disabling.

Should I disable all substitutions with any complaints?

No - some complaint rate is normal (varied preferences). Focus on: statistically significant sample sizes (5+ attempts), high rates (20%+), and severe complaints (refund requests, cancellations).

What if automatic rule has complaints but manual same substitution works?

Automatic rules lack context and personalization. Keep manual approval option. Train staff to check: customer preferences, past orders, dietary restrictions before selecting this substitute.

How do I balance complaint rate vs operational efficiency?

Prioritize customer satisfaction for retention. One cancelled customer (lifetime value loss) costs more than manual substitution time. Use automatic rules only for proven 85%+ acceptance substitutes.

What's worse: downgrade or wrong category?

Data varies by business, but generally wrong category generates more severe complaints (dietary, religious, allergy concerns). Downgrades generate more complaints but less intense. Both should be avoided.

Can I see complaints from specific customer segments?

Yes, filter by customer type (VIP, regular, new). VIP complaints especially critical to address immediately due to higher lifetime value and influence.

How long should I wait before trying a substitution pair again?

After fixing root cause (better supplier, different grade/quality), wait 30 days then test manually (not automatic) for 10-20 instances. If acceptance improves to 80%+, can cautiously automate.

What if customer complained but substitute was actually an upgrade?

Communication failure - customer didn't understand they received better product. Better practice: notify customers proactively about upgrades with explanation. Some customers prefer consistency over "improvement".

Change Log

2026-03-01

  • Initial documentation created
  • All sections completed following template structure

End of Documentation

For additional help, contact your system administrator or Kiva Logic support.