Introduce Address Delivery Instructions

🔍 Problem Statement

As a fulfillment user, I experience issues where customers’ specific delivery preferences (e.g., “leave at back door” or “place under awning”) cannot be recorded or communicated through the platform, which results in missed or incorrect deliveries and lower customer satisfaction.

💡 User Story

As an end user, I want to add delivery instructions to each shipping address so that fulfillment teams and drivers can follow these preferences accurately during delivery operations.

🎯 Definition of Done (DoD)

✔ Given a shipping address record, when a user edits or creates it, then a new text field called delivery_instructions is available and saved with the address.

✔ This change will impact API, Dashboard UI, and SDKs, specifically:

1. Core API & Open API:

2. POST /addresses and PATCH /addresses/:id must accept a new delivery_instructions field (string, nullable).

3. GET /addresses and GET /addresses/:id must return the field.

4. The field must be fully documented in both the Core API and Open API specifications.

5. Dashboard UI:

6. Add an editable text area labeled Delivery Instructions under shipping address management screens.

7. JS-SDK & ReactJS Elements:

8. Expose delivery_instructions in relevant address methods and UI components to ensure full support for read/write operations.

9. Exports:

10. Include the field in List & Fulfillment exports (CSV/Excel).

11. Webhooks:

12. Include delivery_instructions in address.created and address.updated payloads only (excluded from fulfillment events).

✔ This solution will include the following limitations:

1. Only available for shipping addresses, not billing addresses.

2. Character limit: 500 characters max.

3. Not required; field is optional.

4. Field is text only, no formatting or attachments supported.