This article is also available in:
Batches

Batches are used to pre-authorise reseller sales. They are like vouchers except without the product and number of tickets being pre-set. It’s like a shortcut to a reseller voucher but without the product / tier. It automatically opens up the reseller voucher flow for a given reseller but you still have to choose the product and tiers. With Vouchers you need to specify the tier and the number of tickets per voucher.

You can see the following default columns here:

Active
Range Start
Range End
Reseller
Codes
Redeemed

You may add also Reseller Code.

To create a new batch use + New Batch button and set:

Reseller
Active
Range Start
Range End



You may also use Export button or Generate Report which Shows you Total, Minimum, Maximum, Average or Count of:

Range Start
Range End

By:

Active
Redeemed
Reseller
Reseller Code

Vouchers

This section shows an overview of your Vouchers with the following default columns:

Reference
Active
Reseller
Product
Tier
Scheme
Bill Gap
Codes
Redeemed
Price
Notes

You may add also:

Currency
Check Digit
Range Start
Range End
Remaining
Valid From
Valid To
Option
Destination
Settlement (Voucher, Deposit, Deferred)



Vouchers in the context of resellers are their allocations of barcodes. These are recognised by the system, and are instantly redeemable on scan.

The best way to explain this is by example. There are two main ones:

You pre-print booklets with QR codes and hand them out to your hotel concierges. This may be because the product is too cheap to warrant printing a voucher. You will generate these QR codes within this section. The hotel concierge sells a pre-printed voucher and stamps it, the customer goes to the bus stop, the seller scans the voucher and automatically a ticket is printed.

Groupon comes to the operator and strikes a deal: they will sell a certain amount of tickets for a reduced rate and the clients will redeem the vouchers with a set of codes they send to the operator. The operator imports these codes into the vouchers and assigns it to the product and tier. A customer comes with the voucher, it is scanned, and a ticket gets printed automatically.

You may create new voucher with the + New Voucher button in the top right corner by setting:

Reseller
Active
Reference
Valid From - the start of the validity period
Valid To - the end of the validity period
Destination
Product - the related product
Tier - of a customer
Ticket per Code - quantity
Price - of the product
Commission - paid to the reseller
Settlement Method (Bill to my account, Collect my commission as a deposit, Pay later)
Notes
Voucher Blocks - where you upload custom voucher codes
Prefix - to all generated codes
Check digit - this is for a type of barcodes called EAN, which is what you use in supermarket barcodes, they usually have a number that is used for the checksum, the last one
Voucher Codes: pick 1 of 3:

Number Range - set from and to and Collateral formula. This goes sequentially from X to Y by adding one more to the list (X+1, X+2, …, Y-1, Y)
Random Codes - these must be greater than 1 and less than 15,000. They are a set number of codes
CSV Upload - a distributor sends a set of codes exported from their system and you upload it as CSV to the system, as in the Groupon example



When you Create Voucher you can Download Codes or Print Voucher after that.

You can use Bulk Actions to Archive vouchers, Restore button if you want to bring them back, Export button to download Excel or CSV file or Generate Report.

Rewards

The idea of rewards is that concierges can collect points instead of money. These can be redeemed with gift cards. The benefit is twofold: you don’t pay taxes on commission as you’re not moving money, and you can deduct the cost as a business expense.

This motivational section shows Rewards for resellers obtained for selling your products. It contains following subsections:

Rewards
Collections
Leaderboard



Rewards

Here you can see an overview of your custom rewards.

You may create new reward here with the + New Reward button and setting the following details:

Name
Description
Points - the amount needed for obtaining this reward



Note also an option to Blacklist and Whitelist particular destinations, bands and resellers.

Collections

Here you can see which agent collected which reward, for how many points, and if the reward was already delivered.

Leaderboard

Here you can see a list of particular agents with number of points they have gained so far, as well as the reseller they are working for.

Portals

This section serves for creating Sales Portals (previously called Point of Sale) so you can have more than one. For example a regular for you one and the other for partners. It's powered by SSL for SaaS.

To create a new portal use + New Portal button and set it's:

Name - of the portal in Ventrata
Layout - a custom layout (has to be custom build by Ventrata team)
Hostname - url of the portal
Seller - whether has access to the portal or not
Operator - whether has access to the portal or not
Agent - whether has access to the portal or not
Logo - for branding
Logo white - for branding
Favicon - for branding
Terms - you may upload a file containing terms
Email
Telephone
Address



After that you can reach all your portals from the top right of your account.




Connections

This is where all our API connections are going. Currently in development.



Webhooks

This is like an api that you create for one event, it has been implemented to Ventrata.

So say you create a webhook on a flight departure. The airline will update information on that flight departure and you get a notification of changes. But it can also be another event like price, like getting SMS alerts for these changes, but it is done via this API interface and you can request it automatical.

If you want to create webhook, use + New Webhook button and set:

Connection - you need to choose a valid one from Connections section
Event - when it's triggered (Booking Update/ Availability update)
Url - where webhook sends info to



Basically a webhook is a sort of an API. What it does is it sends information as soon as it gets it. And the URL you add is where there is a listener. So webhook sends info URL listens to updates. What happens later is that the listener pushes the info to a third party like an SMS. In this case the webhooks that we have are for booking/creation/update/cancellation.

It's designed mostly to have other services pull info, say something like Microsoft PowerBI which has an external DataBase. Instead of creating custom connections each time we just send the information you find important (like all sales made from this checkout).

This is what we want to use for all the Tax integrations in the EU, they ingest the data we send and outupt it in a government defined form.

Mappings

This is to map products with OTAs through City Connect in Ventrata
In this subsection you can see all City Connect resellers that have products pointing to that account.
Simply press the reseller you want and you will see a table with five columns:

Reseller Product
Reseller Option
Product
Option
Tour



After clicking on a certain Reseller Product in the list a new window will open. Here you can update the mapping for this product by clicking the button Update Mapping.



This action then updates the mapping in the OTA’s extranet.
If any line in the table is red it means that the mapping is not complete and bookings will fail.
You must have a tour set at the mapping level for Viator and Expedia. It’s not necessary for Get Your Guide (GYG).
After selecting GYG or Viator you will be shown the Connect Account button.



To connect, use your admin email / password that you need to login to the reseller’s extranet. That allows automatic building of the reseller’s product list.

When you press that button, you get a form to add your username and password for that reseller and that will automatically create a connection and get all the products you have on that account,so you can map it. With that button you give your credentials to the extranet and the system uses that to create the connection and scrape the extranet to create the mappings for the products.

When you connect through API, this is good for OTAs and suppliers because:

OTAs sell live availability, ie, no overbooking
Their clients can redeem on attraction instead of the suppliers having to collect vouchers and then emitting the ticket
When the mapping comes up, the bookings that come in are assigned to:

a) The correct product (so redemption is automatical)
b) The correct reseller (to make billing easier)

After connecting, there are two buttons. The Disconnect button disconnects the account and The Sync button re-downloads any changes in the product list.
Was this article helpful?
Cancel
Thank you!