Operating reports, notifications & forecast views

With write access, a connected assistant can manage several configuration surfaces that go beyond inventory transactions: scheduled email reports, out-of-stock notification rules, shared email recipients, saved forecast views, and custom Data Modeling tables. This page explains what each covers and the plan requirements that apply.

Scheduled reports

The assistant can read and manage your scheduled report definitions:

List and read reports: see what’s configured, which recipients are attached, and whether each report is enabled.
Preview a report’s data: generate the payload that the next email would contain, without actually sending it. Useful for checking the output before enabling a report.
Create a new scheduled report: set the type (a forecast view summary, purchase-order status report, saved data report, or multi-location comparison), the recipients, the frequency, and when to send it.
Update an existing report: change any of its settings, flip it on or off, or adjust the schedule. Enabling or disabling the report updates the schedule immediately.
Delete a report: also removes it from the schedule.
Run a report now: send the report email immediately, outside of its schedule. The assistant receives confirmation that the send was accepted; delivery happens in the background.

Report delivery times and days use the timezone selected for the report. The next scheduled send is calculated automatically and stays up to date when the assistant edits the report.

Out-of-stock notification rules

Your store can have several notification rules. With write access, the assistant can:

List and read rules to compare their triggers, forecast views, recipients and enabled state.
Create a rule for a separate stock-monitoring workflow, or update an existing rule’s name, triggers, thresholds, view and recipients.
Pause a rule by turning it off, or delete it together with its exceptions and alert history.
Maintain variant exceptions, including location-specific exceptions: enable or mute a variant, override its triggers, or let it inherit the rule’s triggers.

Ask the assistant to merge changes when updating only selected exceptions. Valid rows are saved and any invalid or unresolved rows are reported separately. Replace makes the submitted rows the complete exception list: if any row is invalid or cannot be resolved, the entire replacement is refused and the existing list stays unchanged. Review every reported row before trying again.

Email recipients

Recipients are the shared address book used by both reports and notifications. The assistant can manage it:

List recipients: see all configured email addresses.
Add a new recipient: provide a name and email address. The new recipient immediately becomes available to attach to reports and notification rules.
Remove a recipient: removes the address from the list and detaches it from any reports or rules that were using it.

Forecast views

The assistant can read your saved forecast views and, with write access, create and maintain them:

List all views and read a specific view’s full configuration: locations, filters, columns, sort order, and forecast settings.
Preview how many products match a set of filters without saving the view: useful before committing to a new configuration.
Create a new view: provide a name, the locations to include, column choices, filters, and optional forecast model settings. The view is validated against the forecast engine before saving, so a configuration that produces no results fails before being stored.
Update an existing view: change any of its settings. The existing view stays unchanged if the updated configuration fails engine validation.
Delete a view. Starred views are protected; un-star a view in the app first before asking the assistant to delete it.
Star or un-star a view: controls whether it appears at the top of the view list.

Starting Data Modeling

Data Modeling requires the Elevate plan. With write access, the assistant can initialize a previously empty model, then create custom tables, columns and records. Initialization creates the same default Variant starting point as the Data Modeling studio.

Repeating initialization leaves an existing valid model unchanged. It does not repair an inconsistent model; inspect that model in the studio before continuing. Opening the studio still prepares an unsaved draft until you choose Save.

Plan requirements

Capability	Plan required
Forecast views: read, preview, create (non-Holt/Seasonal), update, delete	Any plan
Forecast views: Holt or Seasonal model	Enhanced
Reports: read, preview, create, update, delete, run now	Enhanced
Notification rules: read	Any plan
Notification rules: create, update, delete and variant exceptions	Enhanced
Data Modeling: initialize and maintain tables, columns and records	Elevate
Recipients: list, add, remove	Any plan