How much of this SKU can we sell today, and where has that order got to?
Cin7 Core is where your stock and orders live. Memtro reads sales with their quote, order, pick, pack, ship, invoice and payment status, one sale's lines and fulfilments, purchase orders, products with price and average cost, and stock by location. When asked and granted, it can create a sale and its order, void a sale, record or remove a payment, create a customer, and post or void a stock adjustment. Cin7 Core can tell Memtro when a sale is backordered or stock changes, and a job can start on it. Sale amounts, contacts and addresses are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Cin7 Core tool, reads what it needs, and answers with the source cited.
These tools change something in Cin7 Core. 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 Cin7 Core for you. Each event can start a job, with the event as its input. Cin7 Core sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Cin7 Core 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.
Cin7 Core + MemtroHow much of SKU TS-100 is available at the main warehouse?
Which Cin7 orders are backordered?
Which sales have shipped but not been invoiced?
Which purchase orders are still waiting to be received?
What is low at the main warehouse?
Priya Sharma, an account manager at Acme Ltd, asked how many of a jacket SKU were available at the main warehouse. Memtro read Cin7 Core stock by location and gave her the on-hand, allocated and available figures, with the next delivery date.
Northwind turned on the backordered event so Tom Reilly, its operations lead, hears about shortfalls early. When a sale was backordered, a job read the sale's lines and the stock for each SKU, and put the short items and their next delivery dates in front of Tom.
The teams that lean on Cin7 Core most, a question each of them asks, and what they connect beside it.
A record in Cin7 Core 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
Codat
ComplyAdvantage
inFlow Inventory
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn Cin7 Core, open Settings → Integrations & API → Cin7 Core API for the account ID. Create an API Application for Memtro alone, since the 60-calls-a-minute limit is per application.
In Memtro, open Connections → Cin7 Core and paste the Account ID and the Application Key. Connect each company separately.
The key has full API access with no scopes. An administrator grants the sale, payment and stock actions by name to the teams that may use them. Events are turned on from the connection's Events tab.
Ask how much of a SKU is available at the main warehouse.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Cin7 Core tools are the same everywhere.
Only when you ask, and only what it has been granted: create a sale (a draft shell for a customer and location); add the order to a sale, as draft or authorised (authorising reserves stock); void a sale; record a payment or prepayment against a sale; remove a recorded sale payment; create a customer; post a stock adjustment (draft or completed); void a stock adjustment. 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.
Account ID and Application Key. In Cin7 Core, open Settings → Integrations & API → Cin7 Core API for the account ID. Create an API Application for Memtro alone, since the 60-calls-a-minute limit is per application.
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 Cin7 Core 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