The QR code opened the wrong album

Why does the code open the album instead of the upload page?

Every album carries 1 code, and that code sits inside 2 addresses: the upload page guests land on, and the album page showing what they sent. The 2 links differ by a few characters and look identical on a table card. Print the viewing address and your guests arrive as an audience with nothing to tap.

The upload page asks for photos. The album page shows the ones already in. Copy the address out of the event itself rather than out of a browser tab you left open in June.

1. Scan the card, not the screen. The artwork that went to the printer is the one to test. The code in your dashboard proves nothing about it.
2. Read the name on the guest page. It is built from whatever album the code resolves to, so the name settles which event you are looking at.
3. Print 1 card before the rest. Download the code from the event you mean, run 1 through the printer, scan it, then release the run.

How do I tell which event a code belongs to?

Scan it with a phone and read the name across the top of the guest page. That page is assembled from whatever album the code resolves to, so the name on screen is the album your guests would fill. Nothing else on a printed card tells you as much in as little time.

Do it on a phone rather than the laptop you set the album up on. Your guests hold phones, and the guest page is drawn for that screen.

Does renaming the event or moving the date change the code?

No. Your code is tied to the album itself. Rename the party, move the date, switch the accent color or upgrade from Free to Celebrate: the card in your hand keeps opening it.

Order signs in January for a June wedding and they still work on the night. So a card that suddenly opens somebody else’s party did not drift; a different file reached the printer.

I claimed a custom link. Are my printed codes dead?

No. Claiming a custom link adds a second code to the same album, and the first one keeps working. Your dashboard then shows the newer code, so the link on screen can look nothing like your spring cards.

Both codes open the album. Use the newer one from here on, and treat the older cards as valid rather than as a fault to chase down.

The page says the album isn’t open yet. Wrong code?

No, and the screen proves it: your event name sits right above that line. A paid album waits as a draft until the charge clears, and an album whose host closed uploads says “Uploads are paused” instead. Both screens are the right album with the door shut, which is why hosts meet them while testing their own sign.

Clear the payment, or reopen uploads from the event. The same card then opens the upload screen with no reprint.

The page says the link doesn’t work. What does that mean?

That wording belongs to a code no album answers to: a share that got truncated, a mistyped character, or a code whose event was deleted. Deleting an event takes its codes with it, and every card printed for it lands there from that moment on. Read the line before you blame the printer.

The other end screen reads “This link has expired” and means the album ran its course. Telling the 2 apart saves you from reprinting for a party that is already over.

What should I check before a print run?

Download the code from the event you mean, print 1 card, then scan it on a phone that never touched the setup. Read the event name, then look at whether the page is asking you for photos. Those 2 answers together are the whole proof.

Give the card its own patch of table. A camera locks onto whichever code it focuses on first, and a menu code an inch away is in the running.