> ## Documentation Index
> Fetch the complete documentation index at: https://docs.winedirectfulfillment.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Notification Events

> The shipment notification events WineDirect Fulfillment recognizes, including sequencing and timing rules, so integration partners can align their own consumer messaging with ours.

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.

<Note>
  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.
</Note>

## 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.

| Seq | Event                           | Status   | Description                                                               | Detailed Status Trigger                 |
| --- | ------------------------------- | -------- | ------------------------------------------------------------------------- | --------------------------------------- |
| 1   | Order Created                   | Planned  | Order imported successfully to WineDirect Fulfillment.                    | — (order import)                        |
| 2   | Preparing Shipment              | Planned  | Order sent to the warehouse and preparing to ship.                        | — (order status: Sent to WMS)           |
| 3   | Shipped                         | **Live** | Shipment record created by WineDirect Fulfillment.                        | — (shipment record created)             |
| 4   | First Scan                      | **Live** | Package scanned for the first time by the final-mile carrier.             | — (first carrier scan)                  |
| 5   | Exception                       | **Live** | An exception to delivery that should be reviewed — may need intervention. | `DELIVERY_EXCEPTION` or `ADDRESS_ERROR` |
| 6   | Estimated Delivery Date Updated | Planned  | Carrier changed the estimated delivery date for the package.              | — (EDD change detected)                 |
| 7   | Out for Delivery                | **Live** | Package is out for delivery.                                              | `OUT_FOR_DELIVERY`                      |
| 8   | Failed Attempt – First          | **Live** | First delivery attempt was unsuccessful; a second attempt will be made.   | `FIRST_DELIVERY_ATTEMPT`                |
| 9   | Failed Attempt – Second         | **Live** | Second delivery attempt was unsuccessful; a final attempt will be made.   | `SECOND_DELIVERY_ATTEMPT`               |
| 10  | Available for Pickup            | **Live** | Package is available for pickup at a carrier holding location.            | `AVAILABLE_AT_HAL` or `AVAILABLE_AT_AP` |
| 11  | Delivered                       | Planned  | Package was delivered, or picked up from a carrier hold location.         | `DELIVERED`                             |
| 12  | Returning                       | Planned  | Package is being returned to sender.                                      | `RETURNING`                             |

## Terminology

| Term               | Meaning                                                                                                                                      |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Notification Event | A defined event type — based on a shipment milestone or a carrier-derived status — that can trigger a consumer notification.                 |
| Detailed Status    | A WineDirect Fulfillment–normalized shipment status, derived from raw carrier events, used to detect when a notification event has occurred. |