download dots
AI PromptsCategoriesRetail

📕 Keep a Product Catalog That Stays Right

Run the shop from one place, including the second and third one. These prompts build the working parts of a retail business: stock that is right across every location, purchase orders that arrive before you run out, gift cards and loyalty, staff rotas, and the numbers you should see every morning.
  • Tested prompts
  • Edit for your use case
  • Works across models
  • Save in Taskade
Keep a Product Catalog That Stays Right

Copy

My product information is in a spreadsheet, my website and my till, and all three disagree. Build me a product catalog app. Keep one record per product with SKU, name, description, category, brand, supplier, cost price, retail price, tax treatment, barcode, images and status. Handle variants such as size or color as variants of one product rather than as unrelated products, each with its own SKU, barcode and stock. Set which fields are required before a product can be marked ready to publish, so incomplete records cannot escape. Add an AI agent that reviews the catalog for incomplete records, likely duplicates, products priced below cost, and descriptions that are missing or too thin to sell with, and that can draft a description from the product attributes. Automate a scheduled weekly catalog health report and an alert when a product is saved with a price below its cost. Two logins: a merchandiser who edits products, and an owner who sets prices and approves publishing.

Run this prompt with AI
STATUS · LIVE
v1

01 / Spark - intelligence awakens

Keep a Product Catalog That Stays Right

Hold one authoritative record per product with variants, images, pricing, and completeness checks before publishing.

Start with AI
// the spark catches · intelligence awakens · the answer unfolds

When product information lives in four places it is wrong in at least two. This holds one record per product and lets everything else read from it.

What's Included

  • One record per product with every attribute in one place.
  • Variants handled properly rather than as separate unrelated products.
  • Images and descriptions held with the product, not in a folder.
  • An assistant that finds incomplete or duplicated records.

How To Use

  1. Keep one record per product and let everything read from it.
  2. Model variants as variants. Separate products break stock and reporting.
  3. Set required fields so an incomplete product cannot be published.
  4. Audit for duplicates regularly. They arrive faster than you expect.

Sell it through ecommerce prompts, and count it with multi-store inventory.

Discover more

More Retail Operations Prompts

View all Retail Operations Prompts