> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vulpy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Manage your catalog in Vulpy Commerce

> Create and organize products, categories, and editorial content across the Medusa admin and Payload CMS in your Vulpy Commerce shop.

Your catalog lives in two places in Vulpy Commerce. Medusa owns the commerce data (products, variants, inventory, pricing), and Payload owns the editorial content that dresses those products and categories on the storefront. This page shows where each surface lives and how to work in them.

<Tip>
  **The fastest way is to ask Fox.** Fox works in the same admins and can do the operational catalog work for you.

  * Create a new product called "Padel Racket X" in the Rackets category.
  * Add editorial hero blocks to the Summer category.
  * Seed the demo catalog.
</Tip>

## Where each surface lives

| Surface       | URL (local)                                                | Owns                                                                                                                     |
| ------------- | ---------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Medusa admin  | [http://localhost:9000/app](http://localhost:9000/app)     | Products, variants, inventory, pricing, categories, orders                                                               |
| Payload admin | [http://localhost:3000/admin](http://localhost:3000/admin) | `pages`, `productContent`, `categoryContent`, `posts`, `media`, plus `site-settings`, `navigation`, and `footer` globals |

<Note>
  Medusa is the source of truth for product identity. Payload `productContent` and `categoryContent` are synced from Medusa; `title`, `handle`, and `medusaCategoryId` are read-only in Payload. Editorial fields (blocks, `h1`, `seo`) are writable.
</Note>

## Create a product

<Steps>
  <Step title="Sign in to the Medusa admin">
    Open [http://localhost:9000/app](http://localhost:9000/app) and sign in with the shared admin credentials set at install (or reset them with `pnpm vulpy user reset`). Or just ask Fox to create the product for you.
  </Step>

  <Step title="Create the product">
    Go to **Products** and click **New product**. Set title, handle, description, and variants (size, color, price).
  </Step>

  <Step title="Assign categories">
    Attach the product to one or more categories. Categories flow to Payload as `categoryContent` for editorial dressing.
  </Step>

  <Step title="Publish and verify">
    Publish the product, then open the storefront at [http://localhost:3000](http://localhost:3000) to confirm it appears on the category and PDP.
  </Step>
</Steps>

<Tip>
  Medusa product and category admin widgets crosslink into Payload admin and the storefront, so you can jump straight from a Medusa product to its editorial page.
</Tip>

## Add editorial content on Pro

Pro adds Payload editorial for products and categories on top of Medusa. Use Payload to layer marketing blocks, SEO metadata, and hero content without touching commerce data.

<Tabs>
  <Tab title="Product editorial">
    In Payload admin, open **Product Content**, find the synced record for your Medusa product, and add blocks (hero, rich text, media, callouts). The storefront PDP renders these blocks alongside the Medusa variant and price data.
  </Tab>

  <Tab title="Category editorial">
    In Payload admin, open **Category Content** and edit `h1`, `seo.title`, `seo.description`, blocks, and visibility toggles. Use this for landing pages that promote a category.
  </Tab>

  <Tab title="Selection pages">
    Selection pages are `categoryContent` entries with `kind: "selection"`, a custom `route`, and a `filterQuery`. The storefront middleware rewrites the public URL to `/selection/[handle]`, so you can build curated pages (for example, "Summer edit") without a real Medusa category.
  </Tab>
</Tabs>

## Seed a demo catalog

For a quick end-to-end demo, seed the padel-shop demo fixtures. Every seeded record is stamped `metadata.demo_catalog = true` so it never mixes with real data and is safe to re-run.

```bash theme={null}
pnpm --filter @apps/medusa-backend seed:demo-catalog
```

## Next steps

<CardGroup cols={2}>
  <Card title="Manage orders" icon="receipt" href="/shop/orders">
    Fulfill orders and manage customers in the Medusa admin.
  </Card>

  <Card title="Storefront content" icon="file-lines" href="/shop/content">
    Publish landing pages and blocks with Payload.
  </Card>
</CardGroup>