By Fahad Murtaza · Published · Updated
Change prices on 50 WooCommerce products, verify, then roll back
A store owner asks for a 10 percent price increase on every product in the “Mugs” category. In wp-admin that is fifty product screens, fifty saves, and no easy way back if the number was wrong. With WP MCP your AI client does the same job in one conversation, and every change it makes is snapshotted first, so you can undo the batch as easily as you made it.
Free or Pro? Free. Every tool in this guide (list-products,
get-product, update-product, update-variation, list-operations,
rollback-operation and rollback-session) ships in the free plugin.
What you need
- WP MCP installed and connected to your AI client (Claude Desktop, Cursor or any other MCP client). The connection docs cover it.
- WooCommerce active, with the products you want to change. Work on a staging copy the first time if you have one; the rollback covers you either way.
Step 1: find the products
Start by asking for the list, not the change. You want to see what the agent is about to touch.
› List every published product in the Mugs category with its current price.
The agent calls list-products with category: "mugs", status: "publish"
and a per_page large enough to get them all (it pages if there are more).
You get names, IDs and prices back. Read the list. If a product is in the
wrong category, or a sale price is already set, say so now, because the
agent will treat whatever is listed as the batch.
For anything that looks odd, ask for detail:
› Show me product 2041 in full.
get-product returns the regular price, sale price, stock and categories for
one product, so you can see exactly what will change.
Step 2: make the change as one session
Now ask for the change, and ask for it as a single undoable unit.
› Raise the regular price of each of those products by 10 percent, rounded to
the nearest .99, as one session so I can undo it all at once.
The agent calls update-product once per product with the new
regular_price and the same session_id on every call. A product is an
ordinary WordPress post underneath, so each call snapshots the product before
writing, and the shared session_id groups the fifty snapshots together.
Variable products need one more step. Prices on a variable product live on
its variations, not on the parent. The agent lists them with
list-variations and updates each with update-variation, again passing
the same session_id.
Nothing in this flow asks for confirm: true, because changing a price is a
reversible write. Deleting a product would be different: delete-product
demands confirmation before it does anything.
Step 3: verify before you walk away
Do not take the agent’s summary at face value. Ask it to read the result back from the store.
› List the Mugs products again and show old price next to new price.
list-products runs again and the agent compares the new prices with the
values it read in Step 1. Then open the shop page in a browser. WooCommerce
caches prices in a lookup table and some caching plugins hold the old page,
so if the storefront still shows the old price, ask the agent to run
clear-cache and reload.
You can also audit the batch itself:
› Show me the last 60 operations.
list-operations returns every write WP MCP made, each with its
operation_id, the object it touched and the session_id it belongs to.
This is the same record the rollback uses, so if a product is missing from
it, that product was never changed.
Step 4: roll back (one product or all fifty)
Say the rounding rule was wrong on one product:
› Undo the price change on product 2041 only.
The agent finds that product’s operation_id in list-operations and calls
rollback-operation. The snapshot is restored exactly, price and stock
included, and the other forty-nine products stay as they are.
Say the whole increase was a mistake:
› Roll back the entire price change session.
rollback-session takes the session_id and unwinds every operation in it,
in reverse order. Fifty products go back to the prices they had before Step
2. Run the Step 3 check again to confirm.
Why this is safer than a spreadsheet import
A CSV import overwrites prices with no memory of the old ones. WP MCP keeps a snapshot per write and a session per batch, so “verify, then roll back” is a normal part of the workflow rather than a recovery project. The agent also never sees your payment gateway: price, stock and description changes are all it needs, and that is all these tools expose.
Try it on your store
Install the free plugin, connect your AI client, and run the four prompts above on a category of your own. When you want Elementor editing, bulk operations across builders, or the WP-CLI and PHP snippet tools, see what Pro adds on the pricing page.
Common questions
Can AI bulk change WooCommerce prices safely?
Yes. With WP MCP the agent updates each product through update-product, and every write is snapshotted first. Passing one session_id on all the calls groups the batch so you can verify it and undo it in one step.
How do I undo a bulk price change in WooCommerce?
Ask the agent to run rollback-session with the session_id used for the batch, which restores every product to its previous price in reverse order. To undo a single product, use rollback-operation with that product's operation_id from list-operations.
Does changing prices with WP MCP need the Pro plugin?
No. list-products, get-product, update-product, update-variation, list-operations, rollback-operation and rollback-session all ship in the free WP MCP plugin.
How do I change prices on variable products?
Prices on a variable product live on its variations, not the parent. The agent lists them with list-variations and updates each one with update-variation, using the same session_id so the whole batch stays undoable together.
Why does the storefront still show the old price after the update?
A caching plugin is usually holding the old page. Ask the agent to run clear-cache and reload, and confirm the stored value by reading the products back with list-products.
All WP MCP guides, or see every plugin integration. Topic: WooCommerce.