Skip to content

Reference

Copilot: Store and membership

Download Markdown

Open Copilot in the site admin and describe the result you want. Use the tables below to check the requests in this area, their approval steps and their available Undo.

Checked against the product’s code on 7 November 2026.

New products start hidden from the shop. A new package is not on sale until you offer it. Publishing, changing an offered product, selling a package and changing an order state have approval boundaries of their own. Adding content to a package or removing it also pauses for approval in chat, because it can change who may read that content.

An order state Undo reverses the supported store record change. It does not return a payment or recall an email. Payment connection secrets must be entered through their trusted settings screens. A connection check reads the stored connection; it does not replace the credentials.

In the tables, Yes under approval means a separate approval is required before applying the request. Available under Undo means the request can be reversed. The specific receipt must offer Undo; it can be limited by the input, later changes or the state that was saved. No means this request provides no automatic Undo. Reading a fact has nothing to undo.

These are plain-language descriptions of requests, not text you must type exactly. Your role, configured connections and site capabilities determine which requests are available. See How copilot requests are governed.

Request Approval Undo
Check the stored payment connection No No
Read the site’s payment connection status No No
Register the address for payment-provider notifications again Yes No
Request Approval Undo
Define a membership level and what members pay Yes Available
List membership levels and the packages they open No No
Update the event list for membership payment notifications Yes No
Request Approval Undo
Cancel a store order Yes Available
Mark a store order complete Yes Available
Refund an eligible Stripe order as an Admin Yes No
Record a refund already made by hand as an Admin Yes Available

| Resend an order email | Yes | No | | Read a store order | No | No | | List store orders | No | No |

| Prepare the matching Orders CSV for your signed in browser | No | No | | Mark a store order paid | Yes | Available | | Mark a store order shipped | Yes | Available | | Add a private note to a store order | No | Available |

Request Approval Undo
Add content to a package Yes Available
Archive a content package Yes Available
Create or rename a content package No Available
Delete an eligible content package Yes Available
Read a content package No No
List content packages No No
Remove content from a package Yes Available
Offer a content package for sale Yes Available
Request Approval Undo
Archive a store product Yes Available
Create a hidden store product No Available
Publish a store product Yes Available
Update a store product Yes Available
List store products by name and state No No
Read a store product by its name or id No No
Request Approval Undo
List coupons by code and state No No
Read a coupon and its uses No No
Create a coupon Yes Available
Change a coupon Yes Available
Pause a coupon Yes Available
Turn a paused coupon back on Yes Available

Coupon changes take effect at checkout without publishing a page. Creation Undo removes only a coupon no order has used. Other Undo requests need the coupon to remain in the state the receipt recorded. Imported coupons can be overwritten by a later import.

Shipping uses the first matching zone. Tax adds every matching rate, including an imported rate for the same place. Imported rules remain read only.

Request Approval Undo
List shipping zones or tax rates No No
Save a native shipping zone or tax rate Yes Available
Remove a native shipping zone or tax rate Yes Available

Setting up the store creates a content type and needs a site Admin. Its Undo needs an Admin too. An Editor’s commerce rights alone do not allow that setup.

Request Approval Undo
Set up the native store pages Yes Available

Return to the copilot request index.

Choose a request that matches your task, then ask the copilot. Review its proposed consequence before approving any change.