Date Adjustments for Subscriptions in the Vendor Time Zone
In CloudBlue Commerce it is possible to set the UTC time zone for a plan so its subscriptions are managed in the same time zone as the vendor's. If the CloudBlue Commerce system time zone has a significant offset to UTC, it can lead to discrepancies between the data on the CloudBlue Commerce side and the data on the vendor side for UTC-based subscriptions, which could lead to CloudBlue Commerce using incorrect dates in the following cases:
-
Scheduled change orders.
-
Subscription co-terming.
-
Subscription cancellation.
-
Displaying subscription expiration and renewal dates.
To prevent such issues with UTC-based subscriptions, starting from 21.19, CloudBlue Commerce keeps subscription event history, ensuring alignment with the vendor time zone and restricts changing subscription's expiration and next billing dates. Additionally, for the installations in locations with a significant positive time offset, like Australia, the following option is added, which is disabled by default:
-
FEA_NextLocalDayExpirationForUTCPlans. When enabled, subscription expiration dates in CloudBlue Commerce are adjusted to the next midnight in the installation's time zone. This ensures that for subscriptions in the vendor time zones, on the installations that are deployed in locations with a significant positive time-zone offset to UTC, the maximum interval between the subscription expiration on the vendor side and in CloudBlue Commerce is 24 hours minus the time-zone offset.
Keep in mind that if the time-zone offset is less than the time after midnight required for daily billing process to complete, enabling this feature may cause actual expiration in CloudBlue Commerce to complete more than 24 hours after it is expired by the vendor, which may break cancellation policies of some vendors.
In the table below, you can see how subscriptions are processed depending on the time zone and configuration. In every example, the following configuration is considered:
-
Subscription period is 1 year.
-
Billing period is 1 month.
-
Billing model is Before Billing Period (BBP).
-
Plan time zone is set to the vendor's (UTC).
-
Subscription event history is being saved.
| CloudBlue Commerce location time zone | Configuration Adjustments | Subscription purchase | Subscription expiration | ||||
|---|---|---|---|---|---|---|---|
| Vendor side (UTC) |
CloudBlue Commerce
(local time zone) |
Date displayed in CloudBlue Commerce UI | Vendor side (UTC) |
CloudBlue Commerce
(local time zone) |
Date displayed in CloudBlue Commerce UI | ||
| GMT+11 | Next local midnight for expiration date. | 10:00 PM, February 23, 2025 |
9:00 AM, February 24, 2025 |
February 24, 2025 | 12:00 AM, February 23, 2026 |
12:00 AM, February 24, 2026 |
February 24, 2026 |
| 1:00 AM, February 24, 2025 |
12:00 PM, |
February 24, 2025 | 12:00 AM, February 24, 2026 |
12:00 AM, February 25, 2026 |
February 25, 2026 | ||
| GMT+2 | None. | 10:00 PM, February 23, 2025 |
12:00 AM, February 24, 2025 |
February 24, 2025 | 12:00 AM, February 23, 2026 |
12:00 AM, February 23, 2026 |
February 23, 2026 |
| 10:00 AM, February 24, 2025 |
12:00 PM, |
February 24, 2025 | 12:00 AM, February 24, 2026 |
12:00 AM, February 24, 2026 |
February 24, 2026 | ||
| GMT-8 | None. |
23:00 AM, February 23, 2025 |
7:00 AM, |
February 24, 2025 |
12:00 AM, February 23, 2026 |
12:00 AM, February 24. 2026 |
February 24. 2026 |
|
05:00 AM, February 24, 2025 |
13:00 PM, February 24, 2025 |
February 24, 2025 |
12:00 AM, February 24, 2026 |
12:00 AM, February 24, 2026 |
February 24, 2026 | ||