If your Spektrix system is connected to a Source System using Spektrix Connect, you can sell tickets to imported Event Instances in the Sales Interface.
| User Permissions |
For selling, Sales User or Sales Administrator Role For reporting, Insights & Mailings User Role |
| Requirements | Spektrix Connect |
Before starting, make sure you’re familiar with:
- Introduction to Spektrix Connect
- How to set up Spektrix Connect as an Agent System
- How to Sell a Ticket
Before you are able to start selling tickets via Spektrix Connect, the General Administrator at your organisation must also have completed the setup of the Source System connection, imported the Event Instances and resolved the required mappings.
What is possible in anAgent System?
In the Agent System, you can manage sales for Source System Events in the following ways.
You can:
- Sell tickets in the Sales Interface.
- Sell tickets on your website or Subsite (web sales are switched on by default).
- Apply Promo Codes, as long as they are created in both the Agent and Source System.
- Change the Ticket Type of an imported ticket after it has been added to the Basket / Cart.
- Print tickets with the Source System's barcodes.
- Return tickets and process refunds for customers.
- Sell tickets to eligible customer within Priority Booking periods.
You can’t:
- Override ticket prices.
- Create Reservations.
- Add Ticket Donations.
- Use Best Available or View from Seat selection through the API.
- Sell imported Event Instances onward to your own Agents through the Agency API.
- Clear Locks or sell Locked seats.
- Run Sales Reports for imported Event Instances.
- Automatically record returns in the Source System. Returns must be manually communicated to and processed by the Source System’s organisation after being returned in the Agent System.
How to view Instances in the Sales Interface
In the Sales Interface, imported Events will appear alongside your existing ones. You can use the Venues dropdown to filter your Events by Source System Venue.
Once you select an Event and Instance, you’ll see the Seating Plan (Reserved Seating Plans only). You’ll notice some key differences on the Seating Plan for imported Events:
- Under the Instance's details, a message shows which Source System it was imported from, for example Imported from Source System 'salesdemo_thecircle'.
The Seating Plan shows live availability from the Source System:
- Seats that are unavailable to sell are shown with an X. These might be seats the Source System or another Agent has sold, or seats that are Reserved or Locked.
- Seats you've sold through your own system are shown as grey seat icons, the same as for your own Event Instances.
- Seats that are unavailable on a Source System can include seats held under a Lock Type that has not been mapped.
REMINDER: A message will display to inform you of unmapped Ticket Types, Price Bands or Locks.
How to Sell a Ticket
The following steps outline how to sell a ticket and what happens in both systems during the process.
- From the Sales Interface in your Agent System, choose the Event Instance. Current availability and prices are requested from the Source System for you to choose tickets from a Reserved or Unreserved Seating Plan.
- Add tickets to the Basket / Cart. The same tickets are held in a corresponding Basket / Cart in the Source System. Changes made before the Order is confirmed, such as removing tickets or changing Ticket Types, are also reflected in the Source System.
-
Add the Customer Record to the Basket / Cart. Eligible Offers will be automatically applied in both systems.
TIP: A seat can become unavailable between being displayed and being added to a Basket / Cart. If someone else has bought it during that time, the customer will need to choose another seat.
- Select a Delivery Method.
- Take the payment and confirm the Order.The corresponding Order is then automatically confirmed in the Source System.
The Source System will receive the following information against each Order:
- Customer name
- First line of the address
- Agent Order ID (Agent order reference)
On the Source System, all Orders processed by the Agent System will be associated with the Agent Customer Record.
Tickets will automatically display with barcodes from the Source System.
Online sales
If an imported Instance is set as On Sale on the Web in the Source System, customers can buy tickets for it through your website. Customers will see live availability from the Source System and the Ticket Types you’ve mapped and made available online.
If the Source System can’t be reached, the customer will see a message asking them to try again. Source confirmation failures also generate an email to your configured Order follow-up addresses.
Returns and Refunds
You can return and refund tickets you have sold on behalf of another organisation in the same way as one of your own sales. For guidance on how to process a refund, follow the steps in Performing a Return and Refund.
A return in your system isn't automatically sent to the Source System.
When you process a refund in the Agent System you’ll see a warning explaining that the tickets will remain sold in the Source System:
This return will only be recorded in this system. The tickets will remain sold in [Source System].
Please contact [Source System] and ask them to return the sale. This will make the seats available for resale and ensure the return is included in your financial reconciliation. If the sale is not returned on [Source System], [your organisation] may still be charged for the tickets.
To complete a return and refund, follow this process:
- Start the return and refund in your Agent system.
- Read the warning and select Continue with return to proceed.
- Contact the source organisation with your Order ID and the ticket details.
- Ask them to return the corresponding tickets in their system.
- The Source System returns the tickets using Agent credit payment/refund, as described in Working with Agents via the Agency API.
WARNING: Refunding the customer in your Agent System does not automatically return the tickets in the Source System. Your organisation may still be charged until the source organisation also returns the tickets.
Troubleshooting Spektrix Connect Sales
Use the reference table below to understand how to troubleshoot different errors when making a sale:
| What you see | What to do |
| A seat or quantity is no longer available | Select other available seats or reduce the quantity. |
| Missing Ticket Type or Price Band mappings | Ask someone with the General Administrator User Role to check the Source System mappings. |
| An unmapped Lock Type warning | Ask someone with the General Administrator User Role to map the source Lock Type. |
| A source-system connection error | Record the Source System name and message, then follow your agreed process with that organisation. |
| A Ticket Type change couldn’t be completed | Retry the change as prompted |
| Tickets removed because the source basket timed out | Select the tickets again if they’re still required and available |
| A message saying the Basket/Cart no longer matches one or more Source Systems | Follow the instruction to cancel the Basket/Cart and start again. If payment has already been authorised, seek assistance before cancelling |
| A source confirmation warning after the Order is confirmed | Contact the source organisation with your Order reference so they can check whether the seats are secured |
| Ticket barcode displays as “Unavailable” | Arrange resolution and check that the customer receives a usable ticket |
| Pricing mismatch | Check the Order with the source organisation and reconcile the difference. |
REMINDER: Removing tickets from an unconfirmed Basket/Cart releases the holds in the Source System. This is separate from returning or refunding tickets after purchase.
What happens if the Source System can’t confirm the booking?
If your Order is confirmed and paid for, but the Source System can't confirm the basket / cart you might see a message which says:
The order failed to confirm on the following system(s):
{source system names}
Please contact them directly to manually reattempt confirmation. Until confirmed, the seats are not guaranteed and could become available for purchase by someone else.
You will also receive an Order follow up email with the subject Order [Order ID] failed to confirm on one or more systems.
If the Source System can’t confirm the Order, contact the Source System organisation with the Order details so they can secure the seats for the customer. If the seats can't be secured, return and refund the tickets in your system.
Checking the Agent System invoice
When you sell tickets for an imported Event Instance, the customer pays you (the Agent system). The Source System will not directly receive the payment when a transaction is made through Spektrix Connect.
In the Source System, the sale is automatically recorded against your Agent Customer Record using the Agent Credit payment type.
The Source System organisation must invoice the Agent System’s organisation and the payment must be settled separately outside of Spektrix. Usually the Source System’s organisation invoices you for the tickets, minus any commission agreed with them.
REMINDER: You’ll need to agree how often you’ll settle payments, how commission is calculated and how returns and cancelled Instances will be handled.
When you (the Agent System) check an invoice from a Source System:
- Ask the Source System organisation for their Agent Invoice report for the period.
- Compare it with your Orders for imported Event Instances. Each Source System Order includes your Order ID as the Agent Order Reference, so you can match them one by one.
- Look out for differences caused by:
- Returns you made in your system that weren't also made in the Source System. A return in your system isn't sent to the Source System, so you may still be charged.
- Orders that failed to confirm in the Source System.
Refunds can be done by the Agent System to the end customer. If invoicing and reconciliation has already occurred.
Depending on how regularly you reconcile between systems, the Agent System may have already paid over to the organisation of the Source System.
TIP: Emails sent to your Order follow-up address can be useful to reference to find Orders that need checking when you reconcile.
How do I report on imported ticket sales?
The report you’ll need to use will depend on which system you’re using:
- For Agent systems: You can use Analysis and Accounting reports to get data on your Orders, tickets, payments and commissions. Sales reports based on seat availability aren’t available for imported Instances.
In Analysis or Accounting Reports, you can use the Source System criteria to report on ticket sales for Instances imported through Spektrix Connect. You'll find it in the Event Instance wrapper when building a Criteria Set or Custom Report.
Choose either:
- Include the following Source Systems: Finds Instances imported from the Source Systems you select.
- Do not include the following Source Systems: Finds every Instance except those imported from the Source Systems you select.