Shipping Deadline Alerts
Shipping Deadline Alerts
Shipping deadline alerts are Watcher’s core workflow. SellerOps evaluates due alerts every minute and sends escalating reminders before each order’s dispatch deadline.
Alert Stages
| Alert | Timing | Priority | Watcher (Live) | Defender Routing (When Enabled) |
|---|---|---|---|---|
| T-24 | 24 hours before deadline | 1 | Can route to Slack; quiet-hours suppression can apply to non-critical channel routing | |
| T-12 | 12 hours before deadline | 2 | Can route to Slack; quiet-hours suppression can apply to non-critical channel routing | |
| T-4 | 4 hours before deadline | 3 | Critical path; quiet-hours suppression does not apply to T-4 |
How Trigger Times Are Calculated
For each eligible order, SellerOps stores three due timestamps:
t24_due_at = dispatch_by_at - 24ht12_due_at = dispatch_by_at - 12ht4_due_at = dispatch_by_at - 4h
The alert runner processes due alerts every minute and sends only the most urgent due tier (T-4 > T-12 > T-24).
Order Eligibility
Alert processing is limited to dispatch-sensitive open statuses:
AWAITING_SHIPMENTAWAITING_COLLECTIONPARTIALLY_SHIPPING
Additional incoming aliases (for example TO_SHIP, PENDING_SHIPMENT, READY_TO_SHIP) are normalized into the supported open-status set.
Duplicate Prevention
Each stage is sent at most once per order, tracked by t24_sent_at, t12_sent_at, and t4_sent_at.
Quiet Hours
Quiet-hours controls are part of Defender routing. For suppressed windows, SellerOps keeps email as the baseline path and suppresses extra non-critical routing channels; T-4 remains unsuppressed.
Countdown Timers
Countdown timers on dashboard and order pages update continuously in the UI while order records refresh on polling intervals.
Order list views currently display an auto-refresh indicator of 5 minutes.