Hi everyone,
Thank you for your ongoing feedback and for clearly outlining your use cases!
While giving event admins and attendees the ability to seamlessly edit an existing registration remains Acknowledged and under active consideration by our Events product team, we want to provide some transparency on why this feature is complex to build, and share the current best practices to handle these situations today.
Modifying a registration is fundamentally different from editing a standard contact profile. Because our Events tool processes live ticket sales and add-on purchases, every registration generates a strict financial record and directly impacts your capacity limits.
Payments: If a user wants to upgrade their ticket or buy an extra add-on after registering, the system must securely process a secondary transaction that links to the original receipt. If they remove an add-on, it requires a secure, partial refund protocol.
Inventory: If you have strict capacity limits (e.g., only 50 Chicken dinners available), and a user tries to change their meal choice after the fact, the system must perfectly check live inventory to prevent overselling.
Building a robust accounting and inventory framework to handle these post-purchase adjustments safely—without creating discrepancies in your revenue reports—takes significant engineering time.
Current Workarounds:
For Free Changes (e.g., simple meal swaps or name corrections): If no money is changing hands, the fastest workaround is to wait until registration closes, export your Registrants Report to Excel/CSV, and manually update the spreadsheet before handing it to your caterer or door staff.
For Paid Changes (e.g., adding a ticket or paid add-on): To ensure your accounting and inventory remain perfectly accurate, the most secure method is currently to cancel/refund the attendee's original registration and ask them to re-register with the correct selections.
We are keeping this thread marked as Acknowledged and open so our development team can continue to track the massive demand for robust backend registration editing. Thank you again for helping us build a better platform!