Grok Bot ecommerce prompts that flag, then wait
Inventory flags, review queues, order exceptions, merchandising drafts. Distinct from paid ads and content. The Bot does not refund, change live prices, or email customers.
In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Inventory flags
5 promptsLow-stock flag vs reorder point
1/21✨ What it does
The Bot flags SKUs in [INVENTORY VIEW] that sit under [REORDER POINT] and writes a restock note with vendor and lead time. You still change the store: you place the PO and edit live availability.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag SKUs in [INVENTORY VIEW] under [REORDER POINT]. Draft a restock note per SKU. Do not change stock, place POs, or edit live availability. Sources: [INVENTORY VIEW], [VENDOR SHEET], [LEAD TIMES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change stock levels or live availability. - Do not place purchase orders or email vendors. Deliverable: SKU, on-hand, reorder point, vendor, lead time, draft restock note. Review point: I change the store.
Pro tip: Name the view and the point. "Low stock" without a number flags everything.
Dead stock in a collection
2/21✨ What it does
The Bot lists SKUs in [COLLECTION] with no units sold in [N] days and drafts a markdown or bundle note for each. You still change the store: you set the sale price and move the collection.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List SKUs in [COLLECTION] with zero sales in [N] days. Draft markdown or bundle notes. Do not change prices or collections. Sources: [COLLECTION], [SALES REPORT], [PRICE RULES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change live prices. - Do not move collections or start a sale. - Do not email customers a clearance note. Deliverable: SKU, last sale, days idle, draft markdown or bundle note. Review point: I change the store.
Pro tip: Give it the window. Forever-slow is not the same as last month was quiet.
Incoming PO vs on-hand mismatch
3/21✨ What it does
The Bot compares open lines on [PO LIST] to on-hand counts in [INVENTORY] and flags qty or SKU mismatches. You still change the store: you receive stock and correct the counts.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [PO LIST] to [INVENTORY]. Flag qty or SKU mismatches. Do not receive stock or edit counts. Sources: [PO LIST], [INVENTORY], [WAREHOUSE NOTES IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not receive purchase orders. - Do not edit on-hand counts. - Do not email the vendor about the gap. Deliverable: PO line, expected, on-hand, mismatch, suggested receive (unpublished). Review point: I change the store.
Pro tip: If a PO line has no SKU match, call it unknown. Do not invent a receive.
Variant inventory drift
4/21✨ What it does
The Bot checks variants on [PRODUCT LIST] where the listing qty does not match [INVENTORY] and drafts a correction table. You still change the store: you fix the variant counts yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find variants on [PRODUCT LIST] whose listing qty does not match [INVENTORY]. Draft a correction table. Do not edit variants. Sources: [PRODUCT LIST], [INVENTORY], live PDPs in the browser. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit variant quantities. - Do not change live prices. - Do not unpublish products. Deliverable: Product, variant, listing qty, inventory qty, draft fix. Review point: I change the store.
Pro tip: Size and color drift is how you oversell. Ask for the listing URL plus the inventory SKU.
Safety stock vs lead time
5/21✨ What it does
The Bot scores SKUs in [CATALOG] against [VENDOR LEAD TIMES] and flags those without enough cover for the next cycle. You still change the store: you raise safety stock and place orders.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Score [CATALOG] against [VENDOR LEAD TIMES]. Flag SKUs without cover for the next cycle. Do not raise safety stock or place orders. Sources: [CATALOG], [VENDOR LEAD TIMES], [SALES VELOCITY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change safety-stock settings. - Do not place purchase orders. - Do not email vendors. Deliverable: SKU, days of cover, lead time or unknown, draft reorder note. Review point: I change the store.
Pro tip: Lead time from the vendor sheet, not a guess. Unknown lead time stays unknown.
Reviews
4 promptsReview queue for the last N days
6/21✨ What it does
The Bot ranks new reviews in [REVIEW TOOL] from the last [N] days by rating, theme, and whether a reply is due. You still change the store: you post the public reply yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rank reviews in [REVIEW TOOL] for the last [N] days. Theme, rating, reply-due. Do not post replies. Sources: [REVIEW TOOL], [REPLY POLICY], [VOICE EXAMPLES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not post public replies. - Do not email reviewers. - Do not change ratings or hide reviews. Deliverable: Review, theme, reply-due yes/no, draft reply unpublished. Review point: I change the store.
Pro tip: A 3-star with a shipping complaint is ops, not a product rewrite.
One-star theme cluster
7/21✨ What it does
The Bot clusters 1-star reviews from [REVIEW TOOL] for [WINDOW] into themes with quotes and a product-fix note. You still change the store: you edit the listing or the product.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Cluster 1-star reviews in [REVIEW TOOL] for [WINDOW]. Themes, quotes, product-fix note. Do not edit listings. Sources: [REVIEW TOOL], [PDP], [RETURNS QUEUE IF RELATED]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit live listings or prices. - Do not email unhappy reviewers. - Do not issue refunds from a review theme. Deliverable: Theme, quote, count, draft listing or product fix (unpublished). Review point: I change the store.
Pro tip: Quotes required. Themes without quotes invent a defect.
Spam review suspects
8/21✨ What it does
The Bot flags reviews in [REVIEW TOOL] that look like spam or a brigade under [RULES] and drafts a report note. You still change the store: you report or remove reviews yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag reviews in [REVIEW TOOL] that match [RULES] for spam or a brigade. Draft a report note. Do not remove or report. Sources: [REVIEW TOOL], [RULES], order history if the tool shows a verified badge. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not remove, hide, or report reviews. - Do not email the reviewer. - Do not change star display on the PDP. Deliverable: Review, why it matches the rule, draft report note. Review point: I change the store.
Pro tip: Write the rules. Without them, every 1-star from a new account is "spam".
Draft public review replies
9/21✨ What it does
The Bot drafts a public reply for each review you mark in [QUEUE], in the voice of [EXAMPLES], and leaves it unpublished. You still change the store: you post or skip each reply.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a public reply for each review in [QUEUE] in the voice of [EXAMPLES]. Leave unpublished. Do not post or email the reviewer. Sources: [QUEUE], [EXAMPLES], [REPLY POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not post replies. - Do not email customers. - Do not offer a refund or discount in the draft unless [POLICY] says to draft one for me to send. Deliverable: Review permalink, draft reply, what you assumed. Review point: I change the store.
Pro tip: Attach two replies you already posted. Otherwise it writes corporate apology.
Order exceptions
4 promptsUnfulfilled older than N hours
10/21✨ What it does
The Bot lists orders in [OMS] older than [N] hours that are still unfulfilled, with a reason if the admin shows one. You still change the store: you fulfill, hold, or cancel.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List orders in [OMS] older than [N] hours and still unfulfilled. Include the admin reason if shown. Do not fulfill, hold, or cancel. Sources: [OMS], [SLA], [WAREHOUSE NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not fulfill, hold, or cancel orders. - Do not email customers about the delay. - Do not refund. Deliverable: Order, age, reason or unknown, suggested next step (unpublished). Review point: I change the store.
Pro tip: Cap the list. A 400-row dump is not a morning pack.
Address and risk flags
11/21✨ What it does
The Bot flags orders in [OMS] that trip [RISK RULES] such as AVS fail, new email, or high qty, and drafts a hold note. You still change the store: you hold, release, or cancel the order.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Flag orders in [OMS] that trip [RISK RULES]. Draft a hold note. Do not hold, release, cancel, or refund. Sources: [OMS], [RISK RULES], payment AVS if visible. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not hold, release, or cancel orders. - Do not refund. - Do not email the customer about a risk hold. Deliverable: Order, which rule tripped, evidence, draft hold note. Review point: I change the store.
Pro tip: Write the rules. A Bot that "feels fraud" will hold good orders.
Return request pack, no refund
12/21✨ What it does
The Bot builds a return pack for [ORDER] from [OMS] and [RETURNS QUEUE]: items, photos, policy fit, and a draft customer note. You still change the store: you approve the return and issue any refund.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a return pack for [ORDER]: items, photos, policy fit, draft customer note. Do not approve the return, refund, or email the customer. Sources: [ORDER], [OMS], [RETURNS QUEUE], [RETURN POLICY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not approve or deny the return. - Do not issue a refund or store credit. - Do not email the customer. Deliverable: Items, photos, policy fit, draft note unpublished. Review point: I change the store.
Pro tip: Policy fit is yes, no, or ask-me. Do not invent a restocking fee.
Split-shipment exceptions
13/21✨ What it does
The Bot finds split or partial shipments in [OMS] for [WINDOW] that still have open lines and drafts a next-step note. You still change the store: you ship the rest or edit the order.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find split or partial shipments in [OMS] for [WINDOW] with open lines. Draft a next-step note. Do not ship, edit, or email. Sources: [OMS], [CARRIER IF VISIBLE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create shipments or edit orders. - Do not refund the missing line. - Do not email the customer a tracking update. Deliverable: Order, shipped vs open, draft next step. Review point: I change the store.
Pro tip: Open lines only. Closed splits are noise.
Like these prompts? There are full tutorials behind them.
Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.
Merchandising drafts
4 promptsCollection merchandising draft
14/21✨ What it does
The Bot drafts a new sort and featured set for [COLLECTION] from [SALES + INVENTORY] and leaves the plan unpublished. You still change the store: you apply the sort and publish the collection.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a new sort and featured set for [COLLECTION] from [SALES + INVENTORY]. Do not apply the sort or publish. Sources: [COLLECTION], [SALES], [INVENTORY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change live collections or sort order. - Do not change live prices. - Do not publish merchandising. Deliverable: Current vs proposed sort, featured SKUs, stock check. Review point: I change the store.
Pro tip: In-stock first unless you say otherwise. Featuring a stockout is a tax on ads.
PDP copy draft, unpublished
15/21✨ What it does
The Bot writes unpublished title, bullets, and FAQ for [SKU] from [BRIEF] and [VOICE], and does not edit the live PDP. You still change the store: you paste and publish the copy.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write unpublished title, bullets, and FAQ for [SKU] from [BRIEF] and [VOICE]. Do not edit the live PDP. Sources: [SKU], [BRIEF], [VOICE], [CLAIMS WE CAN MAKE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit live PDPs or titles. - Do not change live prices. - Do not publish or schedule the copy. Deliverable: Draft title, bullets, FAQ, claims flagged. Review point: I change the store.
Pro tip: This is store copy, not a blog or ad. Keep claims inside [CLAIMS WE CAN MAKE].
Cross-sell and bundle suggestions
16/21✨ What it does
The Bot suggests bundles and cross-sells for [SKU LIST] from [ORDER HISTORY] and drafts the merchandising note. You still change the store: you create the bundle and set the live price.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Suggest bundles and cross-sells for [SKU LIST] from [ORDER HISTORY]. Draft the merchandising note. Do not create bundles or set prices. Sources: [SKU LIST], [ORDER HISTORY], [INVENTORY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create bundles or change live prices. - Do not edit PDPs. - Do not email past buyers a bundle offer. Deliverable: Parent SKU, suggested add-ons, evidence, draft price for me. Review point: I change the store.
Pro tip: Attach attach-rate or order history. Vibes-only bundles sit in the cart and die.
Promo calendar draft, no live price
17/21✨ What it does
The Bot drafts a [N]-day promo calendar for [COLLECTION] with suggested prices from [PRICE RULES], and does not change live prices. You still change the store: you schedule the sale yourself.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a [N]-day promo calendar for [COLLECTION] using [PRICE RULES]. Do not change live prices or schedule the sale. Sources: [COLLECTION], [PRICE RULES], [INVENTORY], [LAUNCH DATES IF ANY]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change live prices. - Do not schedule or publish a sale. - Do not email the list a promo. Deliverable: Day, SKU, suggested price, rule cite, stock check. Review point: I change the store.
Pro tip: Every suggested price needs the rule it came from. No invented discounts.
Make the store Bot durable
4 promptsStore Bot description
18/21✨ What it does
The Bot writes a description for a store Bot named [NAME] covering inventory, reviews, orders, merchandising, and a never-do list. You still change the store: you create the Bot and keep live edits yours.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a store Bot description named [NAME]. Inventory, reviews, orders, merchandising. Never refund, change live prices, or email customers. Sources: [STORE ADMIN], [REVIEW TOOL], [OMS], [REVIEW TIME]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Never refund, change live prices, or email customers. - Never fulfill, cancel, or publish merchandising. Deliverable: Description, weekly pack format, never-do list. Review point: I create it.
Pro tip: Write the store admin and the never-do list in the description before the first routine.
What ecommerce Bots never do
19/21✨ What it does
The Bot writes a never-do list for store Bots using your rules in [POLICY], covering refunds, live prices, and customer email. You still change the store: you paste the list and keep all live clicks.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write the never-do list for store Bots from [POLICY]. Must include refund, live price, and customer email. Sources: [POLICY], my rules. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not apply the list to a live Bot without me. - Do not refund, change live prices, or email customers while writing this. Deliverable: 12 never-do items, including refund, live price, customer email. Review point: I paste it.
Pro tip: Paste this before you hand it Shopify. A taught skill that includes Refund is how the wrong order gets money back at 2am.
Morning store pulse
20/21✨ What it does
The Bot prepares a weekday pulse at [08:00] [TZ] covering stockouts, review spikes, and order exceptions from [STORE TOOLS]. You still change the store: you enable the routine and make the live edits.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekday pulse at [08:00] [TZ]: stockouts, review spikes, order exceptions from [STORE TOOLS]. Do not change the store or Slack it. Sources: [STORE TOOLS]. If admin is down, fail closed. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change stock, prices, or orders. - Do not refund or email customers. - Do not send the pulse to Slack. Deliverable: Routine card and pulse format. Review point: I enable.
Pro tip: Cap it. If the store is quiet, three lines. Fail closed if admin is down.
Handoff to support or ads
21/21✨ What it does
The Bot turns this week's store flags into ticket or brief drafts for [SUPPORT / ADS] with links from [STORE]. You still change the store: you file the tickets and you change live listings.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn this week's store flags into ticket or brief drafts for [SUPPORT / ADS] with links from [STORE]. Do not file them or change listings. Sources: This week's inventory, review, and order packs. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not file tickets until I pick. - Do not change live listings or prices. - Do not email customers or change campaigns. Deliverable: Ticket or brief drafts with admin links, split support vs ads. Review point: I file. I change the store.
Pro tip: Ads get stockouts and PDP mismatches. Support gets delayed orders and review themes. Do not mix the packs.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides