Vendor-Based Fulfillment Segmentation (Platform UI)

🧩 Problem Statement

Publishers delivering newspapers via internal carriers (vendors — e.g., drivers) assign a vendor to delivery addresses.

Currently, Pelcro does not allow flexible segmentation of fulfillments by vendor, nor does the platform-generated fulfillment file clearly structure output by vendor and delivery sequence.

This creates manual operational work when coordinating vendor-based deliveries.

👤 User Story

As a publisher operations manager,

I want to filter lists and fulfillments by vendor,

so that I can generate vendor-specific delivery runs directly from the platform.

As a delivery coordinator,

I want the generated fulfillment file to include vendor name and be ordered by delivery sequence and vendor,

so that operational routing is efficient.

🏗 Proposed Solution

1️⃣ List Builder Enhancements

In List Builder, allow filtering on:

1. vendor (dropdown selector of existing vendors)

2. vendor = null (unassigned addresses)

3. vendor ≠ null (any assigned vendor)

Filtering applies at the Address object level.

2️⃣ Platform Fulfillment File Enhancement

When generating a fulfillment from the Platform UI:

Include Columns:

1. vendor_name

2. delivery_sequence_number

🔌 API Requirements

1. List queries must support filtering by:

2. vendor_id

3. vendor_id = null

4. Fulfillment generation must include:

5. vendor_name

6. delivery_sequence_number

7. Fields must be exposed in fulfillment response payload

✅ Definition of Done (DoD)

✔ List Builder supports filtering by vendor

✔ Can filter for unassigned vendors (null)

✔ Platform-generated fulfillment file includes vendor name

✔ Platform-generated fulfillment file includes delivery sequence number

✔ Fulfillment ordered by sequence ASC, then vendor ASC

✔ API documentation updated

✔ QA validated using:

1. Multiple vendors

2. Mixed assigned/unassigned addresses

3. Mixed sequence values

📊 Business Impact

1. Enables operational vendor segmentation directly in Pelcro

2. Reduces manual spreadsheet sorting

3. Supports scalable newspaper distribution workflows

4. Complements delivery sequence feature