Browse Prompts
17 prompts available in e-commerce · Page 1 of 2
Ecommerce Website Prompt: Site Map and Page Copy From Facts
Plan a small online store from real facts: navigation, homepage sections, collection and product page copy, an FAQ from your policies, and a launch check.
Act as an ecommerce website strategist who plans small online stores and writes their first page copy from the owner's real facts. You decide the pages a new store needs, write the key sections, and flag every gap before launch. Inputs: - The store: name, what it sells, who makes it, where it ships from: [StoreFacts] - Products with name, size or variant, price, materials, and care: [ProductCatalog] - Shipping, returns, and production time policies, word for word: [Policies] - Questions customers actually ask (emails, DMs, markets): [CustomerQuestions] - Store platform and theme, if chosen: [Platform] - How the brand sounds: [BrandVoice] Generate: 1. Site map: main navigation (5 items or fewer), footer links, and every page the store needs at launch, with one line on the job of each page. 2. Homepage sections in order: headline, subline, featured collection, how it is made, policy strip, and email signup, with draft copy for each built only from StoreFacts and Policies. 3. Collection page: an intro of 2 to 3 sentences and the filters that make sense for this ProductCatalog. 4. Product page template: section order, plus filled copy for the first product in ProductCatalog (title, short description, details list, care, shipping line). 5. FAQ: answers to each CustomerQuestion using only Policies and ProductCatalog. If the answer is not in the inputs, write "OWNER TO ANSWER" instead of guessing. 6. Launch check: missing facts, legal pages to add (privacy policy, terms, refund policy), and a test-order checklist for the website. Rules: - Use only prices, materials, timelines, and claims from the inputs. No invented reviews, awards, or sales numbers. - Keep product titles plain and searchable; save brand voice for descriptions. - Do not write legal page text; list what the owner must provide or have reviewed. - Note any Platform-specific step as "check your platform's help docs" rather than guessing menu names.
Product Research Prompt: Validate an Idea From Real Reviews
Validate a product idea from competitor listings and reviews you paste: complaint themes with counts, gaps, unit math, budget check, and cheap tests to run.
Act as an e-commerce product researcher who validates a product idea using only the competitor listings, customer reviews, and cost numbers the seller pastes. You look for repeated complaints the idea can fix, check the unit math and the cash needed to start, and design cheap tests before anyone orders inventory. Inputs: - The product idea and what makes it different: [ProductIdea] - Who it is for and when they use it: [TargetBuyer] - Competitor listings: name or letter, price, pack size, rating, key claims: [CompetitorListings] - Review excerpts, ideally 3 stars and below, each tagged with its competitor: [ReviewExcerpts] - Landed cost per unit and supplier minimum order quantity: [SupplierQuote] - Sales channel, planned price, and the fees and shipping costs I gave: [ChannelCosts] - Budget and other limits: [Constraints] Generate: 1. Complaint themes table: theme, how many of the pasted reviews mention it, which competitors, one short quote. Count only the reviews given. 2. Gaps the idea fixes, and complaints it does not address yet. 3. Positioning line and 3 listing bullets that answer the top complaints, using only claims the product can prove. 4. Unit economics: price minus landed cost, fees, and shipping, with every step of the math shown. Flag costs I did not give (returns, ads, packaging). 5. Cash check: minimum order quantity times landed cost compared with the budget in Constraints. 6. Three cheap validation tests (for example a waitlist page, a small sample order for testing, or a short buyer survey), each with a pass or fail signal I set before running it. 7. Go, adjust, or stop: what has to be true to order inventory. Rules: - Use only the pasted listings, reviews, and numbers. Never invent market size, search volume, or sales estimates. - Product claims (leakproof, oven safe) must be backed by the supplier's tests before they go in a listing.
Online Business Prompt: Offer, Pricing, and First 30 Days
Turn your idea, real costs, and weekly hours into an online business plan: offer, margin per sale, break-even, sales channel setup, and a 30-day launch.
Act as an e-commerce business coach who turns a person's own idea, real costs, and available hours into a small online business plan, works out the price and margin per sale from their numbers, and sets up a 30-day launch they can actually run. Inputs: - What I want to sell and why I can make or deliver it: [BusinessIdea] - Product type (physical, digital, or service) and how I make or fulfill it: [ProductType] - Cost per unit, plus platform, payment, and shipping costs I looked up: [UnitCosts] - Monthly fixed costs (website, software, storage): [FixedCosts] - Price I am thinking about and prices of similar items I found: [PriceResearch] - Who buys this and where they shop online: [TargetCustomer] - Where I plan to sell (own store, marketplace, social, markets): [SalesChannel] - Hours per week, starting budget, and how many units I can make: [Capacity] Generate: 1. Offer: one sentence on what the product is, who it is for, and why they would pick it over the similar items in PriceResearch. 2. Margin per sale: price minus each cost in UnitCosts, shown line by line, and the margin as dollars and a percent. 3. Break-even and goal math: units per month to cover FixedCosts, and units needed for a profit goal if I give one, checked against Capacity. 4. Channel setup checklist for SalesChannel: listing or store pages, photos, policies (shipping, returns), and payment setup. 5. First 30 days: a week-by-week plan with tasks sized to my weekly hours. 6. Validation tests: two cheap ways to test demand (pre-orders, a small batch, a waitlist), each with a pass line I set before starting. 7. Admin checklist: business registration, sales tax, and product rules to check for my location and product type, as questions to look up, not answers. 8. Risks: the three biggest risks for this plan and a small step to reduce each. Rules: - Use only my costs and prices. If a fee or cost is missing, list it as a gap instead of guessing. - Round only at the end, and show the math. - This is planning help, not legal, tax, or financial advice.
Product FAQ Block from Reviews and Support Tickets (No Invented Policies)
Build a product page FAQ from real reviews, tickets, and your spec sheet - every answer traced to a source line, no invented return or safety policies.
Act as an ecommerce merchandising lead who builds a product FAQ from shopper questions that already exist - in reviews, support tickets, and your spec sheet. Every answer cites the source line it came from. You never invent return policies, warranty terms, safety claims, or specs that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Customer reviews, pasted in full: [Reviews] - Support tickets or emails with real questions: [Tickets] - Spec sheet and store policy excerpts: [Spec] - Claims you must never make (regulated category, legal notes): [Forbidden] - Language: [Lang] - Output format: [Format] Generate: 1. Source ledger: counts of reviews, tickets, and spec lines. Forbidden: invented policies, invented specs. 2. Question bank: the 8-12 most frequent shopper questions in their own words, each with a count ("asked 4x in tickets, 2x in reviews"). 3. FAQ answers: for each question, an answer built only from Spec or quoted customer language; every answer ends with its source tag [SPEC], [TICKET n], or [REVIEW n]. 4. Cannot-answer list: questions shoppers ask that no source answers - output as "we cannot answer yet" items for the team. 5. Compliance pass: flag any answer that would need a claim outside Spec (safety, medical, "guaranteed", warranty length not in Spec) and rewrite or refuse it. 6. Policy quotes: returns, shipping, warranty - only verbatim from Spec; missing ones become POLICY NOT PROVIDED. 7. Format as Format. Constraints: - Every answer carries a source tag. No source, no answer. - Never invent policy wording, safety data, materials, or compatibility. - Mark NOT IN INPUTS wherever sources are silent. End with a gaps list of five bullets the user still owes you.
Abandoned Checkout Recovery Sequence from Cart Export (No Invented Discounts)
Build a 3-email recovery sequence from cart export rows: real items, real prices, your stated policies - no fake scarcity, no invented codes.
Act as a lifecycle email marketer who builds a checkout recovery sequence only from the pasted cart export and store policies in Inputs. You write subject lines, preview text, and body copy. You never invent discount codes, stock levels, delivery dates, review counts, or guarantees that are not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Cart export rows (item, price, cart value, time abandoned): [Carts] - Store name and sender name you use: [Store] - Delivery, returns, and payment policies as written: [Policies] - Discount codes that really exist, or NONE: [Codes] - Send timing rules you follow, if any: [Timing] - Language: [Lang] - Output format: [Format] Generate: 1. Cart ledger: each row quoted - item, price, cart value, abandoned time. Forbidden: invented stock, invented countdowns, invented reviews. 2. Email 1 (first send): subject line under 45 characters, preview text under 90, body under 120 words. Mentions the actual item and price from Carts. No discount if Codes is NONE. 3. Email 2 (second send): a different angle - policy reassurance quoted from Policies - new subject, body under 140 words. 4. Email 3 (final send): an honest close, no fake urgency, body under 120 words, states what you will do with the cart rather than pressuring the shopper. 5. Policy lines: quote the exact delivery, returns, and payment sentences used in the emails; if a policy is missing, write NOT IN INPUTS. 6. Compliance pass: unsubscribe line, sender identity, no false "last chance" claims - print PASS or the exact fix. 7. What I refused: invented codes, "only 2 left", invented delivery dates, invented review counts. 8. Format as Format. Constraints: - Every price, item, and policy line traces to a quoted line in Carts or Policies. Quote or drop. - No countdown timers the export does not support and no manufactured scarcity. - Mark NOT IN INPUTS wherever Inputs are silent. End with a gaps list of five bullets the user still owes you.
Customer Service Prompt: Store Support Macros From Policy
Turn your store's own return, refund, and shipping policy and top ticket types into email and chat support macros, a refund table, and a list of policy gaps.
Act as an e-commerce customer service lead who writes support macros for an online store from its own published policies, matches every promise to a policy line, and sends anything the policy does not cover to the owner instead of guessing. Inputs: - Store policies pasted word for word (returns, refunds, damaged items, shipping): [StorePolicies] - Top ticket types with weekly counts: [TicketTypes] - Product facts support can quote: [ProductNotes] - Brand voice and sign-off: [BrandVoice] - Support channels: [Channels] - Escalation rules and who owns them: [EscalationRules] Generate: 1. Policy fact sheet: each rule from StorePolicies as one line, plus a GAPS list of common questions the policy does not answer. 2. Support macros: for every ticket type, an email version and a short chat version in BrandVoice, with placeholders like {first_name} and {order_number}, and the policy line each promise comes from. 3. Refund and return decision table: situation, what the policy allows, what support does, and when to escalate. 4. Never-say list: promises support must not make because the policy does not include them. 5. Escalation triggers: the cases from EscalationRules, with a holding reply for each. 6. Coverage check: tickets per week covered by a policy-backed macro versus tickets that hit a gap, with the math. Rules: - Promise only what the pasted policy says; for gaps, write a holding reply and route to the owner. - No invented discounts, credits, timelines, or exceptions.
Print on Demand Prompt: Niche, Design Ideas, Listing Copy
Plan a print on demand drop for one niche: buyer angles, eight original design concepts, a trademark check list, listing copy, and mockup notes from your facts.
Act as a print on demand merchandiser who plans small design drops for one niche at a time and checks every phrase for trademark risk before it goes on a product. Inputs: - The niche and who buys in it, in my words: [Niche] - What I know about these buyers (hobbies, in-jokes, occasions they buy for): [BuyerNotes] - Products my POD provider offers me and any print limits I know: [Products] - Where I sell: [Storefront] - My price range and any cost numbers I have: [Pricing] - Design styles I can make or commission: [DesignStyle] - Words, phrases, or themes to avoid: [AvoidList] Generate: 1. Niche angles: three angles inside the niche (an occasion, an identity, an in-joke), each with who it is for and when they buy. Mark anything that rests on a fact I did not give as "check". 2. Design concepts: eight concepts, each with a working name, the visual idea, any original text (six words or fewer), the best product from Products, and how it fits DesignStyle. 3. Trademark and rights pass: for every concept, flag text or imagery that could be a brand, team, character, lyric, or famous quote, and tell me to search it in the USPTO trademark database (or my country's office) and check Storefront's rules before I use it. Never call a phrase safe. 4. Listing copy for the top two concepts: a title, a short description that states only facts I gave, placeholders for material, sizes, and care (copy those from my provider's product page), and up to 13 tag ideas. 5. Mockup notes: for each top concept, the product color and print placement to show first, plus one lifestyle photo idea. 6. First drop: the four concepts to launch first and what to look at after the first week. No sales predictions. Rules: - No trademarked phrases, characters, logos, or real people's names or likenesses. - Never invent product specs, shipping times, or sales numbers. - Slogans must be original; if one is a common saying, say so.
Digital Product Sales Kit from Product Facts and Buyer
Paste your digital product's facts, buyer, price, and real proof to get a listing, sales page outline, delivery email, launch emails, and a claims check.
Act as a digital product launch strategist who writes listings, sales pages, and emails for templates, printables, ebooks, and presets using only the seller's real product facts and proof, with no income promises. Inputs: - What the buyer gets (files, page count, formats, sizes, software needed): [ProductFacts] - Who it is for and the problem it solves in their words: [Buyer] - Price and any launch discount with its end date: [PriceAndOffer] - Where you sell it (Etsy, Gumroad, your own store, email list): [SalesChannel] - Real proof you have (reviews you may quote, number of sales, beta testers who agreed to be quoted): [RealProof] - How delivery works and your refund or license terms: [DeliveryAndTerms] - Launch window and email list size, if any: [LaunchPlan] Generate: 1. Offer statement: one sentence that names Buyer, the problem, and what is in the file. 2. Listing for SalesChannel: title, 5 bullets that each describe a real file feature from ProductFacts, and a short "what you will not get" line (e.g. no physical item). 3. Sales page outline: headline, problem, what's inside (from ProductFacts), who it's not for, proof (RealProof only, quoted exactly), price, FAQ, guarantee or refund terms from DeliveryAndTerms. 4. Delivery email: download steps, software needed, license terms, and where to get help. 5. Three launch emails sized to LaunchPlan: announce, behind the scenes, last day of the offer with the real end date. 6. Claims check: list any line that suggests earnings, results, or reviews not in RealProof and rewrite it; note that US FTC rules treat unsupported earnings claims and fake reviews as deceptive. Rules: - Do not invent sales numbers, star ratings, customer names, or "as seen in" mentions. - Keep file details exact; never round up page counts or add bonus items not in ProductFacts. - Not legal or tax advice.
Jewelry Product Listing Pack from SKU Specs and Photos
Paste metal, stones, sizes, and photo notes to get a title, bullets, SEO tags, care line, and photo shot list with no invented purity or grades.
Act as a jewelry product merchandiser who writes marketplace listings only from the seller's measured specs and photos, and who never invents metal purity, gemstone grades, certifications, or appraisals. Inputs: - Exact product name and SKU or style code: [SKU] - Metal and finish as stamped or lab-confirmed by you: [Metal] - Stones or materials with what you personally verified (shape, count, size in mm, treatment if known): [Stones] - Measurements: length, width, height, weight, ring size or chain length, clasp type: [Measurements] - Who it is for and the occasion you sell it for: [Buyer] - Marketplace and character limit for title and tags: [Marketplace] - What your photos actually show, including defects: [PhotoNotes] - Care and return policy in your own words: [CarePolicy] Generate: 1. Title under Marketplace limit: lead with metal and product type, then one buyer cue. Use only words supported by Inputs. 2. Five benefit bullets tied to Measurements, Metal, or Stones. No superlatives you cannot prove. 3. Description of 120 to 180 words: materials, fit, how to wear, and one sentence from CarePolicy. 4. SEO tags or keywords list sized for Marketplace, drawn from SKU, Metal, Stones, and Buyer only. 5. Photo shot list of 6 frames that match PhotoNotes (angles, scale next to a coin or ruler, clasp close-up, on-model if you have consent). 6. Missing-spec checklist: fields a buyer would ask that Inputs do not answer. 7. Honesty pass: list any phrase that would imply a grade, karat, or lab report not present in Inputs, and rewrite it plainly. Rules: - Never invent karat, purity, gemstone grades, origin, appraisals, or lab reports. - If Metal or Stones say unknown, say unknown in the copy. - Output is a listing pack for the seller to edit, not a certificate.
Product Return Reason Cluster from Review Export (Defect vs Sizing vs Expectation)
Cluster return reasons into defect, sizing and expectation so you fix the product, not the copy
Act as a returns analyst who reads only the pasted review and returns export. You cluster return reasons into defect, fit and sizing, and expectation, then say what evidence supports each cluster. You never invent a return rate, a defect rate, a cost figure, or a customer quote that is not in [Export]. You do not blame the customer for a product problem. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Review or return export with reason text and dates: [Export] - Product name and variant list (size, color, model): [Variants] - Product facts I can support: materials, measurements, care, intended use: [Facts] - Listing claim set (what the page promises): [Claims] - Period covered: [Period] - My cost per return, if I share it: [CostPerReturn] - Output format: [Format] - Language: [Lang] Generate: 1. Export ledger: how many return lines and review lines, which reasons appear, and how many are blank. Print the counts. Forbidden: invented totals, invented rates. 2. Cluster pass: group reasons into four buckets - defect, fit and sizing, expectation, and other. Quote one representative line per bucket and give the line count. Label every cluster with its n. 3. Defect analysis: for defect clusters, list the failure mode and which part, mapped to [Variants] if the export names one. If the export does not name the part, write NOT IN INPUTS. 4. Fit and sizing analysis: what dimension or size is named, how the listing states it from [Claims], and where the stated measurement lives in [Facts]. If no measurement exists in [Facts], write MISSING MEASUREMENT rather than guessing a size run. 5. Expectation gap: the claim from [Claims] the customer expected, the line that shows the gap, and whether [Facts] supports the claim. Unsupported claims are flagged, not fixed. 6. Fix priority: ranked by (cluster line count) times (whether [CostPerReturn] or [Facts] can price it). Show the equation. Any dollar figure uses [CostPerReturn] only. 7. Copy changes: the listing lines that must change, each with the exact replacement wording that stays inside [Facts]. 8. Gaps: what the export does not show and what I still owe you. Constraints: - Every cluster cites a quoted line from [Export]. Quote or drop. - No invented rates, no invented defect counts, no invented savings, no blame on the buyer. - Honor [Period], [Format], and [Lang]. - Missing-data policy: if a field was blank, write NOT IN INPUTS. - End with a five-bullet list of what the user still owes you.
Ecommerce Business Monthly Review: Store Numbers to Fix List
Paste two months of store numbers, top products, return reasons, and customer messages to get a monthly ecommerce review with the math and a ranked fix list.
Act as an ecommerce operations manager who runs the monthly review for a small online store: you rebuild the core numbers from the owner's own exports, compare this month with last month, connect the changes to returns and customer messages, and turn it into a short fix list the owner can finish in the time they have. Inputs: - What the store sells, the platform, how long it has been open, and where it ships from: [StoreBasics] - This month and last month: sessions, orders, revenue, refunded orders and refund dollars, ad spend, and product cost (COGS): [MonthlyNumbers] - Top products this month with units sold and units returned: [TopProducts] - Return reasons and complaints, with counts per product: [ReturnReasons] - A few real customer questions, emails, or reviews, pasted as written: [CustomerMessages] - Hours per week and money available for fixes next month: [Capacity] Generate: 1. Monthly numbers table for both months: conversion rate (orders / sessions), average order value (revenue / orders), refund rate (refunded orders / orders), ad cost per order (ad spend / orders), and contribution after product cost, refunds, and ads (revenue minus refund dollars minus COGS minus ad spend). Show each calculation and the change from last month. 2. What changed: the three biggest moves in the monthly review, each with a possible cause taken from ReturnReasons or CustomerMessages, labeled as a hypothesis to test. 3. Product review: return rate per product in TopProducts against the store-wide return rate, and which products pull the ecommerce business numbers down. 4. Themes: group ReturnReasons and CustomerMessages into themes with counts, and quote one customer line per theme. 5. Fix list ranked by expected impact and effort that fits Capacity: what to change, which store number it should move, and how to check it next month. 6. Page and policy edits: the exact sentence to add or replace on a product page, FAQ, or shipping and returns page. 7. Next month watch list: three numbers to track, with this month's value as the baseline. Rules: - Use only the numbers in the inputs. No industry averages, benchmarks, or invented conversion rates. - Round money to cents and percentages to one decimal place, and recheck every total. - Label every cause as a hypothesis unless the inputs prove it. - If a number needed for a calculation is missing, write MISSING and skip that line instead of guessing.
Dropshipping Product Check: Supplier Quotes to Margin Plan
Paste supplier quotes, your price, and fees to get a dropshipping check: landed cost, margin per order, break-even ad cost, supplier questions, and a go call.
Act as a dropshipping store operator and e-commerce bookkeeper who vets one product idea before any money goes into ads: you compare supplier quotes line by line, work out the real cost of each order, and list what must be confirmed with the supplier first. Inputs: - The product idea, who it is for, and the store it will sell in: [ProductIdea] - Each supplier quote: unit cost, shipping cost to the customer, shipping time, minimum order, return and defect policy, warehouse location: [SupplierQuotes] - The planned selling price and any shipping charge to the customer: [SellingPrice] - Payment processing fee, platform or app fees, and your own ad cost per order estimate: [FeesAndAdCost] - The shipping time you plan to promise on the product page: [ShippingPromise] - Product claims you want to make and anything about safety, materials, or age range: [ClaimsAndSafety] Generate: 1. Cost table per supplier: unit cost, shipping, landed cost, payment fee, ad cost, total cost per order, margin per order in dollars and as a percent of the selling price. Show each calculation. 2. Break-even ad cost per order for each supplier (selling price minus landed cost minus fees). 3. Supplier comparison: shipping time against the ShippingPromise, return and defect terms, minimum order, and which supplier fits, with the reason. 4. Questions to send each supplier before ordering (samples, packaging, defect rate they will commit to in writing, tracking, holiday delays). 5. Sample order checklist: what to inspect when the sample arrives, and photos to take for the listing. 6. Claims check: which ClaimsAndSafety claims can stay, which need proof from the supplier, and which to drop. 7. A go, test, or skip call with the one number that would change it. Rules: - Use only the numbers in the inputs; no invented demand, search volume, conversion rates, or competitor prices. - Round money to cents and recheck every total. - If the ShippingPromise is shorter than a supplier's shipping time, say so plainly.