Stock before a sale
Sarah Chen, operations lead at Acme Ltd, asked what was in stock before a weekend sale. Memtro read the inventory levels and gave each item's fulfillable, committed and backordered quantities across fulfilment centres.
Which orders shipped late this week, and what is in stock right now?
ShipBob shows your fulfilment as it stands. You see orders with their shipments, carrier tracking and status timeline, inventory levels by quantity type, products and variants, returns, warehouse receiving orders, fulfilment centres and shipping methods. When asked and granted, Memtro can create and cancel orders, cancel, hold, release or re-address shipments, create and edit products, and create and cancel returns and receiving orders. ShipBob can tell Memtro when an order ships, a shipment is delivered or a return completes, and a job can start on it. The token must come from the root user, and recipient details are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right ShipBob tool, reads what it needs, and answers with the source cited.
These tools change something in ShipBob. 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 ShipBob for you. Each event can start a job, with the event as its input. ShipBob signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce ShipBob 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 orders shipped late this week?
What is in stock right now for the blue mug SKU?
Where is shipment 48213 and when was it promised?
Which warehouse receiving orders are still awaiting stock?
Put the shipments on order ACME-1042 on hold.
Sarah Chen, operations lead at Acme Ltd, asked what was in stock before a weekend sale. Memtro read the inventory levels and gave each item's fulfillable, committed and backordered quantities across fulfilment centres.
At Northwind, a job starts when ShipBob reports a shipment moved to exception. Memtro read the shipment's status details and timeline, checked inventory for its SKUs, and reported both to Tom Reilly, the fulfilment manager.
The teams that lean on ShipBob most, a question each of them asks, and what they connect beside it.
A record in ShipBob 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.
Sign in to ShipBob as the account's root user, go to Integrations, then API Tokens, and generate a new token. It has every scope and does not expire.
In Memtro, open Connections → ShipBob and paste it into Personal access token.
An administrator grants the actions by name, such as Create order or Cancel shipment, to the teams that may use them. Events are turned on from the connection's Events tab.
Ask which orders shipped late this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The ShipBob tools are the same everywhere.
Only when you ask, and only what it has been granted: create an order for fulfilment (ships goods and is billed); cancel an order (permanent); cancel a shipment (permanent); put shipments on hold; release shipments from hold; change a shipment's delivery address; create a product with its variants; edit a product or its variants; create a return order; cancel a return order (permanent); create a warehouse receiving order (inbound fees apply when received); cancel a warehouse receiving order (permanent). 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.
Personal access token. Sign in to ShipBob as the account's root user, go to Integrations, then API Tokens, and generate a new token. It has every scope and does not expire.
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 ShipBob 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