That I've been contemplating on how to do, and when I can do it. Not 100% sure on how it would be implemented, but I can say its sort of in the works.
Maybe have a seperate database for the premade toys?
This database will have toys added to it by hand when Bear has them ready. Dropdowns for toy names/hardnesses and fill-in boxes for color/defects can make things faster and easier for Bear. To make it easier to know which toys are premade, all premade toys will have "Premade" added to the end of their name. For example: Ruff JR Premade
The users will see a special webpage. They can order toys from here by checking the box next to the toy name and clicking "add to cart". When the user clicks the button, a pop-up (javascript) appears with the message "These toys will remain in your cart for 24 hours. If not purchased in that time, they will be returned to the premades page where someone else may buy them. If you intend to buy this toy today, click "OK" to add the toy to your cart".
Clicking "OK" on the confirmation pop-up will copy the information used on the main site (price, model, color) from the premade database to the normal database. The premade database will temporarily remove the checked toys from itself as a "hold", marking them with a hold number.
When the toys are bought, the normal database sends the OK for that hold number's entry to be removed from the premade database. As the premade toys that are purchased are stored in the normal database once bought, having the entries be removed from the premade database makes things clean. A message is also automatically sent to the support box that a premade toy has sold.
Bear will also be able to manually remove toys from the database if he wishes. This does not trigger all the stuff that buying the toy does, it just removes the toy from the database.
So, what do you think?