Which orders came in yesterday, and what is out of stock in our PrestaShop store?
PrestaShop connects Memtro to your own store through its Webservice API. It reads orders by date, customer, status or reference, with the total paid, payment method and status. One order opens with its product lines, the customer's name and email, and its status history. It finds customers by email or last name, lists products with prices excluding tax, and shows stock levels. Customer records never include addresses, phone numbers or birthdays. When asked and granted, it can change an order's status, record a tracking number, emailing the customer only if asked, and set a product's stock quantity.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right PrestaShop tool, reads what it needs, and answers with the source cited.
These tools change something in PrestaShop. 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 PrestaShop 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 came in yesterday?
What is out of stock right now?
Show the status history of order 1042.
Which orders has Priya Sharma placed?
Mark order 1042 as shipped with tracking number JD0146 and email the customer.
Sarah Chen, operations manager at Northwind, asked where order XKBKNABJK had got to. Memtro opened the order and listed its status history, showing payment accepted on Monday and nothing since. She passed the customer's name and email to the warehouse.
Dan Fletcher, buyer at Acme Ltd, asked Memtro to record the courier's tracking number on order 1042 and mark it shipped. Memtro recorded the number, which the customer sees in their account, moved the order to Shipped, and emailed the customer because Dan asked it to.
The teams that lean on PrestaShop most, a question each of them asks, and what they connect beside it.
A record in PrestaShop 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
inFlow Inventory
Metronome
MRPeasy
Persona
Precoro
Printify
Rydoo
Saleor
Snipcart
Swell
Veeqo
Zuora
VAT Sense
PaystackIn the PrestaShop back office, go to Advanced Parameters → Web service, set Enable PrestaShop's webservice to Yes and save.
Add new webservice key, Generate a key, and tick View (GET) on orders, order_states, order_histories, order_carriers, customers, products and stock_availables. Only for the actions you want Memtro to take, add Add (POST) on order_histories and Modify (PUT) on stock_availables and order_carriers. Save and copy the key.
In Memtro, open Connections → PrestaShop and enter Store host, Subfolder if the shop sits in one, and Webservice key.
Ask: which orders came in yesterday?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The PrestaShop tools are the same everywhere.
Only when you ask, and only what it has been granted: change an order's status (the customer is emailed only if asked); set the stock quantity of a product or combination; record a carrier tracking number on an order (the customer is emailed only if asked). 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.
Store host, optional subfolder and Webservice key. In the PrestaShop back office, go to Advanced Parameters → Web service, set Enable PrestaShop's webservice to Yes and save.
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