When you tell Shoperator no, nothing in your store changes. For important supported store changes, Mark, the coordinator you text on Shoperator, shows you what would change and waits for your approval. A no drops the proposal. To reverse a change you already approved, set the old values back through a new supported change or in Shopify admin.
For how to read a preview and reply, see How to Approve or Reject a Change Mark Proposes.
What happens when you tell Shoperator no?
When you tell Shoperator no, the proposed change is not applied. For important supported store changes, Mark shows what would change and asks for your approval before applying it. Without your yes, the preview is just a message in your thread. Your prices, product details, collections, and discounts stay as they were.
For an important supported change, the order of events is the reason a no is safe:
- You text Mark a request, such as "Raise the hoodie to $58."
- Mark replies with a preview showing what would be updated.
- You reply yes or no.
- Only after a yes does Mark apply the change.
What Can I Text Mark? puts it plainly: Mark confirms before making any changes, showing exactly what will be updated. Bulk changes also require you to confirm the exact number of affected items. A no stops the flow at step 3, before anything is written to your store.
What stays the same after you say no?
After you say no, every field named in the preview stays the same: the current price, the compare-at price, product titles and descriptions, product status, collection membership, and discount settings. Anything outside the named scope is not part of the proposal. A denied store proposal does not send shopper email or SMS or change Meta or Google ads.
A quick way to picture it is to split the preview into what it would have changed and what it never touches:
- Would have changed, now unchanged: the specific products, variants, collection, or discount named in the preview.
- Outside the proposal: any order, customer, theme, ad account, or other record that is not explicitly named in the preview.
You do not need to check admin after a no to confirm nothing moved, but you can. Admin stays the system of record. If you want peace of mind on a large proposal, open one or two of the named products and confirm they still show the old price.
A no is also not a penalty or a dead end. You can ask the same question again later, ask for a different version, or never bring it up again.
How do you say no to Mark?
You say no to Mark by replying in the same thread where the preview arrived. A plain "No" works. You can add a reason or a correction, such as "No, only the blue hoodie" or "Not 20%, make it 10%." A correction gets you a new preview to read. A bare no simply leaves the store as it is.
Short replies that work:
- "No, leave prices as they are."
- "No. Skip anything already on sale."
- "Not this week. Drop it."
- "No. Show me just the five best sellers instead."
If you are unsure what a preview affects, a question is better than a yes. "Which products are in that 42?" gets you a list. A proposal you have not answered does not change your store, so you can take the time you need.
Treat any corrected preview as new. Read it from the top, because a narrower scope can change the item count, the dates, or which variants are included. Approve only the version you actually want.
Can you change your mind after you say yes?
You can change your mind after a yes, but the timing matters. Mark applies the change after your yes, so once it is applied, the store reflects it. Changing your mind then means setting the old values back, either by asking Mark for a new change or by editing in Shopify admin. Read the preview closely before replying yes.
Think of it as two separate changes, not one change and a rewind:
- The change you approved, which Mark applied.
- A new change that returns the affected items to their old values.
Plan as if there is no one tap undo. That is why the old values matter. Before you approve anything large, keep the preview in your thread, since it shows the current value next to the proposed one. For bulk work, export a product CSV first. Shopify's CSV guide covers how to export products, which gives you a dated record of every price and field before the change.
If you catch a mistake right after replying yes, say so in the thread right away so Mark knows what you meant, then follow the steps in the next section.
How do you undo a change Mark applied?
There is no universal one-tap undo. For a supported reversible field, set the old value back: text Mark a new request such as "Put the hoodie back to $52," read the new preview, and reply yes. Or reverse it yourself in Shopify admin. Use the old values from the preview or from a CSV you exported first.
Ways to reverse common changes in Shopify admin:
- Price on one product: open the product, set the price and compare-at price back to the old values, and save.
- Prices on many products: use the bulk editor to edit the price and compare-at price columns in one view.
- A sale that should not be running: Shopify Help on sale pricing explains that the compare-at price is what shows a product as on sale. Clear it or restore it.
- A discount: open it under Discounts and deactivate it, or change its end date. Shopify Help on discounts covers editing and deactivating.
- A collection: add or remove products from the collection page. Shopify Help on collections covers manual and automated types.
- A product description: paste the previous copy back in, which is easier if you kept the old text.
Asking Mark is often faster for a supported change like a price, a description, or deactivating a discount code, and it keeps the same preview and yes loop. Admin is the direct route when you want to fix it with your own hands right now.
How do you avoid needing an undo?
You avoid needing an undo by approving only previews that are complete: named items, before and after values, the scope, an exact count for bulk work, and dates for anything time bound. Restate the scope in your yes, test big changes on one product first, and keep a record of old values before any bulk update.
Habits that cut down on reversals:
- Restate the scope in your yes: "Yes, 42 products, 15% off, ends Sunday." If your number does not match the preview, you catch it before anything changes.
- Start small: ask for one product first, check it on the storefront, then approve the rest.
- Ask for dates: a discount with an end date stops on schedule. A compare-at price sale stays until someone changes it back.
- Keep old values: export a CSV before a bulk change and keep the preview in your thread.
- Check after a yes: open two or three affected products on the live storefront, not only in admin.
None of this slows the store down much. It turns a reversal from a hunt into a two minute fix, because you already know what the old values were.
FAQ
What happens when you tell Shoperator no?
When you tell Shoperator no, the proposed change is not applied. For important supported store changes, Mark shows what would change and asks for your approval before applying it. Without your yes, the preview is just a message in your thread. Your prices, product details, collections, and discounts stay as they were.
What stays the same after you say no?
After you say no, every field named in the preview stays the same: the current price, the compare-at price, product titles and descriptions, product status, collection membership, and discount settings. Anything outside the named scope is not part of the proposal. A denied store proposal does not send shopper email or SMS or change Meta or Google ads.
How do you say no to Mark?
You say no to Mark by replying in the same thread where the preview arrived. A plain "No" works. You can add a reason or a correction, such as "No, only the blue hoodie" or "Not 20%, make it 10%." A correction gets you a new preview to read. A bare no simply leaves the store as it is.
Can you change your mind after you say yes?
You can change your mind after a yes, but the timing matters. Mark applies the change after your yes, so once it is applied, the store reflects it. Changing your mind then means setting the old values back, either by asking Mark for a new change or by editing in Shopify admin. Read the preview closely before replying yes.
How do you undo a change Mark applied?
There is no universal one-tap undo. For a supported reversible field, set the old value back: text Mark a new request such as "Put the hoodie back to $52," read the new preview, and reply yes. Or reverse it yourself in Shopify admin. Use the old values from the preview or from a CSV you exported first.
How do you avoid needing an undo?
You avoid needing an undo by approving only previews that are complete: named items, before and after values, the scope, an exact count for bulk work, and dates for anything time bound. Restate the scope in your yes, test big changes on one product first, and keep a record of old values before any bulk update.