> For the complete documentation index, see [llms.txt](https://ordinals-goods.gitbook.io/protocol-specification/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ordinals-goods.gitbook.io/protocol-specification/advanced-features/product-catalog.md).

# Product catalog

Ordinals Goods protocol is designed to deal with large quantities of tokens representing items of a small set of "products" - kinds of goods offered by the business. Naturally, products can be represented as a tree with one-to-many relationships, where at the top will be large categories, and leaves will be very specific instances of products offered to end customers.

Businesses would want to offer bakers more general terms of subscriptions (even potentially weight-specific, like "1 kilo of honey per month"), while customers would want to redeem specific instances, like "2 cans, 250gr oak honey", also having a wide offered range of different products, potentially redeeming different kinds of goods every month, trading on the marketplace, etc.&#x20;

To maintain this logic, organizations must maintain correct weight values when defining products, and fine-tune subscription logic (and a list of product options available for a subscription) with subscription "level" field in protocol messages.

A product catalog built with recursive inscriptions solves the issue. Each product in addition can be configured as not allowing direct redemptions (for categories and top-level products), and can have a different URL for connecting with the business CRM system for redemptions.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ordinals-goods.gitbook.io/protocol-specification/advanced-features/product-catalog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
