This is a repost. Originally published on the Arvio blog: https://arvio.a.xyz/blog/arvio-first-week. The canonical URL points back there.
The goal of your first week is not to change a lot of products. It's to find out whether you agree with what this thing writes.
It's a calibration exercise: approve a few changes, go look at what landed, build a sense of which edits you wave through and which you send back.
Every step below ends with something you can check. If the check fails, stop and look — don't keep going on the assumption that it probably worked.
Day 1: walk the whole path once, end to end
Do one thing on day one: take a single product all the way from install to a verified change in Shopify Admin. Four stops, each with a way to tell whether you're actually at it.
Install, and confirm the app can see your catalog. Open Arvio and ask it about a product you know, by name. How you know it worked: it comes back with that product's real details. If it can't find a product you're certain exists, the connection isn't doing what you think it is — sort that out before approving anything.
Pick one product and ask for one change. Choose something where you'd recognize a bad answer immediately, and ask for one specific thing — rewrite the description, say. How you know it worked: Arvio comes back with a draft of the new text, not a report telling you the old text is short. A list of problems means you asked for an audit, not an edit.
Read the confirmation card before you press anything. This is the step people skip, and the load-bearing one. The card names the scope of this run. On our own demo store it read:
Only this product will be updated — all others left untouched.
How you know it worked: the scope on the card matches the scope in your head. If you asked for one product and the card describes something wider, reject it — don't shrug and press approve.
On how long this takes: in the run we recorded, Arvio's own progress line read Plan complete 39s before the first card appeared, and 22s on the second round. Those are the app's numbers for one product, on our store, reported on screen — not a benchmark, and not the part of day one that actually costs you anything. The time that matters is yours: reading a card properly is a minute or two of attention, and day one is four cards' worth. Budget an hour and you will finish early.
Approve, then go look in Shopify Admin. The result card confirms what happened:
✓ Description updated
and then it hands you the way out:
This action can be undone. Let me know if you'd like to revert it.
How you know it worked: open that product in Shopify Admin yourself. The description field should hold the new text. If the Admin still shows the old text, the change did not land — no matter what the result card said. The Admin is the record; the card is a claim about the record.
On the one product we measured, "it worked" looked like this in the Admin: the old description was 62 characters, the new one roughly 361 to 364, depending on whether you count the HTML tags. Read that as a single before-and-after we happened to record, not as a length you should expect — one product on one store tells you nothing about the average. The number itself doesn't matter to you. What matters is that you can take that measurement yourself, before and after, without asking us.
That's day one: one product, four checks, none of which required trusting the copy.
Day 2–3: widen to a small batch, and start forming opinions
Days two and three aren't about proving the path works — you did that. They're about what you think of the writing. Widen to a handful of products, not the whole catalog: enough to see several drafts side by side.
Ask for the same kind of change across a few products at once. Holding the operation constant is what makes the differences between drafts visible. How you know it worked: the confirmation card names a wider scope than on day one, and that scope matches the set you asked for. If it names one product while you asked for several, stop — better to find that out from the card than from the Admin.
Approve them one at a time, and reject at least one on purpose. Approval is per change, not per pile — that design is the whole subject of how approval actually works in Arvio. Undo has the same grain: one change, one decision, either before it lands or after. Rejecting is the cheap version and reverting is the late one, and you will practise the second half at the end of the week. Find a draft you genuinely don't like and send it back. How you know it worked: open the rejected product in Shopify Admin. Its old text should still be there while the approved ones show new text. A rejection that wrote anyway is the most important failure to catch, and this is how you catch it.
Write down, in one line each, why you approved and why you rejected. Approved — kept the material and the dimensions; rejected — invented a care instruction we never said. You're building a rubric, and you won't remember these reasons by Friday.
How you know it worked: you can read your own notes back and predict the next verdict before opening the draft. If your reasons come out as "felt fine" and "felt off," you don't have a rubric yet — stay at this size longer.
By the end of day three the useful output isn't the number of products changed. It's the list: a few things you'll always approve, a few you'll always reject.
End of week one: go back and look at what you approved
Go back through everything you approved and ask which ones you'd take back.
Re-read your approvals cold. Open them in Shopify Admin a few days later, without the draft next to them. Reading a change the way a customer lands on it is a different experience from reading it in a queue. How you know it worked: you find at least one you want to change. A perfect week usually means you read it the same way twice.
Revert the ones you want back. Using the undo path once during week one is worth more than reading about it. How you know it worked: open the reverted product in Shopify Admin and confirm the old text is back in the field. Don't take the confirmation message as the answer — go look.
Compare the two ends of the week. Export your products at the start of the week and again at the end, then diff them. How you know it worked: the products that differ are exactly the ones you approved. A product that changed without your approval is a real problem, and you want to find it now rather than in month three across the whole catalog. It's the same self-check we describe in what it actually looks like when Arvio writes the fix, and the only one here that needs nothing from us.
When to slow down
Two signals mean stop widening.
The changes start repeating. If the drafts are variations on a shape you've approved many times over, widening adds volume rather than information. Move to a different kind of change, or stay at this size. How you know you're here: you can predict the draft from the product name before opening it, and you're right most of the time.
You've stopped editing what it writes. If you've approved three in a row without changing a word, there are two explanations — the drafts got good, or you stopped reading — and they feel identical from the inside. A queue you approve without reading is worse than no queue: it produces a record that looks like review.
How you know you're here: pick one of your last three approvals at random and open it in Shopify Admin. If you're reading that text for the first time right now, you were rubber-stamping. Drop back to a smaller batch and start editing drafts again.
There's no penalty for staying small. The nightly pass doesn't expire, and a backlog of unreviewed drafts costs nothing but a longer queue.
When you should uninstall us
The last line of our own App Store description says this:
If your catalog is small and rarely changes, you don't need us.
We mean it, and the first week is when you should decide.
If you run a few dozen products and touch them yourself every month or two, you already know your catalog better than a nightly pass will tell you. You'd spot a thin description on sight, and fixing it takes about as long as reading a confirmation card. Installing us puts a review queue in front of a job that didn't have one.
Two other cases, in the same spirit.
Your edits are mechanical and identical. If what you need is one operation applied uniformly — append a phrase to every title in a collection, shift a set of prices by a fixed amount — you don't need something that drafts each change and stops to ask. A tool built for uniform operations across many rows will do that faster. If you already know what every product needs and it's the same thing, the deciding part is dead weight.
You don't intend to review anything. The stop-and-wait design is the product. If you were hoping to install something, grant it access, and never look at the output, this shape of tool is a tax rather than a help: you'd approve without reading, which gets you unreviewed edits plus a queue. Budget the reading time or pick something else.
If any of those three is you, uninstalling in week one is the correct decision and costs you an evening.
Arvio: AI Store Operator — install it on the Shopify App Store.
FAQ
How many products should I start with?
One, on the first day. Day one proves the path works end to end, and one product proves that as well as fifty do while being much easier to check. Widen once you've seen a change land in Shopify Admin with your own eyes.
What if I approve something and then change my mind?
The result card tells you the change can be undone, and undo is per change rather than per batch — reverting one edit doesn't drag the others back with it. After you revert, open the product in Shopify Admin and confirm the old text is in the field. Treat the Admin as the answer, not the confirmation message.
Do I have to review every change forever?
That's the design, and we'd rather say so than imply it fades once you're comfortable. Experience changes your speed, not whether the step exists. If review is something you want to eliminate rather than get faster at, this isn't the right shape of tool for your store.
What if the drafts are wrong?
Reject them and write down why. A rejected draft costs you the time it took to read — nothing lands in your store. The pattern is what matters: if the same kind of error recurs, that's a fair basis for deciding whether to keep the app, and better learned in week one than in month three.
Can I limit what it touches?
You set the scope each time, and the confirmation card prints it back at you before anything is written. The check is simple: the scope on the card should match the scope in your head. If it doesn't, reject — that mismatch is the card doing its job.
Nothing changed in Shopify Admin after I approved. What now?
Trust the Admin over the card. Reload the product page first, in case you're looking at a stale view. If the old text is genuinely still there, the change did not land — tell us rather than approving more changes on the assumption that the first one worked. Go by what the Admin shows.
Originally published at https://arvio.a.xyz/blog/arvio-first-week. More Shopify bulk-editing writeups are on the Arvio blog.
Top comments (0)