Skip to main content
WineDirect Fulfillment tracks every shipment through a defined set of notification events — lifecycle milestones and carrier-derived status changes that determine when a consumer notification is sent. This page documents that event model so integration and marketplace partners can align their own notification triggers and timing with ours, rather than running an independent (and potentially conflicting) set.
Following this model is not required, but strongly recommended. When a partner’s own notifications use different triggers or timing than WineDirect Fulfillment’s, the same shipment can generate conflicting or duplicate-feeling messages for the end consumer — for example, an “out for delivery” text arriving from one system well before or after the corresponding email from the other.

​
How Events Are Sequenced

Events happen in a defined order, and two rules govern which notification actually reaches the consumer when more than one applies in the same window:
  • Last event wins. If a shipment produces more than one applicable event in the same processing window, only the latest event in the sequence is sent. For example, if both First Scan and Out for Delivery occur in the same window, only Out for Delivery is sent.
  • Delivered is final. Once a Delivered event has been recorded for a shipment, no further notifications are sent for it — this keeps late or noisy carrier updates from generating confusing messages after the consumer has already received their order.

​
Notification Event Reference

The table below lists each event in sequence order, with a plain-language description, the detailed carrier status that triggers it (where applicable), and whether it’s live today. Status of “Planned” means the event is on WineDirect Fulfillment’s roadmap but does not fire yet — partners shouldn’t build against it until it moves to Live.

​
Terminology