GraphQL Order Timestamps vs Store-Scoped Timezone Config: Where Should Conversion Happen?

Answer first

For Magento 2.4.x the correct place to shift an order’s created_at from UTC to the store view’s timezone is inside a custom GraphQL resolver that uses \\Magento\\Framework\\Stdlib\\DateTime\\TimezoneInterface. The PHP date.timezone setting must stay UTC, and the resolver should read the store‑scoped timezone via ScopeConfigInterface or StoreManagerInterface. Client‑side conversion is discouraged because the schema offers no built‑in argument for it.

Why a resolver is the supported point

The native GraphQL schema exposes datetime fields as raw UTC ISO‑8601 strings. There is no directive that automatically applies the store view’s offset. Magento’s extension point for GraphQL is ResolverInterface, which is the documented way to transform data before it is sent to the client. Using TimezoneInterface inside a resolver gives you precise control while keeping core logic untouched.

Avoiding double‑conversion

Some third‑party modules may already format dates for display. To prevent applying the offset twice, run the resolver only on the raw UTC value. A simple check is to examine whether the incoming string ends with +00:00 or Z; if it does, skip conversion. If you cannot rely on the format, coordinate with any module that touches the field to disable its own conversion or expose a flag you can read.

Store‑scoped timezone in GraphQL context

When the request contains the X‑Magento‑Store header (or the store cookie is set), Magento resolves the store view and therefore the timezone configured under Stores > Configuration > General > Locale Options. The resolver can obtain the current store ID via \\Magento\\Store\\Model\\StoreManagerInterface or from the GraphQL ContextInterface. The same timezone will be applied to every field resolved for that request, ensuring consistency across the payload.

Practical steps for this scenario

1. Create a new resolver that implements \\Magento\\Framework\\GraphQl\\ResolverInterface.
2. Inject \\Magento\\Framework\\Stdlib\\DateTime\\TimezoneInterface and \\Magento\\Store\\Model\\StoreManagerInterface.
3. In resolve(), fetch the raw UTC value from the order entity.
4. Use timezone->date($utcValue, $storeTimezone) to shift it to the store’s offset.
5. Return the ISO‑8601 string; the GraphQL response will now contain the store‑specific time.
6. Configure the resolver in etc/graphql/di.xml to override or extend the existing field.
7. Clear caches and test with different store headers to confirm the offset changes appropriately.

Cache considerations

Because the output depends on the store, the resolver must be marked as cache‑able by store ID. If you use Varnish or full‑page caching, add the store ID to the cache key or disable caching for this field.