Start-issue Report

✨ Feature Request: Start-Issue Report in Analytics

Affected Components

• API (new analytics/reporting endpoint)

• UI (publisher-facing analytics/report view)

• Data / Reporting layer

• (Optional, future) CSV export / BI integrations

Problem Statement

Publishers lack a Start-Issue Report that shows when subscriptions received in a given month are scheduled to start earning revenue.

Currently, Pelcro analytics focus on order creation and renewals but do not clearly distinguish:

• New orders that start in a future issue/date

• Renewal orders that only begin after the current subscription phase ends

Without a start-issue view, publishers performing circulation modeling and revenue forecasting must estimate subscription start timing, leading to inaccurate projections of earned subscription revenue.

This gap directly impacts financial planning and circulation forecasting for publishers.

User Story

As a publisher,
I want a monthly start-issue report that shows when subscriptions received in that month are scheduled to start,
so that I can accurately model circulation and earned subscription revenue without relying on estimates.

Functional Description

The Start-Issue Report should:

• Be part of the standard Pelcro analytics package (global, not client-configurable)

• Report on orders received within a selected month

• Clearly indicate when each order is scheduled to start earning revenue

• Correctly handle renewal logic, where renewal orders:

  • Do not start immediately

  • Start only after the current subscription phase ends

The report is client-facing, intended for publisher admins responsible for circulation and revenue planning.

Data & Logic Requirements (High-Level)

• Include only orders created within the reporting period

• For each order, determine:

  • order_type (new vs renewal)

  • start_issue or start_date

  • For renewals: calculated start based on current term end

• Ensure logic is consistent with Pelcro’s subscription lifecycle rules

API Expectations (Proposed)

Exact endpoint to be clarified

• New analytics endpoint, e.g.:

  GET /analytics/start-issue-report 

• Filters:

  • order_created_from

  • order_created_to

• Response fields (example):

  • order_id

  • subscription_id

  • order_type (new | renewal)

  • order_created_at

  • start_issue or start_date

  • product / publication

  • term_start_date

  • term_end_date (if renewal)

API must be:

• Documented

• Test-covered

• Usable independently of the UI (API-first)

UI Expectations

• Available in Publisher Analytics

• Monthly report view

• Exportable (CSV at minimum)

• Clear labeling that:

  • Report is based on order creation month

  • Start timing may be in a future issue/month

Definition of Done (DoD)

• A new Start-Issue Report is available in publisher analytics

• Report shows all orders created in a selected month

• Each order includes a calculated start issue/date

• Renewal orders correctly start after current term end

• API endpoint exists, is documented, and covered by automated tests

• UI renders data accurately and matches API output

• CSV export is available

• Logic is validated against real publisher data scenarios

• No client-specific configuration required (global behavior)