Resellers
How to forward travel docs (Weblink, PDF & App) to resellers with automated rebranding
This feature is still in beta phase and not yet 100% available. As soon as all functions are fully available, we will update this page.
With GUIBO, tour operators and resellers can easily share and rebrand travel docs. An operator can define a specific “reseller” for a travel docs release. This release will then also be visible in the reseller's GUIBO account. Additionally, GUIBO transforms the corporate identity of the travel docs to the look and feel of the reseller (see details below).
Release Weblink
Logo from operator is replaced with reseller’s logo
Main color from operator is replaced with reseller’s main color
Tour Guide App
The operator’s App-Link is replaced with a link to the reseller’s App.
When the reseller is not using a Whitelabel App, the GUIBO App is linked.
PDF Booklet
Logo from operator is replaced with reseller’s logo
It is possible that your PDF template is not yet capable to replace logo's. You will notice this if the operator logo is not replaced by the seller logo. In that case, please contact our support and we will update your template.
Prerequisite: Operator and reseller GUIBO accounts must be be connected
As a prerequisite, the GUIBO Account of your reselling partners needs to be connected with your GUIBO Account as a partner account. Please contact our support to connect the reseller's account to your account. We will contact the reseller, ask for permission and connect the accounts. You find the partner accounts when you navigate to Account > Partner Management.
How it works for the operator side
Ensure that your seller's GUIBO account is listed under Account -> Partner Management (more here)
When you create the release, ensure that the field “resellerOid” is set with the GUIBO Account ID of the reseller of your choice. Detailed technical descriptions can be found here.
It could be useful to set a specific “downloadCode” from your reseller so that your reseller can provide his own downloadCode to his travellers. Otherwise, the reseller must provide your downloadCode to his travellers. Detailed technical descriptions can be found here.
That's it. The release is then rebranded and visible in the reseller's GUIBO account to be forwarded to his travellers.
How it works for the seller side
Ensure that your operator's GUIBO account is listed under Account -> Partner Management (more here)
After the operator has defined your GUIBO account number as the seller for a release, this release is visible under "Releases" in the same way as the releases you have created yourself (typically via an API call triggered by your ERP system).
From here on, you can integrate the release link into your processes just as if you had created the release yourself.
Last updated