The short answer
First check whether the customer really placed two orders. If there’s only one order and one payment but twice the tickets, the usual cause is timing: two parts of the site handled the same paid order at the same moment, and each created a set of tickets. Don’t delete anything until you’ve matched every attendee to an order and a payment.
Duplicate tickets cause trouble well beyond the attendee list. The event can show as full when it isn’t, door lists are wrong, and customers get emails for tickets they didn’t buy, which makes them worry they’ve paid twice. Whether you use Event Tickets Plus, FooEvents or another WooCommerce ticketing plugin, the checks are the same: work out which records are real, then find out why the extra ones were made.
Is this what you’re seeing?
- Your WooCommerce site is creating duplicate event tickets: one order for two tickets shows four attendees.
- Your event booking system is generating too many attendees, so the numbers don’t match the tickets you’ve sold.
- An event says it’s sold out, or has fewer places left than it should.
- Customers have received two sets of tickets, or two confirmation emails, for one order.
- It only happens on some orders, not all of them, and you can’t see a pattern.
- You think there’s a conflict between WooCommerce and your events plugin, but nobody can say which one is at fault.
What usually causes it
The customer really did order twice
This is the easy one, and worth ruling out first. A customer clicks the button twice, or the checkout shows an error, so they try again and both attempts go through. Then the tickets are correct: there are two orders. How to tell: search WooCommerce → Orders for the customer’s email address. Two orders a few minutes apart, each with its own payment in Stripe or PayPal, means two real orders.
Two parts of the site handled the same order at the same moment
When an order is paid, several things happen in the background: the payment is confirmed, the order status changes, emails go out, and the ticketing plugin creates the tickets. On many shops, more than one of these steps can tell the ticketing plugin to create tickets. Normally the second one checks, sees the tickets already exist, and does nothing. But if both arrive within a split second of each other, each can check before the other has finished, both see “no tickets yet”, and both create a full set. Developers call this a race condition. How to tell: there’s one order and one payment, but the attendee list shows each ticket twice, with the same order number and almost the same time. It comes and goes, because it depends on timing, which is why it’s so confusing.
The order was processed again later
Ticketing plugins create tickets when an order reaches a particular status, such as Processing or Completed. On some setups, moving an order back to an earlier status and forward again, or re-running an action on it, can create tickets a second time. How to tell: open the order and read the notes on the right. Several status changes, especially one made by hand around the time the extra attendees appeared, point to this.
Two plugins both creating tickets
Sites that have changed ticketing plugins, or added an add-on for check-in, seating or a CRM, sometimes end up with two things creating attendee records for the same order. How to tell: it happens on every order, not just some, and it started when a plugin was added or updated. Look through your plugins list for more than one with “tickets”, “events” or “attendees” in its name.
Custom code that someone else wrote
If a previous developer added custom ticketing, such as group bookings, member allocations or tickets created by a form, that code may create tickets alongside the plugin. How to tell: there’s a plugin with your site’s or the developer’s name on it, or code in the theme, and nobody knows exactly what it does.
What you can safely try
Take a backup first. Every step here can be undone, and none of them deletes anything.
- Make a list of the affected events. For each, note the tickets sold according to WooCommerce, the number of attendees, and the order numbers involved.
- For each affected order, compare three things: the ticket quantity on the order, the attendees listed against that order, and the payment in Stripe or PayPal. That tells you whether you’re looking at two orders, two payments, or just extra records.
- Read the order notes on a few affected orders. Note any repeated status changes and their times.
- Stop changing order statuses back and forth to “fix” an order. On some setups that creates more tickets.
- If an event shows full because of duplicates, you can raise its capacity by the number of duplicates you’ve counted, so real customers can still book. Write down the original figure so you can put it back.
- Check your plugins list for a second ticketing or attendee plugin, and note any updates made around the time it started.
- If a customer has genuinely been charged twice, you can refund the second payment. Check first that it isn’t a second, real order.
When to stop and get help
- There’s one order and one payment, but extra tickets keep appearing. That’s a fault in how orders are processed, and tidying up by hand won’t stop it.
- You’d need to delete attendee records in bulk. It’s easy to delete the real ticket and keep the duplicate, and deleting can’t be undone.
- The event is soon, and the door list or check-in needs to be right.
- Customers may have been charged twice, or sold places that don’t exist.
- The site also runs memberships, subscriptions or a CRM, and you’re not sure what else uses the same orders.
A real example
A membership and events site sells event tickets through WooCommerce, using a ticketing plugin alongside its events calendar. The checkout looked fine: customers could pay, and orders came through. But one order for two tickets created four attendee records. That threw out the event’s capacity figures and raised a worrying question: had anyone been sold, or charged for, the wrong tickets?
It wasn’t two orders. The cause I found was timing. More than one step of the order processing could start creating tickets for the same order. The site did check whether an order already had its tickets, but the note saying they’d been made wasn’t written until later in the process. So if two steps started close together, both could check, both find nothing, and both create a set.
The fix was to make ticket creation take turns. I wrote a small must-use plugin, a type of plugin WordPress always loads and that can’t be switched off by accident from the Plugins screen. It puts a lock around ticket creation, held by the database. Think of it as a single key: whichever step picks it up first creates the order’s tickets, and any other step has to wait. By the time it gets the key, the tickets exist, and it can see that. The plugin loaded correctly, and I tested that the lock works.
That’s where I’d be careful about what it proves. A lock that’s in place and tested stops two steps creating tickets at the same moment. Calling the problem gone for good means watching it handle plenty of real orders and checking that the attendee counts match. It also doesn’t, on its own, tidy up records made before it went in, or answer whether any customer was charged wrongly. Those are separate checks against the orders and the payments.
Getting it fixed
I’ll follow an affected order through WooCommerce, the payment provider and the ticketing plugin to find where the extra tickets come from, then fix that rather than just deleting records. I’ll also give you a list of which attendees are real. See WooCommerce support for the events, membership and subscription plugins I work with. A WordPress repair is a fixed £119, which covers finding the problem and up to 90 minutes of fixing it. Most repairs fit in that, and you’re never charged more without agreeing first. If it needs custom work, such as a lock like the one above, I’ll give you an estimate at £75 an hour before I start.
Questions
Has my customer been charged twice?
Not necessarily. Extra tickets are usually created after the payment, so the customer is often charged once and simply sent too many tickets. The only way to be sure is to check their payments in Stripe or PayPal against their orders.
Can I just delete the extra attendees?
Once you know which ones are extra, yes, but take a backup first, because deleting can’t be undone. Keep the ticket the customer has already been emailed, if you can tell. Depending on the plugin, deleting an attendee may or may not give the place back to the event, so check the capacity afterwards. And until the cause is fixed, new duplicates will keep appearing.
My WooCommerce site is creating duplicate orders, not just tickets. Is it the same thing?
Usually not. Duplicate orders tend to come from customers submitting the checkout twice, or retrying after an error. Duplicate tickets on one order come from how the order is processed afterwards. If customers are being charged but orders are missing or stuck instead, see charged, but no order, and for checkout errors, WooCommerce checkout not working.
Will updating the ticketing plugin fix it?
It might, if the plugin’s changelog mentions duplicate attendees. But don’t update in the hope it helps without a backup, and test it on a copy of the site first if you can. If the cause is two plugins or custom code, an update won’t change anything.
Can you fix custom ticketing that another developer built?
Yes. Most of my work is on sites I didn’t build. I’ll find out what the custom code does before changing it, and you’ll get a plain-English note of what I found and what I changed.
Written by Peter Claridge, who fixes WordPress sites for businesses across the UK from Reading. Last checked on WordPress 7.1, November 2026.