Feature #9285
openFeature #9201: Working users and frontend Timezone update to use company timezone and backend api to use company timezone
Align frontend dashboard date ranges and filters with store timezone
Start date:
07/01/2026
Due date:
07/01/2026 (34 days late)
% Done:
0%
Estimated time:
Description
- Summary of Changes
Aligned frontend date range pickers and preset filter calculations with the store's configured timezone (America/Denver) instead of using the client browser's local time. This resolves timezone offset discrepancies (e.g. a user in GMT+5:30 seeing July 1st while the store is still on June 30th).
- Affected Components & Fixes:
1. Sales Analysis Page (sales&products.tsx):
- Configured date range calculations and presets ("Today", "Yesterday", "This Month", etc.) to use the store's timezone via `dayjs().tz(getCompanyTimezone())`.
2. Main Dashboard (Home.tsx):
- Fixed the issue where the Date Range picker fields remained empty on mount when "Today" was active.
- Initialized default `dateRange` state to today's start/end dates in store timezone context.
- Configured quick filter selection boundaries relative to store timezone.
3. Other Date-Filtered Tables/Lists:
- Pre-order catalogs list (`Preorderlist.tsx`)
- Product subscriptions list (`ProductSubscribersTable.tsx`)
- Subscription transactions list (`ProductSubscriptionTransactions.tsx`)
- Purchase orders list (`PurchaseOrderList.tsx`)
- User management list (`UserManagement.tsx`)
- Migrated all default range initializations to use the timezone-aware `getCurrentMonthRange()` helper.
Subtasks
Related issues
No data to display