Integration · Shopify

Connect Claude to your Shopify stores.

The full order lifecycle as typed tools: fulfilments with carrier and tracking, refunds calculated before they're executed, cancellations, products and inventory. Claude proposes; nothing changes on a store until you sign it off — per client store, on the record.

Claude Desktop · Claude Code · ChatGPT connectors · Gemini CLI · any MCP client

Claude Desktop · mcp.datavessel.io
> customer on #1042 was double-charged shipping — refund it
calculate_refund … €4.90 refundable on shipping
create_refund €4.90 → waiting for your sign-off
✓ approved from the phone · 1 row written to the ledger
The tool catalogue

22 typed tools. 10 of them change the store — every one behind sign-off.

Admin API as one typed catalogue, refunds done properly: the amount is calculated by Shopify first — a dry run — then executed at exactly that number. Reads run free; the 10 writes go through the sign-off inbox.

01

Read the store

  • Orders, products, customers, inventory
  • Discounts and analytics
  • Flexible GraphQL queries for anything else
02

Run the orders

  • Fulfil with carrier and tracking, customer notified
  • Calculate a refund, then execute the exact amount
  • Cancel with restock · fix shipping addresses before dispatch
03

Keep the catalogue

  • Create products — drafts by default
  • Update titles, descriptions, tags, SEO meta
  • Adjust inventory levels
Three ways in

The same tools, wherever the work happens.

One connection; every surface reads and writes through the same typed catalogue, with the same gates.

From Claude, over MCP

Claude Desktop, Claude Code or any MCP client connects to one endpoint and sees the Shopify tools for the store you scope it to.

The MCP endpoint

From the terminal

The datavessel CLI runs the same catalogue as commands and ships a Claude Code plugin whose read agents are structurally blocked from writing.

The CLI

In the operations center

Policies subscribe agents to store events — orders, checkouts, disputes — asking you first or running on autopilot, per client store.

The use cases
Why not just an API key

An LLM with your admin credentials is a liability. This is an operations layer.

01

Writes wait for you

A raw Admin API token lets a model do anything, silently. Here every write pauses in the sign-off inbox — approve from the web or the mobile app — until you trust a job enough to put it on autopilot.

02

Scoped per client store

Tools are scoped to one store at execution time. An agency's clients keep their data and credentials isolated — one store's run cannot touch another's.

03

Every change in the ledger

What changed, on which store, approved by whom, for how much. Refund amounts come from Shopify's own calculation, and the ledger compiles into the per-client report.

Questions

Asked before connecting.

How do I connect Claude to Shopify?

Install datavessel from the Shopify App Store or connect the store in datavessel, then point Claude Desktop, Claude Code or any MCP client at the datavessel MCP endpoint. Claude sees the Shopify tools for that store immediately.

Can Claude change my store?

Only through the 10 write tools, and every write waits in the sign-off inbox until a human approves it. Refunds are calculated by Shopify before execution, new products are drafts by default, and each approved change is recorded in the ledger.

Does this work for several client stores?

That's the point — datavessel is an operations center for agencies. Each client's stores are isolated, tools execute scoped to one store, and each client has their own ledger and report.

Does it work with ChatGPT or Gemini, not just Claude?

Yes. The endpoint is standard MCP, so any MCP client works — Claude Desktop and Claude Code, ChatGPT via connectors, the Gemini CLI, Cursor and others. Inside the operations center, agents run on whichever key you bring: Anthropic, OpenAI or Google.

What does it cost to run?

You bring your own AI key (Anthropic, OpenAI or Google) and pay the model provider directly — datavessel adds no markup on tokens. Plans are priced by connected stores, free for one store, billed through Shopify for App Store installs.

Is my store data used for training?

Your data is isolated per customer and scoped per store, and model calls run on your own key under your provider's terms. See the security page for the full commitments.

Every client's Shopify store, one sign-off away.

Connect a store, ask Claude for the first sweep, and approve what goes out — every change on the record.

Free for one store · 14-day trial on paid plans · no card · bring your own AI key