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, inventory plans, promotional events, planning options, 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.
Inventory planning	Inventory commitments, sales plans and launch plans with their products per location, curves, linked orders and attached documents; plan vs actual sales; a size group’s actual mix since launch; previews that save nothing (targets, launch curves, size splits, launch orders); and your demand types, reason codes and sources.
Promotional events	Your holiday and sales events with their stored and upcoming dates, the uplift each date uses and whether the event is switched on for forecasts, plus the built-in holiday list you add events from.
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, and it doesn’t load the whole API up front either. When it connects it gets a short index of the areas above. From there it looks things up as it needs them:

search: the assistant writes a small search over the catalogue of everything its connection can do (each method’s name, a one-line summary, its inputs and what it returns) and gets back only the matches. For example, every method that mentions supplier credits, or everything in purchase orders.
describe_api: the exact typed definition of the methods or areas it picked: the inputs each accepts and the shape of what comes back. Called with nothing selected, it still returns the definition of everything at once. That is large, so assistants are pointed to the targeted form.
whoami: which store the assistant is connected to, whether the connection can read or also write, and the name of the key or connected app.

This is how a capable assistant figures out, on its own, how to answer a question like “which suppliers have stock waiting for me?”, without spending most of its working memory on parts of the API it never uses.

Ready-made recipes

Logistified also hands your assistant a set of recipes: short, step-by-step guides for the jobs merchants most often give them. They cover sales questions, reports (including a weekly, monthly or quarterly store report), reviewing purchase orders, keeping a supplier’s catalogue up to date, reordering from a forecast view, checking stock positions, and inventory planning (plans, product launches, sales targets, promotional events and plan locations).

Every connected assistant can use them; it needs no special support. It reaches them through two tools and may load one before it starts the job; whether it does is up to the assistant:

list_skills: the list of recipes, each with a one-line description.
get_skill: the full steps of one recipe.

Apps that support MCP prompts also show each recipe as a command you can pick yourself, for example as a slash command in Claude Code, optionally with what you want done (such as “sales for last weekend by channel”).

A recipe only explains how to do the job; what the assistant can actually change still depends on the connection (a read-only key can read the “reorder” recipe but cannot create a purchase order).

The recipes also say how to show figures: right in the chat, as a sentence, a few tiles, a simple chart or a table, with the same labels and number formats every time. The assistant builds no dashboard, page or file unless you ask for one.

Weekly, monthly and quarterly store reports

Ask for “the weekly report” (or the monthly or quarterly report, or a report for your own dates) and the assistant puts together a report on your store in the chat. It follows the same recipe every time, so asking three times in a row gives you the same figures in the same layout. The report answers the three questions of a weekly meeting with your head office or supplier:

How did the period go? Net sales, gross profit (of the items that have a cost), gross margin, orders, average order value and items sold, each compared with the period before; net sales and orders per day; your top sellers and the products rising or falling the most.
What do we need to request? From the forecast view you choose: how many products are overdue, due for the next delivery, due for the delivery after, due later, or have no reorder date yet; the order-by dates for your next two deliveries (or the next 7 and 14 days when the view’s locations have no delivery days); and the products to request with their quantities, what is already on its way, and why.
What should change? A few products to ask for more of (selling faster lately) and to ask for less of (selling slowly or not at all, with stock tied up), new products, and the products that will run out within the next 7 days.

A calendar week (Monday to Sunday), month or quarter is compared with the one before; “last 7 days”, “last 30 days” or your own dates with the same number of days just before. Today is never included: your own dates must end before today. The days follow your store’s time zone.

If you don’t name a forecast view, the assistant uses your only saved view, or asks which one to use and suggests views with “report” in their name first, then your starred views. To skip the question, name the view when you ask (“the weekly report for my Store view”); a view with “report” in its name is suggested first.

Afterwards you can ask follow-up questions, such as “why 20 units?”, and the assistant answers from the figures it already has. In apps that show recipes as commands, pick the store period report and type the period, for example “weekly”, “last 30 days” or “2026-10-01 to 2026-10-31”.

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, inventory plans, promotional events, planning options, 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.