Back to cookbook

AI Prompt to Audit Shopify Inventory and Listings via MCP

0 views Updated

Make this prompt yours

Share

This is a prompt for Shopify store owners using Shopify's Admin MCP server, which connects your store's product, inventory, and order data directly to Claude, ChatGPT, Cursor, and other MCP-compatible AI tools. Instead of clicking through the Shopify admin panel product by product, you can ask the connected AI to pull your actual catalog and flag real problems β€” low stock, mismatched variants, missing metafields, inconsistent tagging β€” in one pass.

The prompt works by having the AI treat your store data like a dataset: it checks specific, named conditions (stock below a threshold, products missing required fields, tags that don't follow your naming convention) instead of giving a vague summary. This makes the output something you can act on directly, not just a general health check.

Because the Admin MCP server exposes real store data through named tools (product, inventory, and order operations), the audit reflects your actual catalog at the time you run it β€” not a cached or approximate view.

Prompt template

Make this prompt yours

prompt-template
130 tokens
Using the Shopify Admin MCP connection to my store, run a catalog audit with these checks: 1. Flag any product with inventory below [STOCK THRESHOLD] units. 2. Flag any product missing [REQUIRED FIELD(S), e.g. description, product type, metafield name]. 3. Flag any product whose tags don't follow this convention: [YOUR TAGGING RULE]. 4. Flag any product with variants that have mismatched or missing pricing. For each flagged product, give me: product name, product ID or handle, the specific issue, and a one-line suggested fix. Group the results by issue type, not by product.

Want it sharper? Optimize this prompt with Prompt Optimizer, check it with the Prompt Debugger or shorten it with the Token Optimizer.

Example input

example-input
137 tokens
Using the Shopify Admin MCP connection to my store, run a catalog audit with these checks: 1. Flag any product with inventory below 10 units. 2. Flag any product missing a product description or missing the "material" metafield. 3. Flag any product whose tags don't follow this convention: all tags lowercase, hyphenated, no spaces (e.g. "summer-collection" not "Summer Collection"). 4. Flag any product with variants that have mismatched or missing pricing. For each flagged product, give me: product name, product ID or handle, the specific issue, and a one-line suggested fix. Group the results by issue type, not by product.

Example output

example-output
223 tokens

Low stock (below 10 units):

  • Linen Button-Up Shirt (handle: linen-button-up) β€” 4 units left. Suggested fix: reorder or mark as low-stock on the listing.
  • Canvas Tote Bag (handle: canvas-tote) β€” 7 units left. Suggested fix: reorder before next promotion.

Missing required fields:

  • Wool Scarf (handle: wool-scarf) β€” missing "material" metafield. Suggested fix: add metafield value "100% wool."
  • Leather Belt (handle: leather-belt) β€” missing product description. Suggested fix: add a description before the next catalog sync.

Tagging inconsistencies:

  • Summer Dress (handle: summer-dress-01) β€” tagged "Summer Collection" instead of "summer-collection." Suggested fix: update tag to match convention.

Pricing mismatches:

  • Ceramic Mug Set (handle: ceramic-mug-set) β€” Small variant priced at $18, Large variant priced at $0 (likely unset). Suggested fix: set a price for the Large variant before it goes live.

When to use it

  • You manage a Shopify catalog with enough products that manual review in the admin panel is slow
  • You want a regular health check for low stock, missing fields, or inconsistent tagging before a sales push
  • You're cleaning up a catalog after a bulk import and need to find what broke or was left incomplete
  • You want the audit findings in a format you can hand to a team member to fix, not just a vague summary

Best practices

  • Set explicit thresholds (like "flag anything under 10 units in stock") instead of asking the AI to judge what counts as low
  • Ask for the audit grouped by issue type (stock, missing fields, tagging) so it's easy to assign and fix
  • Run this after bulk imports or seasonal catalog changes, when manual errors are most likely to have crept in
  • Have the AI output product IDs or handles alongside each flagged issue so you can locate them quickly in the admin panel

Common mistakes

  • Asking for a general "how's my store looking" review instead of specific, checkable conditions β€” vague prompts produce vague audits
  • Not specifying your store's tagging or naming conventions, so the AI can't tell what actually counts as inconsistent
  • Treating the audit as a one-time task instead of running it periodically, especially after imports or supplier changes
  • Skipping product IDs or handles in the output, which makes acting on the findings slower than it needs to be

FAQs

Does this require Shopify's Admin MCP server specifically, or does the Storefront MCP work too?

This audit needs the Admin MCP server, since it requires access to inventory counts, metafields, and pricing data. The Storefront MCP is built for customer-facing product discovery and doesn't expose this level of store management data.

Do I need to set up API credentials for this to work?

Yes β€” unlike Shopify's zero-setup Storefront MCP, the Admin MCP server requires configuring API credentials for your store before an AI tool can access product, inventory, and order data.

Which AI tools can connect to Shopify's Admin MCP server?

Shopify's MCP servers are documented to work with Claude, ChatGPT, Cursor, Perplexity, and Microsoft Copilot, among other MCP-compatible clients.

Can the AI fix these issues automatically once it finds them?

This prompt is written to only report findings, not make changes. If you want the AI to apply fixes (like updating a tag or metafield), say so explicitly and review each change before confirming it.

How often should I run this audit?

It's most useful after bulk imports, supplier catalog updates, or before a seasonal sales push, when manual data entry errors are most likely to have been introduced.

Found this prompt useful? Share it.

Share

More in Data Analysis

Data Analysis

AI Prompt to Segment Customer Data Into Meaningful Groups

This AI prompt for customer segmentation takes a description of your customer dataset and asks the model to propose meaningful groups based…

ROLE
You are a data analyst helping design a customer segmentation scheme.

CONTEXT
Business type: [BUSINESS_TYPE, e.g. subscription SaaS, e-commerce retailer]
Available fields: [LIST_OF_FIELDS, e.g. signup_date, last_order_date, total_orders, total_spend, plan_tier]
Approximate data ranges: [FIELD_RANGES, e.g. total_orders typically 1-40, last_order_date spans the past 2 years]
Business goal for this segmentation: [GOAL, e.g. identify customers to target for a win-back campaign]

TASK
Propose 4-6 customer segments that serve the stated goal. For each segment, provide:
1. A clear, specific name.
2. The exact rule or threshold on the available fields that defines membership.
3. A one-sentence description of what distinguishes this group.
4. One recommended action specific to this segment.

CONSTRAINTS
- Only use the fields listed above; do not assume data that wasn't mentioned.
- Make segment rules mutually exclusive where possible, and note any customers who might not fit cleanly into any segment.
- Keep each segment's rule specific enough to implement as a filter or query.

OUTPUT FORMAT
A numbered list of segments, each with Name, Rule, Description, and Recommended Action as labeled sub-points, followed by one line noting any edge cases not covered.

Make this prompt yours

Data Analysis

JSON Data Extraction Pipeline

This prompt converts messy, unstructured text (emails, articles, transcripts) into a predictable JSON array that your code can parse without…

Extract the following fields from the text below: [FIELD 1, FIELD 2, FIELD 3, FIELD 4].

Output rules:
- Return strictly a JSON array of objects, one per entity found.
- Use exactly these keys: [key_1, key_2, key_3, key_4].
- If a value is missing or unclear, use null. Never guess.
- Do not wrap the output in markdown code fences.
- Do not add any explanation before or after the JSON.

Text:
"""
[PASTE TEXT]
"""

Make this prompt yours

Data Analysis

AI Prompt to Clean and Standardize a Messy Spreadsheet Dataset

This is a data cleaning prompt for turning a messy spreadsheet or CSV export into a consistent, analysis ready dataset β€” built for analysts,…

ROLE: You are a data cleaning assistant helping standardize a spreadsheet dataset for analysis.

CONTEXT: Below is a sample of the dataset. Columns are: [LIST OF COLUMN NAMES]

[PASTE SAMPLE DATA HERE, INCLUDING KNOWN PROBLEM ROWS]

TASK:
1. Review each column and identify formatting inconsistencies (e.g. date formats, capitalization, whitespace, abbreviations, units)
2. Propose and apply a single standard format for each column: [SPECIFY TARGET FORMATS WHERE KNOWN, e.g. dates as YYYY-MM-DD]
3. Flag rows that look like duplicates or outliers, but do not delete them β€” mark them for my review instead
4. Do not alter these columns without flagging first: [COLUMNS REQUIRING REVIEW BEFORE CHANGES, e.g. customer name, ID numbers]

CONSTRAINTS:
- Preserve every original row unless I confirm a deletion
- Do not invent or infer missing values β€” leave them blank and flag them
- [ANY ADDITIONAL CONSTRAINT, e.g. keep a specific column's original casing]

OUTPUT FORMAT:
1. The cleaned dataset as a table
2. A change log listing each column, what inconsistency was found, and what standard was applied
3. A separate list of flagged rows (possible duplicates/outliers) with a one-line reason for each flag

Make this prompt yours