Pull a custom report straight from the shop's data

Paid versionService mode

Any count or list the back office can't show is one question away, with nothing in the shop changed.

What it replaces: 1 h of exports and pivot tables every month

What you write to Claude

„count active, inactive and out-of-stock products per default category, plus products without images. read only, no customer data”

The problem

For the monthly client report I need out-of-stock and hidden products per category. The back office has no such view, so I export and build a pivot table every month.

What Claude does

  1. Claude writes the question to the shop's data and shows it to you.
  2. It runs it in read-only mode, so nothing can change.
  3. It returns a table you can paste into the report.
  4. Customer records stay out unless you have allowed masked access.

What you get

A table of counts per category, ready for the report. Nothing in the shop changes.

You stay in control

Claude only reads. Nothing in your shop changes. This deep access uses the separate, extra-protected connection and works only for the few hours you switch it on.

See pricing

Related use cases

For developers
Area
5 · Service mode
Connector
service connector
In the free Audit
no, paid version only
For
Agency / freelancer, Developer
Tools
ps_db_query

Step by step

  1. Checks that service mode is switched on (time-limited) on the service connector.
  2. Writes one SELECT on product, product_shop, stock_available, category_lang and image (prefix ps_); no customer tables are needed.
  3. Runs it with ps_db_query: read-only transaction, at most 200 rows (LIMIT added if missing), long values cut.
  4. Returns the table; the same query can be reused every month.

Safety

Service mode (block 5) works only through the service connector (separate token, allowlisted IP addresses) and only while its time-limited switch is on (1, 4, 8 or 24 h); then it switches itself off, and the owner gets an e-mail when it is switched on. ps_db_query runs one statement in a read-only transaction and returns at most 200 rows, with e-mails, phones and IPs masked. Staff, permission, configuration and connector tables are blocked. Tables with customer personal data (orders, addresses, carts and similar, detected by their columns, also in third-party modules) follow the customer-data level set by the owner: off (blocked), pseudonymised (personal columns masked; only plain columns and COUNT/SUM/AVG, no aliases, functions, UNION or WITH) or full for 1-24 h with a stated purpose.

Last updated: 2026-10-05