> 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/product.md).

# 3D product registration

We’ve gathered questions about the 3D product registration process and how it is reflected in the editor.

## How do I register a product?

Archisketch product registration proceeds in the following order.

1. **Model registration** — Upload a 3D model file
2. **Component registration** — Create parts based on the model
3. **Product registration** — Create a sales product based on the components

For more details, please refer to [\[Linking 3D Products\]](/guide/dev-kr/contents/custom-furniture/create-sale-product.md).

## What file formats of 3D models can be uploaded?

You can upload a 3D model file to create a model. Please contact the person in charge for supported file formats.

## How will the registered product appear in the Archisketch editor?

Once product registration is complete, it will appear in the furniture library of the Archisketch 3D interior editor. Users can place the product in a space and check through rendering whether it fits the actual space.

## How long does it take for the product to be reflected in the editor after registration?

After uploading a 3D model file, rendering must be completed before it is properly displayed in the editor. Processing time may vary depending on the file size and complexity.


---

# 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/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.