New features, improvements and fixes across the Back Office, WordPress, Salesforce and more.
135 updates in Improvement. Clear
If you are selling a large amount of the same item of merch from your store, it can be time-consuming to scan the same code over and over again.
We've added a quantity field to the display so you can scan an item once. It will add that many items you input before scanning that item's code.
Learn how to sell merch here.
Reports got a little love.
We've added some additional utility to Saved Orders--most notably, you can now associate saved orders with a specific customer.
If you haven't explored them yet, Saved Orders are pending orders where whatever the customer wants is reserved for them until they are ready to pay. It's a great solution for group/VIP reservations or open tabs at the bar.
Saved orders can contain anything--tickets or seats, merch, concessions, passes & packages, gifts, even memberships and donations someone intends to buy or make.
Before now, you could leave notes and see who the order was for. It wouldn't fully assign a saved order to customers already in your data.
Now, you can search for or register a new customer in the Box Office as you normally do; any saved order created or updated with that customer pulled up will be associated to that customer.
When you search for and investigate any saved order, you'll see which customer it's assigned to.
Additionally, when you look up a customer in the Back Office, you'll see any saved orders they currently have.
For integrated systems (CRMs especially), you can get information about any saved orders associated to a customer. There's a lot of potential value: You could auto-remind customers about their saved but expiring order or where and how to make that payment so they don't lose their reservation.
Get to know saved orders here.
A not-so-random assortment of small changes to make your life easier:
Learn more about orphan seat control here.
With this update from v2.3 to v2.4, we've introducing a set of improvements to improve the data sync, adding some small features, and bringing in ticket data as product types. Along with the usual set of bug fixes.
Entries, often called check-ins or scans, can be a ton of data. In an org like Salesforce, where data usage is very limited, it can mount up to a lot of data usage you don't value.
If you aren't planning to use the data about each person's actual attendance, you can check a box in the Elevent Custom Setting to "Skip Entries Import".
In Salesforce, the app creates unique products for every other type of item but tickets--these are the 'SKUs' of your product mix.
Now, Tickets also get created. These are the types of tickets you sell (and used to sell or issue)--associated with the opportunities of their actual issuance to each attendee.
In the Elevent Salesforce app, you can set a cutoff data where all sales before that cutoff date will be ignored.
Imported customers and auto-assigned items, however, have no purchase date--so they weren't being ignored if they were imported before the cutoff date. We're talking about data imported into Elevent.
Now, imported data before the cutoff date will also be ignored if it happens before the cutoff date you specify.
While you could already change this using the Field Mapping tool in our Salesforce app, we changed the default mapping of addresses from Elevent into Other Address. The carefully collected addresses of contacts in Salesforce are often more valued than the billing address from purchases; by changing this default, we tread more carefully around addresses that might already exist.
The calculated values for tangible items wasn't being populated
Has no noticeable effect other than future-proofing.
The Merchandise Sales Revenue Report is your go-to report to see merch revenue.
We're now giving you two options to view your data - grouped up at the merch level or itemized by merch variant.
You'll see a new dropdown in the Report Controls: Include Variants.
Suppose you have a merch line item called Books: Ages 5-9. And you have 3 variants, one for each book title.
If set to No, you will see total amounts for all books Ages 5-9.
If set to yes, you'll see a line item for each variant with sales activity.
Merchandise prices can get very specific--each variant of merch item can have its own price.
Before this change, you couldn't do an ad hoc price override on an individual merch variation--so if the XXL hoodie was $5 more, you couldn't do an emergency discount on that price when selling one.
Now, well, you can.
You just add mech to the cart in the Box Office and press the 
button.
Change that price to a lower price and press Apply.
When creating a donation, it's no longer a requirement that you enter the tax ID (usually an EIN) for every donation campaign you create.
You still need to enter a tax ID if you intend to have Elevent immediately auto-send a tax receipt as an attachment to their order confirmation.
We support importing from for several operations, including:
Airtable puts some restrictions on their integrations--to date, we could only pull in up to 100 records from Airtable at a time. That meant multiple pass-throughs when importing a longer list of items.
We have overcome that limitation now and you can import any of those Airtable bases beyond 100 rows at a time. Be advised--you might not want to go absolutely ham on that. If you have over 500 or so to import, we'd still recommend doing multiple import runs just to make sure everything comes over fine.
Learn about importing info from Airtable:
