Skip to content

Dates and scheduling

The Published date field does more than label a release. It controls the order releases appear in, and it is how you schedule an announcement.

The listing shows releases by published date, most recent first. That is the order a press room is expected to be in, so it is the default everywhere — the storefront list, the admin list and the dashboard.

A visitor can flip the storefront list to oldest first with the sort control, and you can make oldest first the order the page arrives in. Both are block settings — see Block settings reference.

To move a release up the page, change its published date.

The storefront block hides releases dated in the future by default. So to schedule an announcement:

  1. Write the release fully.
  2. Set its date to the moment you want it public.
  3. Save.

It stays off your storefront until that date arrives, then appears automatically. Nothing needs to be published a second time.

Hiding it from the listing is a convenience, not a security control. The release exists in your store from the moment you save it, and its detail page URL is reachable by anyone who guesses or is given the slug.

Do not use scheduling for an embargoed announcement that would cause harm if it leaked early. Write it close to the time, or keep it out of the app until you are ready.

Setting a date in the past is fine and is the normal way to import an archive of older releases. They slot into the list in date order.

Dates are stored with a time. If a release is due at a specific hour — market open, an embargo lifting — set the time as well as the day, and check it appears when you expect on the storefront rather than assuming.