Skip to main content

Getting Started

Requirements​

Before we can begin the development and integration we will need some information on site setup, branding and integration choices. This section covers all the information needed by us, the WhiteLabel features and some guidance on how to pick the best fit for your desired product.

You will be asked to select someone from your technical staff who will communicate with Vio to clarify all technical information and coordinate, together with Vio, all the deployment phases.

Assets & styles​

Before we start the development phase, it is important to have the desired assets at our disposal, so that we can already plan how to best integrate them.

The list of assets we need includes:

  • Graphics
    • Favicon: 48x48 PNG format
    • Brand logo: 146x24 SVG format
    • Brand logo compact: 32x32 SVG format
    • Additional logo: 20x100 SVG format
    • Icon: 12x12 SVG format
  • Color palette

The material needs to be shared with your assigned Vio.com representative as soon as possible during the onboarding phase.

Sub-domains​

The WhiteLabel platform will be fully hosted by Vio.com under the hood, but it will be available to the public on domain(s) or sub-domain(s) chosen by the Partner. We need, at least, 3 domains or sub-domains available to host the relevant platforms.

For instance:

  • hotels.example.com (for the accommodation search results)
  • secure.example.com (for the payment page)
  • bookings.example.com (for the bookings management)

But we can also make the platform available to different brands/languages/markets at the same time upon request. For instance:

hotels.example.com
hotels.example.co.uk
hotels.vorbild.de
hotels.esempio.it
hotels.ejemplo.es

The SSL certificates will be provided by Vio.com at no additional cost.

Hotels offline Mapping​

The recommended way to be sure to map Hotels and Places to our database quickly and consistently is to use the Vio.com Suggest API, as mentioned in the Integration chapter.

However, for Hotels (and properties in general) we also offer offline solutions for that; in general, the quickest and most reliable option is to perform a cross-mapping, pivoting on a common provider database. We can share with you our content static file, which includes the ID mapping for our main providers, so that you can cross-map it according to your needs.

Alternatively, you can provide us with the most up-to-date mapping database with a common partner and our Content team will take care of it.

The mapping elaboration time will depend on various factors, so we suggest to provide the database to us as soon as possible in the requirements gathering phase.

Requirements Checklist​

Here is listed all the information and material the Partner would need to assemble before the development phase. Make sure you have everything collected as soon as possible, to speed up the development phase and avoid bottlenecks.

  • Assets and graphics
    • Favicon
    • Brand logo
    • Brand logo, compact
    • Additional logo
    • Icon
    • Color palette
  • Domains
    • Domains list (3 domains for each deployment)
  • Integrated services
    • Desired widgets (widget type and placement)
    • API key (if applicable, upon request)
    • Footer links list
  • Mapping (if applicable)
    • Common partner cross-mapping database