Where to find it: Activities › Product availability, Activities › Batch closure, Activities › Ticket reserves, and the Times tab of each product
In one sentence: your times say when you sell, your stock says how many places are left, and this stock is shared by all your sales channels, unless you deliberately create a separate stock.
Why it is useful for you
A single stock prevents overbooking. A place sold on your website is no longer offered on an OTA or by a reseller. You no longer need to adjust your capacity channel by channel.
The big picture
Your stock is a tank. Each sales channel is a tap connected to it.
| Element | Role |
|---|---|
| Tank | The stock: the maximum capacity. |
| Taps | The widget on your website, the admin, OTAs, resellers. |
| Level | Each order lowers the level, whatever the tap. An accepted cancellation raises it again. |
| Closed valve | A closure stops sales for a period or a time. |
For an OTA, places are removed from the stock when the payment validation is sent through the API. If an OTA or a reseller cancels and the product’s cancellation conditions allow it, the order is cancelled automatically, the reseller commission is removed and the places go back into the stock. Otherwise, the cancellation is refused and an error is sent back to the reseller. Places freed by a cancellation are immediately available in Tourbiz. On the OTA side, the update can be instant or take a few minutes depending on the type of connection: some OTAs query Tourbiz in real time, others refresh their availability at regular intervals.
Key concepts
- Times: the periods and departure times of the product, set in the Times tab of the product.
- Stock: the maximum capacity. One stock can cover several products.
- Shared stock: adults and children in the same counter. By contrast, a stock per price type counts each rate separately.
- Decrement unit: what a booking removes from the availability counter. In most cases, a booking removes one place per participant. With Tourbiz, you can also set a different unit depending on the product sold, which lets you manage a capacity that is not counted in people.
Example: a racing circuit can run its cars for a maximum of 30 laps per hour. The counter for each time slot is therefore set to 30 units, that is 30 laps. A Bronze package giving 5 laps removes 5 units, a Silver package giving 10 laps removes 10, and so on. The slot is full when the 30 laps are sold, whatever the combination of packages.
This capacity management by decrement unit is exclusive to Tourbiz. - Closure: making a period or a time unavailable for sale.
- Ticket reserve: a batch of tickets bought in advance, whose stock is managed separately. It is used when you resell tickets you have bought in bulk from a third party, for example entry tickets to museums or public monuments. Each sale takes one ticket from the reserve, and the product’s availability depends on the number of tickets left.
Not to be confused
| Concept | What it means |
|---|---|
| Times | When the product can be sold. |
| Prices | How much it costs. Prices have their own calendar, separate from times. |
| Stock shared by channels | The same stock serves the widget, the admin, OTAs and resellers. Deliberate exception: a special product with its own stock for one or more OTAs. |
| Shared stock | The setting that puts adults and children in the same counter. |
A real-life example
A 150-seat boat makes two departures a day, at 11 a.m. and 3 p.m. The “Guided cruise” product has a stock managed per time: 150 places for each departure, shared between all channels. The stock could also be managed per day, whatever the departure time; this choice is made in the stock configuration. For the 11 a.m. departure, 60 places are sold on the widget, 40 on Viator and 20 by a reseller. 30 places remain, for all channels. If the Viator customer cancels within the product’s cancellation conditions, their order is cancelled automatically and their places go back into the stock. On a flood day, the operator closes the whole day for all its products at once with Batch closure.
What you need first / what it affects
- Upstream: a product created, with its times and prices.
- Downstream: what your customers see on the widget and on OTAs, the operations schedule and the orders.
