Run your WordPress and WooCommerce site with Claude

I run a small furniture shop on WooCommerce. New stock arrives from suppliers in batches of about 20: kitchen cabinets, vanity units, sinks, dining tables. Each one is the same routine in wp-admin. Resize the photos, upload them, write a title, write a description, pick the category, type the dimensions and material into the attributes, set the price and stock, save, check the page.

About 10 minutes per product. A batch of 20 is 3 hours 20 minutes of copying the same kind of information from a supplier sheet into the same form.

With Claude connected to the store, the same batch takes me about 5 minutes, and most of that is me looking at the drafts before I say yes.

Where the time goes in manual WooCommerce product entry

The slow part of manual entry is not typing. It is the switching: the supplier sheet in one window, the photo folder in another, wp-admin in a third, and the media library modal that reloads every time you pick an image. Twenty products means twenty rounds of that.

Claude does not get faster at the form. It skips it. It reads your spreadsheet and photo folder, uploads the photos, writes the descriptions in the style of your existing products, and creates all 20 products as drafts in one request.

I measured the machine part on a clean test shop running the same WordPress and WooCommerce versions as mine: 60 photos with alt text and 20 draft products in 10.7 seconds, then publishing and checking all 20 in under half a second. What is left is the part that should be human: reading the drafts.

Why Claude beats the wp-admin product form

• Nothing gets forgotten. By hand, the 17th product is the one missing its material attribute. Claude fills every field from the same sheet, every time.
• Descriptions are consistent. Same structure, same tone, same order of details across the batch.
• No duplicates. Claude checks existing SKUs before creating anything. Running the same batch twice created zero extra products.
• Every photo gets alt text, which almost nobody does by hand.

Why a WooCommerce API key alone is not enough

The obvious setup is: create a WooCommerce API key, paste it into Claude, ask it to add the products. Two things go wrong.

First, it half works. Products appear, the photos do not. A WooCommerce key is not allowed to upload files to WordPress at all, and nothing in the WooCommerce settings tells you so.

Second, and worse, a Read/Write key with no rules means Claude will happily publish, reprice or trash things the moment a prompt is slightly ambiguous. On a live shop, “tidy up the cabinet category” is not a request you want interpreted creatively.

The setup that works fixes both, and the second fix is a single file.

Beyond products: pages, menus, theme and plugins

Products were where I started, because that is where the hours went. The same two keys reach the rest of WordPress: pages and posts, the navigation menu, block theme templates and styles, plugins and site settings. So the same workflow also builds a new shipping page, adds it to the menu, fixes the footer and installs the one plugin you were missing. You describe the change in a sentence, Claude shows the plan, and you say yes.

A site is harder to undo than a product, so the rules get stricter. Claude saves the current version of anything before it overwrites it, and changes one thing at a time. It never edits theme or plugin files, never deletes, and leaves the settings that can take a site offline alone. You take a backup, or work on your host’s staging copy, before any site-wide change. The paid part has the checklist, the ready-made messages for each kind of change, and what to do when a change goes wrong.

What you need to connect Claude to WordPress and WooCommerce

This setup needs no connector and no plugin. Claude talks to the REST API that WordPress and WooCommerce already ship with, using two keys you create in wp-admin. Before you buy, check you have:

• A self-hosted WordPress site on HTTPS, on a current WordPress 6.x. Application Passwords need 5.6 or later and classic menus through the API need 5.9. Most managed hosts qualify. A security plugin that blocks the REST API has to allow it.
• An administrator login, to create the keys. Claude itself can then work under a user with a lower role.
• WooCommerce, for the product part only. Pages, menus, theme, plugins and settings work on any WordPress site, shop or not.
• Claude Code, which needs a paid Claude plan. It runs on your computer, reads the rules file from your folder and makes the API calls. The keys do not work in a normal chat in the Claude app or on claude.ai (more below).
• A backup or a staging copy before site-wide changes. Most hosts offer one or both in their control panel.

Claude Code or the Claude app: which one to use

I found this out the hard way. With both keys pasted into a normal Claude chat, Claude still asked me to add the WordPress connector. It was right to. Chat runs its code in a cloud sandbox whose network, by default, reaches package managers and nothing else (Settings, Capabilities, Domain allowlist: Package managers only). Your shop is not on that list, so the keys have nowhere to go.

• Claude Code, with the keys: everything in this finding. Products, photos from your computer, pages, menus, theme, plugins and settings. It runs on your computer, so it reaches your site directly.
• Claude app or claude.ai, with the WordPress.com connector: posts, pages, media, settings and plugins; its documentation does not cover WooCommerce products. It works on paid WordPress.com plans, and on self-hosted sites only through Jetpack with a paid Jetpack AI or Jetpack Complete plan. The paid part shows where to switch it on.
• Claude app or claude.ai, with the keys only: does not work out of the box. Use one of the two above.

The keys route needs no extra plan and reaches products too, which is why it is the main one here.