Prompt Library

ChatGPT prompts for Shopify welcome, cart and winback emails

30 copy-paste prompts

Copy-ready prompts for welcome, abandoned cart, post-purchase and winback. Distinct from the Shopify hub. Never invent a discount, a result or a product you do not sell.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Drafted with AI assistance (how we make prompts)

Welcome Series

5 prompts

First welcome from brand voice

1/30

✨ What it does

Drafts a first welcome with a short subject, preview text, 90 to 130 word body and a CTA you already chose. A catalog with no product stays tagged; no discount or founder story is invented.

Write the first welcome email from voice samples I paste and facts I sell. Voice samples: [VOICE SAMPLES]. What they signed up for: [SIGNUP SOURCE]. What we actually sell: [CATALOG NOTES]. Output: subject of 8 words or fewer, preview text of 12 words or fewer, body of 90 to 130 words, one CTA labelled from [CTA I WILL USE]. If the catalog notes name no product, write [VERIFY] on the body and do not pick a hero item. Do not invent a discount. Do not invent a founder story. A welcome that promises 10 percent off I did not approve is a lie in the inbox.

💡

Pro tip: Paste two emails you already sent that sound like you, not a competitor's newsletter.

Second welcome, how to use the thing

2/30

✨ What it does

Writes welcome email 2 as numbered first steps from facts you supplied, ending on a support channel you staff. Missing steps stay tagged; no feature or result is invented.

Write welcome email 2 as a how-to for a product they already have or just joined the list for. Product facts: [PRODUCT FACTS]. Steps a new owner takes: [FIRST STEPS]. Support channel we actually staff: [SUPPORT CHANNEL]. Output 110 to 160 words with numbered steps from [FIRST STEPS] only, then the support channel. If first steps are missing, write [VERIFY] and ask me for the unboxing or login step before drafting. Do not invent a feature. Do not invent a result such as 'hair grew in a week'. A how-to that adds a button we do not have will bounce to support.

💡

Pro tip: Walk through the product once while you paste the steps, including the awkward latch.

Third welcome, people and places we have

3/30

✨ What it does

Writes welcome email 3 toward community or store places you already run, using a URL you provided. Empty community facts stay tagged as one real question; no member count is invented.

Write welcome email 3 pointing at people or places we already run. Community or store facts: [COMMUNITY FACTS]. Places they can go: [PLACES]. Output 80 to 120 words, one link slot labelled with a URL I provided in [URL I MAY USE] or the word none. If community facts are empty, write [VERIFY] and turn the email into a single question we actually want answered from [QUESTION WE WANT]. Do not invent a forum. Do not invent a meetup. Do not invent a discount code for showing up. A fake 'join 12,000 members' line is a result I cannot defend.

💡

Pro tip: If you have no community yet, skip this email. An empty Discord invite is worse than silence.

Preference centre copy

4/30

✨ What it does

Writes preference-centre copy from list types you send and a cadence you actually keep. Missing cadence stays tagged; no extra list or stay-for-a-deal pitch is invented.

Write preference-centre copy from list types we actually send. List types: [LIST TYPES]. How often we really send: [SEND CADENCE]. Output: page title, 40 word explainer, one line per list type with a plain-language description, and a save button label. If cadence is missing, write [VERIFY] on that line rather than guessing weekly. Do not invent a list. Do not invent a legal right we did not state in [LEGAL LINES]. Do not mention a discount as a reason to stay. Preferences that promise mail we do not send are how people mark us as junk.

💡

Pro tip: Name the lists as the shopper sees them in the inbox, not as internal campaign names.

Welcome subject lines from our words

5/30

✨ What it does

Produces eight 6-to-9-word welcome subjects from brand words and signup source, labelled plain, curious or specific. Missing brand words stay tagged; no sale urgency is invented.

Write 8 welcome subject lines from words we already use. Brand words: [BRAND WORDS]. Signup source: [SIGNUP SOURCE]. Output 8 subjects, 6 to 9 words, each using at least one brand word, labelled Plain, Curious or Specific. If brand words are missing, write [VERIFY] and stop after asking for three words from the site header. Do not invent a discount. Do not invent an urgency such as 'last chance' on a welcome. Do not claim a result. A subject that shouts SALE on day one trains people to wait.

💡

Pro tip: Steal words from the homepage header, not from a swipe file.

Abandoned Cart

5 prompts

First cart reminder from the cart

6/30

✨ What it does

Writes a first cart reminder that names items in the pasted cart and mentions stock only if you wrote a stock note. An empty cart stays tagged and stops the job; no discount is invented.

Write the first abandoned-cart email from the cart I paste. Cart: [CART CONTENTS]. Store name: [STORE NAME]. Output: subject, 70 to 110 word body that names items from the cart, a button label, and a line that restocks only if I wrote [STOCK NOTE]. If the cart is empty, write [VERIFY] and stop. Do not invent a discount. Do not invent 'selling out'. Do not invent a complementary product. A reminder that adds 15 percent off I did not set will break the till and the trust.

💡

Pro tip: Paste the cart as the shopper sees it, including variant names.

Second reminder with FAQ from the product page

7/30

✨ What it does

Writes a second cart email with two FAQs answered only from the pasted product page. Unanswered FAQs stay tagged and skipped; no shipping day or discount is invented.

Write a second cart email that answers questions using a product page I pasted. Cart: [CART CONTENTS]. Product page: [PASTE PRODUCT PAGE]. Output 90 to 140 words: the items, two FAQs whose answers appear on the page, then a return-to-cart line. If a FAQ would need an answer not on the page, write [VERIFY] and skip it. Do not invent shipping days. Do not invent a size that is in stock. Do not invent a discount. A second email that fabricates 'arrives tomorrow' is a support ticket.

💡

Pro tip: Paste the shipping and returns blocks with the product copy. That is where the real questions live.

Size and fit help from a chart I have

8/30

✨ What it does

Writes a size-and-fit cart follow-up from a chart you pasted and a how-to-measure you filled. Variants the chart does not cover stay tagged; no 'runs large' claim is invented.

Write a cart follow-up about size and fit using a chart I pasted. Cart variants: [CART VARIANTS]. Size chart: [PASTE SIZE CHART]. Output 80 to 120 words that point at the chart, plus a 4 line 'how to measure' taken from [HOW TO MEASURE] if I filled it. If the chart does not cover a variant in the cart, write [VERIFY] beside that variant. Do not invent a centimetre. Do not invent that it runs large. Do not invent a discount for picking a size. A fit email with a guessed bust number is how parcels come back.

💡

Pro tip: Photograph the paper tape method you want shoppers to use, then paste those words.

Stock honesty from notes I trust

9/30

✨ What it does

Names each cart item in stock, low or gone from your notes, with complete, pick a listed alternative or wait. Missing SKU notes stay tagged; no restock date is invented.

Write a cart email that is honest about stock using notes I trust. Cart: [CART CONTENTS]. Stock notes: [STOCK NOTES]. Output a short email that names each cart item as In stock, Low, or Gone from my notes, with a next step: complete the cart, pick a listed alternative from [ALTERNATIVES I SELL], or wait. If a SKU has no stock note, write [VERIFY] and do not guess. Do not invent a restock date. Do not invent a discount to clear the last one. Fake scarcity is still a made-up result.

💡

Pro tip: Copy stock from the admin at send time. Yesterday's low stock is often already gone.

Cart subjects without fake urgency

10/30

✨ What it does

Produces eight 5-to-10-word cart subjects that name an item or the store, skipping last-chance language unless you allowed it. A cart with no item name stays tagged; no countdown is invented.

Write 8 abandoned-cart subjects that stay true to the cart. Cart: [CART CONTENTS]. Words I allow: [ALLOWED WORDS]. Output 8 subjects, 5 to 10 words, each naming an item or the store, none using last chance, selling out, or a percent off unless those words are in [ALLOWED WORDS]. If the cart has no item name, write [VERIFY] and stop. Do not invent a countdown. Do not invent a cart value. A subject with a ticking clock I did not start is fake urgency.

💡

Pro tip: Name the product. 'You left something behind' is weaker than the actual tote.

Post-Purchase

5 prompts

Thank you and what happens next

11/30

✨ What it does

Writes an 80 to 120 word thank-you with order items, next steps you supplied and a contact line. Missing next steps stay tagged; no delivery day or bonus gift is invented.

Write a post-purchase thank-you using fulfilment facts I have. Order facts: [ORDER FACTS]. What happens next: [NEXT STEPS]. Output 80 to 120 words: thanks, items from the order, next steps in order, a contact line from [CONTACT]. If next steps are missing, write [VERIFY] and ask me whether we send a later shipped email before drafting. Do not invent a delivery day. Do not invent a bonus gift. Do not invent a discount on the next order. A thank-you that promises Friday when we did not say Friday is a complaint.

💡

Pro tip: Match the next steps to the email Shopify already sends for paid, so you do not contradict it.

How to start using what they bought

12/30

✨ What it does

Writes a post-purchase how-to from start steps and care lines you already print, skipping unnamed downloads. Missing download names stay tagged; no glow-up result is invented.

Write a post-purchase how-to for the items on the order. Order: [ORDER ITEMS]. Start steps: [START STEPS]. Safety or care lines we print: [CARE LINES]. Output 100 to 150 words with numbered start steps, then care lines. If a step needs a download we did not name in [DOWNLOAD I MAY LINK], write [VERIFY] and skip the download. Do not invent a result. Do not invent a 7 day glow-up. Do not invent a refill date. A how-to that guarantees an outcome we do not print on the box is a claim.

💡

Pro tip: Copy care lines from the insert in the box, not from a blog you meant to write.

Review request without invented ratings

13/30

✨ What it does

Writes a 70 to 110 word review request for named items, with a prompt question and your real review link. Missing wait-days stay tagged; no star count or review reward is invented.

Write a review request that does not fake social proof. Order: [ORDER ITEMS]. Days since delivery I will wait: [DAYS SINCE DELIVERY]. Review link I actually use: [REVIEW LINK]. Output 70 to 110 words: ask for a review of the named items, one prompt question from [PROMPT QUESTION], the link. If days since delivery is blank, write [VERIFY] on the send-when line. Do not invent a star count. Do not invent that 'everyone loves' the tote. Do not invent a discount for reviewing. A request that quotes 4.9 stars we did not earn is a fabricated result.

💡

Pro tip: Send it after they have the parcel, using the delivery date you have, not a guessed average.

Replenish reminder from an interval I set

14/30

✨ What it does

Writes a 60 to 100 word replenish reminder from items they bought and an interval you set. A missing interval stays tagged and stops the job; no run-out claim is invented.

Write a replenish reminder using an interval I set and items they bought. Items: [ORDER ITEMS]. Interval I want: [INTERVAL I SET]. Output 60 to 100 words: the item, the interval in my words, a return-to-product button label. If the interval is missing, write [VERIFY] and stop rather than guessing 30 days. Do not invent that they ran out. Do not invent a repeating-order plan. Do not invent a discount for coming back. A 'you must be empty by now' line I cannot know is creepy and untrue.

💡

Pro tip: Set the interval from how long the last buyer said it lasted, if you have that note, not from a wish.

Next-product note from the catalog I pasted

15/30

✨ What it does

Suggests at most two catalog items that pair with the order for a reason you wrote. No pair stays tagged as send-nothing; no SKU or bundle deal is invented.

Write a next-product email using only items in a catalog I pasted and the order they already have. Order: [ORDER ITEMS]. Catalog: [PASTE CATALOG]. Output 80 to 130 words suggesting at most two catalog items that pair with the order for a reason I wrote in [PAIR REASON]. If the catalog has no pair, write [VERIFY] and send nothing rather than stretching. Do not invent a SKU. Do not invent a discount bundle. Do not invent that buyers who got A also got B unless that sentence is in [PAIR REASON]. A made-up 'complete the set' is a result I did not measure.

💡

Pro tip: If you have no pair reason, skip the email. Silence beats a random upsell.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. Easy-to-follow tutorials inside AI Academy, and the library keeps growing.

Try AI Academy Free

Shipping and Delivery

5 prompts

Shipped notice from tracking facts

16/30

✨ What it does

Writes a 70 to 110 word shipped notice from carrier, tracking number, ship date and items. A missing tracking number stays tagged and holds the send; no delivery window is invented.

Write a shipped email from tracking facts I have. Carrier: [CARRIER]. Tracking number: [TRACKING NUMBER]. Ship date: [SHIP DATE]. Items: [ITEMS]. Output 70 to 110 words: items, carrier, tracking number, ship date, a tracking button label. If tracking number is missing, write [VERIFY] and hold the email. Do not invent a delivery window. Do not invent a locker. Do not invent a live map we do not have. A shipped mail with a fake Thursday arrival is a one-star review waiting.

💡

Pro tip: Paste the tracking string from the carrier, not from memory of the dashboard.

Delay notice from a carrier note

17/30

✨ What it does

Writes a 90 to 140 word delay notice from a pasted carrier or warehouse note and what you can still do. A note with no date stays tagged; no weather story or apology deal is invented.

Write a delay notice using a carrier or warehouse note I pasted. Note: [DELAY NOTE]. Order: [ORDER ITEMS]. What we can still do: [WHAT WE CAN DO]. Output 90 to 140 words: the delay in the note's words, items, what we can do, a reply path from [REPLY PATH]. If the note has no date, write [VERIFY] rather than inventing one. Do not invent a weather event. Do not invent a discount apology. Do not invent that it will land tomorrow. An apology with a new date we do not have is a second delay.

💡

Pro tip: Quote the carrier sentence. Your paraphrase is where extra promises creep in.

Delivered plus unboxing notes

18/30

✨ What it does

Writes a delivered email that points at unboxing notes you include and a contact if something is wrong. Missing delivery facts stay tagged and block the send; no delight or extra code is invented.

Write a delivered email with unboxing notes we actually include. Delivery fact: [DELIVERY FACT]. Unboxing notes: [UNBOXING NOTES]. Output 70 to 110 words: delivered, what to check from the notes, who to write if something is wrong from [CONTACT]. If delivery fact is missing, write [VERIFY] and do not send. Do not invent that they love it. Do not invent an unboxing video. Do not invent a discount code in the tissue. A delivered mail that assumes delight lands wrong when the box is dented.

💡

Pro tip: Tell them which insert to keep. That is the one support will ask about later.

Address problem triage mail

19/30

✨ What it does

Writes an 80 to 120 word address-problem email from the error text, items and the reply you need. Missing error text stays tagged; no customs rule or reship is invented.

Write an email for an address problem using the error we have. Error: [ADDRESS ERROR]. Order: [ORDER ITEMS]. What we need them to reply with: [WHAT WE NEED]. Output 80 to 120 words: the error in plain language, the items, the reply we need, a deadline I set in [REPLY BY] if I set one. If the error text is missing, write [VERIFY] and ask me to paste the carrier error. Do not invent a customs rule. Do not invent a fee. Do not invent that we already reshipped. A triage mail with a made-up postcode fix will bounce twice.

💡

Pro tip: Paste the carrier error, then ask for one field, such as flat number, not the whole address again.

Pickup reminder from locker or shop notes

20/30

✨ What it does

Writes a 60 to 100 word pickup reminder with place, hours, items and hold-until if you have it. Missing hours stay tagged; no parking rule is invented.

Write a pickup reminder from locker or shop notes I have. Pickup place: [PICKUP PLACE]. Hours: [HOURS]. Order: [ORDER ITEMS]. Hold until: [HOLD UNTIL] if I have it. Output 60 to 100 words: place, hours, items, hold until. If hours are missing, write [VERIFY] on that line. Do not invent a parking rule. Do not invent a neighbour. Do not invent that the locker texts them unless [LOCKER TEXTS] is yes. A reminder with shop hours we did not copy is how parcels return to us.

💡

Pro tip: Copy hours from the pickup point's page the morning you send, because they change.

Winback

5 prompts

We miss you from a last-order date

21/30

✨ What it does

Writes a 70 to 110 word winback from a last-order date and items you supplied, plus a question. A missing date stays tagged and stops the job; no day-count or discount is invented.

Write a winback email from a last-order date I supply. Last order date: [LAST ORDER DATE]. Last items: [LAST ITEMS]. Output 70 to 110 words: we noticed the date, the items in one clause, a question, a shop button. If the date is missing, write [VERIFY] and stop. Do not invent how many days it has been beyond the date I gave. Do not invent a discount. Do not invent that their favourite is back unless that sentence is in [BACK IN STOCK NOTE]. A '90 days of missing you' I did not count is a fabricated result.

💡

Pro tip: Pull the date from the order list, not from a segment you have not checked.

New from us, only items I listed

22/30

✨ What it does

Writes an 80 to 120 word winback naming at most three new items with facts you supplied. An empty new-items list stays tagged as do-not-send; no drop or waitlist count is invented.

Write a winback that shows new items I listed, not a whole season I imagine. New items: [NEW ITEMS]. Last items they bought: [LAST ITEMS]. Output 80 to 120 words naming at most three new items with one fact each from [ITEM FACTS]. If new items is empty, write [VERIFY] and do not send a 'new arrivals' email. Do not invent a drop. Do not invent a waitlist count. Do not invent a discount for coming back. A launch they cannot find on the site is an invented catalog.

💡

Pro tip: Link the exact product URLs you listed. A collection URL hides whether the item exists.

Ask why they left, survey only

23/30

✨ What it does

Writes a 60 to 90 word ask-why email with your approved questions and a thank-you that contains no offer. Missing questions stay tagged and stop the job; no price multiple-choice is invented.

Write a winback that only asks why they left, using questions I approve. Questions: [QUESTIONS]. Where answers go: [WHERE ANSWERS GO]. Output 60 to 90 words plus the questions as a numbered list, and a thank-you with no offer. If questions are missing, write [VERIFY] and stop. Do not invent a multiple choice about price. Do not invent a discount for answering. Do not invent that we already fixed a complaint I did not paste. A survey that sneaks a deal is not a survey.

💡

Pro tip: Three questions is plenty. Put where answers go so someone on the team will read them.

Winback without a made-up offer

24/30

✨ What it does

Writes a 70 to 110 word come-back email around last items, quoting an offer only if you pasted one you already run. NONE means no percents or codes; missing offer numbers stay tagged.

Write a winback that has no offer unless I pasted one we already run. Offer we already run, or NONE: [OFFER OR NONE]. Last items: [LAST ITEMS]. Output 70 to 110 words that invite them back to those items. If OFFER OR NONE is NONE, include zero percents, codes or free-shipping claims. If I pasted an offer, quote it exactly and write [VERIFY] if any number is missing. Do not invent a code. Do not invent a result like 'customers who came back'. An invented 20 percent back is still a discount I did not set.

💡

Pro tip: If you have no live offer, the honest invite outperforms a code the till will reject.

Stop the sequence when they bought again

25/30

✨ What it does

Writes a kill rule for when a purchase lands, plus an optional short thanks that names the new order only if you filled those facts. A missing how-we-know stays tagged; no loyalty tier is invented.

Write a kill rule and a last email for a winback sequence when someone buys again. How we know they bought: [HOW WE KNOW]. Last winback email they might have seen: [LAST WINBACK]. Output: a one-line kill rule in ops language, and a 40 to 70 word optional 'thanks, we will stop nudging' note that names the new order only if [NEW ORDER FACTS] is filled. If how we know is missing, write [VERIFY] on the kill rule. Do not invent a loyalty tier. Do not invent a discount on the new order. A sequence that keeps begging after checkout is how people unsub.

💡

Pro tip: Wire the kill on paid, not on add-to-cart. A cart is not a purchase.

Go from copy-pasting to actually mastering AI.

AI Academy: hands-on tutorials on ChatGPT, Claude, Midjourney, and many other tools. New tutorials are added regularly.

Start Your Free Trial

Voice and Compliance

5 prompts

Plain-language pass

26/30

✨ What it does

Rewrites a draft in plainer language and lists claims that were dropped because they were not in the original. Sentences that need new facts stay tagged and dropped; no friendlier deal is invented.

Rewrite this Shopify email in plain language without adding claims. Draft: [DRAFT]. Reading level I want, in my words: [READING LEVEL]. Output the rewrite, then a list of claims you dropped because they were not in the draft. If a sentence needs a fact I did not give, write [VERIFY] and drop the sentence. Do not invent a discount to make it friendlier. Do not invent a result. Do not add slang I did not use in [VOICE SAMPLES]. A simpler email with a new promise is still a new promise.

💡

Pro tip: Read the rewrite aloud. If you need a breath in the middle of a sentence, split it.

Brand voice match from samples

27/30

✨ What it does

Rewrites an email to match pasted voice samples and lists sound changes, not fact changes. Jokes that need new claims stay tagged and skipped; no mascot or deal is invented.

Match this email to voice samples I paste, keeping every fact. Email: [EMAIL]. Samples: [VOICE SAMPLES]. Output the rewritten email, then three bullets on what changed in sound, not in facts. If a rewrite wants a joke that needs a new claim, write [VERIFY] and skip the joke. Do not invent a mascot. Do not invent a discount in the new tone. Do not invent a founder pet. Voice is how we say what is already true, not a second catalog.

💡

Pro tip: Paste samples from the same channel. Site banner voice is not inbox voice.

Mobile length trim

28/30

✨ What it does

Trims a body to a max word count you set, with a short subject and a preview line taken from existing sentences. A missing max stays tagged as a 90 word draft cap; no new offer is invented.

Trim this email for a phone screen using lengths I set. Email: [EMAIL]. Max body words: [MAX WORDS]. Output a trimmed body at or under the max, a subject of 6 to 8 words, and a preview line of 10 words from existing sentences. If max words is missing, write [VERIFY] and use 90 as a draft cap I must confirm. Do not invent a new offer in the leftover space. Do not invent an emoji. A shorter email that adds 'shop the sale' I did not write is still a new claim.

💡

Pro tip: Preview on a real phone width. The fold is higher than a desktop window suggests.

Required footer lines check

29/30

✨ What it does

Tables each required footer line as present or not, quoting it when found. Missing lines stay tagged as gaps; no address or unsubscribe sentence is invented.

Check that required footer lines I supply actually appear. Email: [EMAIL]. Required lines: [REQUIRED LINES]. Output a table with columns Required line, Present yes or no, Quote if present, Gap if not. If a required line is missing, write [VERIFY] in Gap and do not invent legal text. Do not invent an address. Do not invent an unsubscribe sentence I did not provide. A helper that writes a fake company address is worse than a flagged gap.

💡

Pro tip: Paste the footer your lawyer or ops already approved, not a template from memory.

Two subject angles I already chose

30/30

✨ What it does

Writes two 6-to-9-word subjects from angles you chose, each tied to a body fact, and notes how they differ. Angles that need missing facts stay tagged; no open rate is invented.

Write two subject lines from two angles I already chose, with no guessed performance. Angle A: [ANGLE A]. Angle B: [ANGLE B]. Email body facts: [BODY FACTS]. Output two subjects, 6 to 9 words, each tied to a fact in the body, plus a 20 word note on how they differ. If an angle needs a fact not in the body, write [VERIFY] on that subject. Do not invent an open rate. Do not invent a winner. Do not invent a discount to make B spicier. A predicted 'this will crush' is a fabricated result.

💡

Pro tip: Pick angles such as item name versus next step, not 'funny versus fear'.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

This page is only inbox copy: welcome, abandoned cart, post-purchase, shipping and winback. The Shopify hub covers store and product work. Use this page when the job is an email the shopper will open.
They are written not to. If you did not paste a live offer, codes and percents stay out. Star counts, member counts and 'selling out' lines get tagged [VERIFY] or dropped. Check every number against admin before you send.
Yes. Paste the draft into whichever sender you already use. Keep the footer lines your ops already approved. The prompts do not set up a flow for you; they write the copy inside one you run.
The cart as the shopper sees it, the product page blocks for shipping and fit, and stock notes from admin at send time. Skip last-chance language unless you typed those words on purpose.
Use the kill-rule prompt. Wire it on paid, not on add-to-cart. The optional thanks may name the new order only if you pasted those facts. Do not keep nudging a person who already checked out.

Prompts are the starting line. Tutorials are the finish.

A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.

Start 7-Day Free TrialCancel anytime.
Explore AI for Marketers