> For the complete documentation index, see [llms.txt](https://docs.roomle.com/rubens/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roomle.com/rubens/rubens-admin/requirements-and-sample-products/sample-products-and-files.md).

# Sample products and files

## Basic product

If you do not have 3D data files at hand, you can use our already created sample products. Display or hide the sample products at the top of the overview by opening the menu in the right upper corner and select the `Show sample products` or `Hide sample products` entry.

Or use our sample files to [create a product](/rubens/rubens-admin/rubens-admin-help/products.md#create-or-archive-a-product) by yourself:

### 3D model samples

* For `fbx` extension [Sample1.fbx](https://catalog.roomle.com/samples/Eames_Plastic_Armchair_RAR_fbx.zip), [Sample2.fbx](https://catalog.roomle.com/samples/Lounge_Chair_fbx.zip)
* For `obj` extension [Sample1.obj](https://catalog.roomle.com/samples/Eames_Plastic_Armchair_RAR_obj.zip), [Sample2.obj](https://catalog.roomle.com/samples/Lounge_Chair_obj.zip)

## Configurable product

Configurable products are based on components. If you do not have ready components to use in your products, you can use one of the sample components.

1. Navigate to `Catalog management`
2. Choose a catalog and select `Components`
3. Click on the three vertical dots menu on the upper right corner of the components table
4. Select `Show sample Components`
5. Choose one sample component and open the detail view
6. Copy the `External identifier` of the component and create and configure a new product with it
7. For more details read the [create configurable products](/rubens/rubens-admin/rubens-admin-help/products.md#create-a-configurable-product) section


---

# 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.roomle.com/rubens/rubens-admin/requirements-and-sample-products/sample-products-and-files.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.