Problem Statement

The platform currently does not support a clear notion of redelivery for missed, failed, or damaged shipments.

When a shipment needs to be sent again, there is no standardized way to:

1. Mark the original fulfillment as requiring redelivery.

2. Identify all subscriptions that need a replacement shipment.

3. Generate a fulfillment list specifically for redeliveries.

4. Track whether the redelivery was completed.

5. Distinguish the replacement shipment from the original fulfillment.

As a result, redeliveries must be managed manually outside the normal fulfillment workflow, increasing the risk of missed requests, duplicate shipments, and inaccurate reporting.

User Story

As an operations administrator,

I want to mark a shipment as requiring redelivery on the subscription details and generate a fulfillment list containing all pending redeliveries,

so that replacement shipments can be processed, tracked, and completed through the standard fulfillment workflow.

Definition of Done

Redelivery Status

1. A fulfillment or shipment associated with a subscription can be marked as requiring redelivery.

2. The redelivery indicator includes a clear status, such as:

3. Redelivery Required

4. Redelivered

5. Redelivery Cancelled

6. SIMILAR TO SHIPMENTS & RETURNS FLOW > SIMILAR TO RETURNS

7. Redelivery reason.

8. Notes.

9. Quantity to redeliver.

10. Original fulfillment reference.

Fulfillment List Filtering

1. Lists can be filtered to show subscriptions/ shipments with a pending redelivery.

2. Administrators can generate a dedicated fulfillment list for all eligible redeliveries.

3. The original fulfillment record remains unchanged for historical accuracy.

4. Approving the replacement fulfillment updates the redelivery request to Redelivered.

5. Should be logged under the sub details the redelivery changes.

Duplicate Prevention

1. Administrators receive a warning or validation message when a replacement fulfillment already exists.