Amazon Seller Integration using SOAP - osCommerce Admin

I have a highly modified osCommerce install and I need to intergrate a custom admin for the Amazon Seller program. Amazon APIs, Item Classification Guides, sample Feeds, and WSDL will be provided. PROJECT MUST BE COMPLETED BY 9/10/06! BUDGET FOR THIS PROJECT IS $500. If you cannot complete the project in this time for this budget, please don't bid. Bids over budget or off schedule will be ignored. The admin must do the following: 1. Post documents to Amazon as follows: * Products data * Product images data * Relationship data * Inventory availability data * Price data * Order acknowledgement data * Order adjustment data * Order fulfillment data * Override data Choreography 1. Seller posts document to [login to view URL] using the published API. 2. [login to view URL] acknowledges the successful receipt with a transaction reference identifier. Failures are reported back using appropriate fault codes. 3. Seller records the transaction reference identifier. 4. Seller checks the processing status using the transaction reference identifier at opportune times. 5. [login to view URL] processes the document and performs necessary business functions. As a part of this processing a document is generated to report the result of processing. 2. Retrieve documents from Amazon as follows: * Orders data * Payment settlement data Choreography 1. [login to view URL] generates these documents periodically. Every document is assigned a unique document identifier. 2. Merchant requests a set of document identifiers for a given document type from [login to view URL] using the published API. 3. Merchant chooses the required document identifiers from the set. 4. Merchant requests a document given an identifier using the published API. 5. Download failures are reported back using appropriate fault codes. 3. Retrieve Document Status * Products data * Product images data * Relationship data * Inventory availability data * Price data * Order acknowledgement data * Order adjustment data * Order fulfillment data * Override data Choreography 1. [login to view URL] processes the submitted document and performs only XSD validation; a document is generated to report processing result. 2. Merchant uses [login to view URL] provided transaction reference identifier (document id) to query for processing status using the published API. 3. If the document is under processing then a work in progress status is returned, else a document identifier is returned for downloading the processing report. 4. Merchant downloads the processing report using the published API. 4. Post Document Acknowledgements as follows: * Orders data * Payment settlement data Choreography 1. [login to view URL] generates these documents periodically (as described above). Every document is assigned a unique document identifier. 2. Merchant requests a set of document identifiers for a given document type from [login to view URL] using the published API. 3. Merchant chooses the required document identifiers from the set. 4. Merchant requests a document given an identifier using the published API. 5. Download failures are reported back using appropriate fault codes. 6. Merchant feeds the document into their fulfillment or point of sale systems. 7. Merchant acknowledges the successful receipt of this document. 8. [login to view URL] uses this acknowledgement to update the list of pending documents. 5. Import Item Classification guides 6. Ability to associate osCommerce catagories with Item Classifications 7. Product feeds will have to strip out all HTML and special characters for compatibility with Amazon.