Subscription Start-Date Override (Platform + API)

It would be VERY helpful to be able to select a start date when either adding a new subscription or renewal. For instance, another box on the ‘pricing’ screen when setting up the renewal or subscription to select a start date for the subscription would be the most convenient space. I understand I have the option of delaying shipments which I have been using, but when I do this, it does not reflect in the subscription period. The subscription period still says the original start and end date which leads me to having to manually edit each individual invoice. Very tedious. On top of that, the data is out of sync. Can this be addressed soon please?

Thank you

Problem Statement

Clients require a reliable mechanism to retroactively align subscription periods for shipment-based plans. Historically, teams used a workaround by shortening a subscription’s end date to simulate an earlier start date. This method is now blocked due to platform restrictions introduced to enforce correct revenue-recognition behavior for time-based subscriptions.

Because no alternative mechanism exists for shipment-based plans, clients cannot:

• Align subscription windows to institutional or seasonal cycles (e.g., Jan–Dec).

• Issue retroactive shipments when subscribers should receive earlier issues.

• Correct timelines when renewals occur late but entitlements should begin earlier.

Shipment-based plans do not follow time-based revenue recognition and often do not auto-renew, so allowing controlled end-date shortening poses no revenue risk. The absence of this capability interrupts fulfillment workflows, causes inaccurate subscription histories, and creates operational overhead for multiple clients.

This enhancement is required across the platform, not for a single client.

User Story

As an operations or fulfillment administrator,
I need the ability to shorten a subscription’s end date when the plan uses shipment-based revenue recognition,
so that I can retroactively align the subscription period with the correct entitlement timeline without violating revenue-recognition rules for time-based plans.

Definition of Done (DoD)

The platform must restore controlled end-date shortening only for qualifying subscriptions, with guardrails to protect renewal logic and revenue rules.

Functional Requirements

1. Eligibility Logic

   • End-date shortening is allowed only for subscription plans using shipment-based revenue recognition.

   • Ignore prior notions of Group Owner vs Group User; only plan’s revenue-recognition type matters.

   • Backdating/shortening is not permitted for time-based plans.

2. Guardrails

   • Operation is allowed only if the subscription is not scheduled to auto-renew.

     • Condition: Subscription must either be cancelled at period end or have no renewal action scheduled.

   • Operation is blocked if:

     • The subscription has an active auto-renewal setting.

     • A scheduled renewal phase exists.

     • Any future invoice/renewal event is tied to the current end date.

3. Behavior

   • Shortening the end date updates the subscription period but must not automatically generate missed shipments.

   • Shipment creation remains entirely under client operational workflows.

4. UI Labeling / Messaging (minimal requirement)

   • In any UI surface where end-date modification is enabled, the action must clearly state:
     “Available only for shipment-based revenue recognition plans.”

5. Platform Consistency

   • Feature is delivered as a general platform enhancement, not client-specific.

   • Applies across all environments once released.

[Merged into Configurable Invoice Due Dates for Subscriptions]

Is it possible to be able to change the due date for individual invoices. For an order I do not plan to ship until April of 2026 for instance. I want to be able to make it due at that time, not a month from when I enter it today. Is this a feature that can be added; to be able to adjust the due date easily?

🔍 Problem Statement

As an admin, there is no controlled way to set or backdate a subscription's start or end date — needed for service recovery, aligning entitlement periods, and correcting timelines. Setting end_date from the platform was possible in the past but has since been removed, and there is no API-first way to do it either. When a date is extended by other means, the Subscription Details page does not reflect it, so admins must check the API to confirm the real expiry.

💡 User Story

As an admin or integrator, I want to set or backdate a subscription's start and end date from both the Platform UI and the Core API, and to see the current dates on the Subscription Details page, so that timelines can be corrected and verified without workarounds.

🎯 Definition of Done (DoD)

• ✔ Given a subscription, when an admin edits its start and/or end date in the Platform UI, then the new date(s) are persisted and reflected in access/entitlement, renewals, and reporting.
• ✔ The same set/backdate operation is available via the Core API (subscription resource), including backdating the end date.
• ✔ Given a subscription whose end date has been extended by any means, when an admin views the Subscription Details page, then the effective end date is displayed clearly, distinguished from the original billing-cycle end date.
• ✔ Works for autorenew subscriptions; adjusting dates does not corrupt the renewal schedule or recognized revenue.
• ✔ This change will impact UI / API — specifically the Subscription detail page (Platform UI) and the subscription resource (Core API).
• ✔ Limitations: end date cannot be set earlier than the start date; date edits do not retroactively re-charge or refund.