Rubens Knowledge Base

Price management with the Rubens Configurator

Rubens is the first cloud-based digital product configurator of its kind that defines a new standard for highly configurable products across all channels. The importance of product price visualization to drive online and in-store product sales has become more and more important nowadays. Roomle does not claim price sovereignty and therefore prices will not be maintained or manually setup within the Rubens Configurator scripts. We enable our clients to manage prices in different ways.

  • 1. Price via your web shop
  • 2. Prices via external price service (generic price service)
  • 3. Generic price service via Roomle Rubens

1. Prices via your web shop

If you have an existing E-Commerce platform in place where prices are maintained on your side already today, prices still we be managed by your web shop. Your web shop is connected to the Roomle Configurator via API and receives dedicated configuration part lists (with dedicated article numbers) in real-time. Matching Roomle´s article numbers against the ones maintained in the web shop enables you to calculate prices live on your side. The lead on managing prices on a regularly basis stays on your side.

Further deep dive into our Configurator Embedding API documentation to find out how the integration works.

Online Shop integration references:

Price visualization within the Roomle Rubens iFrame
Price visualization outside the Roomle Rubens iFrame

2. Prices via external price service (generic price service)

Alternatively, prices can be managed on your side via a generic external price service. The maintenance and storage of prices remains within your sovereignty. The provided PriceEndpoint will be requested by Roomle. It can be defined whether the request should happen as GET or POST. In the case of POST, the parameters can be passed as x-www-form-urlencoded body. The query happens server-to-server: the external priceendpoint is only requested from the roomlebackend. There are no requests from the browser / client directly to the PriceEndpoint.

Requested parameters:

  • articleNr[] : list of all requested article numbers
  • country: Isocode of your the respective country 

Expected result is an Array with the corresponding data. Per requested article number which receives a price there should be one single entry. If there is no price for an article number, the entry can be omitted.

content-type: application/json

   “price”: ,
   “currencySymbol”: “currency1”
   “price”: ,
    “currencySymbol”: “currency2”

3. Generic price service via Roomle

If you do not have a price management process and service in place today, we offer to manage prices via a Roomle price service. The service we offer is a very rudimentary process. Roomle provides you with a simple price list CSV template which you can upload via the Roomle platform.

Individualized product request form - example
Roomle pricing .csv template

💡Country-specifc prices

Within Roomle´s template also country-specific price lists can be defined and handled by the Rubens configurator.

💡Price management for dimensionally flexible products
The Rubens configuration part list consists of individual parts with article numbers and parameters. Based on this information you can even calculate prices parameter-based for highly individual customizable products.

Cabinet example:
Besides the article number for an highly individual cabinet element you also receive parameter details for each configuration component about:

  • type of material selected
  • individual height selected
  • individual width selected
  • ...

    Based on this information you can basically calculate the product on your side accordingly:
    Component 1:
  • Corpus Article number x Product Count
  • Material: 312343 oiled oak
  • Height: 232cm
  • Width: 355cm
  • ...

    Component 2:
  • Door Article number x Product Count
  • Material: 312343 oiled oak
  • Height: 232cm
  • Width: 50cm
  • ...

    Within the configurator script there is also an option to setup a m2-number as a 'component count' to handover when requesting the configuration part list via the API.