The work Claude can take off your hands
Start by letting Claude check your store and report what's wrong. Then let it fix texts, then prices, then the look of your store and your modules, one switch at a time. You see each change before it's saved.
| Step | Example job | After install |
|---|---|---|
| Free check-up | "Why can't customers find the Oslo sofa?" | On |
| Texts and Google | "Rewrite the descriptions in Running shoes." | On once you allow changes |
| Prices and stock | "10% off all sofas for Black Friday." | Off until you switch it on |
| Look of the store | "Move the trust badges above the Add to cart button." | Off until you switch it on |
| Modules | "Switch off the newsletter pop-up module." | Off until you switch it on |
| Service mode | "After the update the store shows a blank page. Check the files and settings." | Off, switched on for 1 to 24 hours |
Free check-up
After install: On"Why can't customers find the Oslo sofa?"
Texts and Google
After install: On once you allow changes"Rewrite the descriptions in Running shoes."
Prices and stock
After install: Off until you switch it on"10% off all sofas for Black Friday."
Look of the store
After install: Off until you switch it on"Move the trust badges above the Add to cart button."
Modules
After install: Off until you switch it on"Switch off the newsletter pop-up module."
Service mode
After install: Off, switched on for 1 to 24 hours"After the update the store shows a blank page. Check the files and settings."
Customers' personal data stays hidden from Claude by default.
You see every change first, and you can always go back
Claude can look at your store freely. When it wants to change something, it first shows you what it will change: the current text or price and the new one. It saves only after you say yes.
Change safety →Free check-up: Claude finds what's wrong
After installation Claude can only look, and it can't change anything. That's already useful. Ask it what's wrong with your store and it will tell you, in plain words:
Free check-up →Texts and Google, for a whole category at once
The work that eats whole afternoons: rewriting descriptions copied from the manufacturer, fixing how products look in Google, filling in image descriptions, updating the Delivery and Returns pages. Claude does it for one product or a whole category in one go, in your tone and your language. It can also add new products with photos (as switched-off drafts for you to check) and translate your store into another language.
Texts and Google →Prices, promotions and stock, with a safety net
A clumsy description is a cosmetic problem. A wrong price or a discount code with no limit can cost you money within minutes. That's why prices sit behind their own switch, off until you turn it on.
Prices and stock →The look of your store, with a copy of every file
Small design changes usually mean a message to your developer and a wait. Claude can change texts and layout in your store's theme when you ask, and it saves a copy of every file before touching it. If you don't like the result, one sentence brings the old version back.
Look of the store →
Don't know where to start? Pick a ready-made job.
Every paid license includes 14 ready-made jobs, such as "Get my product pages ready for Google and AI search", "New products from a list", "Prepare Black Friday" or "Why isn't this product showing?". Pick one from Claude's menu and Claude takes it from start to finish: it looks, makes a plan, shows you each change and reports back. Four of them work in full in the free edition, and seven more give you a plan of changes there.
The TellMyShop Consultant comes with them: what a good e-commerce adviser knows about Google, AI search, product pages and selling, so Claude can tell you which changes matter most.
For your developer
The jobs are MCP prompts exposed by the module, so they appear in the connector's menu in Claude with nothing to install. The Consultant is a Claude skill downloaded from the customer account.
Modules and service mode
Two steps for the moments when you'd usually call your developer. Both are included in every paid license, are off after installation and work only through a separate, more restricted connection to Claude, just like the Look of the store.
- Modules. Claude switches a module on or off, changes its settings, installs or updates a module from a ZIP file at an address you give, and when there's no other way, edits a module file after making a copy. It warns you about payment and shipping modules. Uninstalling deletes a module's data, so Claude suggests switching it off first, and to uninstall you have to type the module's name.
- Service mode. You switch it on for 1, 4, 8 or 24 hours, then it turns itself off. During that time Claude has developer-level access: store files, the database and PrestaShop settings. Every change has a preview, a copy is made before a file or database rows change, and files with passwords are blocked. Customer data stays hidden unless you change the access level yourself.
- Anything that can't be undone, such as uninstalling a module or database changes made by a module update, Claude tells you about before saving.
Your customers' data stays private
Claude works on your catalog, texts and settings. Your customers' names, emails and addresses are hidden from it by default.
The module finds personal data on its own. coming soon
It recognises every table with emails, names, phone numbers, addresses and IP addresses, including tables from other vendors' modules. You don't have to point at anything.
Three levels instead of one switch. coming soon
No access. Hidden data (default): Claude sees order numbers and amounts, but not who bought. Full access for 1 to 24 hours, for example to handle a complaint, then it switches itself off. You type the reason when you turn it on, and the module logs it.
Files Claude won't open. coming soon
Server logs, customer uploads, database dumps and files with passwords are always blocked. In the error log, emails and IP addresses are hidden.
Encrypted change history. coming soon
Personal data in the change history and file backups is encrypted with a key kept outside the database. A leak of the database alone won't expose it.
For your developer: table detection by column names (email, firstname, lastname, phone, address1, ip_address…) in INFORMATION_SCHEMA; one filter on every tool's output; var/logs, upload/, download/, *.sql, *.gz, .git, parameters.php blocked; libsodium encryption with the key in a file outside the database.
What you need
- A store on PrestaShop 8.1 or newer, including 9, on a server with PHP 8.1 or newer
- Any Claude account, including the free one
- Nothing else: no PrestaShop Account, no API keys, no extra subscriptions
For your developer
PrestaShop 8.1+ or 9, PHP 8.1+, HTTPS with a public address (Claude connects from Anthropic's servers, so staging copies need this too). Any Claude account will do, including a free one.
The English version launches in January 2027
Join the list and you'll hear first when it opens, with a 72-hour head start on the launch offer.