Orders on hold
Priya Sharma, e-commerce manager at Acme Ltd, asks which Printful orders are on hold. Memtro filters by status and lists each with the recipient's name and country, the items and the Printful cost.
Has that Printful order shipped, and which orders are stuck on hold?
Printful reads your print-on-demand fulfilment: orders with status, Printful cost, retail total, items and shipments with tracking, sync products with their variants, and the stores the token can see. Recipients come back with name, city and country only. When asked, and once an administrator has granted the action by name, it creates draft orders, updates and confirms them, cancels pending orders, and creates, changes or deletes store products and variants. Confirming an order charges the store owner's card and sends goods to print and ship. Cancelling returns the charge and cannot be undone. Deleting a product is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Printful tool, reads what it needs, and answers with the source cited.
These tools change something in Printful. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Printful for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Printful signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Printful 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 Printful orders are on hold?
Has order 1042 shipped?
What did order @1042 cost us compared with the retail total?
What sizes and colours does the Classic Tee come in?
Cancel order @1051, the customer changed their mind.
Priya Sharma, e-commerce manager at Acme Ltd, asks which Printful orders are on hold. Memtro filters by status and lists each with the recipient's name and country, the items and the Printful cost.
Tom Reilly, customer support at Northwind, asks Memtro to cancel order @1051 before it prints, because the customer changed their mind. Memtro checks it is still pending and cancels it, and Printful returns the charge to the store owner's card.
The teams that lean on Printful most, a question each of them asks, and what they connect beside it.
A record in Printful 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.
At developers.printful.com, open Your tokens → Create. Choose Store access for one store, or Account access for all of them.
Pick the orders/read and sync_products/read scopes, adding orders or sync_products only for the actions you will grant (confirming an order charges the store owner's card). Choose an expiry date, and copy the token, which is not shown again.
In Memtro, open Connections → Printful and paste the Private token. Leave Store ID blank unless you made an Account-level token.
Ask "Which Printful orders are on hold?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Printful tools are the same everywhere.
Only when you ask, and only what it has been granted: create an order as a draft, or submitted for fulfilment (charges the store owner's card) when asked; update a draft order's recipient, items or shipping; confirm a draft order for fulfilment, charging the store owner's card; cancel a pending or draft order, returning any charge; create a store product with its variants and print files; change a store product variant's price, SKU, files or ignored flag; delete a store product with all its variants, permanently; delete one store product variant, permanently. 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.
Private token, plus Store ID for account tokens. At developers.printful.com, open Your tokens → Create. Choose Store access for one store, or Account access for all of them.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Printful for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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