If You Plan On Pre-Registering For SDCC 2015 Save Your 2014 Badge! New Rules In Place! FYI!

san diego comic con sdcc 2014 long logo

Hey kids!

For those of you who can’t get enough SDCC news, here’s what we think will happen in 2015… Okay, I’m kidding. I’m not that crazy.

BUT…

I wanted to share some info that those who plan on going will need to in order to pre-register. The rules keep changing and when we hear things that you might need to know, we want to help.

Now, to pre-register for 2015 which right now is tentatively set for fall 2014, you will need your physical badge that you picked up at SDCC this year. It’s the not number in your email confirmation, but a number on the physical badge.

san diego comic con logo rare sdcc 2013 2014

It’s the “badge ID” so don’t throw away your badge from this year, otherwise you can’t pre-register. Got it?

Again, the number you need is at the bottom of your physical badge for general passholders.

As far as I know, an email will go out and you have to type this code in to “unlock” preregistration for 2015. Phew…

Here’s what SDCC said…

“If you purchased a badge for Comic-Con 2014, you may have noticed a “Badge ID” printed at the bottom of your badge. Keep this number safe, as it is the key that will unlock 2015 preregistration for you! Sometime in the next couple of weeks you will receive a very important email from Comic-Con with instructions on how to enter your badge ID online for preregistration validation. The validation period will only be open for a short window of time so keep an eye out for this very important email or bookmark Toucan, the official blog of Comic-Con International, WonderCon Anaheim and APE. We will post helpful registration hints and tips on the blog in the weeks preceding preregistration.”

So, be safe, take a pic of your badge, write that number down, scan it, put your badge in the cloud, whatever you need to do.

Share on Facebook
Comments(2)
  1. Avatar SDCC Burnout August 18, 2014
  2. Avatar Susan August 18, 2014

Leave a Reply

%d bloggers like this: