How to Set up and Manage Shipment Alerts?
Overview
Shipment Alerts lets you proactively monitor unusual happening in logistics operations. Instead of waiting for weekly or monthly reports, you can track important shipping metrics like delays, lost packages, or abnormal shipment patterns and set up rules to trigger real-time notifications. This will help your team respond quickly, minimize disruption, and keep customers informed.

What you’ll learn
In this article, we will show you:
- Step 1: Define alert conditions
 - Step 2: Preview with data + AI insights
 - Step 3: Configure notifications
 - Step 4: Set check time and frequency
 - Step 5: Enable rule
 
- How to manage alert rules
 - View alert history
 - What to do after an alert triggers
 - Best practices for using shipment alerts
 - Recommended alert rules to create
 - Key takeaways
 - FAQs
 
How to set up shipment alerts
Follow the steps below to set up the rules that will trigger your alert:
Step 1: Define alert conditions
- Go to Settings > Shipment alerts.
 

- Choose a pre-built rule or create a custom rule.
 

- Configure your rule:
 
a. Apply filters: Focus on specific carriers, destinations, stores, vendors, issues, or shipment statuses.

b. Choose a metric: Select the available metric that you want to monitor, such as:
- Number of shipments
 - Percentage of exceptions
 - Delivery rate
 - On-time or early rate
 - EDD coverage
 - Average transit time
 - Average order-to-delivery time
 - Average processing time
 - Average pickup time
 - Pending rate
 
c. Set a condition: Use operators like “greater than,” “less than,” or “relatively increased by” to define when alerts should trigger.
Example: Trigger an alert if the average transit time for Carrier X is greater than 5 days in the last 7 days.

Operator types and example
Operator  | Description  | Example condition  | 
|---|---|---|
General operator ↓  | 
  | 
  | 
Is equal to  | Triggers when the metric value exactly matches the threshold.  | On-time or early rate is equal to 95% in the last 7 days.  | 
Is between  | Triggers when the metric value falls within a defined range.  | Average transit time is between 3 and 5 days in the last 14 days.  | 
Is greater than  | Triggers when the metric value is higher than a set threshold.  | The number of shipments is greater than 50,000 in the last 7 days.  | 
Is less than  | Triggers when the metric value is lower than a set threshold.  | The delivery rate is less than 90% in the last 14 days.  | 
Is greater than or equal to  | Triggers when the metric value meets or exceeds the threshold.  | Pending rate is greater than or equal to 5%.  | 
Is less than or equal to  | Triggers when the metric value is at or below the threshold.  | Average pickup time is less than or equal to 2 days.  | 
Comparison operator (vs. previous period) ↓  | 
  | 
  | 
has absolutely increased by  | Compares the current value to the previous X-day period and triggers when the increase in the actual number exceeds the threshold.  | The number of shipments has absolutely increased by 20,000 compared to the previous 7 days.  | 
has absolutely decreased by  | Triggers when the absolute decrease exceeds the threshold.  | Exception shipments have absolutely decreased by 5,000 compared to the previous 7 days.  | 
has relatively increased by  | Compares percentage change between periods and triggers when the relative increase exceeds the threshold.  | On-time rate has relatively increased by 10% compared to the previous 14 days.  | 
has relatively decreased by  | Triggers when the relative (percentage) decrease exceeds the threshold.  | Average transit time has relatively decreased by 15% compared to the previous 30 days.  | 
How do comparison periods work
When using comparison operators, the system compares the “last X days” period to a previous period (Y days) that you define in the alert condition. Know how it works:
Current period  | Previous period  | Example  | 
|---|---|---|
Last 7 days  | Previous 7 days  | Compare shipments created Oct 20–26 vs Oct 13–19  | 
Last 7 days  | Previous 14 days  | Compare shipments created Oct 20–26 vs Oct 6–19  | 
Absolute vs. Relative difference
Type  | What it measures  | Formula  | Example  | 
|---|---|---|---|
Absolute difference  | The raw numerical change between current and previous values.  | Current - previous  | If shipments increased from 100,000 to 120,000, the absolute increase is 20,000.  | 
Relative difference  | The percentage change relative to the previous value.  | (Current – Previous) / Previous × 100%  | If shipments increased from 100,000 to 120,000, the relative increase is 20%.  | 
Step 2: Preview with data + AI insights
Before turning on your alert, preview how it will behave using data and AI insights:
- Historical trend chart: Displays how your chosen metric performed over the last 60 days.
 
- Threshold overlay: Shows your selected threshold directly on the chart, highlighting where the condition would have been met.
 - AI insights: Get clear explanations about key trends, anomalies, and typical ranges for better accuracy. It also suggests how to adjust your alert settings, whether it's triggering too often or rarely triggering to maintain the right balance.
 
Example: “Average transit times are usually between 2–3 days. With your threshold of 2.5, the rule would have triggered 12 times in the past 30 days. Consider adjusting it to reduce false alerts.”

Step 3: Configure notifications
Configure notifications to decide where you want to be notified when alerts trigger.
- In-app alerts: View alerts directly on the home page Alert section.
 - Email notifications: Add recipients to receive alert summaries and quick access links to the details.
 

Step 4: Set check time and frequency
Choose how often the system should check your alert conditions:
- Daily: At a fixed time each day (e.g., 10:00 AM).
 - Weekly: On a selected day and time (e.g., Monday at 9:00 AM).
 - Monthly (date-based): On a specific date (e.g., 1st of the month, 2:00 PM).
 - Monthly (week-based): On a weekday in a specific week (e.g., last Friday at 5:00 PM).
 

Step 5: Enable rule
Turn on the alert rule to start monitoring:
- Click Save to successfully create the rule.
 - Toggle Enable alert rule to activate the configurations.
 - Once enabled, the system will automatically check based on the defined schedule.
 - Review your rules periodically and update them as per your business requirements.
 
How to manage alert rules
You can manage all your alert rule configurations from the Alert Rules Management list.
- View all rules: See all active rule names, types, conditions, notification channels, and check frequency (next scheduled) in one place.
 - View rule details: Open a single rule to review its current conditions, preview the chart with historical data, and trigger history.
 - Edit rules: Update conditions, thresholds, recipients, or notification frequency anytime for changing business needs.
 - Pause rules: Temporarily stop a rule without deleting it. Paused rules remain inactive in the list but won’t trigger until re-enabled.
 - Delete rules: Permanently remove unwanted rules. However, this cannot be undone; you cannot recover them.
 

View alert history
Each time a rule’s conditions are met, the system generates an alert notification. All triggered alerts are saved in your Alert History Log. You can:
- Triggered alerts: Review a list of past alerts, including date/time, trigger rule, and affected shipment details.
 - Notification channels: See which notification channels (email or in-app) were used to deliver notifications.
 

What to do after an alert triggers
You can take the following actions when an alert is triggered:
Review alert details:
- Check when and why the notification is triggered.
 - View the metric value.
 - Use the historical chart and AI insights to understand context, trends, and anomalies.
 
Investigate affected shipments:
- Click View shipments in the notification to open the pre-filtered list.
 - Check shipment statuses, identify problem carriers, and take corrective action.
 
Best practices for using shipment alerts
1. Start with business-critical metrics
- Focus on important KPIs that directly impact customer experience or operational visibility, like shipment import volume, on-time/early delivery rate or average transit time.
 - Avoid setting up too many low-impact alerts, which can reduce focus on critical issues.
 
2. Use AI and historical data for a realistic threshold
- Leverage the AI preview panel to analyze past performance trends before setting thresholds to avoid unnecessary alerts.
 
3. Validate with “what-if” simulation
- Use the data preview to see how often your rule would have triggered in the past.
 - Adjust thresholds to strike the right balance. Such that the rule is sensitive enough to catch real issues but not too sensitive that it sends too many false alerts.
 
4. Use the right notification channel
- Use the in-app Alert section for ongoing monitoring and visibility.
 - Reserve email notifications for urgent alerts that require immediate attention and escalation.
 
5. Review and adjust regularly
- Revisit and adjust rules as business conditions evolve, such as busy seasons, new carriers, or updated SLAs. Keep alerts accurate, relevant, and actionable.
 
Recommended alert rules to create
To get the most out of shipment alerts, focus on rules that catch the most common and business-critical logistics risks:
Alert type  | Why it matters  | Example configuration  | 
|---|---|---|
AI Volume anomaly (drops/spikes)  | Unusual drops or surges in shipment volume may signal operational disruptions (e.g., import delays, system sync failures, or demand spikes).  | 
  | 
AI Delivery delay spike  | Detects sudden increases in transit time that risk SLA violations and customer trust.  | 
  | 
AI Lane-level anomaly  | Identifies specific lanes where transit time performance deviates from historical norms (e.g., customs delays on US → EU shipments).  | 
  | 
AI Clustered exception anomaly  | Flags an unusual concentration of exceptions in a region, often an early sign of systemic disruption.  | 
  | 
Shipments missing the first scan  | Detects shipments stuck in “Info received” without a first in-transit scan, often signaling pickup or data issues.  | Shipment status is “Info received”, and the last update date is not in the last 2 days  | 
Stuck shipment risk  | Identifies shipments in transit with no movement for extended periods, signaling possible delays or loss.  | Shipment status is “In transit”, and the last update date is not within the last 2 days  | 
On-time delivery drop  | On-time delivery indicates delivery reliability from the customer’s perspective, crucial for satisfaction and retention.  | On-time or early delivery rate < 85% in the last 7 days  | 
Return to sender shipment spike  | A sudden increase in returns indicates fulfillment errors, address issues, or carrier problems.  | Return-to-sender shipments have relatively increased by 30% compared to the previous 7 days  | 
Lost shipment risk  | Early detection of lost packages reduces customer impact and claims cost.  | Lost shipments > 100 in the past 2 days  | 
Carrier performance anomaly  | Detect underperforming carriers proactively by comparing their performance against the SLA  | Carrier X on-time rate <80% (based on Carrier EDD)  | 
Data quality issue (EDD coverage gap)  | Ensures the Estimated Delivery Date (EDD) is consistently provided, critical for customer communication.  | EDD coverage < 80% in the last 7 days  | 

Key takeaways
- Set up shipment alerts for key logistics issues like delays, exceptions, or stuck shipments.
 - Use filters, metrics, and thresholds to define alert conditions that matter most to your operations.
 - Leverage AI insights and preview historical data to optimize thresholds and reduce false alerts.
 - Get real-time alerts through in-app (Tracking homepage) notifications or emails based on urgency.
 - View, edit, pause, or delete alert rules anytime from the Alerts Management dashboard.
 - Regularly review and adjust rules as business needs, carriers, or SLAs change.
 
FAQs
1. How to create a new shipment alert rule?
- Go to Settings > Shipment Alert.
 - Click Create alert rule.
 - Assign a name for the rule and description.
 - Apply filters to be more specific about a carrier, destination, etc.
 - Set appropriate trigger conditions.
 - Choose a notification channel and set up a schedule.
 - Click Save and enable the rule to make it active.
 
Updated on: 03/11/2025