Fair Queue Settings
Control how notifications are sent to ensure fair distribution and prevent inventory rushes
Show all sections (42)
- Inventory Rush Scenario
- How Fair Queue Works
- Batch Processing
- Automatic Pause
- Configuring Fair Queue
- Access Settings
- Basic Settings
- Default Configuration
- Choosing the Right Settings
- Small Restocks (< 50 units)
- Medium Restocks (50-200 units)
- Large Restocks (200+ units)
- High-Demand/Limited Items
- Advanced Strategies
- Priority Queue (Coming Soon)
- Product-Specific Settings (Manual)
- Time-of-Day Optimization
- Monitoring Queue Performance
- Queue Dashboard
- Notification History
- Real-World Examples
- Example 1: Fashion Boutique
- Example 2: Electronics Store
- Example 3: Limited Edition Drops
- Best Practices
- Start Conservative
- Monitor Conversion Rates
- Communicate the Policy
- Test Before Launch
- Review Monthly
- Disabling Fair Queue
- When to Disable
- How to Disable
- Troubleshooting
- Queue Not Processing
- Queue Too Slow
- Queue Too Fast
- FAQ
- Next Steps
Fair Queue controls how notifications are distributed when products restock. Instead of notifying everyone at once, it sends emails in controlled batches—giving all customers a fair chance to purchase.
What you'll accomplish
- Understand why Fair Queue exists and what problem it solves
- Configure batch size and interval for your inventory patterns
- Monitor queue performance and adjust settings over time
Requirements
- Plan: Free plan or higher (Fair Queue is available on all plans)
- Access: DemandLoop dashboard access
- Prerequisite: At least one active subscription so you can observe queue behavior
The Problem Without Fair Queue
Inventory Rush Scenario
Situation: 200 customers waiting, 20 units restocked
Without Fair Queue:
10:00 AM - All 200 customers notified simultaneously
10:02 AM - First 50 customers rush to store
10:05 AM - All 20 units sold
Result:
+ 20 happy customers
- 180 disappointed customers (notified but product already gone)
- Potential negative reviews
- Frustrated customers unsubscribe
With Fair Queue:
10:00 AM - First 20 customers notified
12:00 PM - Next 20 customers notified
Result:
+ 20 happy customers (purchased)
+ 20 customers notified but not disappointed (stock sold before their turn)
+ 160 customers still waiting for next restock (not disappointed)
+ Fair distribution maintained
How Fair Queue Works
Batch Processing
Notifications are sent in batches instead of all at once.
Key settings:
Batch Size - How many customers per batch
Batch Interval - Time between batches
Example configuration:
Batch Size: 10 customers
Batch Interval: 2 hours
Timeline:
10:00 AM - First 10 customers notified
12:00 PM - Next 10 customers notified
2:00 PM - Next 10 customers notified
4:00 PM - Next 10 customers notified
...continues until all notified or stock runs out
Automatic Pause
Smart inventory tracking:
When inventory reaches zero, the queue automatically pauses:
- Remaining subscribers stay in queue
- No more notifications sent
- Queue resumes when product restocks again
Example:
Subscribers: 50 customers
Inventory: 15 units
Queue: Batch size 10, interval 2 hours
10:00 AM - Notify first 10 customers
10:30 AM - 8 units sold (7 remaining)
12:00 PM - Notify next 10 customers
12:45 PM - 7 units sold (0 remaining)
Queue PAUSES - 30 remaining customers NOT notified
Next Week:
Inventory: 25 units added
Queue RESUMES - Continue notifying remaining 30 customers
Configuring Fair Queue
Access Settings
Go to: Notifications → Fair Queue Settings
Basic Settings
Enable/Disable Fair Queue
- Toggle ON: Notifications sent in batches (recommended)
- Toggle OFF: All notifications sent immediately
Batch Size
Recommended: 10-20 customers per batch
Minimum: 5 customers
Maximum: 100 customers
Batch Interval
Recommended: 1-4 hours between batches
Minimum: 30 minutes
Maximum: 24 hours
Default Configuration
When you first install DemandLoop:
Fair Queue: Enabled
Batch Size: 10 customers
Batch Interval: 2 hours
These defaults work well for most stores.
Choosing the Right Settings
Small Restocks (< 50 units)
Recommended:
Batch Size: 10 customers
Batch Interval: 2 hours
Why: Gives each batch enough time to purchase before next batch arrives.
Example:
Restock: 30 units
Subscribers: 100 customers
Result: First 3 batches (30 customers) get notified
Remaining 70 customers wait for next restock
Medium Restocks (50-200 units)
Recommended:
Batch Size: 20 customers
Batch Interval: 3 hours
Why: Faster notification with still-fair distribution.
Example:
Restock: 100 units
Subscribers: 200 customers
Result: 5 batches over 15 hours
~100 customers notified
Stock likely sells out before all notified
Large Restocks (200+ units)
Recommended:
Batch Size: 50 customers
Batch Interval: 4 hours
Why: High confidence you have enough stock for all subscribers.
Example:
Restock: 300 units
Subscribers: 150 customers
Result: 3 batches over 8 hours
All 150 customers notified
Stock remaining for walk-in customers
High-Demand/Limited Items
Recommended:
Batch Size: 5 customers
Batch Interval: 1 hour
Why: Maximum fairness, everyone has equal chance.
Example:
Product: Limited Edition Sneakers
Restock: 25 pairs
Subscribers: 500 customers
Result: 5 batches (25 customers) notified
Each batch has great chance to purchase
Remaining 475 customers not falsely alerted
Advanced Strategies
Priority Queue (Coming Soon)
VIP customers first:
Tier 1: VIP customers (first 2 batches)
Tier 2: Repeat customers (next 5 batches)
Tier 3: New customers (remaining batches)
Currently all customers are treated equally (first-come, first-served).
Product-Specific Settings (Manual)
Different settings for different products:
Example:
Regular T-Shirt (restocks weekly):
Batch Size: 50
Interval: 6 hours
Limited Hoodie (restocks monthly):
Batch Size: 5
Interval: 1 hour
How to implement: Contact support for custom configuration.
Time-of-Day Optimization
Best times to send notifications:
- Morning: 8-10 AM (high open rates)
- Evening: 6-8 PM (high conversion)
- Night: 11 PM-6 AM (low engagement, avoid)
Current behavior: Batches send regardless of time
Workaround: Set batch interval to align with business hours
Example:
Restock detected at 11 PM
Batch Interval: 10 hours
First batch: 9 AM next day (perfect timing)
Monitoring Queue Performance
Queue Dashboard
Go to: Notifications → Fair Queue
What you'll see:
- Active queues (products currently notifying)
- Customers notified vs remaining
- Next batch send time
- Estimated completion time
Example display:
Product: Premium Hoodie - Black / Large
Queue Status: Active
Notified: 30 of 120 customers (25%)
Next Batch: 2:00 PM (in 45 minutes)
Estimated Completion: 8:00 PM (6 hours)
Notification History
Go to: Subscriptions → Notification History
Filter by:
- Date range
- Product
- Batch number
Use this to:
- Verify batches are sending
- Check conversion rates per batch
- Identify optimal batch sizes
Real-World Examples
Example 1: Fashion Boutique
Store: Small fashion boutique
Product: Designer jeans (popular item)
Challenge: Limited inventory (10-30 units per restock)
Configuration:
Batch Size: 5 customers
Batch Interval: 1 hour
Results:
- 95% of notified customers purchase
- Very few "sold out" complaints
- Customers feel they have fair chance
Example 2: Electronics Store
Store: Tech accessories
Product: Phone cases (regular restocks)
Challenge: High volume (100-200 units per restock)
Configuration:
Batch Size: 30 customers
Batch Interval: 3 hours
Results:
- All subscribers notified within 24 hours
- Inventory almost always sufficient
- Fast notification cycle = happy customers
Example 3: Limited Edition Drops
Store: Streetwear brand
Product: Limited sneakers (monthly drops)
Challenge: Extreme demand (1000+ subscribers, 50 units)
Configuration:
Batch Size: 5 customers
Batch Interval: 30 minutes
Results:
- 50 customers notified over 5 hours
- Each batch has high purchase rate
- Remaining 950 customers not disappointed
- Fair perception maintained
Best Practices
Start Conservative
First time setup:
Batch Size: 10 customers
Batch Interval: 2 hours
Monitor performance for 2-3 restocks, then adjust.
Monitor Conversion Rates
Track these metrics:
- Notifications sent vs purchases made
- Inventory remaining after queue completes
- Customer complaints about "sold out"
Adjust based on data:
- High conversion (>50%) → Increase batch size
- Low inventory remaining → Decrease batch size
- Many complaints → Decrease batch size or interval
Communicate the Policy
Add to FAQ:
Q: Why didn't I get notified immediately?
A: We use a fair queue system to ensure everyone has
an equal chance to purchase limited items.
Notifications are sent in batches over several hours.
Benefits of transparency:
- Customers understand delays
- Reduces support inquiries
- Builds trust in fairness
Test Before Launch
Before enabling Fair Queue:
- Set up configuration
- Use test product with controlled inventory
- Subscribe test emails
- Monitor batch sends
- Verify timing and behavior
- Adjust settings if needed
Review Monthly
Set calendar reminder to:
- Check queue performance metrics
- Review customer feedback
- Adjust settings based on inventory patterns
- Test different configurations seasonally
Disabling Fair Queue
When to Disable
Consider disabling if:
- You always have abundant inventory
- Products restock very frequently (daily)
- Customer base is small (< 100 subscribers)
- Speed is more important than fairness
Example scenario:
Store: Grocery delivery app
Product: Organic milk
Restock: Daily, 500 units
Subscribers: 50 customers
Decision: Disable Fair Queue (plenty of stock)
How to Disable
- Go to Notifications → Fair Queue Settings
- Toggle "Enable Fair Queue" to OFF
- Save changes
Behavior after disabling:
- All notifications sent immediately when product restocks
- No batching or delays
- First-come-first-served (fastest customers win)
Troubleshooting
Queue Not Processing
Problem: Batches not sending
Check:
- Fair Queue enabled in settings
- Product actually restocked (inventory > 0)
- Subscribers exist for the product
- No Shopify API issues (check status page)
Solution:
- Manually trigger queue from dashboard
- Check system status
- Contact support if issue persists
Queue Too Slow
Problem: Taking too long to notify all customers
Current settings:
Batch Size: 10
Batch Interval: 4 hours
Subscribers: 200
Time: 80 hours (3+ days!)
Solution:
Increase batch size to 25
Reduce interval to 2 hours
New time: 16 hours (much better)
Queue Too Fast
Problem: Inventory selling out before queue completes
Current settings:
Batch Size: 50
Batch Interval: 1 hour
Inventory: 30 units
Result: First batch buys everything
Solution:
Decrease batch size to 10
Increase interval to 2 hours
Better distribution across more batches
FAQ
Q: Can I pause an active queue?
Yes. Go to Notifications → Fair Queue → Find active queue → Click "Pause."
Q: Can I manually trigger the next batch?
Yes. Go to active queue → Click "Send Next Batch Now."
Q: What if product sells out mid-queue?
Queue automatically pauses. Remaining subscribers stay queued for next restock.
Q: Do I need Fair Queue if I have unlimited inventory?
No. If you always have 100+ units, you can disable Fair Queue and notify everyone immediately.
Q: Can I prioritize certain customers?
Not currently. All customers are treated equally (first-come-first-served by subscription date).
Q: Does Fair Queue work with preorders?
No. Preorders don't use Fair Queue since all customers can purchase immediately (no inventory limits).
Q: Can I see which customers are in which batch?
Yes. Go to Notifications → Fair Queue → View Queue → See batch assignments.
Next Steps
- How Notifications Work - Understand notification flow
- Email Templates - Customize notification content
- Understanding Analytics - Track queue performance
Was this article helpful?
Let us know — your feedback helps us improve our documentation.