WooCommerce + WordPress Studio + OpenClaw: The Local Dev Setup

If you are building or testing a WooCommerce store locally, WordPress Studio handles the environment. OpenClaw handles the store management. Together, they cut out most of the time you spend clicking around the WooCommerce admin.

This post covers the local development workflow. If you are connecting OpenClaw to a live production store, see OpenClaw + WooCommerce: Managing Your Store with AI.

npm install -g @skunkceo/cli   # Install Skunk CLI
skunk install woocommerce      # Add the WooCommerce skill to OpenClaw
studio wp plugin install woocommerce --activate
studio wp wc update            # Run database setup

WordPress Studio uses SQLite as its default database. For most local development and testing this works fine. WooCommerce runs on top of it without any manual configuration needed.

If you need to test against MySQL specifically, Studio supports that too. You have two options:

Option 1 — Add an existing site with MySQL already configured. If you have a site directory that includes a wp-config.php pointing to a MySQL server, Studio will detect it, skip the SQLite setup, and use the configured database.

Option 2 — Switch an existing Studio site from SQLite to MySQL. If you have already created a site in Studio and want to move it to MySQL:

This is a manual file-level operation rather than a setting in the Studio UI. For most WooCommerce development work the default SQLite setup is the path of least resistance.

The WooCommerce skill gives OpenClaw the context it needs to manage WooCommerce stores through Studio's WP-CLI wrapper.

Install it with the Skunk CLI:

skunk install woocommerce

That is all the configuration needed. Once the skill is installed, OpenClaw knows how to work with WooCommerce via the studio wp commands.

With the skill installed and a Studio site running, you can ask OpenClaw to handle the WooCommerce installation:

"Install and activate WooCommerce on my local Studio site."

OpenClaw will run the plugin installation through Studio's WP-CLI wrapper:

studio wp plugin install woocommerce --activate

After activation it will run the database update to make sure all required tables are created:

studio wp wc update

You can ask OpenClaw to verify the installation:

"Check that WooCommerce installed correctly and all tables are in place."

Once WooCommerce is active, ask OpenClaw to configure the basics:

"Set up the store for UK with GBP currency."

OpenClaw runs the relevant WP-CLI commands:

studio wp wc setting update general woocommerce_default_country --value="GB"
studio wp wc setting update general woocommerce_currency --value="GBP"

From here you can manage the store through natural language rather than individual commands.

The WooCommerce skill exposes products, orders, customers, and coupons through Studio's WP-CLI. Here is what that looks like in practice.

//Products

"Create a simple product called 'Starter Kit' priced at 29.99 with 50 units in stock."

"List all products currently out of stock."

"Update all products in the accessories category with a 10% price increase."

//Orders

"Show me all orders from the last 7 days still in processing status."

"How many orders were completed this week?"

Useful during development for checking your store flow is working without opening the admin dashboard each time.

//Customers

"List all customers who registered in the last 30 days."

"Does a customer account exist for this email address?"

//Coupons

"Create a 20% discount coupon valid until the end of the month."

"List all active coupons and their usage counts."

Once the skill is installed and WooCommerce is active, verify the connection:

studio wp wc --info

This outputs the WooCommerce version, database version, and any warnings. No errors means OpenClaw has full access to the store.

The local development workflow with Studio and OpenClaw is faster because you are not switching between the terminal, the browser, and the admin dashboard. You ask, OpenClaw acts, and you see the result immediately.

It is also useful for populating test stores. Instead of manually creating 20 products through the admin, describe what you want and OpenClaw builds them.

For production stores and REST API configuration, the full guide covers that setup in detail.