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

# Build your catalog

> Turn the stock you own into offers a customer can buy, priced and grouped the way they browse.

Step 5 of the [launch path](/docs/guides/launch/overview). Inventory is what you own; the catalog is what a customer can buy. They are deliberately separate — one listing can draw on stock at several locations, and one unit can be offered as a rental, a sale, or both.

## Build one listing end to end

Build a single listing all the way through first, as the pattern for the rest: its variants, its price, its limits, and where it sells. Getting one right and then repeating it is much faster than getting twenty half-right.

<Note>
  A guide for building your first listings is in progress. Until it lands: [Create and publish a listing](/docs/guides/catalog/create-and-publish-a-listing), [Set up variants](/docs/guides/catalog/set-up-variants), [Price a listing](/docs/guides/catalog/price-a-listing), [Build a price table](/docs/guides/catalog/build-a-price-table).
</Note>

**Done when:** a listing shows correct availability for a real date. That is this step's real finish line.

## Connect stock to listings

The part that catches people: **a listing's stock is not a field on the listing.** The Variants tab shows an availability number that reads editable but is derived — the actual binding lives in a fulfilment rule. A merchant who does not know that cannot add stock to a new SKU.

<Note>
  A guide for how stock binds to a listing is in progress and is the highest-priority gap on this step. Until it lands: [Control what stock a listing draws from](/docs/guides/catalog/listing-inventory-rules) and the [stock items](/docs/concepts/inventory/stock-items) concept.
</Note>

**Done when:** you can add a new SKU to an existing listing and see stock register against it.

## Group it the way a customer browses

Collections are how a customer finds things, not how you file them. Build them around the way people shop — by activity, by season, by who it is for — rather than mirroring your internal categories.

<Note>
  Until a dedicated guide lands: [Build a collection](/docs/guides/catalog/build-a-collection).
</Note>

**Done when:** someone who has never seen your catalog can find a representative item in two clicks.

## Decide where each listing sells

Three separate gates decide whether a customer can buy something: the listing's own status, whether it is available at that location, and whether that location offers a fulfilment method for that purchase type. Merchants routinely find one and not the others, then report a bug.

<Note>
  A guide for controlling where each listing sells is in progress. Until it lands: [Where a listing sells](/docs/guides/sales-channels/control-where-a-listing-sells).
</Note>

**Done when:** everything meant to be on sale is visible where you intend, and nothing else is.

## Related articles

<CardGroup cols={2} className="doc-rows-condensed">
  <Card title="Launch path" href="/docs/guides/launch/overview">
    The whole path, in order.
  </Card>

  <Card title="Bring in your data" href="/docs/guides/launch/bring-in-inventory-and-catalog">
    The previous step, which this one builds on.
  </Card>

  <Card title="Design your storefront" href="/docs/guides/launch/shape-the-storefront">
    The next step: making it look like you.
  </Card>

  <Card title="Catalog guides" href="/docs/guides/catalog/overview">
    Every catalog task, in full reference detail.
  </Card>
</CardGroup>