> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/sell-on-lid/create-a-product.md).

# Create a product

How to create a digital product on Lid: what buyers get, title, description, price in dollars or free, commission for sharers, refund window, publish.

A product on Lid is anything digital you can deliver with a file or a link: an ebook, a template, a guide, access to a private folder. Courses have their own flow: see [Courses](/sell-on-lid/courses.md).

![The first step of New product on Lid: "What do buyers get?", with a choice between files and a link, and a preview of how buyers will see the product.](https://1004546140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQKVT6WDKWT4P06WmWa57%2Fuploads%2FCrv8xFy9Svg8l4ZcX8Eo%2Fcreate-product-step-1.png?alt=media)

## Steps

1. Open **My store** in your [dashboard](https://lid.pro/dashboard) and click **New product**.
2. Choose what buyers get. Upload files (PDF, ZIP, video) or paste a link, like a Notion page or a shared folder. Only buyers see it, and Lid delivers it the moment they pay.
3. Add a title. Concrete beats clever.
4. Write the description. Say what the buyer gets and who it is for. Lida can draft it for you with **Draft it**.
5. Set the price in US dollars, or choose **Free**.
6. Set the commission you share with people who bring you sales. Anywhere from 1% to 50%; it starts at 10%. A common setup: you keep 87%, the sharer gets 10%, Lid gets 3%.
7. Choose a refund window. With none, you are paid at once. See [Refunds and protection](/sell-on-lid/refunds-and-protection.md).
8. Click **Publish**. Your page is live.

## Optional extras

* **Free previews.** Add files anyone can open before buying, next to the private files only buyers unlock.
* **Co-creators.** Split your share of every sale with other creators, in the same transaction.
* **Visibility.** List the product in Explore, or keep it unlisted so only people with the link find it.
* **A second language.** Add an English or Spanish version of the title and description.

## FAQ

<details>

<summary>Can I edit after publishing?</summary>

Yes. Title, description, price, images, delivery files and commission stay editable from **My store**, and buyers who already paid keep their access. A new price applies to the next sales; past purchases stay as they were.

</details>

<details>

<summary>What does Lid charge?</summary>

A flat 3% on every sale, shown up front, and $0 a month to sell.

</details>

<details>

<summary>How do I get paid?</summary>

In seconds, automatically, in digital dollars. See [Getting paid](/sell-on-lid/payouts-and-usdc.md).

</details>

This is the link if you want to sell: [lid.pro](https://lid.pro)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lid.pro/sell-on-lid/create-a-product.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
