What the assistant can read

A connected assistant can read data across most of Logistified. With a read-only connection it cannot change anything — see Read-only by default; with write access it can additionally operate purchase orders, transfer orders, stock takes and stock adjustments, supplier returns, reorder rules, suppliers, reports, notifications, email recipients, forecast views, Data Modeling tables, Product & variant attributes, and purchase-order Constraint Studio rules — see the operating pages in this section. This page lists the read surface so you know what you can ask about.

The data it can reach

The assistant can read across these areas, scoped to your single store:

Area	What it can see
Purchase orders	Orders and their line items, receiving schedule, payments, additional costs & discounts, documents, shipments (an order can have more than one, each with the line items and quantities it carries), addresses, activity log, and supplier credits — both those already applied to the order and those still available from that supplier.
Transfer orders	Orders, line items, shipment, documents, addresses, and activity log — including the from/to locations.
Return orders	Orders and their line items — including return quantities and credit totals. Addresses, activity log, return codes (reason / condition / disposition), and credit history on the Elevate plan.
Manufacturing orders	Orders and their builds — items being built, target and built quantities, material requirements, and the purchase orders, transfers, stock releases and stock adjustments each build links to — plus the activity log. Elevate plan, read-only.
Stock takes	Stock takes, their line items, value totals, and the count-reason list.
Stock adjustments	The delta-only siblings of stock takes (SA-…) — headers with operator, value and quantity totals, per-line deltas and how much of each reached Shopify, the shared reason list, and the links between an adjustment and its reversal.
Suppliers	The supplier directory, per-supplier detail, supplier–variant mapping (cost / MOQ / lead time), stock held at the supplier, consignment stock, and the supplier credit balance and ledger.
Locations	Your locations and any name overrides.
Variant constants	Per-variant, per-location min / max / reorder / target values.
Products	Your product catalogue and per-product detail.
Variants	The variant catalogue — SKU, barcode, product, vendor — and lookups by id.
Inventory levels	On-hand quantities by variant and location, across all eight quantity buckets.
Forecast views & projections	Your saved forecast views — name, filters, columns, model settings — and the full per-product forecast rows behind any of them: predicted demand, reorder point, days of stock, and suggested reorder quantities.
Dashboards	Shop-wide KPI summary — inventory health, stock-out counts, restock-timing buckets, ABC grades and seasonal trends — plus the open supply-order roll-up. The KPI figures come from the nightly inventory snapshot, so they’re typically a day behind the live forecast and reporting reads.
Notification rules	Your out-of-stock notification rule and its current trigger settings. Readable on any plan; changing the rule needs the Enhanced plan.
Reports	Your scheduled report definitions and their configurations. Enhanced plan.
Reporting (interactive)	The reporting engine behind Reporting — the report catalogue, your canonical and saved views, and any report’s rows, totals and scorecard tiles, including a full export of up to 50,000 rows. Any plan. Not the same thing as the scheduled Reports above.
Label printing & scanning	Printing Studio print runs with their line items and generated documents, and Cloud Platform label-checking sessions with their per-day and per-run scan statistics.
Settings & reference data	Purchase tax rates, carriers, email templates and each order’s email send-history, accounting connections and sync state, multi-store settings, and the data-exclusion / order-exclusion settings.
Data modeling	Your custom tables, their columns, rows, values, and the relations between tables. Reading is available on any plan.
Product & variant attributes	Attribute definitions and their values on products and variants, including a full read of the attributes grid. Elevate plan.
Purchase-order constraint rules	Your Constraint Studio rule set, the ready-made preset library, and the field catalogue rules can check. Elevate plan.
Orders	Sales orders and their line items (as current as the latest Shopify webhook).
Fulfillments	Fulfillment detail for an order, including the fulfilling location.

How it explores the API

The assistant doesn’t have to guess what’s available. Alongside run, it can call describe_api, which returns the live, typed definition of everything it can read — every area above, the inputs each accepts, and the shape of what comes back. This is how a capable assistant figures out, on its own, how to answer a question like “which suppliers have stock waiting for me?”

Reading the documentation

The assistant can also read this documentation site through two tools:

list_docs — the index of every documentation page.
get_doc — the full text of one page.

This lets it ground its answers in how Logistified actually works — what DOH means, how a purchase order’s lifecycle runs, what a forecast model does — instead of guessing.

What’s not included yet

Writing (beyond the operated surfaces). With a write-scope connection the assistant can operate purchase orders, transfer orders, stock takes, stock adjustments, supplier returns, reorder rules, suppliers, reports, notification rules, email recipients, forecast views, Data Modeling tables, Product & variant attributes, and purchase-order Constraint Studio rules — see the operating pages in this section — plus a few smaller surfaces those pages don’t cover, such as label print runs, saved reporting views, purchase tax rates and accounting settings. Locations and sales orders remain read-only, and your Shopify product catalogue itself can’t be edited — the assistant can only write Logistified’s own per-variant planning fields (forecast settings, unit costs).
A dedicated sales-history feed. There’s no separate per-variant sales-history series (the one behind the forecast models). Historical sales still reach the assistant — date-filtered sales orders, and the reporting engine’s Sales reports (best sellers, sale items) — just not as a dataset of their own.