WordPress Store Operations with MCP that keeps catalogue work apart from money.

WooCommerce and FunnelKit: which plugin owns which part of the sale

The two commerce modules are not alternatives. WooCommerce owns the catalogue, the orders, the customers and the money that moves through them. FunnelKit sits in front of that as a sequence of landing, optin, checkout and thank-you pages, and one of its funnels can replace WooCommerce's checkout for the whole shop. An agent working on a store that runs both has to know which plugin answers each question, because they keep separate records.

• Store-wide figures come from WooCommerce orders, through woocommerce-sales-summary, woocommerce-sales-report and woocommerce-product-sales. Funnel figures come from FunnelKit's own conversion log, through funnelkit-funnel-stats. The two can disagree, and neither is an accounting or payout report.
• FunnelKit's free edition records no page views, so it reports optins, orders and revenue per step but never a conversion rate.
• A funnel step page is built in Elementor, Divi, Oxygen, Gutenberg or Bricks. funnelkit-update-step renames, re-slugs, publishes or drafts a step; the page's content is edited with that builder's own abilities.
• Drafting a live step makes visitors skip it. On the store-checkout funnel that changes what every buyer sees, so treat it as a checkout change, not a page edit.

Split store work across three credentials

Keeping catalogue and money apart is easier to do than to remember. A store that uses an agent regularly ends up with three jobs, and each deserves its own access token with its own safety ceiling, so a mistake in one cannot spill into another:

• Catalogue: products, variations, attributes, categories, tags and bulk price or stock updates. It needs no order, customer or gateway ability at all.
• Reporting: the sales summary, sales report and product sales reads, plus FunnelKit stats. With customer and order reads switched off, a token for weekly figures sees totals and never a name or address.
• Order operations: reading orders, adding notes, changing status, refunds and customer accounts. Keep this token closest, give it to the fewest people, and use it with a person watching.

What can be undone in a store, and what cannot

Rollback in WooCommerce follows where data is stored, not what the change meant. A post or an option row can be put back from the change ledger, which covers product edits, attribute terms until they are deleted, and gateway titles and switches. Anything WooCommerce, a gateway or an email has already acted on cannot be put back.

• Most order writes are not reversible from the ledger: creating an order or editing one with woocommerce-update-order is recorded as irreversible. A status change through woocommerce-update-order-status keeps the previous status and rollback-change can set it back, but only the status field: a customer email the change triggered is not recalled. Setting an order to refunded, cancelled or failed is recorded as irreversible, because WooCommerce has already refunded, restocked or released stock and coupon usage for it.
• Refunds are always confirmed and never reversible, and sending the money back through the gateway is a separate opt-in from recording the refund.
• A product that manages its stock keeps no undo for a bulk price or stock update, or for an edit that sets its stock, because restoring it would write back the old stock count and erase every sale since. Change those values back by hand. An edit that leaves stock alone, such as a description or a single price, can still be rolled back without touching the live stock level.
• Global attribute definitions, tax rates and deleted terms or coupons are final. A customer update returns the previous values for you to write back by hand.

Free, Pro and WooCommerce's own abilities

GoBuildWP Free covers the reads a store owner asks for first: the setup check, store settings, products, variations, categories, tags, orders and customers, plus a single-product edit of name, description, prices and stock. Order and customer reads still need a WordPress user with manage_woocommerce, whatever the token allows. Pro adds creating products and variations, attributes, bulk updates, order and refund writes, coupons, reviews, shipping, tax, gateway settings, sales reporting and every FunnelKit ability.

WooCommerce can also expose abilities of its own under a woocommerce/ prefix. They have their own contracts and connection routes, so do not assume GoBuildWP's dry runs, confirmations or change ledger apply to them; inspect their live schema on the version you run. The WooCommerce MCP comparison sets the two side by side, and the WooCommerce MCP guide goes task by task.

Store checks before an agent works on a live shop

Rehearse anything near money on a staging copy with a test gateway first. Then, on the live store:

• Run woocommerce-check-setup and note whether HPOS is the order store, whether Block Checkout is in use and which extensions are present. A subscriptions extension, for example, adds product types the module does not list.
• Put product images in the media library before asking for them, since images are set by attachment id, never by URL.
• On a very large store, expect sales reports to come from WooCommerce Analytics rather than a direct read, and compare one figure with the Analytics screen.
• Open FunnelKit once in wp-admin after activation. Its funnel table is created on that first visit, and the funnel list is empty until then.
• Leave grouped and external products, brands, checkout fields, order bumps and upsell offers to the plugins' own screens; none of them are written here.

Easy Digital Downloads' own abilities, recorded

Easy Digital Downloads 3.7 registers 29 abilities of its own, which any MCP client on the site can reach. From GoBuildWP Free 1.18.0, GoBuildWP's change log knows what each of their writes touches. A download is a WordPress post, so editing one is recorded with a snapshot of the whole post and can be undone from the Changes screen; creating one is recorded with the advice to trash it.

Orders, customers, notes and discounts live in EDD's own tables, and receipts and notes are emailed, so those writes are recorded as irreversible with that reason rather than a generic one. You can see what an agent did to an order; you put it back by hand.