Stop pulling the same report every Monday

The report you already built, not a new one

A schedule doesn't start from a blank form. Open any report, hit Quick Actions → Schedule Report, and the schedule captures that report exactly as it's sitting on screen — the same breakdown, time range, filters, and columns you were already looking at. That includes reports you didn't build by hand: Assisty's AI Report Builder answers a plain-English question — sales, inventory, forecasting, replenishment, lost revenue, or stock availability — by querying your live store data, and a report built that way can be saved to My Reports and opened in the full editor to add charts, same as any report you built with a template. From there it's schedulable the same way as anything else in the library, so a one-off question doesn't have to become a recurring manual pull just because you keep asking it. For everything built the traditional way, nine ready-made scheduling templates cover the classics — low stock, sales summary, reorder now among them — and reusable schedule profiles keep a cadence you use often one click away instead of a form you fill in from scratch each time.

Delivered where the work already happens

A scheduled report doesn't wait for someone to log in and export it. Email delivery lands with a CSV, Excel, or PDF attachment, sent to multiple recipients at once, so a report can reach everyone who needs it without a separate setup step for each person. A schedule can sync a fresh Google Sheet or append to the one your team already lives in, drop the file into Google Drive alongside the rest of your records, or fire a Shopify Flow trigger — the same trigger that can alert Slack or Teams, or push the data straight into your ERP. The report doesn't change depending on where it's headed; only the delivery channel does, so the same low-stock report reads the same whether it lands in an inbox or a shared spreadsheet.

On your clock, not a calendar reminder someone has to act on

Cadence is a setting, not a recurring task on someone's calendar. A schedule can run daily, weekly, or monthly, on the specific weekdays or days of the month you choose, at the hour you pick — a low-stock report every Monday morning, for instance, run in your store's own timezone rather than a server's. Nothing stops a schedule from running the same report more than once a day if that's what a fast-moving week calls for. And a report that would otherwise send an empty result on a quiet week doesn't have to land in anyone's inbox at all — sending on empty is optional, so a schedule can stay silent until there's something worth reading.

Test it, trust it, trace it

A schedule you can't verify isn't one you can rely on. Run now sends a test delivery the moment you save a schedule, so the first time you see whether it worked isn't the following Monday. A schedule can also diverge from the report it was built from — its columns and filters can be edited on their own, without touching the source report everyone else still uses, so one team can get a narrower view without changing what anyone else sees. And every run stays in history, each one paired with the exact file it sent and re-downloadable any time, so a schedule that's been running for months is still one click from proving what it delivered and when.

That holds even for a report that started as a question typed into chat. A report built by asking Atlas exports as CSV, PDF, or Google Sheets and schedules exactly like any other report in the library — there's no separate delivery path for a question answered in conversation versus a report opened from a template. The breakdown, filters, and columns a schedule captures are the same whichever way the report got built in the first place.