Driver Delivery Sequence Number

🧩 Problem Statement

Publishers delivering newspapers via internal drivers (not USPS) require a structured delivery order per address.

Pelcro currently has no field to store a delivery sequence number, making it impossible to preserve or manage route order within the platform or during migration.

Publishers must manage delivery order externally, creating operational inefficiencies.

👤 User Story

As a publisher operations manager,

I want to assign a driver delivery sequence number to an address,

so that delivery order can be preserved and included in fulfillment exports.

As a publisher migrating to Pelcro,

I want to import this sequence number via API,

so existing driver routes are not disrupted.

🏗 Proposed Solution

Add a new field to the Address object:

delivery_sequence_number

Field Specifications

1. Type: Integer

2. Nullable: Yes

3. Validation: Must be ≥ 1 if set

4. No enforced uniqueness

🔌 API Requirements

1. Field available in:

2. POST /addresses

3. PUT /addresses/{id}

4. GET /addresses/{id}

5. Import / migration endpoints

6. Included in API responses

7. Fully documented in API schema

🖥 Admin UI Requirements

1. Add numeric input field in Address Edit View

2. Label: Driver Delivery Sequence

3. Validation: Integer ≥ 1

4. Editable from platform

📦 Fulfillment Export Update

1. Add a new column in print fulfillment exports:

   delivery_sequence_number

2. No change to default export sorting logic.

3. If value is null, export cell remains empty.

✅ Definition of Done (DoD)

✔ Address object includes delivery_sequence_number

✔ Editable via Admin UI

✔ Create/update via Core API

✔ Supported in migration imports

✔ Visible as a column in fulfillment export

✔ API documentation updated

✔ QA validated on staging