Returning Registration is this Saturday and CCI wants you to be prepared

 29 SEPTEMBER 2025



This weekend, we jump into battle for our 2026 SDCC badge - we being any attendee who attended Comic-Con this summer. 

That means we've all been through a badge sale before, but CCI has valiantly launched a battalion of guides to help us. That includes:

  • Returning Registration General Info
  • The Essentials
  • Buying for Friends
  • A Prep Guide
  • Survival Guide

Surely some of those could have been consolidated? 



Here's what you need to know:

Log into your Member ID account and put your credit card information back in. Yes, even if you put it in last year. Confirm that you are eligible for Returning Registration.

Speak to your buying group about buying order, who wants what days, etc. Review Member IDs - this is where a critical badge-buying moment can turn dire, when someone's Member ID doesn't validate and you end up screaming "Is that a number 1 or letter 1?" over Discord voice chat.

Be sure your tech is in order. They go through that here - browsers, power save settings, VPNs, etc. (This page has an unnerving waiting room graphic that somehow replicates the anxiety of a badge sale, but maybe it's just me.)

Stop any planned shenanigans or you could be banned from SDCC for life. Or something. Okay, I made up the "for life" part but CCI does include a warning about this. If you travel in Comic-Con circles, you've no doubt heard of the bots and other high-tech trickery people claim are getting them the best badges and hotel rooms. I won't travel that road so I can't attest to its efficacy, but you should know that there are real consequences for getting caught.


Last year, RR wasn't too bad. I don't have numbers to back this up, but it does seem demand has lightened just a bit. So try not to be too nervous Saturday morning. Just lay the groundwork for a successful sale and remember that even if the worst happens, you'll get a second bite at the apple in November.

Good luck and I'll talk to you Saturday.



No comments:

Post a Comment