You approve or reject a change Mark proposes by reading the preview in your thread and replying yes or no. A yes means the preview matches what you want, and Mark applies the change after your yes. A no means nothing changes. After a yes, you check the result on your storefront.
Most store owners already know they should look before a price, collection, or discount changes. The harder part is knowing what to look for and what to type back. For the reasoning behind a human yes, see Should an AI Change Shopify Prices Without Approval?.
How do you approve or reject a change Mark proposes?
You approve or reject a change Mark proposes by replying in the same thread where the preview arrived. Read what will change and what it affects. Reply yes if it is right, no if it is not, or send a correction to get a new preview. Mark applies the change after your yes, and then you check the storefront.
The whole loop fits in one conversation:
- Text Mark the change in plain language, such as "Preview 15% off the Summer collection through Sunday" or "Show me the hoodie at $58."
- Wait for the preview in the thread. Mark routes merchandising work to Annie, who drafts the proposal.
- Read the preview. Check the products or collection named, the old and new values, and the scope.
- For a bulk change, check the exact number of affected items.
- Reply yes, no, or a correction.
- If you said yes, Mark applies the change.
- Check the storefront once it is applied.
You do not need to open admin to read the preview or to make the change. Admin stays the system of record, so you can always see the result there. What Can I Text Mark? lists the kinds of changes you can ask about: prices, products, collections, discounts, and bulk updates.
What should a proposed change show before you say yes?
A proposed change should show exactly what will be updated: which products, variants, or collection, the current value, the new value, and how far the change reaches. A bulk proposal should state the exact number of affected items. Discount proposals should include dates. If any of that is missing, ask before you answer.
Use this checklist on every preview:
- Named items. The product, variant, collection, or discount is named, not described loosely.
- Before and after. You can see the current value and the proposed value.
- Scope. You know whether the change covers one product, a collection, every variant, or a market.
- Count. For bulk work, the exact number of affected items is stated. What Can I Text Mark? notes that bulk changes require you to confirm that count.
- Dates. A discount or sale shows when it starts and ends.
- Side effects. A sale price may also change the compare-at price, which is what shows the crossed-out price.
Shopify Help on sale pricing explains that the compare-at price is what displays a product as on sale. If a preview changes price but says nothing about compare-at, ask. A preview that says "update the summer items" without names or a count is not specific enough to approve. Ask Mark to list them.
How do you approve a change Mark proposes?
You approve a change Mark proposes by replying yes in the thread, ideally restating the scope, such as "Yes, 42 products, 15% off through Sunday." Mark applies the change after your yes, so the yes is what makes it happen. Read the preview closely before you send it, then check the storefront once it is applied.
A clear yes is short and specific:
- "Yes, the blue hoodie to $58, all sizes."
- "Yes, 42 products in Summer, 15% off, ends Sunday night."
- "Approved. Update the classic tee description with the new fabric line."
Restating the scope is a habit, not a formality. If your restated number does not match the preview, you catch the mismatch before anything changes.
What happens after your yes:
- Mark applies the change you approved. You do not open admin to make it.
- Keep the preview open so you can compare what you approved with what the storefront shows.
- If you later want to adjust something by hand, admin works as it always has. Many prices at once go through the bulk editor, and Shopify Help on collections covers manual and automated types.
For a large change, export a product CSV before you say yes so you have a record of the old values. Shopify's CSV guide covers the export.
How do you reject a change Mark proposes?
You reject a change Mark proposes by replying no in the thread. Nothing in your store changes because of a proposal you turned down. You can drop the idea entirely or send a correction, such as a different percentage or a narrower set of products, and Mark comes back with a new preview to read.
A no can be final or it can steer the next draft:
- "No, leave prices as they are."
- "No. Only the blue hoodie, not every color."
- "Not 20%. Make it 10% and show me again."
- "No. Leave out anything already on sale."
Treat a correction as a brand new preview. Read it from the top with the same checklist, because a narrower scope can change the count, the dates, or which variants are included. Do not approve a preview that is half right and plan to fix the rest in admin. Ask for the version you actually want and approve that one. Mark applies the change after your yes.
Saying no is also the right answer when you are unsure. If you cannot tell what a proposal affects, reply with a question instead of a yes: "Which products are in that 42?" Mark can list them. A proposal sitting unanswered does not change your store, and you are never required to approve. You can decline, revise, or simply leave the store as it is.
What should you check after Mark applies an approved change?
After Mark applies an approved change, open the storefront and check a few affected products. Confirm the price, the compare-at price, and every variant. For a discount, confirm its status and dates on the discount's page. For a description change, confirm the new copy shows on the product page. If anything does not match, tell Mark or fix it in admin.
A two minute check after each change:
- Open two or three affected products on the live storefront, not only in admin.
- Check each variant, since a price change on one size can miss another.
- Check the sale display. If a crossed-out price should appear, the compare-at price must be higher than the price.
- For a discount, open it in Discounts and confirm it is active for the right dates.
- For a description change, open the product page on the storefront and read the new copy.
If something is wrong, you can reverse it in admin. Shopify Help on managing discounts explains that you can edit, deactivate, or delete a discount, and that a customer who applies a deactivated code gets an error. For prices, use the CSV you exported before the change as your record of the old values. You can also text Mark what you see and ask for a preview of the fix. Mark applies the fix after your yes, the same way.
What does approving a proposal not do?
Approving a proposal applies the change in the preview and nothing else. It does not message your customers, and it does not touch your ads. Mark applies the change after your yes. Shoperator does not send shopper email or SMS, and it does not pause, launch, or edit Meta or Google ads.
Clear boundaries:
- Not a blank check. Mark applies the change you approved and nothing outside that preview.
- Not SMS marketing. The thread is how you talk to the operating team, not to shoppers. See SMS Marketing vs SMS Store Operations.
- Not an ads change. If an ad quotes the old price, update it in your ad tools yourself.
- Not Shopify Sidekick. Sidekick is Shopify's admin assistant. Texting Mark is an operator thread. See Shopify Sidekick vs AI Store Operator.
- Not the same as a creative request. Image generation, including Magic SMS, uses credits. How Do Credits Work? explains what each run costs.
- Not a replacement for Shopify admin. Admin stays the system of record.
For the bigger picture, see What Is an AI Shopify Store Operator? and How to Run a Shopify Store by Text. Shoperator is the example here because the preview and the yes or no live in one text thread.
FAQ
How do you approve or reject a change Mark proposes?
You approve or reject a change Mark proposes by replying in the same thread where the preview arrived. Read what will change and what it affects. Reply yes if it is right, no if it is not, or send a correction to get a new preview. Mark applies the change after your yes, and then you check the storefront.
What should a proposed change show before you say yes?
A proposed change should show exactly what will be updated: which products, variants, or collection, the current value, the new value, and how far the change reaches. A bulk proposal should state the exact number of affected items. Discount proposals should include dates. If any of that is missing, ask before you answer.
How do you approve a change Mark proposes?
You approve a change Mark proposes by replying yes in the thread, ideally restating the scope, such as "Yes, 42 products, 15% off through Sunday." Mark applies the change after your yes, so the yes is what makes it happen. Read the preview closely before you send it, then check the storefront once it is applied.
How do you reject a change Mark proposes?
You reject a change Mark proposes by replying no in the thread. Nothing in your store changes because of a proposal you turned down. You can drop the idea entirely or send a correction, such as a different percentage or a narrower set of products, and Mark comes back with a new preview to read.
What should you check after Mark applies an approved change?
After Mark applies an approved change, open the storefront and check a few affected products. Confirm the price, the compare-at price, and every variant. For a discount, confirm its status and dates on the discount's page. For a description change, confirm the new copy shows on the product page. If anything does not match, tell Mark or fix it in admin.
What does approving a proposal not do?
Approving a proposal applies the change in the preview and nothing else. It does not message your customers, and it does not touch your ads. Mark applies the change after your yes. Shoperator does not send shopper email or SMS, and it does not pause, launch, or edit Meta or Google ads.