Background:
* Our Client desires an .aspx (C#) tool to create one or more Purchase Orders (PO) automatically in Quickbooks Premier 2006 based on a user click.
* Our customer operates an e-commerce site. Sometimes they need to place orders to 3rd party vendors to fulfill customer orders. They presently cut and paste this information from an admin screen on the web site into QB to create the Purchase Order.
* Our client has experience with integration with QB for other aspects of its business (e.g. inventory synchronization). However, the existing QB code is in ASP and uses QBSDK 5.0 / QBFC with their QB Premier 2006 installation.
* The deliverable will be to create a separate .NET solution to address the new features of creating the purchase orders and of adding any items into QB necessary to complete the PO. Our client does not want to recreate any functionality of its existing .ASP code and does not want to use the existing code at all to create this .aspx solution.
* They are willing to install a newer version of QBSDK as necessary, but will stay with the 2006 version of QB.
The deliverable should include the following:
1. An .aspx page that can be run by a Our Client admin user as a link from their existing site.
2. It would be passed a parameter via a POST of Our Client's order number.
3. Then the .aspx page would use LLBLGen Pro to read access several tables associated with that order. We have LLBLGen Pro and can provide you with C# code to access our client's database.
4. The deliverable, through LLBLGen Pro, will read such from several tables from the e-commerce site. These include: orders, orderitems (there can be multiple items in each order), products, suppliers.
5. With this data, your solution should be able to identify those items within an order that are to be 'drop shipped' (there is a dropship flag for each orderitem that indicates if it is to be dropshipped).
6. For each supplier (there can be dropship items from many suppliers in a single order), the code needs to create a new PO. We will provide finalists with a more detailed examples of how we want the data in the QB PO to be entered.
7. To do this, we will need to query QB to see if each item exists (by manufacturer's part number) in QB. If an item does not already exist in QB, we should add the item (such as item code, description, cost, vendor/supplier, etc) into QB automatically
8. Once we are sure we have matched the supplier ('Vendor' in QB) and have a match on the item code, the PO can be entered.
All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components (other than QBSDK), etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
****
We expect this project to be completed within 10 days of acceptance.
In your response, please provide examples that demonstrate your significant QB experience using the .NET QB interfaces. Also, please confirm in your initial bid that you have LLBLGen Pro experience.
****
Thank you.