The complete open source platform to run your entire marketplace. Storefront, vendor panel, admin console, and integrations in one enterprise-grade platform you own.
TypeScript b2b-marketplacecomposable-commerceecommerceenterpriseheadless-commercemarketplacemedusamedusajsmulti-vendortypescript
---
title: "Catalog"
sidebarTitle: "Overview"
description: "Keep one shared product catalog, decide which stores may sell each product, and review what stores submit."
---
Use Mercur to keep one product catalog for the whole marketplace and control which stores can sell each product.
The catalog is Medusa's Product module (`Modules.PRODUCT`) with a marketplace layer on top. Products, variants, categories, collections, tags, and types are native Medusa models. Mercur adds the `product_seller` allowlist, a review flow over the product `status`, an audit record for every submission, and its own product workflows. No store owns a product: a store sells a master product through an [offer](/platform/offer/overview) that carries its own SKU, price, and stock.
<img className="block dark:hidden" src="/images/figures/catalog-overview-light.svg" alt="A product_seller link table behind a Products list of the shared catalog: each master product shows its status, the stores on its allowlist, and its offer count, with the Linen shirt restricted to ACME highlighted." />
<img className="hidden dark:block" src="/images/figures/catalog-overview-dark.svg" alt="A product_seller link table behind a Products list of the shared catalog: each master product shows its status, the stores on its allowlist, and its offer count, with the Linen shirt restricted to ACME highlighted." />
<Note>
There's no Mercur catalog module. Resolve the service with `Modules.PRODUCT` from `@medusajs/framework/utils`, and run Mercur's product workflows from `@mercurjs/core/workflows`. Mercur's `createProductsWorkflow` has the same name as Medusa's, so check the import path.
</Note>
## Key features
The catalog layer covers how products enter the marketplace and who can sell them:
- **Shared master products**: one `Product` record per item, sold by any number of stores through offers
- **Store allowlist**: the `product_seller` link restricts a product to the stores on it; a product with no rows is open to every store
- **Review flow**: vendor submissions start as `proposed` and an operator publishes or rejects them
- **Submission audit**: every create and review step writes a confirmed `ProductChange` record with the actor who did it
- **Attribute-driven variants**: products take Mercur attributes on create, and variant-axis attributes become the options variants bind to
- **Native structure**: variants, categories, collections, tags, and types come straight from Medusa's Product module
## How it works
A product moves through the catalog in a fixed order:
1. A store or an operator runs `createProductsWorkflow`. Vendor submissions default to `proposed`.
2. The workflow records a `PRODUCT_ADD` change with the creator as `created_by`, and links any `seller_ids` to the product.
3. An operator runs `confirmProductsWorkflow`, `rejectProductWorkflow`, or `requestProductChangeWorkflow` on the proposed product.
4. Once `published`, the product shows in the Store API and to every store its allowlist permits.
5. Each store that sells it creates an offer against one of its variants.
## Get started
Learn how master products, the allowlist, and statuses fit together.
<CardGroup cols={2}>
<Card title="Master products" icon="box" href="/platform/catalog/concepts/master-products">
Why products belong to the catalog and how Mercur records who submitted them.
</Card>
<Card title="The store allowlist" icon="user-lock" href="/platform/catalog/concepts/product-seller-allowlist">
How the `product_seller` link decides which stores see and sell a product.
</Card>
<Card title="Status lifecycle" icon="arrows-rotate" href="/platform/catalog/concepts/status-lifecycle">
The four statuses and the workflow behind each transition.
</Card>
<Card title="Variants & categories" icon="sitemap" href="/platform/catalog/concepts/variants-categories-collections">
The Medusa models that structure the catalog, and where Mercur extends them.
</Card>
</CardGroup>
## Examples
Build against the catalog in your own server code.
<CardGroup cols={2}>
<Card title="Create a master product" icon="plus" href="/platform/catalog/guides/create-a-master-product">
Run `createProductsWorkflow` with attributes, variants, and an allowlist.
</Card>
<Card title="Allowlist stores" icon="user-plus" href="/platform/catalog/guides/allowlist-stores">
Restrict a product to chosen stores, or open it to all of them again.
</Card>
<Card title="Publish or reject" icon="gavel" href="/platform/catalog/guides/publish-or-reject-a-product">
Review a proposed product from a route or a subscriber.
</Card>
</CardGroup>
## Resources
The data models, links, workflows, service methods, and events behind the catalog.
<CardGroup cols={2}>
<Card title="Data models" icon="table" href="/platform/catalog/reference/data-models">
`Product`, `ProductVariant`, `ProductCategory`, and the other Product module models.
</Card>
<Card title="Links" icon="link" href="/platform/catalog/reference/links">
How products and categories link to stores, offers, attributes, changes, and media.
</Card>
<Card title="Workflows" icon="diagram-project" href="/platform/catalog/reference/workflows">
Mercur's create, review, allowlist, and category workflows with their hooks.
</Card>
<Card title="Service" icon="gear" href="/platform/catalog/reference/service">
Medusa's Product module service, resolved with `Modules.PRODUCT`.
</Card>
<Card title="Events" icon="bell" href="/platform/catalog/reference/events">
The events Mercur emits when products are created and reviewed.
</Card>
</CardGroup>