ChatGPT for E-commerce: Best Prompts

Write a product description for a ceramic coffee mug.

The Problem the Store Owner Faced

Most guides to chatgpt prompts for ecommerce lead with product descriptions, and a small home goods store owner started there too when she first adopted ChatGPT for her Shopify store. It helped, modestly. But when she actually tracked where her time and revenue were most affected over a quarter, the bigger win turned out to be somewhere she hadn't expected: customer service response templates for her most common support tickets.

The Wrong Approach

Her early product description prompts were the standard, underspecified kind:

Write a product description for a ceramic coffee mug.

What this does: produces a description that could apply to literally any ceramic mug on the internet -- no material specifics, no use case, no differentiation from the dozens of similar mugs a shopper has already scrolled past.

For customer service, her first attempt at building response templates was similarly generic:

Write a response to a customer asking about a late shipment.

What this does: produces a reasonable-sounding but non-specific apology that doesn't actually address why the shipment is late or give the customer anything concrete to expect next, which means she still had to rewrite most of it manually before sending.

⚠️ Common mistake: Building customer service templates without connecting them to your actual shipping data, return policy specifics, or common failure reasons. A generic apology template still requires manual editing every time, which defeats the purpose of having a template at all.

The Correct Prompt

The fixed version for customer service ties directly into her store's actual shipping carrier data and gives a concrete next step:

Write a response to a customer whose order shipped 3 days ago via USPS but tracking hasn't updated in 48 hours. Explain this is common with USPS scan delays and doesn't necessarily mean a problem, give them the tracking link, and offer a specific next step: if there's no update in 72 hours from now, reply and we'll open a trace with the carrier.

What this does: naming the specific likely cause (USPS scan delays) reassures the customer without overpromising, and the explicit 72-hour next step gives them something concrete to hold onto instead of an open-ended "we're looking into it" that tends to generate a follow-up message anyway.

⚡ Pro tip: For shipping-related customer service templates, always include a specific timeframe for the next action, even if that action is just "reply again if X hasn't happened by Y." Open-ended reassurance without a timeframe is one of the most common causes of repeat contact on the same issue.

Results and What Changed

After rolling out a set of situation-specific customer service templates -- late shipment, wrong item received, sizing question, return request -- her average first-response time dropped significantly, and repeat-contact rate on the same issue (customers writing back again because the first response didn't actually resolve anything) dropped too, since each template gave a concrete next step instead of vague reassurance.

For product descriptions, she eventually found her way to a more specific structure as well, once she started providing the same level of detail she'd learned to use for customer service:

Write a product description for a handmade ceramic mug. Specifics: stoneware clay, holds 12oz, dishwasher and microwave safe, glazed in a speckled matte finish, made by a single potter in small batches (not mass-produced). Target customer: someone buying a thoughtful gift, not just a functional mug.

What this does: the specific material details plus the "thoughtful gift" framing produces a description that differentiates the product from mass-produced alternatives, which matters for a handmade goods store competing against much cheaper mass-market options on the same platform.

How to Apply This to Your Situation

A different e-commerce operator selling supplements applies a similar level of specificity to abandoned cart recovery emails, which are often left as generic platform defaults:

Write an abandoned cart email for a customer who left a 30-day supply of magnesium glycinate in their cart 24 hours ago. Reference the specific product, address a common hesitation for first-time supplement buyers (wondering if it actually works), and include one specific detail that builds trust (third-party tested, no fillers).

What this does: addressing a specific, common hesitation rather than a generic "don't forget your cart!" nudge gives the customer an actual reason to reconsider, rather than just a reminder of something they already chose not to complete.

⚠️ Common mistake: Leaving abandoned cart emails as generic platform defaults instead of customizing them per product category to address that category's most common purchase hesitation. A supplement buyer's hesitation is different from a clothing buyer's hesitation (fit, not efficacy), and a generic template addresses neither well.

A small business selling custom pet portraits uses ChatGPT to draft responses to a specific recurring question type: customers unsure about photo quality requirements before ordering.

Write a response to a customer asking if their phone photo is good enough quality for a custom pet portrait. Explain the actual technical requirement (at least 3MP, good lighting, pet's face clearly visible) in plain, non-technical language, and offer to review their specific photo if they're unsure.

What this does: translating a technical spec (3MP) into a plain-language explanation while still offering a concrete fallback (photo review) addresses both the informed customer and the customer who just wants reassurance, without requiring two different templates.

Handling Negative Reviews and Public Feedback

Public-facing responses to negative reviews carry more weight than private customer service, since future customers read them too. A skincare brand owner uses ChatGPT to draft review responses that acknowledge the issue without being defensive, while also subtly reassuring future readers of the review:

Draft a public response to a 2-star review complaining that a serum "didn't do anything" after 2 weeks of use. Acknowledge their experience without being defensive, mention that visible results typically take 6-8 weeks for this product type (this is accurate per our product testing), and invite them to reach out directly for a refund or exchange if they'd like.

What this does: providing the accurate timeframe context (6-8 weeks) reframes the review for future readers without dismissing the original reviewer's frustration, and the direct invitation to reach out shows good faith without making promises in a public forum where tone matters enormously.

⚠️ Common mistake: Responding to negative reviews defensively or with a generic "we're sorry to hear that" that doesn't address the specific complaint. Future customers reading the review thread notice whether a brand actually engages with the substance of a complaint or just offers a hollow apology.

⚡ Pro tip: When responding publicly to a negative review, always include one piece of accurate, relevant product information (like an expected results timeframe) that helps future readers interpret the review in context, not just an apology directed at the original reviewer.

A subscription box company uses ChatGPT to handle a specific recurring complaint type: customers wanting to pause rather than cancel their subscription, which requires steering the conversation toward retention without being pushy about it:

Write a response to a customer requesting to cancel their monthly subscription. Before processing the cancellation, mention the pause option (skip up to 3 months, no fee) as an alternative, framed as genuinely helpful information, not a retention tactic they need to push back against.

What this does: framing the pause option as helpful information rather than a retention script keeps the tone respectful of the customer's decision while still surfacing a genuinely useful alternative they might not know exists -- a difference that matters both ethically and in how it reads to the customer.

FAQ and Product Page Support Content

Beyond direct customer service, a home fitness equipment retailer uses ChatGPT to build out FAQ content for product pages, addressing the specific questions that generate the most pre-purchase support tickets:

Write 4 FAQ entries for a product page for an adjustable dumbbell set. Base these on our top support inquiries: assembly time, weight increments available, whether it works on carpet without a mat, and return policy for opened items. Keep each answer under 40 words.

What this does: basing the FAQ directly on actual recurring support inquiries, rather than generic guessed questions, means the FAQ page actually reduces support volume by answering what customers are genuinely asking before they need to open a ticket.

⚡ Pro tip: Pull your FAQ content directly from your actual support ticket history, not from guessing what customers might ask. The gap between assumed questions and real questions is usually larger than store owners expect, and closing that gap is where FAQ pages actually earn their keep in reduced support volume.

Next Steps

The pattern that held across product descriptions, customer service, and cart recovery: specificity about the actual product, the actual customer hesitation, or the actual operational detail (carrier, timeframe, technical requirement) is what separates a template that still needs heavy editing from one that's ready to send as-is.

If you're running a store with recurring customer service scenarios and product categories, it's worth saving these templates with your specific operational details built in -- shipping carriers, return windows, common hesitations by category -- rather than rebuilding them from a generic starting point each time. PromptABCD works well for storing this kind of reusable, situation-specific e-commerce template library.