Monday dispatch
On Monday morning the shop manager asks which orders are still unfulfilled. Memtro lists them with order number, customer, payment state and item count, and opens any order whose line items and shipping address matter for packing.
What sold this week, which orders are unfulfilled, and what is low on stock.
Connect Squarespace Commerce with a Developer API key, and Memtro reads store orders with customer, payment and fulfilment state, totals and line items, products with variants, prices and stock, inventory per SKU, transactions with payments, refunds and taxes, and the site's contacts. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can mark an order fulfilled with tracking, adjust live stock, add or edit contacts, and permanently delete a contact or a product. Nothing is refunded, and customers are emailed only if you ask.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Squarespace Commerce tool, reads what it needs, and answers with the source cited.
These tools change something in Squarespace Commerce. 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, then add the address it shows as a webhook in Squarespace Commerce, choosing the same kinds; the tab shows Squarespace Commerce's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Squarespace Commerce signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Squarespace Commerce 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.
What sold this week?
Which orders are unfulfilled?
What is low on stock?
Mark order 1042 fulfilled with Royal Mail tracking number RM123456789GB and email the customer
Set stock for the blue mug to 40
On Monday morning the shop manager asks which orders are still unfulfilled. Memtro lists them with order number, customer, payment state and item count, and opens any order whose line items and shipping address matter for packing.
After packing order 1042 for a Northwind buyer, Ella Grant asks Memtro to mark it shipped with the tracking number and tell the customer. Memtro marks the order fulfilled with the carrier and tracking link, and Squarespace emails the customer about the shipment.
The teams that lean on Squarespace Commerce most, a question each of them asks, and what they connect beside it.
A record in Squarespace Commerce 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.
Developer API keys need the Squarespace Commerce Advanced plan
In Squarespace open Settings → Advanced → Developer API Keys and generate a key with Orders, Products and Inventory, Transactions (Read Only) and Contacts. Choose Read and Write on Orders, Products and Inventory or Contacts only where Memtro should fulfil orders, change stock or edit contacts. Permissions cannot be changed later
In Memtro open Connections → Squarespace Commerce, paste the Developer API key, shown only once, add a Site name if you like, and connect
Ask which orders are still unfulfilled
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Squarespace Commerce tools are the same everywhere.
Only when you ask, and only what it has been granted: add a contact to the site's contacts (never subscribed to marketing); mark an order fulfilled with shipment tracking, emailing the customer only if asked; increase, decrease or set stock for product variants; edit a contact's name, locale or email (marketing consent untouched); delete a contact (permanent); delete a product from the store (permanent). 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.
Developer API key. Developer API keys need the Squarespace Commerce Advanced plan.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Squarespace Commerce, choosing the same kinds; the tab shows Squarespace Commerce's own steps. 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