# Ecommerce MCP: put your AI behind the store counter

> Ondes PRO’s ecommerce MCP server lets your AI check orders, update products, create promo codes and track shipments, with order writes in test mode by default.

Updated on 2026-10-21 · The Ondes PRO team · https://ondes.pro/en/integrations/mcp/modules/online-store

With Ondes PRO’s **MCP server**, your AI assistant works straight inside your online store: it finds an order, moves its fulfilment forward, fixes a product page, sets up a promo code or checks a shipment. It relies on the real API resources — `shop/commandes`, `shop/produits`, `orders/expeditions` — and its writes to orders go to **test mode** until you ask for the real thing.

## Monday morning, weekend orders

_Example conversation · demo data (Atelier Lumen)_

> **You** : Which orders paid since Friday haven’t shipped yet? Move them to “preparing”.
>
> 🔧 `ondes_ressource` Reads the `shop/commandes` sheet: available filters, the `statut-lot/` action, the test twin.
>
> 🔧 `ondes_appeler` `GET shop/commandes` filtered on paid status and `paid_at` since Friday — 7 orders.
>
> **Assistant** : Seven paid orders are waiting to be prepared, including two Arc floor lamps and one Brass pendant. One thing first: on this resource my writes go to **test mode** by default and would only touch test orders. To update your real orders I need to write for real. Shall I move all seven to “preparing”, without emailing the customers?
>
> **You** : Yes, for real.
>
> 🔧 `ondes_appeler` `POST shop/commandes/statut-lot/` with `reel: true` — 7 orders updated, real write stated.
>
> **Assistant** : Done: all seven orders now show “preparing” in your fulfilment log. As this action specifies, customers were not emailed.

## What your AI can read and do in the store

An ecommerce MCP server is only worth having if it reaches live sales data, not yesterday’s export. Through the `ondes_appeler` tool, the assistant queries your catalogue and orders at the moment you ask, using the filters, search and sorting each resource offers.

For writes, it uses the same moves as the admin: add a fulfilment step to an order, record an offline payment, create a manual sale, update a price or description, upload a gallery image, create a shipment. None of this is rebuilt for the AI: the real API view answers, with its own checks.

## Ecommerce resources available over MCP

| Resource | What the AI reads | What the AI can do |
| --- | --- | --- |
| `shop/commandes` | Orders, amounts, customer, status, payment date | Create, add a fulfilment step (`statut/`, `statut-lot/`), `marquer-payee/`, `manuelle/` sale |
| `shop/produits` | Catalogue, prices, SKUs, category | Create a product, edit prices and descriptions |
| `shop/images-produit` | Each product’s gallery | Add or remove an image |
| `shop/codes-promo` | Existing codes | Create a discount code |
| `shop/paniers` | Open carts | Read-only: a cart is born in the checkout flow |
| `orders/expeditions` | Shipments and tracking | Create or update a shipment |
| `orders/regles-livraison` | Shipping fee rules | Adjust a rule |

Before calling a resource, the assistant reads its full sheet (required fields, filters, actions) with `ondes_ressource`.

## Orders in test mode: the store’s safeguards

A mistake on an order lands on a real customer. The server is built around that.

- **Test mode by default**: `shop/commandes` has a twin under `/api/v1/test/`. Without `reel: true`, a write only touches test orders, which stay out of revenue figures and exports.
- **No delete, no full rewrite**: a paid order is an accounting record. It is corrected with a note or a refund, never erased.
- **The payout account is not a parameter**: it follows from the company concerned, falling back to the parent company. An AI cannot redirect a payment.
- **Fulfilment without email**: the `statut/` and `statut-lot/` actions do not write to the customer, so a batch update never sets off a flood of messages.
- **Simulated payments**: in test mode, `simuler-paiement/` confirms a payment with no card and no Stripe account, so you can check an entire flow before opening the store.

## Typical requests and what happens

| You ask | What the assistant does |
| --- | --- |
| “Where is Maison Verdier’s order?” | Searches `shop/commandes`, reads `shop/statuts-commande` and the linked shipment. |
| “Set the Arc floor lamp to €449 excl. VAT.” | Reads the product, proposes the `PATCH` on `shop/produits`, runs it once you approve. |
| “Create a 15% code for the newsletter, valid until Sunday.” | Creates the entry in `shop/codes-promo` and repeats the exact code back to you. |
| “Log the trade-fair sale, paid by cheque.” | Creates a `manuelle/` order, then calls `marquer-payee/`. |
| “Run a full test purchase without charging anything.” | Creates a test-mode order and confirms the simulated payment. |

## A sale does not stop at the store

An MCP server built only for ecommerce stops at checkout. In Ondes PRO, the same connection carries on: a sale linked to stock deducts the sold units in [inventory management](https://ondes.pro/en/integrations/mcp/modules/inventory), a business customer can get an invoice from [invoicing](https://ondes.pro/en/integrations/mcp/modules/invoicing), and their record grows in [the CRM](https://ondes.pro/en/integrations/mcp/modules/crm).

So you can ask for “best sellers whose stock is running low” or “set up tomorrow’s picking in the Logistics board”: the assistant combines store, inventory and [Kanban](https://ondes.pro/en/integrations/mcp/modules/kanban) in a single answer.

> **Store permissions apply to the AI too** — An MCP connection acts with your role. Without access to the Store module, the assistant sees neither orders nor the catalogue. For a colleague who should only look, create an API key limited to reading the store. Full details on the [MCP server security](https://ondes.pro/en/integrations/mcp/security) page.

## Keep exploring

- [Ecommerce](https://ondes.pro/en/integrations/mcp/industries/ecommerce) — Orders, stock, promotions and customer service: your AI assistant runs the store alongside you.
- [Connect your website](https://ondes.pro/en/integrations/mcp/guides/connect-your-website) — Show the catalogue and take Stripe payments from a site that is already live, without rebuilding it.
- [Stripe](https://ondes.pro/en/integrations/stripe) — Take store payments into your own Stripe account, company by company.
- [Modules available over MCP](https://ondes.pro/en/integrations/mcp/modules) — Eleven business modules behind one MCP server: what the assistant can read and do in each.

## Frequently asked questions

### What is an ecommerce MCP server?

It is a standard access point that lets an AI assistant such as Claude read and change an online store’s data: orders, products, promo codes, shipments. In Ondes PRO it is built into every workspace at `https://<workspace>.ondes.pro/mcp/`.

### Could the AI change a real order by mistake?

Not without being explicitly told to. Writes to `shop/commandes` go to test mode by default; the `reel: true` flag is required to touch a real order, and every response states which mode was used.

### Can an order be deleted through the API?

No. Orders cannot be deleted or fully rewritten, because a paid order is an accounting record. You correct it with a note, a fulfilment step or a refund.

### Can the assistant take a payment?

It can create an order, which generates its Stripe payment and returns what the customer needs to pay, or record a payment received offline. The account that gets paid follows from the company concerned and cannot be chosen in the request.

### Does the store’s MCP access cost extra?

No, it is included in every Ondes PRO plan, just like the store module itself. See [pricing](https://ondes.pro/en/pricing).

### Do customers get an email when the AI updates fulfilment?

Not with the `statut/` and `statut-lot/` actions, which add a fulfilment step without writing to the customer. That keeps a batch update from sending a string of messages.