Fulfillment Returns

🔍 Problem Statement

Pelcro Billing Agent currently lacks a dedicated mechanism to log, manage, and validate returns related to physical fulfillments. Without this, collaborators cannot track returned quantities, enforce delivery constraints, or audit historical return records.

💡 User Stories

1. As a Pelcro collaborator, when I process a return from a subscription’s fulfillment record, a new entry must be created in a returns table linked to the related shipment.

2. As a Pelcro collaborator, I must not be able to return more items than were delivered in the original shipment.

3. As a Pelcro collaborator, I should be able to view all returns associated with a specific shipment in a dedicated section under the fulfillment table in the subscription view.

✅ Definition of Done (DoD)

Platform

1. A “Process Return” button to trigger the return creation modal. Every fulfillment record on the fulfillment table must have 3 dots where if clicked, you can click on Process Return.

2. Prevent users from inputting a return quantity greater than the available amount.

3. Add a “Returns” section under Subscription > Fulfillments.

4. Table content: Return quantity, reason, and creation date.

5. Database migration for returns table implemented and linked to shipments.

6. UI includes Returns section with create/view functionality.

7. Unit and integration tests validate:

8. Over-return prevention logic.

9. Correct return record creation and retrieval.