Custom product export for a supplier or marketplace
A marketplace or supplier gets exactly the file they ask for, without building an export by hand.
What it replaces: 1-2 h of building an export
What you write to Claude
„give me a csv of active products in Work gloves: ean, reference, name, gross price, stock, main image url, default category. comma separated”
The problem
A marketplace wants a file with EAN barcode, stock, price and a link to the main photo. The standard export doesn't have the columns I need.
What Claude does
- Claude collects exactly the columns you need.
- It shows you how it gets them before running.
- It gives you a ready file and flags products with missing data.
What you get
A spreadsheet file with exactly the columns you asked for. 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.
Related use cases
- Report products that haven't sold in 12 months
- Find products without images, EAN or manufacturer
- Pull a custom report straight from the shop's data
For developers
- Area
- 5 · Service mode
- Connector
- service connector
- In the free Audit
- no, paid version only
- For
- Store owner, Agency / freelancer
- Tools
- ps_db_query, ps_search_products
Step by step
- For small lists, uses ps_search_products columns without service mode.
- For larger or custom exports, writes one SELECT on product, product_lang, product_shop, stock_available, image and category_lang and runs it with ps_db_query in service mode, shown first; product data is not customer data, so no customer-data level is needed. Large exports are paged 200 rows at a time.
- Builds image URLs from the image IDs and shop domain, and returns the data as CSV text you can save.
- Flags rows with missing EAN or images.
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