Events & Ticketing

What your event page promises and what your checkout charges

The problem is not the service fee. The problem is an unexplained number, and an unexplained number at the moment of payment does more damage to advance sales than the fee itself ever could.

Your event page advertises a ticket price. A guest clicks through, enters their details, and the total they are asked to pay is higher than the number that brought them there. No line item explains the difference. It is simply a larger number, appearing at the exact second they were reaching for a card.

Almost every operator's first reaction is defensive, and fairly so: the fee is real, the platform charges it, and there is nothing dishonest happening. All true, and all beside the point. Nobody is accusing you of anything. The issue is not the amount. It is that the amount is unexplained, and the effect of an unexplained charge is measurable regardless of how justified it is.

What an unexplained number does at the moment of payment

Ticket fees at checkout land on the least forgiving screen you own. The buyer has already decided to give you money and is now confirming that decision, which means they are alert in a way they were not alert three clicks earlier. A number that does not match the promise gets noticed there and nowhere else.

Two things then happen, and neither one is loud. Some buyers finish the purchase and file away a small note that your pricing is not quite what it says. Others abandon, and their abandonment is indistinguishable from ordinary browsing in every report you will ever read. You will not see a complaint. Complaint volume is close to useless as a signal here, because the response to a surprise fee is not to write to you. It is to close the tab.

A disclosed fee is a cost of doing business. An undisclosed fee is a trust event, and it lands at the one moment when trust converts directly into money.

The version of this that does real damage

One version of an advertised price different at checkout goes beyond irritation and starts reshaping buyer behaviour, and it happens when the door price is not published anywhere.

Consider what a buyer works out, assuming they reached a checkout at all, which is not a given. They paid the advertised price plus an unexplained addition to buy in advance. They arrive and discover that walk-up guests paid the advertised number flat, with nothing added, because a person at a gate with a card reader does not charge an online service fee. The advance buyer, who committed early, gave you certainty, and helped you staff the night, paid the most. The person who waited paid the least.

That buyer has now learned something durable about your events, and it is not about this event. Next time, they wait. They do not announce this decision. It shows up as a soft advance count, and a soft advance count is the number you staff, pour, order, and schedule against. The fee did not cost you the fee. It cost you your own forecasting.

The check, and it is short

1. Buy a ticket to your own event, in an incognito window, all the way to the final confirmation screen. Not the product page. The screen with the total on it.
2. Write down every number a real buyer sees in order: the price advertised on the event page, the subtotal, every addition, and the final total.
3. Ask whether every step of that sequence is explained on the screen where it appears. If the total is higher than the advertised price and nothing on the page says why, that is the whole finding.
4. Then answer a separate question: what does somebody pay at the door, and is that number published anywhere at all? If nobody can state it, that is a bigger issue than the fee, because it means your own advance-versus-gate incentive is undefined.

For farm events and agritourism venues selling a mix of advance and gate admission, run this before the next date on the calendar. Most owners have never seen their own checkout as a stranger sees it, because they have never bought their own ticket. Everything about your view of your own site is privileged: you skip the search, you skip the listing, you skip the cart, and you never see the total.

Three fixes, in order of effect

• Itemize. Show the fee as its own line with a plain name. The single change from an unexplained total to a labelled line removes nearly all of the damage, because buyers object to being surprised far more than they object to paying a few dollars.
• State the total on the event page. Advertise the all-in figure, or advertise the price and name the addition beside it. The goal is that the number on the page and the number at checkout are the same number, or that the difference was disclosed before anybody entered a card.
• Publish the door price, and price advance below it. Whatever the fee structure, the all-in advance total should be less than or equal to what a walk-up pays. That single rule makes buying early the rational choice, which is the entire reason advance sales exist. If advance costs more than the door, you have built an incentive against the behaviour you most need.

What to measure instead of complaints

Since nobody complains, you need a number that moves whether or not anybody speaks. Track two, separately, for every event: how many tickets sold in advance, and how many people paid at the door.

That advance ticket versus gate price ratio is the honest measure of whether your pricing is doing its job, and it is the only one that survives a bad-weather night. Weather moves the door count. Pricing and disclosure move the advance count, weeks earlier, before anyone has looked at a forecast. Kept apart, those two numbers tell you which problem you actually have. Added together, they tell you nothing and every soft night gets blamed on rain.

Our free Brand Continuity Snapshot walks your public purchase path as a stranger and reports what a buyer is shown at each step, including the checkout total. It is a no-cost first look at what your own pricing is teaching your customers. When the question is what to do about it across a full season, that is the Brand-to-Revenue Continuity Audit.