Playbooks
Operator Loops
Operator Loops turn one-off prompts into repeatable operating rituals. ShopMCP supplies the live commerce context, certified playbooks, action packet, and readback contract; Claude or ChatGPT can run the loop manually or on a supported schedule.
Think in loops, not prompts
A prompt asks for an answer once. A loop defines the operating rhythm: what runs, when it runs, what evidence is required, who owns the next action, and when the result should be checked again.
- Prompt:
What happened last week? - Playbook:
Run the Weekly Trading Deck once - Loop: Run that review every Monday, produce a trading deck and one owner-led action packet, then read it back next week.
- Deliverable: Trading deck → Action Packet → readback.
Scheduling belongs to the host AI
Public loop packs
These are the first loop packs ShopMCP exposes because they map cleanly to existing certified playbooks and action-packet contracts.
weekly
Weekly Trading Review
A weekly trading review that turns last week's sales, customer, channel, and payment signals into one owner-led follow-up for the week ahead.
Composition
Weekly Trading Deck (primary) · Monday Trading Update (when relevant) · Pace to Target (when relevant)
Why run it
Run it before the week starts so leadership is not reacting to disconnected dashboards. The loop picks the highest-confidence issue, labels missing evidence, and sets a readback date.
Required integrations
Commerce platform, Ad platform, GA4, Klaviyo, Stripe, Google Search Console
weekly
Paid Growth Risk Loop
A weekly paid-media risk review that turns spend waste, creative fatigue, and account anomalies into a KILL, REFRESH, or WATCH queue.
Composition
Wasted Spend Killer (primary) · Creative Fatigue Board (when relevant) · Performance Anomaly Watch (when relevant)
Why run it
Run it before budget changes so the team can separate real waste from learning-phase noise, weak tracking, or missing commerce context.
Required integrations
Ad platform
weekly
Agency Client Risk Loop
A weekly client-risk triage that ranks the client or workspace needing attention and packages the evidence into an AM-owned next step.
Composition
Agency Client Health Score (primary) · Agency Portfolio Monday Digest (when relevant) · Agency Ad-Account Risk Watch (when relevant)
Why run it
Run it before Monday planning so the agency starts with the client risk that has evidence, not the loudest Slack thread or latest dashboard panic.
Required integrations
Commerce platform, Ad platform
weekly
Cin7 Buying and Replenishment
An operator review of buying and replenishment that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Buying and Replenishment (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
daily
Cin7 Receiving and Put-away
An operator review of receiving and put-away that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Receiving and Put-away (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
daily
Cin7 Warehouse and Stock Control
An operator review of warehouse and stock control that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Warehouse and Stock Control (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
daily
Cin7 Fulfilment and Dispatch
An operator review of fulfilment and dispatch that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Fulfilment and Dispatch (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
triggered
Cin7 Sales and Customer Service
An operator review of sales and customer service that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Sales and Customer Service (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
weekly
Cin7 Catalog and Master Data
An operator review of catalog and master data that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Catalog and Master Data (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
monthly
Cin7 Finance and Reconciliation
An operator review of finance and reconciliation that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Finance and Reconciliation (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
triggered
Cin7 Production and Assembly
An operator review of production and assembly that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Production and Assembly (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
triggered
Cin7 CRM and Relationship Operations
An operator review of crm and relationship operations that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 CRM and Relationship Operations (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
triggered
Cin7 Administration and Integration Control
An operator review of administration and integration control that turns current evidence into an exact proposal or manual handoff.
Composition
Cin7 Administration and Integration Control (primary)
Why run it
Catch exceptions before they become rework, keep a named owner on each decision and prove the resulting state before reviewing the later operating outcome.
Required integrations
Cin7 Core
How to schedule a loop
Run the loop manually once before saving the schedule. Keep the write boundary in the prompt so scheduled runs produce an evidence-backed action packet instead of making consequential changes.
ChatGPT setup
- Open ChatGPT on web or mobile and confirm ShopMCP is connected in the workspace you want to use.
- Open Scheduled from the sidebar, then create a new task. You can also paste the prompt into ChatGPT and ask it to create the task.
- Set the schedule to every Monday at 8:00am in the store or operator timezone.
- Enable the notification channel you actually check, then run the loop manually once to confirm the output includes evidence, owner, approval posture, and readback date.
textEvery Monday at 8am, run the Weekly Trading Review using ShopMCP. Review last week's trading performance and return a trading deck, one action packet with evidence, owner, approval posture, and next readback date. Do not make platform changes.
Claude Cowork setup
- Open Claude Desktop, switch to Cowork, and confirm ShopMCP is available in Cowork.
- Create a new Cowork task, paste the loop prompt, and run it once.
- Type /schedule in that Cowork task, or open Scheduled in the left sidebar and choose + New task.
- Set the schedule to weekly on Monday at 8:00am, then confirm the scheduled task when Claude asks.
textSchedule a weekly Monday 8am task: run ShopMCP's Weekly Trading Review. Use the connected commerce source as truth, add GA4/ads/lifecycle/search/payment context only when available, and finish with a trading deck, one owner-led action packet, and the readback date. Do not perform writes.
Loops by persona
Personas tune the cadence and defaults. The real unit of value is the situation: trading review, paid-risk queue, client-risk review.
Founder / CEO
Keep the business on plan without drowning in channel dashboards.
- Weekly Trading Review - Are we on plan, what changed, and what deserves an owner this week?
Next loop ideas
Pace-to-target check, Margin and cash risk review, Founder anomaly watch
Head of Ecommerce
Turn trading, funnel, launch, tracking and Cin7 finance/control signals into owned work.
- Weekly Trading Review - Are we on plan, what changed, and what deserves an owner this week?
- Cin7 Finance and Reconciliation - Which finance exceptions have enough evidence for the responsible operator's next decision?
- Cin7 Administration and Integration Control - Which admin exceptions have enough evidence for the responsible operator's next decision?
Next loop ideas
Checkout health loop, Launch monitor, Funnel leak review
Marketing Lead
Connect commercial outcomes to campaign, creative, offer, and lifecycle decisions.
- Paid Growth Risk Loop - Where are we wasting money, what needs refreshing, and what should not be touched because the data is weak?
Next loop ideas
Creative brief from winners, Offer threshold loop, Launch readiness loop
Performance Marketer
Run paid-media risk, pacing, wasted-spend, and anomaly checks on a predictable cadence.
- Paid Growth Risk Loop - Where are we wasting money, what needs refreshing, and what should not be touched because the data is weak?
Next loop ideas
Daily performance dashboard, PMax deep dive, Tracking health loop
Email / Retention Lead
Watch flow health, deliverability, campaign value, and customer-quality movement.
No public default loop yet. Use the next-loop ideas below as the operating cadence.
Next loop ideas
Monday retention recap, Flow health loop, Deliverability watch, VIP and replenishment loop
SEO / Content Lead
Make organic growth operational with traffic pulse, quick wins, decay, and schema checks.
No public default loop yet. Use the next-loop ideas below as the operating cadence.
Next loop ideas
Monday organic pulse, Quick-win keyword loop, Content decay loop, AI-search visibility loop
Merchandiser
Keep feed, stock, product, category, and price issues from silently leaking revenue.
- Cin7 Catalog and Master Data - Which catalog exceptions have enough evidence for the responsible operator's next decision?
Next loop ideas
GMC feed rescue, Stock cash tied up, Dead stock watch, Price competitiveness loop
Operations / Support
Catch purchasing, warehouse, fulfilment, production and service-quality risks before they reach customers.
- Cin7 Buying and Replenishment - Which buying exceptions have enough evidence for the responsible operator's next decision?
- Cin7 Receiving and Put-away - Which receiving exceptions have enough evidence for the responsible operator's next decision?
- Cin7 Warehouse and Stock Control - Which warehouse exceptions have enough evidence for the responsible operator's next decision?
- Cin7 Fulfilment and Dispatch - Which dispatch exceptions have enough evidence for the responsible operator's next decision?
- Cin7 Sales and Customer Service - Which support exceptions have enough evidence for the responsible operator's next decision?
- Cin7 Production and Assembly - Which production exceptions have enough evidence for the responsible operator's next decision?
- Cin7 CRM and Relationship Operations - Which crm exceptions have enough evidence for the responsible operator's next decision?
Next loop ideas
Daily ops standup, WISMO risk loop, Dispute evidence loop, Returns quality review
Agency AM / COO
Rank client risk, prep owner actions, and keep follow-through visible across the portfolio.
- Agency Client Risk Loop - Which client needs action, what is the evidence, and what should the AM or strategist do next?
Next loop ideas
Portfolio Monday digest, Client health score, Paid media triage, Retention intelligence packet
What ShopMCP adds
- Certified playbook routing instead of loose prompt memory.
- Connected commerce, ads, lifecycle, search, payment, and feed evidence where available.
- Action packets with owner, evidence, approval posture, and write target.
- Readback fields so a loop checks whether the action worked.
- Fail-closed caveats when data, permissions, or connected-platform coverage are weak.
To browse the loop library inside the app, open Playbooks and choose Loops.