SShopSeller
Guide··12 min·Facu

10 More Claude Prompts for Shopify Operators (Beyond the CLI Basics)

Ten proven Claude prompts for real operational tasks in Shopify: Klaviyo flows, product descriptions, schema, legal policies, bulk operations. Copy-paste ready.

#claude-code#shopify#ai#prompts#workflow
TL;DRLo clave en 30 segundos

The first prompts article covered CLI setup and core theme workflows. These 10 are the second layer: what you actually need once the base is running. Configuring Klaviyo from admin, generating brand-consistent product descriptions, implementing schema correctly, running bulk operations via API. All tested in production.

Who this is for

If you haven't read the first one yet, start with the Claude Code + Shopify CLI base guide. It covers setup, session onboarding, and the 7 prompts I use day to day.

What follows is the second layer: specific operational tasks that show up once the base flow is in place. Stack configuration beyond the theme. Working against the Admin API. Generating content with consistent voice.

Each prompt comes with its real use case and bracketed placeholders you replace before pasting.

Prompt 1: Brand-consistent product descriptions

Classic problem when adding products: descriptions drift in tone between what you write, what the team writes, and what you wrote six months ago and never reviewed.

Prompt 1 · Consistent product descriptions

Generates new descriptions matching the tone and structure of existing ones in your store.

I'll share 3 product descriptions already published in my Shopify store. Analyze them to detect:

1. Voice tone (formal, friendly, technical, lifestyle)
2. Structure (how many paragraphs, how many bullets, info order)
3. Typical length (total words)
4. Recurring words or phrases that make up the brand voice

After that, generate new descriptions for [N products I'll share later] maintaining:
- The same detected tone
- The same structure
- Similar length (varying up to 10% above or below)
- Brand words where applicable

Before generating, summarize the 4 things in a short list. I confirm or adjust, then you generate.

Prompt 2: Build Klaviyo welcome flow from scratch

When you start with Klaviyo, the welcome series is the first flow you build. With Claude you can bring decent setup from 6 hours down to 90 minutes.

Prompt 2 · Klaviyo welcome series

Generates full setup with triggers, splits and copy. You build it manually in Klaviyo following the plan.

I need to build the welcome series in Klaviyo for a Shopify store selling [niche/category]. Typical AOV [$X]. People enter through a popup offering [typical discount, e.g. 10%].

GENERATE THE FLOW PLAN:

1. Trigger: what Klaviyo event triggers the flow (signed up to list, etc.)
2. Filters: conditions for entering or not
3. Email sequence (recommend 4-5):
   - For each: timing from trigger, subject, alternative subject for A/B testing, email objective
   - For each: 3-4 key content points (not full copy, just what it has to communicate)
4. Splits or conditional logic: where the flow branches based on behavior (opened, didn't open, bought, etc.)
5. Exit conditions: when the user exits the flow

DO NOT generate full copy yet. Just the plan first. I approve, then we generate copy email by email.

Prompt 3: Popup that doesn't kill UX

Popups capture emails but also wreck conversion if poorly done. The basic rules everyone knows: exit intent, not immediate, mobile-friendly. The problem is implementing them well.

Prompt 3 · Balanced popup

Designs popup considering timing, mobile, accessibility and UX respect. Output: HTML/CSS structure + trigger rules.

I need an email capture popup for my Shopify store. Constraints:

- DOES NOT appear in the first 30 seconds
- DOES NOT appear if the user is already in checkout
- DOES NOT appear on mobile while scrolling (only on exit intent or after 60 seconds)
- Closes with outside click + visible X button + escape key
- Accessible (focus management, aria-labels)
- Persuasive but short copy (max 12 words in headline)

RETURN:

1. Semantic HTML structure with classes for CSS
2. Trigger rules in vanilla JS (no libraries)
3. Copy of headline + subhead + CTA + disclaimer (3 variants for A/B test)
4. Responsive CSS breakpoints

Don't touch the theme yet. First the plan in isolated code so I can review.

Prompt 4: Optimized email subject lines

Subject lines define open rate. Good ones are short, specific, create curiosity without clickbait.

Prompt 4 · Optimized subject lines

Generates 10 A/B-testable variants, avoids common AI patterns (excessive emoji, caps, false urgency).

I need 10 subject line variants for a Klaviyo email in my Shopify store.

EMAIL CONTEXT:
- Goal: [e.g. announce new product / recover abandoned cart / win-back]
- Audience: [e.g. repeat buyers / leads who never purchased]
- Product/offer: [brief description]

RULES FOR THE 10:
- Between 5 and 9 words
- No emojis (0 emojis, none)
- No false urgency ("LAST CHANCE")
- No excessive caps
- Vary between: curiosity, direct benefit, social proof, question, specific data point, personalization

For each one, also give me the preview text (first 50 characters that appear after subject in the inbox).

Mark your top 3 favorites and explain why.

Prompt 5: Correct JSON-LD schema

Structured data is what makes your products show stars in SERPs. Implementing it badly is worse than not implementing it.

Prompt 5 · JSON-LD structured data

Audits and generates correct JSON-LD for Product, Organization and FAQPage following current Google guidelines.

I'll share the product page file from my Shopify theme. I need to:

1. AUDIT the current JSON-LD (Product schema):
   - Is it present?
   - Does it have all fields required by Google? (name, image, description, brand, sku, offers)
   - Does it have recommended fields that improve rich snippets? (aggregateRating, review, gtin)
   - Any field poorly formatted (price without currency, dates wrong, etc.)?

2. GENERATE the CORRECT JSON-LD using Liquid variables (no hardcoded values):
   - Pulling data from {{ product }} instead of literal strings
   - Handling edge cases (product without image, no reviews, no variants)
   - Including BreadcrumbList if the page has breadcrumbs

3. SUGGEST whether the page should also have:
   - FAQPage schema (if there are visible FAQs on PDP)
   - VideoObject (if there's product video)

Don't modify the theme yet. First the report + proposed code. I approve, then you apply.

Terms, privacy, returns, shipping policy. Required pages that get filled with generic boilerplate. Without customization for your operation, they don't protect much.

Prompt 6 · Ecommerce legal policies

Generates policies specific to your operation, not generic boilerplate. For real legal validation consult a lawyer, this is starting point.

I need to generate legal policies for my Shopify store in [country, e.g. UK]. Operation:

- Products: [type, e.g. accessories, electronics, clothing]
- Markets: [countries you sell to]
- Payment methods: [card, PayPal, COD if applies]
- Shipping policy: [typical times, costs, restrictions]
- Returns policy: [how many days, conditions, who pays return shipping]
- Personal data you collect: [email, address, phone]
- Cookies and tracking: [Google Analytics, Meta Pixel, others]

GENERATE 4 PAGES:

1. General terms and conditions
2. Privacy policy (GDPR-compliant if you sell in EU)
3. Returns and refunds policy
4. Shipping policy

RULES:
- Clear language, not pretentious legalese
- Specific to my operation, not generic copy
- Include all mandatory clauses for the country
- Mark with [VALIDATE WITH LAWYER] points needing specialized legal review

NOTE: output is starting point. For final validation consult lawyer specialized in ecommerce in your jurisdiction.

Prompt 7: Detect duplicate content between products

When you have many similar products, descriptions tend to look alike. Google penalizes that with thin content / duplicate content. Detecting it manually is impossible past 50 products.

Prompt 7 · Detect duplicate content

Similarity analysis between product descriptions. Output: pairs with high similarity + suggestions to differentiate.

I'll share a CSV exported from Shopify with all products in my store. Columns: handle, title, body_html, type, vendor, tags.

ANALYZE:

1. Detect product pairs with descriptions more than 60% similar (measure lexical similarity, not just keywords)
2. For each pair, show:
   - The two handles
   - Similarity percentage
   - Specific segments that repeat verbatim

3. Detect products with very generic title (unique words less than 3, e.g. "Pack 5 units")

4. Detect products without description or with less than 50 words (thin content)

RETURN A REPORT:
- Top 10 most similar pairs (fix priority)
- Top 10 most generic titles
- Top 10 with least content

Don't suggest yet how to differentiate them. First the diagnosis. Then we decide what to do.

Prompt 8: Bulk operations via Admin API

When you need to update 200 products (raise price 10%, change a tag, modify a metafield), doing it manually from admin wastes a day. Admin API + Claude brings it down to 30 minutes.

Prompt 8 · Bulk operations Admin API

Safe script with dry-run first, then real execution. Output: code + rollback plan if something goes wrong.

I need to do a bulk operation in my Shopify store via Admin API. Task:

[Describe exactly what change, e.g.:
"Raise price by 10% on all products with tag 'winter-2026'.
Keep decimal without rounding. Apply also to variants."]

GENERATE THE SCRIPT IN NODE.JS:

1. FIRST a dry-run that lists which products would be affected and what change would be made, WITHOUT executing anything
2. API rate limit handling (Shopify has 2 calls/second in REST, 1000 cost points in GraphQL)
3. Retry logic if a call fails
4. Log to file of each change for later audit
5. Rollback plan: how to undo if I detect something went wrong later

MANDATORY CONFIRMATION between dry-run and real execution (no autorun, wait for my OK).

Also show me what environment variables I need (.env with SHOPIFY_ADMIN_TOKEN, SHOP_DOMAIN).

Prompt 9: Custom Shopify Flow trigger

Shopify Flow automates internal tasks but native triggers sometimes don't cover your case. Building one custom with webhook + simple function solves it.

Prompt 9 · Custom Shopify Flow trigger

Designs webhook + handler for automations native Flow doesn't cover.

I need an automation in my Shopify store that native Flow doesn't cover. Case:

[Case description, e.g.:
"When a customer makes 3 orders in less than 60 days AND total AOV exceeds $200, add the tag 'vip-emerging' to the customer. If tag already exists, don't duplicate."]

DESIGN THE SOLUTION:

1. Shopify webhook to use (orders/create probably)
2. Endpoint where to receive the webhook (recommend: Vercel function, Cloudflare Worker, AWS Lambda)
3. Handler logic: how to query customer history, how to apply the condition, how to avoid duplicates
4. Error handling (what happens if Shopify retries, what happens if handler fails)
5. Testing plan: how to test without affecting real data

GENERATE THE handler function code in Node.js using Shopify Admin API. Use GraphQL to minimize calls. Include comments explaining each part.

Prompt 10: Audit meta tags and Open Graph

Basic technical SEO: every page has correct title, description and OG tags. Auditing manually page by page is tedious.

Prompt 10 · Meta + OG audit

Complete metadata analysis by page type: home, collection, product, blog. Output: issues + proposed fix.

Audit meta tags and Open Graph of my Shopify theme for each page type:

1. Home (templates/index.liquid)
2. Collection (templates/collection.liquid)
3. Product (templates/product.liquid)
4. Blog index (templates/blog.liquid)
5. Article (templates/article.liquid)

FOR EACH TYPE, REVIEW:

- title tag: does it use a template with Liquid variables? does it include main keyword? length between 50-60 chars?
- meta description: present? uses variables? length 150-160 chars? includes CTA?
- og:title, og:description, og:image, og:url: complete?
- og:image: correct dimensions (1200x630)? uses product image on PDP?
- twitter:card: summary_large_image configured?
- canonical: present? points to correct URL without parameters?
- hreflang: if multi-language, correctly implemented?

RETURN A REPORT with:
- What's correct
- What's missing or wrong
- For what's missing: exact code to add to the theme, using Liquid variables where appropriate

Don't modify anything yet. First the report. I approve, then you apply.

How to combine these prompts with the previous ones

The 7 prompts from the previous article covered direct theme work. These 10 are the layer above: stack configuration, content, data, automations.

Recommended workflow: one session per domain. Don't mix "theme audit" with "configure Klaviyo flows" in the same Claude Code session. Each needs its own context. The onboarding prompt is still the start of every new session.

Verdict

💡What matters

The real value of Claude for Shopify operators isn't in one magical prompt. It's in having a library of prompts covering tasks you do over and over.

If you save these ten + the seven from the previous article in a reference file, six months from now you have a personal operations manual worth more than most paid "AI for ecommerce" courses.

Then you write your own for cases specific to your stack. That's the real asset.

Frequently asked questions

Which of the 10 should you try first?

Prompt 1 (product descriptions). It saves the most time in the first month, especially if you're adding many new products. If you configure it well, you end up generating consistent descriptions in 3-5 minutes each.

Do these prompts also work with ChatGPT?

Yes, mostly. The concepts are the same. The difference: Claude Code runs inside your project and can edit files directly. ChatGPT gives you the code and you paste it manually. For prompts 5, 8 and 9 (which generate code that touches theme files or API), Claude Code saves several steps.

How do I manage API keys that appear in some prompts?

Always in environment variables (.env, not committed to git), never hardcoded in code. For Shopify Admin API you need to create a custom app from admin → Settings → Apps → Develop apps → Create app, and give it only minimum necessary scopes (specific read/write, not full admin).

Is Claude Pro worth paying just for this?

If you use 3-5 of these prompts once a week, the Pro plan ($20/month) pays for itself in the first month. The right question isn't "is Claude Pro worth it" but "does the time I invest in this justify the savings vs doing it manually?". For operators with 10+ weekly hours in technical operational tasks, the ROI is direct.


Newsletter

Recibe los cambios de TikTok Shop antes que los demás.

Cambios de política, comisiones, fees y herramientas que valen la pena. Cada viernes. Sin spam.