Where to find it: Orders
In one sentence: an order is born on a sales channel, goes through several statuses, and each step can trigger an e-mail to the customer, the sending of a ticket or a stock movement.
Why it is useful for you
Understanding this journey helps you spot the orders that need action on your part. You avoid oversights, double bookings and customers left without confirmation.
The big picture
| Step | What happens |
|---|---|
| 1. Origin | The order comes from the widget on your website, from the admin, from a connected OTA (a booking platform such as Viator or GetYourGuide) or from a reseller. |
| 2. Recording | It appears in Orders with a status. It uses places in the stock of the departure, shared by all your channels. For an OTA, places are removed when the payment validation is sent by API. |
| 3. Processing | You follow it and move it between the statuses Unpaid, To process, Pending and Processed. |
| 4. End of life | It stays Processed, or it moves to Cancelled or Refused. A cancellation coming from an OTA or a reseller is automatic if the product cancellation conditions allow it: the reseller commission is removed and the places go back into stock. Refused covers one specific case: reselling a third-party supplier product with supplier validation, without API. The supplier receives an e-mail to validate the order and can refuse it. |
An order paid online gets the Processed status when there is nothing left to do on it. In other cases, the exact order of statuses and the automatic changes depend on the channel and the payment.
Reading the Status badge
In the Orders list, the badge in the Status column combines two pieces of information. Its colour gives the booking status. Its text gives the payment status. Hover over the question mark next to Status to see this reminder.
| Badge colour | Booking status |
|---|---|
| Grey | Unpaid |
| Orange | To process |
| Blue | Pending |
| Green | Processed |
| Pink | Cancelled |
| Black | Refused |
The text shows where the payment stands, for example Accepted, Awaiting transfer, To refund or Deferred. A green badge marked Deferred therefore means: booking processed, payment deferred. In the order form, the two pieces of information are shown separately, on the Status and Payment status lines of the Reference panel.
The Documents tab: quotes, contracts and invoices
The Documents tab of the order form groups all the commercial and accounting documents of the file. The New document button offers:
| Stage | Document | What it is for |
|---|---|---|
| Pre-sale | Quote | A priced proposal, with no accounting value. |
| Pre-sale | Sales contract | The terms of the service, accepted online by the customer. |
| Invoicing | Pro forma invoice | A provisional invoice, which does not trigger VAT. |
| Invoicing | Deposit invoice | The invoice for part of the total. VAT is due. |
| Invoicing | Invoice | The invoice for the balance, deposits deducted. |
Tourbiz locks the types that are no longer possible and shows the reason. For example, once an invoice is issued, correcting it requires a credit note. The Invoicing summary tracks the total including VAT of the file, the deposits invoiced, the credit notes issued, the amount collected and the amount left to invoice. The tab also shows a Payment schedule and the Billing details, which can differ from the customer record.
Key notions
- Order form: the details of an order, with the Order form, Payment, Documents, History and Commercial proposal tabs.
- Status and Payment status: the state of the booking and that of the payment. In the list, they are combined in a single badge: the colour for the booking, the text for the payment.
- Transactional e-mails: the messages sent to the customer, which you write in Configuration › General Settings › E-mail. For a widget sale, two e-mails are sent: a payment confirmation, then a booking confirmation with the ticket. For an OTA sale, depending on the OTA, either the OTA sends its own tickets, built with the information sent by Tourbiz, or the Tourbiz tickets are used.
- History: the record of changes made to the order.
Do not confuse
| Notion | What it shows |
|---|---|
| Order status | Where the processing of the booking stands. |
| Payment | What the customer has paid: Order total, Total paid, Remaining balance. |
A concrete example
A cruise company receives three orders on the same day for the 8 pm departure. The first comes from the widget on its website, paid online. It becomes Processed and the customer receives a payment confirmation, then a booking confirmation with the ticket. The second comes from GetYourGuide. GetYourGuide collects payment from the customer. The places are removed from stock when the payment validation is sent by API. The third is entered in the admin for a group that will pay later: it stays Unpaid until payment. All three draw on the same stock. The group then adds two people. The team modifies the order, then clicks Send a payment request to send the extra amount due.
What you need before / what it affects
- Before: products with availability, active payment methods and transactional e-mails ready.
- After: stock, the operations schedule, invoicing and accounting.
