Knowledge BaseImporting session card purchases
Customers' session cards move from a previous system with one CSV file that holds purchases of any number of cards, with their remaining sessions or hours and expiry dates.
The purchase import brings the session cards your customers already own into Thril. One CSV file can hold every customer's cards across all your session cards, with what each customer has left and when the card expires. Each row adds a new card to the customer.
For one or two customers, grant the card from the customer's profile. See Granting a session card by hand.
Starting the import
- For a file with many different cards, open More actions on the Session cards page and choose Import purchases.
- For one card's purchases, open More actions on that card and choose Import purchases. The card is preselected for every row, and the file needs no session card column.
Columns
One row is one purchase. The sample CSV in the import shows the format.
| Column | What it does |
|---|---|
| Customer email | Finds the customer by email. Required unless the file has a customer name. |
| Customer name, or First name and Last name | Finds the customer by name when a row has no email. |
| Session card | The card's name. Rows can name different cards. |
| Active until | The day the customer's card expires. Leave it empty to follow the card's own validity. |
| Remaining sessions or hours | What the customer has left. Leave it empty to give the card's full usage limit. |
Your old system's column names can stay. Thril proposes a match for each column, and you check it on the Match columns step.
Card names and customers
The Match session cards step matches each card name in the file to the session card with the same name. Choose a card for any name left over, or pick Do not import to leave its rows out.
The import adds cards to your existing customers. Import new people first. See Importing customers. A row with an email matches the customer with that exact email. A row without one matches on first and last name, and when several customers share the name, you choose the right one on the review step.
Remaining amount and validity
On a Usage count card the remaining amount is whole sessions. On a Duration-based card it is hours, and 4.5 is four and a half hours. A customer with 7 of 10 sessions left gets a card that holds 7.
A date in Active until is the last day of the customer's card. Thril reads 2030-12-31, 31.12.2030 and other common formats. Validity counts as started on the import day, or on the first day of a fixed date range. Without a date, the card follows its own validity as if bought on the import day.
Review and confirm
The Review rows step shows every row before anything is saved. Change a row's customer, card, expiry date or remaining amount there, or remove the row. Confirm import saves all rows at once. One file holds up to 5,000 rows.
Imported cards count as paid outside Thril and start with no usage history.
Managing customers' session cards
Staff can update session cards customers already own, void or add uses, change one customer's card and validity, and grant a card by hand.
Credits and credit top-ups
Customers top up a prepaid balance and spend it at your venue like money. Top-ups can give a bonus, expire on a date and pay for almost everything you sell.