I need a skilled reliable programmer(s) who can program a customizable “update” interface between my wholesalers and my ecommerce website ([url removed, login to view]). A completely Web-based (ASP) application is too slow and bugy (most of my product’s data has been compromised in beta production), considering I have over 107,828 products to process, there is no doubt .NET is the best solution.
The interface needs to be dynamic enough to download various files: some .zip, .tab, .csv and .bat files (the .zip files may either carry data files or pictures; sometimes both). Then, the new interface processes the new information and my website is updated accordingly. A manageable pricing system (applied to all or certain specified categories) will also be needed for effective marketing. While updating, this interface will be checking for duplicates, updates and/or new products, and it must anticipate category changes (deletions, add-ons, or lack thereof). The interface must also log each transaction (.xml) and archive the new link in a database for future reference, or comparison. It would be helpful if the interface generated an on-screen report or table comparing the last update with the current one (this assures correct marketing techniques) - complete with thumbnails. A more detailed description of the process(s) will be given to each team member.
Keep in mind that the program that you build will be traversing many password protected sites in order to get the information (files) my online store needs. The program should be resilient enough to check for changes in the wholesaler’s site structure and dynamic enough that the end user may add/delete wholesalers as he/she whishes, simply by adding a URL, username and password (along with any other variables).
The program should run on the latest .NET framework (in Windows XP) and should install to a designated computer fairly easily with a .msi or .exe application.
This application is intended to be a “one-touch update;” a “set it and forget it” type program that is reliable! The end user is just expected to set a few variables and push the “update” button – and, after the process finishes, the end user closes the program - knowing the site was updated successfully!