eCommerce / Point of Sale integration and enhancement project

We have licensed an eCommerce package ( [ASPDotetStorefront][1] ) which we now need to integrate with our existing Retail Point of Sales/Inventory Management system. We have licensed the full VB.NET/C# source for the eCommerce package. The POS/IM software was developed in-house, we have full VB6/VB.Net/SQL source. We have budgeted for a new BizTalk Server 2006 license for this project, and expect the solution will be build around BizTalk orchestration due to the transactional nature of what we want to accomplish, but are open to suggestions. This project is broken down to two parts: Data Sync (between the inventory system and the storefront) and Order Processing Pipeline (rules-based order fulfillment logic and support systems). There will need to be various web/winform interfaces developed in order to manage settings, rules, and update progress status. Preference will be given to coders or companies with relevant Microsoft certifications. (MCSD, Biztalk MVP) ## Deliverables **Part 1: Data Sync** eCommerce ([login to view URL] website, full source) integration with in-house retail management system (vb.net/sql server) Data transformation and sync engine While the data structures between the two products are similar, there is still some transformation that needs to occur. We have 45,000 items in our retail POS system, which need to be discriminately populated into the web store’s database. Because the structure of the source or destination data sources, or the rules used to process the transforms, may change over time, we envision building this component using BizTalk Server 2006 orchestration in order to support future changes. The data sync needs to be as close to real-time as possible. Triggered by database updates? The following is a brief overview of what needs to be synced: * Product definitions from POS to Web Store * CRUD updates to descriptions, costs, availability, etc. * product images * Inventory levels from POS to Web Store * levels tracked by location, colors/sizes **Part 2: Transaction-based Order Pipeline** **Order Fulfillment ??" Rules & Assignment Decisions** Again, we see BizTalk Server 2006 as being a key platform element for this. As an order is entered on the eCommerce site, a custom rules engine must determine which of 20 locations is assigned the order. There are several factors which will determine the location that fills the order, including freight efficiency (complete vs. partial orders), inventory levels, inventory costs, etc. **Order Fulfillment ??" Variable Management** One of the factors that determines which location fills an order is how much that location is willing to discount their inventory. A webservice and web/winform interface needs to be created in order to give the locations the ability to manage their discount levels based on Supplier/Category. **Order Fulfillment ??" Processing and tracking** A service needs to be developed in order to track the state of order fulfillment. Based on the various stages of the order, events may be triggered such as send email to customer or notify head office. The sequence of events may change over time, and as such, the system must be able to accommodate business logic changes. **EXPECTATIONS:** ONLY bid on this project if you or your company are able to devote the time required. We are under time pressures for this project, and partial deliveries are of no use to us. We are paying for a full implementation, including *design*, *development*, and *deployment*. In order to be considered for this project, you or your company will need to be able to assure a high level of quality. It will be expected that you are able to design a solution that will be stable, secure, scalable, and responsive. The middleware components will be developed in vb.net or C#, utilizing either the dotnet 1.x or 2.0 framework. Continual communication in English during PST Time Zone business hours via MSN Messenger or Email is expected. The coder will review the requirements overview (this document) and develop a detailed design document, outlining the development tasks, the technologies that will be used, and a timeline for delivery of the various components. During the development of the design document, we will be available between 9am and 5pm PST in order to answer questions and deliver project details such as database schemas, access to source code, etc. It is critical that the coder identify any opportunities for improvement at this and all stages of the project. Both project parts are deliverables for the project. The project will be done in phases (scope documentation, development of part I, testing of part I, etc.) Funds may be released during the development process. Our concern is ensuring the developer remain committed throughout the scope of the project. *This will be discussed with the winning bidder in advance of the project being accepted*, but here is an EXAMPLE: Documentation and scope complete - **5%** Part 1 delivered - **10%** Part 1 tested and signed off by buyer - **20%** Part 2 delivered - **20%** Part 2 tested and signed off by buyer - **45%** It is weighted towards the end of the project in order to ensure project integrity. **STANDARD STUFF:** 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) 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, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform BizTalk Server 2006, VB.NET, SQL 2000, C#