Skip to content
Often SoftwareOften Software

Scheduled exports

A scheduled export uploads one file per run to your SFTP or FTP server, containing the orders placed since the previous run. It can run as often as every hour, on the hour, though most merchants run it daily or twice daily. Support configures the schedule on a template, and the template’s Delivery settings page shows when the last upload succeeded or why it failed.

A scheduled export produces one file covering a time window on a regular schedule, for example every day at 06:00 covering the previous day’s orders, and uploads it to your SFTP or FTP server. Support sets the schedule up on a template for you; this article explains what to expect and how to check that it is running.

As often as every hour, on the hour. Most merchants run one export a day, for example at 06:00 for the previous day, or two, for example at 12:00 and 17:00 so the orders reach the warehouse before each collection.

If each order needs to be sent within minutes of being paid, use Automatic per-order exports instead, which send one file per order as it happens (Advanced plan).

Each run covers a set period, usually the time since the previous run ended, so the periods follow on from each other with no gaps. With runs at 12:00 and 17:00, the 12:00 file contains the orders placed from 17:00 the day before until 12:00, including overnight, and the 17:00 file contains the orders placed from 12:00 until 17:00. Each file can contain any number of orders.

Exportify does not mark orders as exported in Shopify. Each run selects orders by when they were placed, and the back-to-back periods are what keep an order from being sent twice.

A schedule can also include only some orders, for example only paid orders, or only orders that are still unfulfilled when the run happens. An order that a filter leaves out is not picked up by a later run, because each later run covers a later period.

Contact support@exportifyapp.com with:

  • which template to use (or describe the layout you need and we will build one)
  • how often and at what times the export should run, and in which time zone
  • which orders each run should cover (for example “orders since the previous run”, or “orders from the previous calendar day”), and any filter, such as only unfulfilled orders
  • the SFTP or FTP server to deliver to (see Deliver exports to your SFTP or FTP server)

Support configures the schedule and delivery on the template. Templates managed by support show a Managed by support badge in Settings.

Settings page: the custom templates list, with a support-managed template marked Managed by support

Settings page: the custom templates list, with a support-managed template marked Managed by support

Open the template in Settings, then Delivery settings. After the first run, the Last delivery card shows when the last upload was attempted and when an upload last succeeded.

Delivery settings: the Last delivery card, showing the last attempt and the last successful delivery

Delivery settings: the Last delivery card, showing the last attempt and the last successful delivery

If the last upload failed, the card says so and gives the reason, so you or your IT team can correct it and then use Test connection on the same page.

Delivery settings: the Last delivery card after a failed upload, with the reason it failed

Delivery settings: the Last delivery card after a failed upload, with the reason it failed

A failed run is not repeated automatically: the next run covers its own period. To send the orders from a failed run, run a manual export with the same template for that period and download the file from Recent exports.

Scheduled runs are not listed under Recent exports, which shows the exports you start yourself.

You can also ask Sidekick in your Shopify admin, for example “Did my scheduled Exportify export run today?”. It checks the recent scheduled runs for you and explains any failure.

If no orders match the window, the run still completes and a file containing only the header row is uploaded (an empty file, for templates configured without a header row), so the receiving system sees that the run happened.

Contact support with the change. Time-of-day changes, a different window or a different destination folder are all quick to apply.