Designing a ink-stamp ordering website for a client. Need the proof and ordering screens developed. As this project is in the planning stages I believe the site will utilize a OSCommerce (http://www.oscommerce.com/) solution, however I’m open to suggestions. An example of what my client is after would be similar to site found at http://www.rubberstamps.com/. Please note that this site is using ASP whereas I prefer to stick with a PHP/SQL solution like with OSCommerce. Additionally, looking for a more Web2.0 look versus the stripped down simplicity of the example found at http://www.rubberstamps.com/. Make sure to click on one the stamps there so you can see how the customization of the stamp is done and how end user can view their proof. The approved proof needs to generate a PDF file which will attach to the order and be used by my client to produce the end user’s stamp. The amount of stamps that will be in database is unknown at this time. Figure you will be responsible for uploading 4-5 stamps and the balance will be done by client thus a way to easily generate new stamp products is key. Finally, the online proof must be able to warn or prevent client from being able to add lines or use text that’s too big to fit the predetermined image area size of stamp being ordered. Again, using the site http://www.rubberstamps.com/ as an exampple, make sure you view various sizes of stamps so you fully understand what needs to happen. PayPal will be used initially for checkout process.
Before you quote please read and acknowledge these minimum requirements:
Must understand, read and write in fluent English
Must have ability to communicate via phone or email, although most communication will be via email
Must be familiar with OSCommerce
Must detail with your quote exactly how you intend to do this project (i.e., structure, db, etc)
Must be able to work within Central Standard Time, Monday thru Friday
Under normal circumstances, replies to my communication are within 2-6 hours
Payment via Scriptlance Escrow only
Payment will be in three parts, 1/3 at project start, 1/3 after successful testing on your server, 1/3 after successful testing on client’s server
