> For the complete documentation index, see [llms.txt](https://docs.tiun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiun.io/guides/getting-started/creating-first-product.md).
# Create your first product
Every tiun integration is wired to one or more **products** you configure in the dashboard. This guide walks through creating a product end-to-end and captures the **product ID** you'll use in code.
***
## 1. Open Products
In the [my.tiun.business dashboard](https://my.tiun.business/), go to **Products**. The catalog belongs to whichever environment the **Sandbox** toggle is showing — live and sandbox each have their own products and IDs. Most teams create products in **sandbox** first while integrating, then recreate them in **live** when shipping.
Starting a new product opens one form. You'll work down it in the order of the steps below — name, what you're selling, how you charge, and the fields that appear for the pricing model you pick.
The create-product form, with Subscription selected.
***
## 2. Pick a pricing model
Start a new product and choose the pricing model that matches how you want to charge. tiun supports three:
* **Subscription** — you charge a flat price on a repeating interval (daily, weekly, monthly, yearly, or any multiple of those). Best when the value is access to the product itself over time.
* **One-time purchase** — you charge a single price and access never expires. Best for consulting engagements, lifetime licenses, or a single course, report, or deliverable.
* **Time-based** — you charge for the time the user spends with your content. Best for media-style products (articles, audio, video) where engagement varies per visit.
If you're not sure, see [Products](/reference/generic/products.md) in Reference for a fuller comparison.
***
## 3. Configure pricing
The configuration depends on the pricing model. Here's what each field actually represents — you'll be asked for the relevant ones during creation.
**For a subscription product:**
* **Product name** — shown to your customers at checkout (for example "Pro", "Light").
* **Interval** — a count plus a unit: day, week, month, or year. *Every 3 months* is how you'd set a quarterly plan.
* **Price** — charged at the start of each interval.
* **Trial period** (optional) — enable it to set a **trial length** and a **trial amount**. The trial amount is charged upfront; enter `0` for a free trial, or less than the subscription price for a discounted one.
**For a one-time product:**
* **Product name** — shown to your customers at checkout (for example "Full course", "Lifetime license").
* **Price** — the single amount charged at checkout. It incurs only once; there's no interval and no trial.
**For a time-based product:**
* **Product name** — shown to your customers at checkout.
* **Interval** — measured in **minutes**; it's the only unit time-based billing offers.
* **Interval fee** — what one interval costs, charged at the start of it.
* **Monthly limit** — caps what a user can be charged in a calendar month, so heavy users don't run up surprise bills.
Field semantics live in the [Products](/reference/generic/products.md) reference if you want the full picture.
***
## 4. Pick a tax category
Whatever the type, you also file the product under a **tax category**. It's required and there's no default. tiun is the Merchant of Record for your sales, so this is what determines how the product is taxed.
Subscription and one-time products also have a **tax behavior** — **Automatic** (the default) applies the usual pricing convention for the customer's region, **Include tax** means the price shown includes tax, and **Exclude tax** adds tax on top at checkout.
The form lists the available categories with a short description, guidance on where each one ends, and examples. Pick the one your product **genuinely** belongs to — not the closest-looking match.
If none of them fit what you sell, choose **Something else** and describe your product. tiun follows up with you instead of filing it under an approximate category, so it's always better than picking a near-match.
{% hint style="info" %}
**The option "Something else" lives in this form only.** It's part of creating a product in the dashboard at [my.tiun.business](https://my.tiun.business/) — it is not available over the [MCP server](/guides/agent-integration/agent-integration.md), so an agent can't pick it for you. If you're setting products up through an agent and none of the categories fit, submit the missing category here in the dashboard instead.
{% endhint %}
{% hint style="warning" %}
**Choose carefully — this one is permanent.** Unlike the name and price, a product's tax category cannot be changed after the product is created. Correcting it means archiving the product and creating a new one, and archiving cannot be undone. If you're unsure which category applies, use **Something else** rather than guessing.
{% endhint %}
***
## 5. Save and copy the product ID
Once the product is saved, copy its **product ID** — it's prefixed `p-test-...` in sandbox and `p-live-...` in live. Use it with the matching SDK environment (`sandbox: true` for `p-test-...`, live default for `p-live-...`). See [Sandbox](/reference/generic/sandbox.md) if you need both environments.
---
# 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.tiun.io/guides/getting-started/creating-first-product.md?ask=&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.
