Photo Products using a set library of photos... Attributes Configuration Question

I take photos at a local theme park. I'm new to ZC and trying to incorporate the sale of our custom photo products.

Here's what I got so far:
Our Photo novelty products (TShirts, Mouse Pads, Magnets, Banners, Mugs, etc.) are loaded and tentatively configured.
Photos (about 500 to 1000 a day for 60 days) have a uniques id/filename each, have been uploaded and (through easy populate) bulk configured as products as well. Photos are easily searchable and marked as display only.

The theme park and my online shop opens Oct 30th.
As of now: A customer will have to:

1. Search for their photo (They receive a ticket with their number, which matches the filename/product ID in the inventory)
2. They will see a proof of their image (all the originals are with me offline)
3. They will proceed to buy a novelty product (ex: T-Shirt - Large or Banner or Mug, etc)
4. They will enter their photo number on a required text box.
5. I will process the order.
   I got that far.

QUESTION:
Given the scenario above, is there any way I can tie the photo with the novelty without having to create 100 custom products per photo? (tshirts- 1 of each size per product, banners- 1 of each style per product, you get the idea.)

I have the basic knowledge for size and style configurations, but I don't know how to tie in the photo.

In short, I have 100 products. They ALL take a photo of a customers choosing (which are already uploaded as products themselves.)
Can I tie one to the other to insure the customer received the correct order?

Possible?

Any help is greatly appreciated.

Javier Unzueta

The way I see it, might be best to create a $_SESSION[] variable that is populated on some custom page, then on your product check to see if the session value is set, if it is not use some generic photo like your photo goes here and also present a link to goto fill in the session variable.

The only issue I see in getting it all to work is "overlaying" the image onto the product(s), but perhaps that is easier than I'm thinking. It may require some special field to be incorporated for each product (or css per product page) to size and manipulate the image as applicable.

Just some food for thought I guess. Seems like a lot to accomplish in 2 weeks.

Curious, is the number system like a two part piece of information so that one could not get the picture just before or just after the number they were given? What's to minimize the chances of someone purposefully requesting someone else's photo?