AI for manufacturers, from the ERP to the shop-floor database
A manufacturer's answers are in the ERP, the sales system, the production database and a Teams channel, and the person who can join them is always on the floor. Memtro connects to NetSuite or Dynamics 365 Business Central, the sales CRM, the databases and the documents, and answers questions across them with every figure cited to the order, stock record or row it came from.
7-day free trial · card on file, nothing charged until it ends · cancel any time
Orders, stock, suppliers, quality records and the ledger answered from one memory, with every figure cited to its record.
The systems these questions draw on, connected to one memory. Every connector reads by default; the tools that change something are granted by name, per team.
What it looks like today
- 01Whether an order can ship depends on stock in the ERP and a schedule in a database nobody outside production can query.
- 02Customer promises on delivery dates are made in email and checked in the ERP, by hand.
- 03The same part number means different things in two systems and nobody wrote down which is right.
- 04Month-end questions from finance land on the operations manager, who answers them from memory.
- 05A supplier's delay is known on the floor on Monday and in sales on Thursday.
- 06Quality issues are argued out in a Teams thread and summarised in a spreadsheet, and neither one is the record.
What Memtro does about it
One memory in front of the systems you already pay for, reading by default and acting only where an administrator has granted the tool by name.
- Connect NetSuite or Dynamics 365 Business Central, Dynamics 365 Sales, SQL Server or Postgres, Outlook, Teams, SharePoint and monday.com, reading by default and acting where you grant it.
- Ask whether an order can ship and the answer joins the order, the stock and the production schedule, with the SQL shown and each figure cited.
- Jargon that recurs across systems, a part name used two ways, is found overnight and put to a person, whose answer rides in every later prompt.
- Commitments on delivery made in email are kept as a register and checked against the ERP for whether they were met.
- Schedule jobs: orders due to ship this week without stock, purchase orders overdue from suppliers, a daily production summary posted to Teams.
System by system
What Memtro reads in each part of the stack, and what it may change there once the tool has been granted.
The ERP
NetSuite or Dynamics 365 Business Central: sales orders, items, stock, purchase orders, bills and the month's position, read as the system of record it already is.
Sales
Dynamics 365 Sales, HubSpot or Salesforce: quotes, orders in the pipeline and the customer behind each promised date.
Production databases
SQL Server, Postgres, MySQL or MongoDB: schedules, routings, batches and yields. Schema first, then a bounded read-only query with a row cap and a timeout, and the SQL shown.
Mail and chat
Outlook and Microsoft Teams: what was promised to a customer, what a supplier confirmed, and the channel a scheduled summary is posted into.
Documents
SharePoint and OneDrive: specifications, drawings, certificates and quality records, searched by what they contain rather than by who filed them.
Work tracking
monday.com, Asana, Jira or ClickUp: the engineering changes, introductions and corrective actions that follow a problem on the floor.
There are 144 connectors in all, each with its own tools, its own permissions and a page of its own. Browse every connector →
Who asks what
Operations manager
Answers the ship-or-not question from the order, the stock and the schedule at once, with the query shown and every figure cited.
Planner
Sees what the week cannot make before the week starts: orders without stock, orders without a slot, and the purchase orders holding each up.
Account manager
Tells a customer the truth about their date, from the ERP rather than from the last thing anybody said on a call.
Quality
Pulls the batch, the specification and the correspondence together, and keeps what was agreed with the customer where the next person will find it.
From order to despatch
- 01
The order
Before a date is promised, one question reads the stock, the schedule and the open purchase orders, so the promise is made against the systems rather than against optimism.
- 02
The plan
A morning job lists orders due to ship in seven days with insufficient stock or no production slot, named by customer, so the escalation happens while it is still cheap.
- 03
The supply
Overdue supplier purchase orders arrive each Monday with the sales orders they block, which turns chasing from a hunch into a list.
- 04
Despatch and after
What was promised in email is checked against what the ERP shipped, and the quality record, the specification and the thread stay joined for the next time the part comes up.
Ask it like this
Plain English, from chat, your editor, a scheduled job or your own agent. In agent mode each question also checks the other systems that know about the same people, companies and references, and the answer ends with a line per system consulted.
- NetSuite
- Dynamics 365 Business Central
- Dynamics 365 Finance & Operations
- ERPNext
- Odoo
Every figure in the answer cites the record it came from, and the run ends with a line per system consulted.
- ›Which purchase orders from Acme Components are overdue, and what do they hold up?
- ›What did we promise BigCo on delivery in the last month, and did we meet it?
- ›Stock on hand for part 4411-B across both warehouses, with the query you ran
- ›Which customer orders are at risk this month, and what is the cause of each?
- ›What did the last three batches of 4411-B yield, and how does that compare with the year?
- ›Which suppliers have been late more than twice this quarter, and on what?
- ›What specification did we agree with BigCo for the revised part, and where is it written down?
Work that runs itself
A job is a prompt the agent runs on a cron schedule as its owner, with their tools and connections. Say any of these in chat and the job exists; every run's report is kept in a chat you can question.
- schedule:Every day 07:00: orders due to ship in seven days with insufficient stock or no production slot
- schedule:Every Monday 08:00: supplier purchase orders overdue, with the open sales orders they block
- schedule:Every day 17:30: production summary by line against plan, posted to the operations channel
- schedule:Every Monday 07:30: quotes and orders with a promised date in the next three weeks and no production slot
- schedule:Every day 08:00: quality issues raised in Teams or the ERP yesterday, with the part, the batch and the customer affected
Questions people ask
Can it change the ERP?+
Only where you grant it. Actions are marked, granted by name per team and used when a person asks; Teams can post a message today, and ERP actions are granted the same way as they arrive. Database queries always run inside read-only transactions with a row cap and a timeout.
Does it reach our MES or custom systems?+
Any system that exposes a database is reachable over SQL Server, Postgres, MySQL or MongoDB, schema first, with the SQL shown in every answer.
Who can see what?+
Connections are granted to named teams, tool by tool, and nothing shared is usable until an admin says so. Production can query the schedule without seeing payroll.
Does this need an integration project?+
No. A connector is credentials and a grant, and the agent reads the schema itself rather than waiting for somebody to model the data first. Most of a stack is connected in an afternoon.
Can it reach a system on the factory network?+
Where it exposes a database, yes: Postgres, MySQL and SQL Server connections take an optional SSH tunnel through a bastion host, so nothing needs a public address.
Who sees cost and margin?+
Whoever you grant it to, tool by tool. Production can query the schedule without touching the ledger, and the ledger can be granted to finance alone; somebody in two teams gets whatever either of them allows.
The same work, by team
The same connectors and the same memory, described through the job somebody does rather than the business they do it in.
- OperationsMonitors and digests that run themselvesJobs are prompts the agent runs on a schedule with the same tools as their owner. Create them in plain language, get the report in a chat, pause or change them in a sentence.Memtro for operations
- Data and analyticsQuestions answered from the warehouse, with the SQL shownPoint Memtro at a read-only replica and anyone can ask the warehouse a question in plain English. The agent reads the schema, writes the query, runs it inside a read-only transaction, and shows its work.Memtro for data and analytics
- FinanceAsk the ledger questions in plain EnglishXero, Stripe and the warehouse answer through tools that read by default, and Xero can raise a draft invoice or record a payment when you ask and an administrator has granted it. Duplicate charges, aged receivables, revenue by segment: one question, with the figures cited to their source.Memtro for finance
Ask it about your own business
Connect the first two systems, ask the question you opened this page with, and see where the answer comes from. About five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time