Timezone standardisation capabilities (API formats, shadow fields, offset preservation, and event handling) are available across the platform for all organizations, regardless of when they were created.

However, full end-to-end behaviour is controlled by configuration flags.

Organizations created from 2026 onwards
Timezone standardisation–related configurations are enabled by default.
Organizations created before 2026
The standardised APIs and response formats are already available.
However, certain configurations that control behaviour in the UI and Loyalty processing are gated and may remain disabled.

To enable complete timezone standardisation for older organizations, create a support ticket to the Capillary Product Support team and enable the timezone standardization configuration TIMEZONE_ENABLED.

Module Coverage

Timezone handling is applied across supported UI modules and APIs. However, some modules are already aligned, some are in progress, and some remain unchanged.

This section clarifies what is covered and what is not.

Modules covered

Timezone handling is fully supported in:

Transaction APIs (v2)
Behavioural events
Event notifications

These modules follow the standardised timezone model.

Modules not yet covered

The following modules do not currently follow the standardised timezone model:

Offers API
v1 and v1.1 APIs

For these modules:

Existing timezone behaviour remains unchanged.
Legacy display or processing logic may still apply.

Future Rollout

Timezone standardisation for some of the above modules is planned as part of ongoing revamp initiatives. These modules are not being deprecated. They will adopt the standardised model in future releases.