Every one of these is a real question asked during four weeks of early use across
three properties. Ask in a sentence. The answer comes back in the assistant you already have open.
Ask in a sentence
Anyone on your team asks in plain language, signed in as themselves. No export, no ticket, no waiting on someone who knows the report.
Answers carry their sources
Every figure comes back with the orders, receiving notes and invoices behind it, so it can be checked rather than trusted.
One connector, the whole path
Requests, orders, receiving, invoices, stock, recipes and catalogues answer together, under the permissions that person already has.
What the trend is doing
Spend and commitments read forward, not just back, so the question is what to do next rather than what happened.
Guardrails
It can read. It can draft. It cannot act for you.
Every session is a real PurchasePlus user, not a shared service account. The assistant
sees exactly what that person can already see, and nothing more. Tools they are not entitled to are
never offered.
Read Always
Anything that person can already open in PurchasePlus.
Purchase requests, orders, receiving notes
Invoices, credit notes, statements
Stock on hand, stocktakes, transfers
Recipes and their current cost
Supplier catalogues and prices
Any report they can already run
Draft Reviewed
Created as a draft and left open. Nothing is submitted.
Create or update a purchase request
Add lines, or reorder into a new draft
Add a product to a buy list
Create a buy list from an invoice
Add an ingredient to a recipe
Create suppliers from a list
Create a catalogue from an invoice
Export a report and take the link
Decide You
Never the assistant. There is no setting that changes this.
Approving a request, invoice or credit note
Sending or placing a purchase order
Deleting a record
Deactivating a supplier
Completing a stock transfer
"The guardrails are right. Because approving, sending, deleting and deactivating stay
with a person, we never worried the connector could do something irreversible."
André Bosman (FC), Crocombe Hotels
From four weeks of early use
Real questions, real money found.
A resort group, three properties, about twenty working sessions. Supplier names,
product names and exact figures are removed.
01Before you pay
A price typed at ten times the real price
One supplier had a pile of invoices and finance wanted to know if anything was wrong before the money went out. They caught a price entered at ten times the real one, and a bill that may have been paid twice. "This is saving real dollars."
02Across the group
The morning that used to go on exports
Finance wanted one picture of what was still open across three properties and three currencies. "I used to spend a morning on exports for that picture. Now it is one conversation, so I can spend that time on the exceptions."
03Matching
Why is this invoice blocked?
A milk invoice was blocked and the block did not explain itself. The milk had been counted as single units instead of cartons. Minutes instead of an hour-long hunt, and fixed on the spot.
04Suppliers
Who is actually cheaper, once freight is in
The same seafood line came from several suppliers, and the invoice price was not the full story until freight was added. On one line the cheaper name changed, worth a five-figure difference a year.
0
purchaser tools on the production connector
The whole purchaser path, plus everything around it. A user who
is not entitled to drafts, inventory, recipes or report export simply sees fewer.
The config above has no credentials in it, on purpose. Access is tied to your own
PurchasePlus user and we set it up with you on a short call, so your permissions, your
organisations and your guardrails are right from the first question.
Connect our MCP to your procurement operation with AI agents.
We will connect it with you, show you what your team can ask on day one,
and set the guardrails before anyone types anything.