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.

You typed a prompt. You got a stunning image. Cool, right?

Now do it 50 more times. For 200 SKUs. With consistent brand colors. In three ad formats. By Friday.

That's where the party trick falls apart.

Nate B. Jones recently analyzed the massive leak of Claude Code’s source code (Anthropic accidentally published it) and found something that every seller should hear: the actual AI call is only 20% of the system. The other 80%? Plumbing. Session management, error handling, tool coordination. Infrastructure.

Here's why this matters to you.

When we build any AI creative at PPC Ninja, the "generate image" step is ONE step in a pipeline of many.

We’ve made tools for every conceivable step of the way. 80% of the steps are plumbing.

And they're the reason we can easily deliver 100+ RUFUS audits a week instead of weeks or months.

So next time you're tempted to spend an hour perfecting one prompt, ask yourself: do I have a system that could run this 50 times without me?

If not, you don't have an AI advantage. You have a hobby.

Build the pipes!

PPPC Ninja is helping brands future proof their listings for AI. We'll audit your listings for RUFUS readiness, build stunning AI images and videos, and scale your content across Amazon ads, posts, and social media. Learn more about our RUFUS Audit or hit reply to chat with us. https://www.ppcninja.com/rufus-audit.html

One of the best way to invest in plumbing is to build your own tools. If you build once you can use them over and over again. This is the basic principle of automation.

Google AI Studio makes all of this super easy.

Step 1: Describe your app. Type what you want to build in the prompt box. Be as specific as possible. For example: "A tool that takes a product image and lets me choose from 5 AI background styles, then composites them together." or “Create an app where I can upload a script and receive a sequence of generated storyboard images.”

Step 2: Add capabilities with the chips. See those buttons at the bottom (Generate music, Add database and auth, Create & edit images, Add voice conversations)? Those are AI Chips. Click any that apply to your app and they get folded into your prompt automatically. For an image processing tool, you'd tap "Create & edit images."

Step 3: Hit enter (or "I'm feeling lucky" if you want Gemini to surprise you). Gemini generates the full code and shows a live preview on the right side. It defaults to a React frontend.

Step 4: Iterate via chat or annotations. Don't like something? You can either type a follow-up in chat ("make the background selector a grid instead of a dropdown") or use annotation mode to highlight a specific part of the UI and describe what you want changed.

Step 5: Deploy. When it's ready, you can deploy to Google Cloud Run or share with collaborators.

The whole thing is basically vibe coding inside Google's environment. No local setup, no terminal. You describe, it builds, you refine.

One thing to note: this is the same Google AI Studio you already use for image processing (resize, upscale, background removal). The "Build" mode just adds app generation on top of it.

You know what's even better than a great AI workflow? One that runs without you.

The Claude desktop app now supports scheduled tasks. You describe a task once, set a cadence (daily, weekly, hourly, whatever you want), and it runs automatically in its own session with full access to your tools and data.

In Cowork (the desktop UI), click "Scheduled" in the sidebar, write your instructions, pick a frequency, and you're done. No deployment pipeline. No terminal.

If you're a developer using Claude Code (the CLI version), you get the same feature with /schedule and cron expressions for precise timing.

Here's where this ties back to the plumbing thesis.

A scheduled task IS plumbing. It's the part of your workflow that says "run this pipeline every Monday at 9am whether I remember to or not." I use one to collect newsletter topic ideas every week. It searches the web for AI and e-commerce news, curates the top stories, and drops a markdown file into my folder. By the time I sit down to write, the research is already done.

That's one task. Now imagine stacking five of them. Weekly competitor price checks. Daily search term report analysis. Monday morning ad performance summaries. A Friday creative audit.

Each one takes 10 minutes to set up. Then it runs forever (well, as long as your computer is awake and Claude is open).

Example:
"What's new in AI" briefing. You tell Claude "Every Monday at 8am, search for the latest AI tools and news relevant to e-commerce, summarize the top 5 stories, and save a report to my folder." You wake up Monday, coffee in hand, and your research is already sitting there.

The catch: scheduled tasks only run locally. No cloud execution yet. Your machine needs to be on. But for most sellers working from a desk? That's not a dealbreaker.

Pro Tip: Start with one. Pick the task you do every week that's mostly "go gather this information and summarize it." That's your first scheduled pipe.

The tools are there. The automation is there. Most people just don't know where to look.

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