P
AI for Retail Buyer

Claude Project: Build a Category Knowledge Base

Claude

For Retail Buyers

Tools: Claude {{tool:Claude.plan}} | Time to build: 1-2 hours | Difficulty: Intermediate-Advanced Prerequisites: Comfortable using Claude for sales reports and competitive research. see Level 3 guides

What This Builds

A persistent Claude Project that functions as your category's institutional knowledge repository. pre-loaded with vendor intelligence, seasonal strategy, competitive positioning, and buying philosophy. It works as a thinking partner for strategic decisions and as an onboarding accelerator for new team members.

Prerequisites

  • {{tool:Claude.plan}} subscription ({{tool:Claude.price}}). Projects require a paid plan
  • Documents to upload: vendor list, seasonal OTB plan, prior business reviews, category strategy notes
  • 1 hour to write the project instructions and upload documents
  • Optional: prior season trend briefs, competitor research notes

The Concept

A Claude Project maintains context and uploaded documents across all conversations, unlike regular chat where every session starts fresh. Think of it as a filing cabinet that Claude can actually read and reason about. You upload your category documents once; every future conversation references them automatically.

Build It Step by Step

Part 1: Gather your category documents

Before building the project, collect what you want Claude to know:

  • Vendor list with context: Names, volume, sell-through, relationship status (growing/maintaining/exiting), key contacts
  • Current seasonal OTB plan: Where the budget is allocated by category/subcategory/vendor
  • Prior season's business review: Performance, what worked, what didn't, strategic pivots
  • Competitive positioning notes: How you see yourselves vs. key competitors
  • Category strategy memo: If you've ever written down your buying philosophy, include it

De-identify financial data as needed per your company's information security policies.

Part 2: Create a new Claude Project

  1. Log into Claude at {{tool:Claude.url}} with your {{tool:Claude.plan}} account
  2. Click Projects in the left sidebar
  3. Click New Project
  4. Name it: "[Category] Buying Intelligence" (e.g., "Women's Accessories Buying Intelligence")

Part 3: Write your Project Instructions

In the Project Instructions area, write your category brief:

Copy and paste this
You are an AI buying assistant and strategic thinking partner for the [Category] buying team at [Retailer type].

YOUR CATEGORY KNOWLEDGE:
- Category: [Name and scope]
- Annual volume: approximately $[X]
- Key performance targets: [sell-through %, margin %, turn rate]
- Customer profile: [brief description]
- Brand positioning: [how we position vs. competitors]

HOW TO USE THIS PROJECT:
- Vendor evaluation: When I bring you vendor performance data or a new vendor pitch, help me evaluate fit, risks, and opportunity
- Negotiation prep: Help me build negotiation briefs using what you know about our vendor landscape
- Business review writing: When I give you performance data, help me write the narrative
- Strategic thinking: Help me think through category strategy questions, trend implications, or buy plan pivots
- Onboarding: New team members can use this project to get up to speed on the category

IMPORTANT LIMITATIONS:
- You don't have real-time data — verify any specific current figures against our ERP before acting
- When I haven't given you specific data, ask for it rather than inventing it
- My uploaded documents may become outdated — always defer to current data I provide over older documents

RESPONSE STYLE:
- Commercial and action-oriented (like a senior buyer, not a consultant)
- Specific over general — name vendors, price points, competitors when relevant
- Concise — buyers are time-pressed, get to the point

Part 4: Upload your category documents

In the Knowledge section, upload:

  • Your vendor list document
  • Current OTB plan (if permitted by company policy)
  • Prior business review(s)
  • Any competitive research you've compiled

What you should see: Documents listed in the Knowledge section with file names visible.

Part 5: Test with key scenarios

Open a conversation in the project and test 3 scenarios:

  1. Vendor evaluation: "Here's a pitch from a new vendor in the [subcategory] space: [brief description]. Based on what you know about our category, what should I look out for and what questions should I ask?"

  2. Strategy question: "I'm thinking about shifting 15% of my OTB from basics to trend-forward styles next season. What's the risk/reward based on what you know about our category?"

  3. New team member query: "I just joined as assistant buyer in this category. what's the most important context I should understand about our vendor landscape?"

Part 6: Invite team members

Go to Project settings → sharing → invite your assistant buyer or buying manager by email (they need their own {{tool:Claude.plan}} account). Each person has their own conversation thread within the shared project.

Real Example: Onboarding a New Assistant Buyer

Setup: Claude Project loaded with vendor list, current OTB plan, and last two seasons' business reviews.

New assistant buyer's first question: "I'm starting in the Women's Accessories category next Monday. What are the three most important things I should know about our vendor landscape?"

Claude's response: Draws from the uploaded vendor list to identify the highest-volume and highest-risk vendors, references the prior business review to explain recent strategic shifts, and flags the two vendors currently in performance review. providing 3 months of context in 2 minutes instead of the typical 2-week learning curve.

What this replaces: Hours of verbal onboarding, paging through old documents, asking the same questions of a senior buyer who's already overwhelmed.

What to Do When It Breaks

  • Claude doesn't seem to reference uploaded documents → Ask explicitly: "Based on the vendor list I uploaded, which vendors have the lowest sell-through?". direct document references prompt better recall
  • Project instructions feel too generic → Add more specific category details. the more concrete the category context, the more useful the outputs
  • Team members can't access the project → Confirm they have active {{tool:Claude.plan}} subscriptions; free accounts cannot join shared Projects
  • Documents are outdated → Upload updated versions; note in the Project Instructions "The uploaded documents are from [date]; for current data, I'll provide it in conversation"

Variations

  • Simpler version: Use Claude Projects just as a knowledge hub for your own use (skip team sharing). still valuable as a thinking partner with category context
  • Extended version: Create a separate "Questions and Decisions Log" conversation in the project where you document significant buying decisions and the reasoning. useful for personal reference and team transparency

What to Do Next

  • This week: Build the project with at least your vendor list and current strategy memo; test 3-4 queries
  • This month: Add your prior season business reviews; share with your assistant buyer
  • Advanced: Start logging significant buying decisions in the project. over time it becomes a rich record of category history and rationale

Advanced guide for retail buyer professionals. Requires {{tool:Claude.plan}} subscription at {{tool:Claude.price}}.