Before the pick
At nine the warehouse lead asks what is waiting to ship. Memtro counts the orders awaiting shipment and on hold per store, then lists the oldest ones with their ship-by dates and requested services.
What is waiting to ship, what went out and what it cost, from ShipStation.
Connect ShipStation with an API key and secret and Memtro reads orders by status, store, customer or date, shipments with carrier, tracking number and label cost, fulfilments done elsewhere, and the stores, carriers and warehouses behind them. Every hour it writes each new shipment into memory. When asked, and once an administrator has granted each action by name, it creates, holds, restores, tags or deletes orders, marks them shipped, gets and voids labels, refreshes a store and adds ship-from locations. A label charges postage to the carrier account, a voided label is permanent, and marking shipped can email the customer.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ShipStation tool, reads what it needs, and answers with the source cited.
These tools change something in ShipStation. 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 ShipStation 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.
How many orders are awaiting shipment right now, and how many are on hold?
What shipped to Priya Patel last week and what was the tracking number?
What did we spend on labels in October?
Which orders containing SKU TEE-NAVY-L are still unshipped?
Put order 10482 on hold until Monday while we check the address
At nine the warehouse lead asks what is waiting to ship. Memtro counts the orders awaiting shipment and on hold per store, then lists the oldest ones with their ship-by dates and requested services.
Ruth Evans sent a Northwind order by local courier and asks Memtro to record it and tell the customer. Memtro marks the order shipped with the courier and tracking number, with the customer email switched on, so ShipStation emails the customer. There is no way to un-ship it afterwards.
The teams that lean on ShipStation most, a question each of them asks, and what they connect beside it.
A record in ShipStation 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 ShipStation open Settings → Account → API Settings and click Generate API Keys. Copy both the key and the secret
Generating again replaces both, and anything using the old pair stops working, so keep the pair somewhere safe
In Memtro open Connections → ShipStation, paste the API key and API secret, and connect. It names the connection after the stores it finds
Ask what is waiting to ship. ShipStation allows 40 requests a minute, and shows times on its own clock, US Pacific
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ShipStation tools are the same everywhere.
Only when you ask, and only what it has been granted: create an order in ShipStation; mark an order shipped without a label, optionally emailing the customer and telling the sales channel; buy a shipping label for an order, which spends postage on the carrier account; void a label, which cannot be undone; put an order on hold until a date; restore an order from hold to awaiting shipment; add a tag to an order; remove a tag from an order; delete an order from ShipStation (it is set inactive); refresh one store so new orders import now; add a ship-from location. 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 ShipStation records into memory as entities.
API key and API secret. In ShipStation open Settings → Account → API Settings and click Generate API Keys. Copy both the key and the secret.
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