Anonymised order report by carrier and region

Paid versionService mode

You see which carriers and regions bring the most revenue without any customer names leaving the shop.

What it replaces: half a day of exports and pivot tables

What you write to Claude

„revenue and order count per carrier and per region (state / voivodeship) for q3 2026, paid orders only, no personal data”

The problem

I want to know which carriers and regions bring the most revenue, but I can't get that from the stats tab and I don't want customer names flying around.

What Claude does

  1. Claude prepares a summary grouped by carrier and region, without names or addresses.
  2. It shows you how it will count before running it.
  3. It returns totals in your shop currency.

What you get

A small aggregate table you can share with the team. No personal data leaves the shop in readable form.

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
Marketer / SEO, Agency / freelancer
Tools
ps_db_query

Step by step

  1. Checks service mode and the customer-data level: orders and addresses are customer tables, so the owner must have allowed at least pseudonymised access.
  2. Writes one aggregate SELECT: COUNT and SUM of the order totals from orders joined with address and state, grouped by carrier and state, paid states and Q3 dates only. In pseudonymised mode only plain columns and COUNT/SUM/AVG are allowed, without aliases or functions, so names, e-mails and streets cannot be selected.
  3. Shows the query, runs it with ps_db_query (read-only transaction) and maps carrier and region IDs to names (carrier and state are not personal tables).
  4. Returns totals in the shop currency, net and gross.

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