# Getting started

To create an importer/converter from any given 3D data into Roomle you need to answer those questions:

  • How is the data structured which I want to import?
  • How is Roomle data structured?
  • How can I prepare my data for import?
  • How do I import the prepared data into Roomle?

# How is the data structured which I want to import?

To convert from one format into another you need to understand both. We can not guide you through this process since we do not know with which format you are starting. Also we do not have deep understanding of all the formats available.

# How is Roomle data structured?

To get started we recommend you are taking a look at the definition (opens new window) of different terms we are using when talking about Roomle data.

To create a product you need to understand Roomle Script (opens new window) and all parts necessary, especially:

We recommend to go through our Hello World example (opens new window) and the scripting course (opens new window).

# How can I prepare my data for import?

You will find an overview of all possible imports, exports and how they need to be structured in the Rubens Admin documentation (opens new window).

If you have existing 3D data and you want to use external meshes you can export them using our Blender Addon (opens new window)

# How do I import the prepared data into Roomle?

You can either import it manually in Rubens Admin (opens new window) as described here (opens new window) or you can use our REST API (opens new window) to import it automatically from within your code.

# Example

In the following we will work with a simple example to explain the best practices of converting. For this we assume that we have an item list in CSV format.

This list includes all variations of the product with item number 122. The product has two changeable properties, the color and the width. Each variation in the list is a separate entry, so each property has exactly one value (e.g. color: white). We assume that there are only three different variations.

  • white, 50cm wide, 80cm high
  • white, 60cm wide, 80cm high
  • black, 50cm wide, 80cm high

The product is not available in black and 60cm width.

"Item number","Color","Width(cm)","Height(cm)"

# Requirements

As explained in Getting Started, you need to understand the Roomle structure to prepare your data for import. First you have to answer if you want multiple start configurations, how products should be configurable and which materials exist.

Should there be several start configurations per product?

We only want one start configuration. The configurator should always show the variant white, 50cm wide to start with.

How should the articles be configurable?

In our example, the product has three parameters. The color, the width and the height. The height is the same for each variation, therefore it should not be configurable. The color and the width, however, should be.

Do materials exist and if so, in what form?

There are no existing materials but we want to store the specified colors as materials and therefore we need to extract them from the item list.

# Roomle data structure

The requirements described above result in the data structure in Roomle described below.


Products, components and materials are assigned to catalogs in Roomle. Therefore, a catalog must be created (opens new window) first.

The following properties are set for the catalog:

"Catalog name", "Roomle internal catalog ID"
"My catalog", "mycatalog"


Two materials must be created. You can find the description how to import materials here (opens new window).

The following properties are set for the materials:



To ensure the configurability described above, a component must be created. The component script given below meets the specified requirements.

  • There are three parameter: height, width and color
  • The width is displayed as 'Width' and can be changed between two values. The default value is 50cm.
  • The height is displayed as 'Height' but cannot be changed.
  • Two materials are available, they are displayed under the label 'Color' and white is the default. The materials are referenced with the respective catalog prefix.
  • The geometry of the component is also added. If there is no geometry available, it needs to be added manually after the import.
  • The article number is automatically built depending on the configuration.

    "id": "mycatalog:122",
            "key": "width",
                "en": "Width"
            "type": "Integer",
            "unitType": "length",
            "defaultValue": "500",
            "key": "height",
                "en": "Height"
            "type": "Integer",
            "unitType": "length",
            "defaultValue": "800",
            "key": "color",
                "en": "Color"
            "type": "Material",
            "defaultValue": "mycatalog:white",
                    "value": "mycatalog:white"
                    "value": "mycatalog:black",
                    "condition": "width != 600"
    "geometry":" AddCube(Vector3f{width,500,1000});SetObjSurface(color);",
    "articleNr": "articleNr= '122_'; if(color == 'mycatalog:black') { articleNr = articleNr | 'b_';} else { articleNr = articleNr | 'w_';} articleNr = articleNr | (width/10); if(width == 600) { articleNr = articleNr | '60'; } else { articleNr = articleNr | '50'; }"


The created component must be referenced in a product. You can find the description how to import products here (opens new window).

The following properties are set for the product:


With the data created, the product is now ready to be displayed in a Rubens configurator.