Schedule a Shopify Discord drop across time zones

Identify the clock beside each schedule.

Shopify’s future-publishing guidance tells merchants to verify the store’s time zone. Find it under Settings → General → Store defaults. Record the existing setting before planning the release; changing the whole store’s zone is not a shortcut for one teammate working elsewhere.

MemberPort’s current drop form uses the time zone reported by your browser. It shows that zone beside the date-and-time field. When you save, the app converts the entered local time into a UTC timestamp. UTC is a common reference for one instant; it is not another launch you need to schedule.

Opening a saved drop on a device in another zone can therefore show a different local hour for the same instant. Confirm the zone label when creating or editing a drop, especially after travelling or changing device settings. This is different from assuming the app follows Shopify’s store zone.

Give publication and announcement separate rows.

Consider this fictional release: Shopify uses America/Toronto, while the person scheduling MemberPort works in America/Winnipeg. The desired announcement is September 24, 2026 at 18:00 in Winnipeg. The team chooses to publish products fifteen minutes earlier so someone can check the public links.

The table uses 24-hour times. Each row is one event expressed in three zones; the two rows are deliberately different events. The fifteen-minute gap is this example’s review window, not a delivery guarantee or a recommended setting for every store.

• In Shopify, enter September 24 at 18:45 after confirming the store uses Toronto time.
• In MemberPort, enter September 24 at 18:00 after confirming the displayed browser zone is Winnipeg.
• Have the person checking the launch compare both saved schedules with the UTC references.
• If the public-link check fails, pause the announcement and agree on a new time before resuming.

Use the launch date’s offset, not today’s.

A zone such as America/Winnipeg includes rules for seasonal clock changes. An offset such as UTC−05:00 describes the relationship at a particular time. Do not copy September’s offset into a winter launch simply because the local hour stays the same.

The National Research Council lists Manitoba among provinces that change clocks for daylight saving time. IANA also updates its time-zone database when jurisdictions change their rules. Use the actual release date when converting times, and keep the device and software used for scheduling updated.

Around a clock change, some local times repeat or do not occur. MDN notes that a local date-time input can accept a value inside a spring-forward gap. Choose an unambiguous local time outside the clock-change window. MemberPort’s current form does not let you choose between two occurrences of a repeated hour.

Reopen the saved drop before handing it over.

After saving, reopen the drop and check the date, local time, zone and selected products. Separately confirm the destination channel in Setup. A teammate in another zone should compare the converted instant, not expect the same clock reading. The zone label gives you the context needed to explain a difference.

If the saved time looks wrong, correct it before the launch. Pausing a MemberPort drop retains its schedule. Resuming an unannounced drop whose time has already passed makes it eligible for a later worker run; it does not move the date into the future. Review or edit the schedule before selecting Resume.

MemberPort processes scheduled announcements in a background worker. The saved time is an eligibility point, not a promise that Discord receives a message at that exact second. Check the drop status and the channel before attempting another send. Use Announce now only when you intend an immediate announcement.

Check storefront readiness as its own task.

A correct announcement time cannot make an unavailable product link work. Shopify requires products to be Active for its future publishing to work. MemberPort’s optional activation step sets product status Active; it does not configure publication to your sales channel.

For the broader readiness checks, use the Active versus available guide. Assign someone to confirm the public product links before the announcement is due. If that check cannot be completed, change the plan rather than letting a matched pair of timestamps stand in for a ready storefront.

Keep a handoff the next person can use.

Download the blank launch-time handoff sheet and keep it with the release brief. It records the two events, the zones used to enter them, the UTC references, the person responsible for the public-link check, and the decision to proceed or delay. It is a manual worksheet; it does not change your store, convert dates automatically or send a Discord message.

MemberPort is accepting early-access inquiries for Shopify product-drop announcements in Discord. Use the scheduled-drop guide to review the workflow and discuss a launch with the actual products, channel and timing you need.