> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/faq-en/partner-developer/parametric.md).

# Parametric furniture

We’ve gathered questions about the concept of parametric furniture and how to set it up.

## What is parametric furniture?

Parametric furniture is customizable furniture that users can directly adjust options such as width, height, and color in the Archisketch editor. For example, you can freely change a sofa’s width between 1,200 mm and 2,400 mm, or choose a fabric color.

## Is registering parametric furniture different from registering a regular product?

The basic flow is the same, but you need to additionally set parameters (adjustable options) during the component creation stage. Parameter setup requires developer integration. For more details, [\[Register a Parametric Component\]](/guide/dev-kr/contents/custom-furniture.md).

## When is parametric furniture used?

Parametric furniture is suitable in the following cases.

* Custom furniture that requires freely adjustable dimensions, such as sofas and desks
* Furniture that should allow users to directly choose options such as color and material
* Products with various combination methods, like modular furniture


---

# 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.archisketch.com/guide/faq-en/partner-developer/parametric.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.