How many units of this product are available, and what is still on order?
inFlow Inventory connects Memtro to your stock and orders. It reads sales orders with their inventory and payment status, totals, balances and lines, then purchase orders with vendor and lines. It reads products with stock on hand, and a product's stock by location: available, reserved, on order and in transit. Vendors, locations and customer ids complete the picture. When asked and granted, it can create sales and purchase orders, customers and products, adjust or transfer stock, and confirm, invoice, mark paid, fulfil, ship or cancel sales orders. Customer names and contact details are never read back.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right inFlow Inventory tool, reads what it needs, and answers with the source cited.
These tools change something in inFlow Inventory. 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 inFlow Inventory 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.
inFlow Inventory + MemtroWhich sales orders are still unfulfilled?
How many units of SKU MUG-01 are available at the main warehouse?
Show purchase order PO-000123 with its lines.
Which vendors do we buy from, and what are their lead times?
Create a purchase order to our mug supplier for 50 blue mugs.
Maya Okafor, sales lead at Acme Ltd, asked whether a product was in stock for a large order. Memtro read its stock by location and gave on hand, reserved and on order at each warehouse. She promised a date the stock could meet.
Dan Fletcher, operations manager at Northwind, asked Memtro to ship a confirmed sales order. With the action granted, Memtro shipped it in one step, moving its stock out of inventory. Anyone opening the order in inFlow now sees it shipped.
The teams that lean on inFlow Inventory most, a question each of them asks, and what they connect beside it.
A record in inFlow Inventory 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.
NetSuite
Ramp
FreeAgent
Holded
Mollie
QuickFile
Recurly
Airwallex
Maxio
Pennylane
Charity Commission (England and Wales)
Checkout.com
FCA Register
Soldo
Spendesk
Lago
Recharge
Katana
Chaser
Unleashed
Printful
Orb
Quaderno
Donorbox
Avalara AvaTax
Billy
Cin7 Core
Codat
ComplyAdvantage
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn inFlow, open Options → Integrations → API keys and generate an API key. It needs the API access add-on (or a trial) and administrator rights.
In Memtro, open Connections → inFlow Inventory and paste the API key and the Company ID shown beside it.
An administrator grants the actions by name, such as Ship a sales order, to the teams that may use them. The key acts for the whole company.
Ask "How many units of the blue mug are available, and how many are on order?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The inFlow Inventory tools are the same everywhere.
Only when you ask, and only what it has been granted: create a sales order; create a purchase order; create a customer; create a product; adjust stock at a location; transfer stock between locations; confirm a sales order; mark a sales order invoiced; mark a sales order paid; fulfil a sales order (deducts stock); ship a sales order (picks, packs and ships); cancel a sales order; approve a purchase order; receive a purchase order into stock; cancel a purchase order. 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.
API key and Company ID. In inFlow, open Options → Integrations → API keys and generate an API key. It needs the API access add-on (or a trial) and administrator rights.
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