Order Count Tracker Documentation¶
Menu Location: Reports > Order Count Tracker
Access Level: Manager and above
Last Updated: 2026-03-01
Overview¶
Order Count Tracker logs order volume at regular intervals (typically every 10 minutes), creating a historical record of order activity throughout each day. This data helps identify peak ordering times, measure marketing campaign impact, and optimize staffing.
Primary Functions:
- Track order count every 10 minutes
- Create historical order volume data
- Identify peak ordering times
- Measure marketing campaign effectiveness
- Optimize operations scheduling
- Monitor order volume trends
Page Layout¶
Filters:
- Date range selector
- Time of day filters
- Chart vs. table view toggle
Display:
- Line chart showing order volume over time
- Table with timestamp and order count
- Summary statistics (total orders, peak time, average)
Data Collected¶
Logged Every 10 Minutes:
- Timestamp
- Total order count at that moment
- New orders since last check
- Order delta (increase/decrease)
Useful Metrics:
- Hourly order patterns
- Day of week trends
- Marketing campaign spikes
- Seasonal volume changes
- Growth over time
Common Use Cases¶
Use Case 1: Identify Peak Ordering Times¶
Goal: Determine when customers place most orders.
Analysis:
- Select last 30 days
- Group data by hour of day
- Identify peak times (e.g., 10 AM and 7 PM)
- Use to schedule customer service availability
Use Case 2: Measure Email Campaign Impact¶
Goal: See if email blast drove orders.
Steps:
- Note email send time (e.g., sent at 9 AM Tuesday)
- View order count tracker for that day
- Look for order spike 30-120 minutes after send
- Compare to baseline Tuesday volume
- Quantify campaign's order impact
Use Case 3: Staff Customer Service¶
Goal: Optimize CS staffing for order volume.
Approach:
- Analyze typical weekday patterns
- Identify 2-4 PM as peak support time
- Schedule more CS reps during those hours
- Reduce staffing during slow periods (e.g., late evening)
Use Case 4: Monitor Flash Sale¶
Goal: Track order surge during limited-time promotion.
Actions:
- Note sale start time (12 PM noon)
- Watch order count in real-time
- See orders jump from 5/10min to 50/10min
- Ensure systems handling load
- Measure total orders during sale period
Use Case 5: Identify System Issues¶
Goal: Detect if ordering stopped working.
Alert: Normal 10 AM sees 20 orders/10 min, today showing 0.
Investigation:
- Check if website down
- Verify payment processing working
- Check for checkout errors
- Fix technical issue quickly
Analysis & Reporting¶
Useful Reports:
- Peak Times: When do most orders occur?
- Day of Week: Which days see highest volume?
- Campaign Impact: Order spike after marketing push?
- Growth Trends: Are orders increasing month-over-month?
- Seasonal Patterns: Holiday rush vs. slow periods?
Export Options:
- CSV download for Excel analysis
- Chart image for presentations
- Data API for custom dashboards
Interpreting Data¶
Normal Patterns:
- Gradual build throughout morning
- Peak midday or early evening
- Taper off at night
- Weekend patterns differ from weekdays
Unusual Patterns:
- Sudden spike: Marketing campaign, media mention, or viral social post
- Sudden drop: Technical issue, site down, payment processing problem
- Sustained high: Flash sale, holiday rush, successful campaign
- Sustained low: Off-season, customer service issue, competitive pressure
When to Investigate:
- Zero orders during normally busy period
- Unexpected large spike (verify not spam/fraud)
- Declining trend over weeks
- Pattern disruption without known cause
Best Practices¶
- Review weekly - Check patterns regularly to spot trends
- Correlate with events - Note marketing campaigns, holidays, PR
- Set baselines - Know "normal" for each day/time
- Alert on anomalies - Flag significant deviations
- Use for planning - Base inventory, staffing, promotions on patterns
Quick Reference Card¶
| Task | Action |
|---|---|
| View today's orders | Select today in date filter |
| Compare to last week | Select same day last week |
| See campaign impact | Filter to campaign send time |
| Export data | Click Export CSV button |
| View peak times | Look for highest points on chart |
| Check real-time | Most recent datapoint shows current rate |
FAQs¶
How often is data logged?¶
Every 10 minutes. Data collected 24/7/365.
How long is data retained?¶
Typically 12-24 months. Older data may be archived or aggregated.
Can I see individual orders?¶
No, this tracks counts only. For individual orders, use Orders page.
Why would order count decrease?¶
If orders cancelled or deleted. Most timestamps show flat or increasing counts.
Can I set alerts for low/high order volume?¶
Depends on system. Contact Kiva Logic about automated alerting.
Is this real-time?¶
Near real-time (10-minute delay). For instant counts, use Orders dashboard.
End of Documentation
For additional help, contact your system administrator or Kiva Logic support.