agentos.guide › blog

Grok Bot For Ecommerce: Five Copy-Paste Prompts For Rival Checks, Listings, Order Mail And Supply Reorders In Your Agent OS

By Julian Goldie · 7 November 2026 · agentos.guide

Grok Bot for ecommerce slots into an Agent OS as the store's legs: your agent plans the week and writes the briefs, and Grok Bot opens the shop dashboard, rival sites and the order inbox on its cloud computer.

This guide gives you a quick start, five prompts to paste and a weekly rhythm for a small online shop.

The facts come from xAI's computer and apps docs, the Vault docs, the routines docs and the Grok Bot changelog.

It's written for the shop owner; personal buying lives in our Grok Bot shopping guide.

Want a hand fitting this to your own shop? Book a free SEO strategy session with my team.

Quick start: five settings before the first store task

1. Check access: Grok Bot is part of Premium, Super and Ultra on The X Subscription, not Plus (plan page).
2. Connect Gmail and Google Sheets from Connect apps.
3. Save the shop dashboard login in Settings → Vault so the Bot can sign in without ever seeing the password.
4. Claim the Bots' address at mail.grokbot.com; you only get one and it can't be renamed, so pick it with care.
5. Add Ask first rules for customer email, product edits, refunds and payments.

There's no documented Shopify or other store-platform connector, so the Bot uses the browser for your dashboard.

Who plans, who clicks

Your Agent OS holds the shop's memory: the range, the tone of voice, the suppliers and the returns policy.

Grok Bot does the browser work and keeps it going in the cloud with the laptop lid shut.

Every Bot on your account uses one shared cloud computer, hosted in Cursor's cloud, and each Bot works on a screen of its own there.

The handover point is always a file or a sheet: the Bot writes it, your Agent OS reads it, and you sign off.

That way neither side needs the other's logins, and every decision leaves a record you can check later.

Prompt 1: give the store Bot its job

Paste this into a new Bot chat so it learns the role and the limits.

You are Shop Ops for [shop name], an online shop selling [range].
Your jobs: rival checks, listing drafts, order mail drafts and
supply reorders. Sources: the shop dashboard (browser, Vault login),
Gmail, and the "Shop Ops" Google Sheet.
Never: change products or prices, send email, issue refunds or pay
for anything without my approval card.
If a page won't load, say so. Don't guess numbers.
Remember this job and these limits.

xAI's use cases page suggests exactly this: tell the Bot its job and limits in chat and ask it to remember them.

🔥 Want the full Shop Ops prompt pack?

The AI Profit Boardroom gives you step-by-step video trainings, the installable Agent OS, four coaching calls a week and 3,400+ members sharing the prompts they run on their own shops.

→ Join the AI Profit Boardroom

Prompt 2: the Monday rival check

Every Monday at 8:00 AM, open the rival product pages listed in
the "Rivals" tab. Add one row per page: date, shop, product,
listed price, stock status, any new product, link.
Open each page fresh; don't rely on memory for prices.
Write "not loaded" if a page fails. Don't touch our shop.
Post a three-line summary here.

Example: a soap maker tracks three rival shops selling goat's milk bars.

After saving, open the routine, check When to run and the timezone, then press Test, because a new routine waits for its next slot.

Prompt 3: listings from supplier files

Using only the attached spec sheet and photos, draft for each
product: a title, a short description and five bullets in our
tone (see brand doc). List any claim the files don't support.
Return a Google Doc. Don't edit the shop.

Example: a yarn shop attaches a mill's fibre sheet and colour cards for a new range.

The Bot reads PDFs, spreadsheets and images per the files and results docs.

When the doc comes back right, ask the Bot to save the method as a skill so every Bot can reuse it.

Prompt 4: order mail on an alias

Set up a routine on [address]+orders@mail.grokbot.com, only for
mail from [store notification domain] and customers who reply to it.
Label each message: order status, return, product question, other.
For order status, check the order in the shop dashboard and
draft a reply from the reply templates. Draft only.

Plus aliases land in the same inbox, and a routine on an alias only runs for mail sent to it.

Keep a sender filter on, because anyone can write to an alias.

Routine email waits as a draft until you press Send, and the Bot treats instructions inside other people's emails as information only.

Prompt 5: reorder supplies with approval

We're low on [item]. Find three options from suppliers we can
buy from, shown as product cards. Recommend one with a reason.
When I pick, use Buy now and wait for my approval. Then track
the order and tell me when it ships and when it arrives.

Product cards, Buy now and order tracking come from v0.78.1 on 27 October 2026 in the changelog; the docs pages don't cover them yet.

The same release lets you connect Shop Pay in the Vault's Payments tab, while the Vault docs list Link or X Money as payment accounts.

Mind the card: a card saved in Vault fills at checkout with no prompt, so leave it unsaved or use a one-time Link card if you want to approve every payment.

The steps only you can do

Some sign-ins can't be filled by a form: a passkey, single sign-on, a code sent to another device, a QR code or a CAPTCHA the Bot can't clear.

For those, the Bot hands you its computer.

Choose Take over on the request, finish only that step, choose I'm done, and tell the Bot to carry on.

The signed-in session then stays on the computer for later tasks, and your other Bots can use it too.

That's handy for a shop dashboard, and it's also why a Bot you don't fully trust shouldn't sit on the same account.

If the dashboard keeps timing you out, tell the Bot to pause and ping you rather than trying to get round the check.

Split the shop across three Bots

Once Prompts 2 to 5 run cleanly, one Bot starts to juggle too much.

xAI's use cases page shows teams such as a Campaign team and a Support queue, where each Bot owns one part and passes work along.

For a shop, try this split:

1. Rivals: owns Prompt 2 and nothing else.
2. Counter: owns Prompt 4 and the order replies.
3. Stockroom: owns Prompts 3 and 5, listings and supplies.

Each Bot has its own screen on the shared computer, so all three can browse in parallel.

Private skills are one library across your Bots, so the dashboard skill you saved once serves all three.

Ask your primary Bot to set the team up, or start from dr eggbot, which asks a few questions and creates one Bot per job.

Keep usage in mind: every routine run counts, so give Rivals a weekly slot, not an hourly one.

The weekly shop rhythm

1. Monday: Prompt 2 runs; your Agent OS reads the sheet and notes any price moves worth answering.
2. Daily: Prompt 4 drafts order replies; you send them.
3. When stock dips: Prompt 5 brings options; you approve one.
4. New stock: Prompt 3 drafts listings; you publish.
5. Friday: ask Grok Bot for a page with the week's orders, refunds and low-stock items, if Pages is live on your account.

Pages is still rolling out and isn't on Enterprise teams yet, so a Google Sheet works as the fallback.

📞 Want my team to look at your shop?

Book a free SEO strategy session and we'll review your shop's search traffic and which of these jobs are worth handing over.

→ Book the free strategy session

Guardrails your Agent OS should write into every brief

• One job per Bot, with the job and the limits saved to memory.
• "Draft only" on anything going to a customer or supplier.
• A no-data rule: report missing pages instead of reusing old numbers.
• Answer approval cards quickly: those raised by a routine expire after 30 minutes.
• Remember that sign-ins are shared, so a shop session opened for one Bot is open for all of them.
• Re-test a skill after your dashboard or a rival's site changes layout.

The Boardroom classroom walks through each guardrail on screen.

FAQ

Which prompt should I paste first?

Prompt 1, so the Bot remembers its shop job and its limits. Then run Prompt 2 once in chat before you schedule it.

Can Grok Bot edit my shop listings directly?

It can work in your dashboard through the browser, but keep product edits behind an Ask first rule and paste listings yourself at first.

Why use an alias for order mail?

A routine on an alias only runs for mail sent to that alias, so order mail stays separate from receipts and reports in the same inbox.

Does my Agent OS need its own copy of the shop login?

No. Keep the login in Grok Bot's Vault, where it fills straight into the page, and let your Agent OS work from the sheets and reports.

Final word on Grok Bot For Ecommerce

Paste Prompt 1 today, test Prompt 2 on Monday, and join the AI Profit Boardroom to run Grok Bot for ecommerce in your Agent OS.

Related guides on agentos.guide

→ Grok Bot Shopping In Your Agent OS: A Quick Start, 5 Copy-Paste Prompts And A Weekly Buying Workflow

→ Grok Bot For Business: Write The Approval Rules, Inbox Wiring And Team Setup With 5 Prompts In Your Agent OS

→ Grok Bot AI Full Course (Step By Step)

→ The Ghost Team

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide