If you sell on Shopify or WooCommerce, the hard part of Provedly is already done for you. Paid orders arrive through signed webhooks and show as verified purchase notifications, with no code in your theme beyond switching on the app embed or installing the plugin. So what does connecting an AI assistant add for a store like yours?
Mostly, it makes the parts you still change by hand quicker: bars, widget status and reporting. This post walks through what changes and what stays exactly as it is.
What stays the same
Your order flow does not change. Shopify orders come in through the Provedly app's webhooks, WooCommerce orders through the signed webhook the WordPress plugin sets up. Both arrive as verified records. None of that involves the API or the MCP server, and nothing you do from a chat window touches it.
Verification does not change either. The Verified mark still comes only from those signed webhooks. An assistant connected to your account can add a record with add_record, for example a sale taken in person, and that record shows with a visible "Imported" label. It cannot turn anything into a verified purchase. For a store that already has verified orders flowing, that is the right arrangement: your real orders carry the mark, and anything else is labelled. Why your assistant cannot verify a purchase has the reasoning.
Billing does not change. Shopify stores are billed through Shopify, and the API and MCP server are available on every plan, including Free.
What gets quicker
Bars for promotions. Store owners change bars more than anything else. Free shipping thresholds, weekend sales, holiday cut-offs, launch countdowns. From an assistant:
Create a countdown bar ending Friday at 5pm with the message "Order by Friday 5pm for delivery before the holidays, {timer} left".
The bar is created paused. Check the wording, then:
Turn it on.
Activation respects your plan's bar limit. For a whole campaign done this way, see running Black Friday from a chat window.
Pausing and resuming widgets. Useful during a theme change or a checkout test:
Pause the widget on the cart page while we test the new checkout.
Resume it.
Plan limits apply to resumes, as they do in your Shopify admin or WordPress dashboard.
Reporting. The question most owners actually want answered:
How many orders did my widgets assist in the last 30 days, and what revenue was attached?
Because your orders arrive through store webhooks, the verified orders in Provedly's stats are your real orders. Proof-assisted orders count buyers who saw a notification before buying, within a 30-day window. Measuring proof-assisted orders explains the method.
Who sets it up
The MCP server works with Claude Code, Cursor and other MCP-compatible tools. These are developer tools, so if you do not use one, the person who builds or maintains your store probably does. Setup is creating a key in Provedly under Settings, then API keys, and adding one server entry in their tool. The Claude Code guide and the Cursor guide each take a few minutes.
If a developer does it for you, decide the access level together. A read-only key lets them, or their assistant, report on results and fetch the install snippet without being able to change anything. A read and write key is for whoever runs your promotions. Choosing an API key covers the trade-off.