If you’re new, welcome! If you’re a regular, thanks for being here as we navigate this AI shift in eCommerce. I share what I’m testing and what’s actually moving the needle. Where’s the vault you ask? Every previous edition is saved here.
In this edition (shortcuts):
Claude Works Nights. You Take the Weekend.💥
Stop Paying Opus Prices for Haiku Work 🤓 🤓
Midjourney V8.1 vs Nano Banana 2 🎬
News Worth Reading
Claude Works Nights. You Take the Weekend.
Who here feels like the work never actually stops?
Well, lucky you, because today I am going to show you how to hand off the parts that repeat. To something that keeps working long after you have closed the laptop.
Here is the thing most sellers do not realize. You can hand Claude a task, walk away, go live your life, and come back to a finished summary sitting in your inbox. No terminal left running. No machine humming in the corner. No babysitting.

This is called a Routine. And once you set one up, it changes how you think about repetitive work.
First, What Is a Routine?
A Routine is a Claude Code task you set up once and then let run on its own on a pre-determined frequency. You give it a prompt, point it at the data it needs, and pick a schedule. After that, it runs without you.

The magic word here is Remote. Routines run on Anthropic's own infrastructure, not on your computer. That means your laptop can be closed, asleep, or in your bag at the airport. The task still runs.
Compare that to the old way. Before, if you wanted Claude to do something on a schedule, your machine had to be on and a session had to be open. Forget to leave it running? Nothing happens.
Routines remove that fragility entirely.

The Three Ways to Schedule (And When to Use Each)
Here is where most people get confused, so let me lay it out clean. There are three ways to put Claude on a schedule, and they are not the same.
Cloud Routine | Desktop Task | /loop | |
|---|---|---|---|
Runs on | Anthropic cloud | Your machine | Your machine |
Laptop can be off? | Yes | No | No |
Open session needed? | No | No | Yes |
Sees your local files? | No (fresh copy) | Yes | Yes |
Shortest interval | 1 hour | 1 minute | 1 minute |
Best for | Set and forget | Local file work | Quick polling |
Read that table twice. It is the whole framework.
🔶 Cloud Routine: use this for anything that should run reliably whether or not you are around. Weekly summaries, nightly checks, scheduled reports. This is the one that works while you sleep.
🔶 Desktop Task: use this when the job needs your actual files on your actual machine. It runs locally, so the computer has to be on.
🔶 /loop: use this for quick checks during a session you are already sitting in. It needs the window open, so it is not a leave-it-overnight tool.
[Heads up: Cloud caps out at one run per hour no matter what, but Desktop only defaults to hourly. Ask Claude in plain English and a Desktop task will go down to one minute.]
For the "walk into Monday with it done" use case, you want a Cloud Routine. Every time.
How I Set One Up
I wanted a simple thing. Every Sunday at 7am, pull my key numbers from BigQuery, write a tight summary, and email it to me before I am even awake.
Here is the experience, start to finish.
I went into Claude Code on the web and opened the Routines area. Creating one is a simple form: the prompt to run, what data it should reach, and the cadence. I picked weekly, Sunday morning. I described the summary I wanted in plain English, the same way I would ask a teammate.

Then I closed my laptop and forgot about it.
Sunday morning, the email was there. Clean summary, the numbers I asked for, ready before coffee.
That is the part that still feels a little magic. I did nothing. The work just showed up.
Pro Tip: describe the output format in your prompt as specifically as you can. "Three bullets, top metric first, flag anything that moved more than 10 percent." The more precise the brief, the better the Sunday email reads.
The Guardrails You Should Know
I would be doing you a disservice if I only showed you the shiny part. So here are the honest limits.
🔶 There is a daily cap. Pro plans get 5 routine runs a day, Max gets 15, Team and Enterprise get 25. Plenty for most sellers, but worth knowing before you schedule ten of them.
🔶 The shortest cloud interval is one hour. Routines are built for "every night" and "every Monday," not "every five minutes." For fast polling, that is what /loop is for.
🔶 Cloud Routines run in the cloud, not on your machine. A Routine cannot reach files sitting on your local desktop. It gets what it needs through connectors (Slack, Google Drive, and the like) and whatever sources you point it at when you set it up.
🔶 They run on their own. No approval prompts mid-task. So write the prompt carefully and start with low-stakes, read-only jobs (summaries, reports) before you let one take any real action.
None of these are dealbreakers. They are just the shape of the tool. Match the job to the tool and you are fine.
Why This Matters for Sellers
Step back and look at what just happened. A task that used to need your attention, your open laptop, and your memory to kick it off now runs itself on a schedule you set once.
That is the difference between doing the work and designing the work.
The seller who sets up three Cloud Routines (a Monday summary, a midweek check, a Friday wrap) has effectively hired a junior analyst who never sleeps and never forgets. The seller who does not is still opening spreadsheets by hand.
This is the quiet advantage I keep coming back to. The tools are here. The access is here. Most people just have not set them up yet.
Your laptop deserves a weekend. So do you.
Know anyone who needs an AI-first agency to build cool, creative videos for E-commerce? Forward them this newsletter and let them connect with us at [email protected].
NERD BYTES (FOR NERDS)
Stop Paying Opus Prices for Haiku Work 🤓
Quick question. Which Claude model are you using right now?
If your answer is "the one it picked for me" or "the same one I started with months ago," this one is for you.
Here is what most people miss. There are three Claude models on the menu, and they cost wildly different amounts. Using the most expensive one for simple work is like taking a sports car to pick up groceries. It works. You just overpaid.
Here are the current API prices, per million tokens:
🔶 Haiku 4.5: $1 in, $5 out. The cheapest. Fast and great for bulk, repetitive jobs.
🔶 Sonnet 4.6: $3 in, $15 out. The middle. The workhorse for most real tasks.
🔶 Opus 4.8: $5 in, $25 out. The most powerful. Save it for the hard stuff.
Look at that spread. Opus output costs five times what Haiku does. If you are running 500 product description rewrites a week on Opus, you are lighting money on fire for work Haiku handles fine.
So here is the simple rule of thumb:
🔶 Simple, high-volume, repetitive work: ... Reach for Haiku.
🔶 Everyday real work: ... Reach for Sonnet. It is the workhorse for the bulk of what you do. Rumor has it that Sonnet 5 is on its way (gaining some of Fable’s capabilities without triggering the powers above)
🔶 The genuinely hard stuff: ... That is where Opus 4.8 earns its keep. It scored 84 percent on a leading browser-agent benchmark, the best of any model tested.
One more lever. If you run big batches that are not time sensitive, the Batch API takes 50 percent off both numbers. Half price for work you do not need back this second.
The caveat: do not cheap out on the tasks that matter. A bad competitor analysis costs you more than the Opus tokens would have. Match the model to the job, do not just minimize the bill.
That is the whole trick. The model picker is the cheapest optimization most sellers never touch.
COOL TOOLS
Midjourney V8.1 vs Nano Banana 2 🎬
If you make product images with AI, two tools keep coming up. And people keep asking me which one to use.
The honest answer is: it depends what you are making. So let me put them side by side.
Midjourney V8.1 dropped April 30. It is fast now, around 4 to 5 times faster than the older version, with HD 2K output and a new "Raw mode" built for realistic lighting and product visualization. It also finally lives on the web. Discord is now optional.
Nano Banana 2 is the Google model most of us already use for listing photos. Cheap, quick, and accurate where it counts.
The Scoreboard
Midjourney V8.1 | Nano Banana 2 | |
|---|---|---|
Speed | 4 to 5x faster than V7 | ~10 to 15 seconds |
Cost | From $10/month (GPU hours) | ~$0.03 per image |
Resolution | HD 2K | Production ready |
Text on packaging | Often gibberish | Better, readable |
Best at | Mood, lighting, concept | Accurate product shots |
Web access | Yes (Discord optional) | Yes |
Where Midjourney Wins
🔶 Atmosphere and mood. Cinematic lighting, editorial styling, scenes that feel like a magazine shoot.
🔶 Concept and ideation. Raw mode gives you direct control to explore looks before you commit.
🔶 Lifestyle backdrops. Beautiful environments to drop a product into.
Where It Falls Short
🔶 Text and logos. Packaging copy comes out as gibberish. Reflections sometimes defy physics.
🔶 Branding accuracy. Not reliable enough for the actual main image on a listing. 🔶 Consistency. Holding the same product look across many images is still hard.
So Who Is This For?
Here is my take. These are not really competitors. They are teammates.
Use Midjourney V8.1 for the dreaming: mood boards, lifestyle concepts, creative direction, the hero-shot vibe you are chasing. Then use Nano Banana 2 for the doing: the accurate, on-brand product images that actually go on your listing where the text has to be correct and the details have to be real.
Midjourney shows you the destination. Nano Banana gets the product there accurately. Reach for the right one and you stop fighting either of them.
NEWS WORTH FOLLOWING
🔶 Amazon's Ads AI image generator adds aspect ratio control. More flexibility for sellers generating creative directly inside the Ads console.

🔶 Amazon now shows AI-generated product images inside mobile search. As of June 3, US mobile shoppers see AI-rendered "inspiration" thumbnails sitting right next to real listings. Time to audit your main images at thumbnail size and finish your structured attributes.
🔶 Google retired Gemini CLI on June 18. If you had any script calling the gemini command, it broke with no grace period. The replacement is Antigravity CLI.
🔶 Antigravity 2.0 brings agent teams and a Planning mode. Google's new agent-first platform pairs a 1M context window with squads of subagents working in parallel.
We hope you liked this edition of the AI for E-Commerce Newsletter! Hit reply and let us know what you think! Thank you for being a subscriber! Know anyone who might be interested to receive this newsletter? Share it with them and they will thank you for it! 😃 Ritu

