Time zones & Retail Connectors
Opteroo uses two different time-zone concepts. Mixing them up is the main cause of “why doesn’t the week match my sync day?” questions. Both are legitimate; they solve different problems.
1. Workspace default time zone (Region & Time zone)
Set under Settings → Region & Time zone (/settings/region-timezone). This settings page is available on the Growth plan. It stores your workspace’s default IANA time zone (for example Australia/Sydney).
If the workspace default is left empty (or you are on a plan without the settings page), the API still exposes an effective time zone - typically falling back to Australia/Sydney - which Action Inbox uses for ISO week labelling.
It drives:
- Calendar and ISO week labelling for Action Inbox Prioritised decisions / Budget recommendations - which Monday–Sunday period counts as the “latest completed” week and how week codes and date ranges are shown for product/SKU and budget views.
Amazon Keywords may additionally label weeks using each advertising profile’s time zone. That is separate from the workspace default.
2. Application scheduling time zone
This value comes from the backend environment and is exposed on your session (for example via auth profile as the application scheduling time zone). It defines what “local time” means for scheduled jobs such as the weekly Retail Connector sync.
It drives:
- Weekly Retail Connector sync at 01:00 on the sync weekday you choose (Monday–Friday) per connector under Retail Connectors (
/settings/integrations).
Why both exist
Your business might plan campaigns and weeks in one region’s clocks while infrastructure runs scheduled jobs in another. When the two zones differ, the in-app copy under Retail Connectors and Action Inbox Schedule help explains how a single instant in time appears in each zone.
Retail Connectors checklist
- Open Settings → Retail Connectors (
/settings/integrations). The sidebar label is Retail Connectors; the path still usesintegrations. - Add or enable the retailer connection your organisation uses (for example Criteo, Amazon Ads, DoorDash).
- Set each connector’s sync weekday (Monday–Friday). The weekly job runs at 01:00 in the application scheduling time zone.
- After a successful run, new rows for the relevant data week typically appear in prioritised views; use the Bidding Grid if you need other weeks while data is catching up.
- If Apply is blocked with a re-sync message, run sync again so line-item and product identifiers are present for API push.