An unshipped order backlog
Maya Okafor, operations lead at BigCo, asked which paid orders had not shipped. Memtro listed the unfulfilled orders with totals, channel and dates.
Which paid orders have not shipped, and how much stock is left?
Saleor shows you orders by status, channel and date with totals, payment and fulfilment state. It reads one order's lines, fulfilments and history, products with variants, prices and stock per warehouse, and channels and warehouses. When asked and granted, it can add a staff note, and create, complete or delete a draft order. It can confirm, fulfil, mark paid or cancel an order. It can also update or cancel a fulfilment's tracking, rename a product, set stock and create a customer. Fulfilling or updating tracking emails the customer only when you ask for it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Saleor tool, reads what it needs, and answers with the source cited.
These tools change something in Saleor. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Saleor is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Which paid orders are still unfulfilled?
How many blue hoodies are in stock in each warehouse?
What were yesterday's orders in the UK channel?
Show the history of order 10423.
Which channels sell in euros?
Maya Okafor, operations lead at BigCo, asked which paid orders had not shipped. Memtro listed the unfulfilled orders with totals, channel and dates.
Dan Fletcher at Acme Ltd counted the mugs in the Leeds warehouse and asked Memtro to set the stock to match. With the action granted, Memtro set the variant's stock there, and the storefront's availability followed.
The teams that lean on Saleor most, a question each of them asks, and what they connect beside it.
A record in Saleor is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Saleor Dashboard open Extensions, then Add Extension, then Provide details manually. Name the app, grant only the permissions it needs, and create a token.
In Memtro open Connections → Saleor and fill in the GraphQL API URL, ending in /graphql/, and the App token.
Creating the app needs a staff user with MANAGE_APPS. An administrator grants the order, stock and customer actions by name.
Ask: which paid orders are still unfulfilled?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Saleor tools are the same everywhere.
Only when you ask, and only what it has been granted: add a staff note to an order; create a draft order; complete a draft order into a real order; delete a draft order; confirm an unconfirmed order; fulfil order lines from a warehouse (optionally emails the customer); update a fulfilment's tracking number (optionally emails the customer); cancel a fulfilment and restock its items; mark an order as paid; cancel an order; rename a product or change its slug; set a variant's stock in a warehouse; create a customer account (an email app may email them). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Saleor records into memory as entities.
GraphQL API URL and app token. In Saleor Dashboard open Extensions, then Add Extension, then Provide details manually. Name the app, grant only the permissions it needs, and create a token.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time